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 produces findings with impact ratings and a prioritized action plan.

Migration traffic loss usually comes from missing 301 redirects, incorrect canonical tags, blocked crawlers in robots.txt, or outdated XML sitemaps. Check Search Console's coverage report for indexation errors and verify every old URL redirects to its new equivalent.

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

Google's thresholds are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. Pages loading in 5-6 seconds are well above acceptable limits and can negatively affect rankings, especially on mobile.

The most common errors are missing self-referencing entries, non-reciprocal links between locale pairs, 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 adding FAQ schema to product pages. An SEO audit diagnoses issues and prioritizes fixes but defers actual structured-data implementation to the dedicated schema skill.