seo-audit

Start with crawlability and indexation checks (robots.txt, XML sitemap, canonical tags), then review technical foundations like Core Web Vitals and HTTPS, followed by on-page elements and content quality. The audit produces a prioritized action plan ordered by impact.

Migration traffic loss usually comes from missing 301 redirects, incorrect canonical tags, blocked crawlers in robots.txt, or unsubmitted sitemaps. Check Search Console coverage reports for indexation errors and verify redirect mapping from old to new URLs.

No, web_fetch strips script tags and curl only sees static HTML, so both miss JSON-LD injected client-side by CMS plugins like Yoast or RankMath. Use a browser tool, Google Rich Results Test, or Screaming Frog, which render JavaScript.

LCP (Largest Contentful Paint) should be under 2.5 seconds, INP (Interaction to Next Paint) under 200ms, and CLS (Cumulative Layout Shift) under 0.1. Measure them with PageSpeed Insights, WebPageTest, or the Search Console Core Web Vitals report.

Ensure every page has a self-referencing hreflang entry, reciprocal return links between locale pairs, valid ISO 639-1 and ISO 3166-1 codes, and an x-default fallback. Each locale page must self-canonical; never canonical across locales.

Use a schema skill when the task is implementing structured data like FAQ or product markup. An SEO audit diagnoses ranking and traffic issues; it identifies missing schema but defers actual implementation to the dedicated schema skill.