seo-audit

Start with crawlability and indexation (robots.txt, XML sitemap, canonical tags), then check technical foundations like Core Web Vitals and HTTPS, followed by on-page elements and content quality. The audit report organizes each finding by issue, impact, evidence, fix, and priority.

Migration traffic loss usually comes 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 redirect mapping from old to new URLs.

No. Many CMS plugins inject JSON-LD via client-side JavaScript, which web_fetch and curl cannot see because they do not render scripts. Use a browser tool, Google Rich Results Test, or a Screaming Frog export to accurately detect structured data.

Largest Contentful Paint should be under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Measure these with PageSpeed Insights, WebPageTest, or the Search Console Core Web Vitals report.

Frequent errors include missing self-referencing entries, non-reciprocal links between locale pages, invalid codes like en-UK instead of en-GB, and cross-locale canonicals that suppress indexing. Each locale page must self-canonical and appear in the hreflang set.

Use a schema skill when the task is implementing structured data such as FAQ or product markup. An SEO audit diagnoses ranking and traffic issues; it identifies missing schema as a finding but does not perform the implementation.