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. Tools like Google Search Console and PageSpeed Insights provide the underlying data.

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's coverage report for indexation errors and verify every old URL redirects to its new equivalent.

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 Screaming Frog instead.

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 page speed is a confirmed ranking factor, especially on mobile.

The most common hreflang errors are missing self-referencing entries, non-reciprocal links between language pairs, invalid codes like en-UK instead of en-GB, and canonical URLs that conflict with the hreflang set. Any of these can cause Google to ignore the annotations entirely.

Use an SEO audit to diagnose ranking, traffic, crawlability, and content problems across a site. For implementing structured data like FAQ or product schema, use a dedicated schema implementation approach, since auditing and markup generation are distinct tasks.