seo-audit

An SEO audit follows a priority order: crawlability and indexation first, then technical foundations like speed and mobile-friendliness, then on-page optimization, content quality, and authority. The output should list each issue with its impact, evidence, fix, and priority.

Traffic drops after migration usually come from missing 301 redirects, incorrect canonical tags, blocked crawlers in robots.txt, or outdated XML sitemaps. Check Search Console coverage reports for indexation errors and verify every old URL redirects to its new equivalent.

Ranking failures typically involve misaligned title tags, H1s, and URLs, thin content compared to competitors, keyword cannibalization between pages, or indexation problems. Compare your page's depth and E-E-A-T signals against the current top-ranking results.

No, static HTML fetching and tools that strip script tags cannot reliably detect schema markup, since many CMS plugins inject JSON-LD via client-side JavaScript. Use a rendering browser, Google's Rich Results Test, or a Screaming Frog crawl instead.

Common hreflang errors include missing self-referencing entries, non-reciprocal links between pages, invalid codes like en-UK instead of en-GB, and canonicals pointing outside the hreflang set. Any of these can cause Google to ignore the annotations entirely.

Use a dedicated schema skill when the task is implementing structured data such as FAQ or product markup. An SEO audit diagnoses issues and identifies missing schema, but implementation of the markup itself belongs to the schema skill.