SEO Audit

How it works

An SEO audit begins by checking crawlability and indexability. The auditor reviews robots.txt, noindex directives, canonical tags, and XML sitemaps to confirm that important pages can be found and indexed by search engines. Google Search Console provides coverage and indexing reports, crawl stats, Core Web Vitals data, manual action notices, and rich results reports.

The audit then examines duplicate URL variants such as www versus non-www, HTTP versus HTTPS, and trailing-slash differences, ensuring they resolve to one preferred version via canonical tags. For JavaScript-heavy sites, the auditor checks rendered output because Google may see different content in raw HTML versus the final rendered page. Orphan pages, broken links, redirect chains, redirect loops, and soft 404s are flagged as common findings that can weaken site quality and crawl efficiency.

Structured data is validated using Google's Rich Results Test and compared with Search Console enhancement reports for errors and eligibility issues. The final output is an action list that ranks issues by severity (high, medium, low), affected URL count, traffic impact, and implementation effort, often using status fields like pass, fail, and N/A.

Why it matters

For SEO practitioners, an audit turns vague performance problems into a prioritized fix list by showing what blocks discovery, rendering, indexation, and trust. It helps separate high-impact technical issues from lower-value optimizations so teams can spend effort where it matters most.

Without an audit, accidental noindex tags, robots.txt blocks, or broken internal linking can silently prevent entire sections of a site from being indexed. Duplicate URL variants dilute ranking signals across multiple versions of the same page, and JavaScript rendering issues can cause Google to index incomplete or empty content.

Where it changes your decision

• When a site loses traffic without a clear cause: an audit reveals whether the drop is due to a crawling block, a manual action, or a technical regression.
• Before a site migration or redesign: an audit identifies existing issues that must be preserved or fixed, preventing new problems from being introduced.
• When planning a content or link-building campaign: an audit confirms that the target pages are indexable and load quickly, so the campaign effort is not wasted.

What it is not

• A one-time checklist: an SEO audit should be a recurring process that is rerun after major site changes, not a single pass that is never repeated.
• Just a tool report: focusing only on tool output without manually checking source code, rendered pages, and real page behaviour misses issues that automated tools cannot detect.
• Only about page speed: while speed is part of an audit, it also covers crawlability, indexation, duplicate content, structured data, and internal linking.
• A competitor analysis: an audit examines your own site's technical health, not how your site compares to competitors' content or backlink profiles.

Worked example

An e-commerce site with 10,000 product pages sees a 40% drop in organic traffic over three months. The SEO audit begins by checking crawlability: the robots.txt file accidentally blocks the entire /products/ directory, and 3,000 product pages have a noindex meta tag left over from a staging environment. Google Search Console shows a sudden spike in excluded URLs in the coverage report.

The audit also finds 500 broken internal links, a redirect chain of four hops on the homepage, and 200 orphan pages that have no internal links pointing to them. The action list ranks the robots.txt block and noindex tags as high severity because they affect 5,000 pages directly, while the broken links and redirect chain are medium priority. After fixing the robots.txt file and removing the noindex tags, the site recovers 80% of its lost traffic within two weeks.