search-growth-os

Report which search and AI crawlers (Googlebot, Google-Extended, Bingbot, OAI-SearchBot, GPTBot, ChatGPT-User, PerplexityBot, ClaudeBot) can reach the site per robots.txt, meta/X-Robots directives and (when logs are connected) verified crawler hits. Reports facts; does not change access.

Build an Answer Map for one commercial topic — real questions clustered by intent, with a placement decision per cluster (existing page, service page, case study, guide, comparison, glossary, or new page). Not a FAQ generator. Use for AEO work.

Discover candidate competitors for one site from permitted evidence (Search Console query overlap, AI citation/mention overlap, topic overlap, pages actually read), classify each into strictly separated categories, and hand the owner a short validation list. Produces CANDIDATE_COMPETITOR only — never a confirmed competitor.

Compare the site against its owner-confirmed competitor set on coverage, depth, evidence, architecture, entities, links, media, technical quality and citations; output a Competitor Gap Matrix that separates "better", "irrelevant", "risky" and "we can be superior". Use for "why does X outrank us".

Find content opportunities modelled on intent, task, entity/topic coverage and first-party evidence for the site's core commercial topics. Produces page briefs and an explicit "do not add" list. Use for "what should we write", "content gaps".

Run the complete Search Growth OS audit for a registered site — read-only crawl, technical/content/schema/media checks, integration status, expert-agent interpretation and a prioritized dry-run report. Use when asked to "audit the site", "full SEO audit", "search health check".

Generative-search visibility diagnosis by stage (discovery → crawl → indexing → retrieval → citation → mention → referral → conversion) with AI-crawler access facts and stored AI-visibility observations. Use for "are we cited by ChatGPT/AI Overviews", "AI visibility".

Assess what is (or would be) in the index — thin, duplicate, soft-404, parameter, stale and low-value URLs vs commercially important pages; consolidation candidates. Uses Search Console index coverage when connected.

Analyse the internal link graph from crawl data — depth, inbound counts, orphan candidates, anchor text quality, nofollow waste, navigation coverage of commercial pages. Use for "internal linking", "orphan pages", "site architecture".

Audit images and video as search assets — alt semantics, captions, surrounding text, dimensions, lazy loading, responsive delivery, image sitemap needs, video metadata/transcripts/thumbnails, and whether key original visuals are discoverable. Use for a photo/film studio's portfolio visibility.

Check every registered site at once: how long each has gone without publishing, which are overdue against their own cadence, and — for onboarded sites only — what to publish next. Triggers on 'siteleri kontrol et', 'check my sites', 'portföy kontrolü', 'which sites need content', 'ne yayınlamalıyım'.

Pre-release regression test for search — crawl the preview/staging URL, compare with the last production crawl, and report metadata, indexability, canonical, redirect, structured-data, link and tracking regressions. Use before merging a website PR.

Quarterly deep review — architecture, content and evidence inventory, entity/trust, competitor gap, AI visibility, experiment outcomes and what the system learned about this site. Expensive; run at most quarterly or after a major site change.

Audit JSON-LD for syntax, schema.org validity, and consistency with visible content; build/refresh the entity graph; recommend only truthful, supported types. Use for "schema markup", "rich results", "structured data".

Technical-only search audit (crawlability, indexability, canonicals, redirects, sitemaps, robots, rendering, hreflang, mobile). Faster and cheaper than full-site-audit. Use for "check indexing", "canonical issues", "why isn't X indexed".

Propose at most three specific things to publish next for ONE onboarded site, each tied to real demand evidence and an SEO/AEO/GEO rationale. Triggers on 'ne yazmalıyım', 'blog konusu öner', 'what should I publish', 'trend konu', 'content idea'.

Forensic workflow for an organic or AI-referral traffic drop. Segments first-party data, correlates with deploys and confirmed search updates, produces ranked hypotheses with tests — never a reflexive "algorithm update" verdict. Use for "traffic dropped", "clicks fell", "lost rankings".

Weekly review — first-party performance deltas (when connected), new technical regressions from a lightweight crawl, experiment status, and at most three decisions for the owner. Silent when nothing material changed.