SEO Audit
An SEO audit is a structured review of a website’s technical, content, and authority signals to find issues that may limit crawling, indexing, ranking, or traffic.
Key takeaways
- An SEO audit is a structured review of technical, content, and authority signals.
- Start with crawlability and indexability, then move to sitemaps, mobile usability, page speed, and structured data.
- Google Search Console is essential for coverage, Core Web Vitals, and rich results reports.
- Common findings include orphan pages, broken links, redirect chains, and accidental noindex tags.
- Audits should be repeated quarterly or after any major site change.
An SEO audit helps you identify what is blocking your site from reaching its full organic potential.
Example: A 5-Page E‑commerce Site Audit Walkthrough
- Step 1 – Crawl the site with Screaming Frog (free version).
- Step 2 – Check robots.txt for accidental disallow of product pages.
- Step 3 – Review XML sitemap – ensure all 5 product URLs are included and no 404s.
- Step 4 – Inspect canonical tags – each product page should self-canonicalize.
- Step 5 – Run Core Web Vitals in Google Search Console – fix LCP if >2.5s.
- Step 6 – Validate structured data with Rich Results Test – correct product schema errors.
- Outcome: You find a noindex tag on the checkout page (should be indexable) and a broken link in the footer. Fix both → 20% more crawled pages in 2 weeks.
How to Perform an SEO Audit in 5 Steps
- Crawl your site – Use a tool like Screaming Frog or Sitebulb to get a full list of URLs, status codes, and meta data.
- Check indexability – Review robots.txt, meta robots tags, and X-Robots-Tag headers. Ensure important pages are not blocked.
- Analyze sitemaps – Verify XML sitemap is submitted in Google Search Console and contains only canonical, indexable URLs.
- Evaluate page speed – Use PageSpeed Insights for Core Web Vitals (LCP, FID, CLS). Prioritize fixes for pages with poor scores.
- Review structured data – Validate all schema markup with the Rich Results Test and cross-check with Search Console enhancement reports.
Prerequisites for a Successful SEO Audit
- Access to Google Search Console – for coverage, crawl stats, and manual action reports.
- A crawling tool – Screaming Frog (free up to 500 URLs) or Ahrefs Site Audit.
- Basic knowledge of HTML – to inspect source code and rendered output.
- Understanding of robots.txt and meta robots – to avoid blocking critical pages.
- Familiarity with canonical tags – to resolve duplicate content issues.
Common SEO Audit Mistakes
- Treating the audit as a one-time checklist – SEO changes constantly; rerun after major site updates.
- Relying only on tool output – always manually check source code, rendered pages, and real user behavior.
- Ignoring duplicate URL variants – www vs non-www, HTTP vs HTTPS, trailing slash differences can dilute signals.
- Prioritizing low-impact issues – fix accidental noindex tags, robots.txt blocks, or broken internal links before optimizing title tags.
Next step
FAQ
What is an SEO audit?
An SEO audit is a systematic review of a website's technical health, content quality, and authority signals to identify issues that block crawling, indexing, and ranking.
How often should you run an SEO audit?
At least quarterly, or after any major site change such as a redesign, migration, or new content launch.
What is the difference between an SEO audit and an SEO checker?
An SEO audit is a comprehensive, manual review of multiple factors, while an SEO checker is a tool that provides a quick, automated scan of basic issues.
Related topics
Sources
- Google Search Central — Primary documentation for crawling, indexing, sitemaps, robots directives, and structured data.
- Google Search Console Help — Official source for coverage, crawl stats, manual actions, rich results, and report interpretation.
- Moz SEO Audit Checklist — Clear, practical audit checklist structure with prioritization fields and repeatable workflow.
- Search Engine Land — Widely cited SEO publication for audit tactics, technical SEO, and search engine updates.
Reviewed by Lucía Marín, Founding editor.