seo-audit

Follow a priority order: crawlability and indexation first, then technical foundations like speed and HTTPS, then on-page optimization, content quality, and authority. Check robots.txt, XML sitemaps, canonical tags, title tags, and heading structure, then compile findings into a prioritized action plan.

Traffic drops after migrations 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 redirect mapping from old URLs to new ones.

No. Many CMS plugins inject JSON-LD via client-side JavaScript, which static fetch tools cannot see because they strip script tags. Use a browser rendering 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.

Common errors include missing self-referencing entries, non-reciprocal links between pages, invalid codes like en-UK instead of en-GB, and canonical tags conflicting with hreflang annotations. Any of these can cause Google to ignore the entire hreflang cluster.

Use a schema skill when the task is implementing structured data such as FAQ or product markup. An SEO audit diagnoses ranking and indexing problems; it does not write or deploy structured data code.