An SEO site audit is a structured review of crawling, indexing, content, and speed to surface fixes that improve visibility and user experience.
If a website isn’t growing, an audit pinpoints why. A good one shows what blocks discovery, what slows pages, and what keeps content from earning clicks. Done well, it turns guesswork into a clear action plan with measurable wins.
SEO Site Audit Basics And Scope
An audit maps how search engines reach, understand, and rank your pages, then checks how real people experience them. You’ll review technical setup, content quality, internal linking, structured data, and performance. The end product is a prioritized list of fixes with evidence and expected impact.
What You Get From A Quality Audit
- A crawl map that reveals dead ends, loops, and thin sections.
- Index status for key URLs, with reasons when pages drop out.
- Page templates and components flagged for speed and layout issues.
- Content gaps, duplication, and weak intent alignment.
- Simple wins: redirects to add, tags to adjust, and links to tidy.
Who Should Run It
Any site that relies on search traffic benefits, but the payoff is strongest for sites with many templates, large archives, frequent releases, or a recent redesign. New sites also gain by setting clean baselines.
Audit Snapshot: What To Check Early
The list below helps you spot big blockers fast. It also shows where to find proof inside common tools.
| Area | What To Check | Tools / Where To Look |
|---|---|---|
| Crawl Access | robots.txt rules, blocked paths, server responses | Site root /robots.txt, server logs, crawler reports |
| Index Coverage | Canonical tags, noindex, duplicate sets | Search Console, page HTML, crawl diff |
| Site Architecture | Depth to key pages, orphan sections, anchor text | Crawl graphs, internal link exports |
| Page Speed | Core Web Vitals, heavy scripts, image sizing | Lab tests + field data, template review |
| Content Fit | Intent match, duplication, thin pages | SERP checks, content inventory |
| Structured Data | Schema coverage, errors, rich result gaps | Validator tests, template snippets |
| Redirects | Chains, loops, mixed protocols | Server config, crawl exports |
| Images | Alt text, lazy-load, file weight | Template review, media library |
| Mobile UX | Tap targets, layout shift, viewport | Device tests, field data |
| Duplicate Control | Params, faceted pages, printer views | Rules in robots, canonicals, sitemaps |
How To Run A Clean, Proof-Based Audit
You’ll move faster with a repeatable flow. The sequence below balances speed with depth and keeps findings actionable.
1) Scope And Goals
Define the pages and templates in play, the markets you care about, and the metrics that matter. Common goals: recover lost traffic, prepare for a launch, or raise the ceiling on top pages.
2) Baseline Signals
Pull last 90 days of clicks and impressions for core sections. Flag sudden drops by template or device. Mark any releases that match those dates. This frames the search for root causes.
3) Crawl The Site
Run a crawl with JavaScript on for main templates, and a second pass with scripts off to catch render pitfalls. Export status codes, directives, canonicals, and internal links. Note sections blocked by rules or templates that render thin content.
4) Check Index Status
Confirm that key URLs are discoverable and indexable. Review canonical signals, duplication, and soft 404s. If a page matters and isn’t in the index, collect the exact reason and a test URL that proves it.
5) Measure Real-User Speed
Pair lab runs with field data. Lab runs help you fix regressions; field data confirms the fix actually lands for users at scale.
6) Review Content Quality
Open the top queries for each target page. Compare the page to the current winners. Check intent, depth, freshness, and clarity. Flag thin sections, stale data, and template copy that repeats across many URLs.
7) Validate Structured Data
Spot missing types and fix errors. Keep schema aligned with what’s visible on the page. When a template shows ratings, events, or recipes, the markup should match.
8) Prioritize Fixes
Group tasks by payoff and effort. Quick wins often sit in redirect cleanups, template speed trims, and indexability tweaks. Bigger lifts include architecture changes or large-scale content refreshes.
Where Official Guidance Fits In
Two references help you stay aligned with search best practices while you audit. The SEO starter guide summarizes how search engines discover, understand, and show pages. For user experience and speed, the Core Web Vitals page explains the metrics and thresholds that shape real-world performance.
Technical Checks That Move The Needle
Robots Rules And Access
Confirm that the robots file lives at the site root and that it doesn’t block sections that need visibility. If you need to keep a folder out, pair robots directives with clear internal linking to the content that should rank. When you need to keep data private, use authentication, not robots rules.
Canonicals And Alternate URLs
Each page should send a strong self-reference unless you’re consolidating to a main URL. Watch for mixed signals across canonicals, redirects, and sitemaps. For series pages and UTM parameters, point signals to a single version.
Internal Links And Depth
Key pages should be reachable within a few clicks from the homepage or a hub. Use descriptive anchors that match page intent. Trim low-value tag pages that siphon equity and slow crawls.
Performance And Stability
Audit script weight, third-party tags, image formats, and layout shift. Ship images with modern formats and correct sizes. Defer non-critical scripts. Keep font swaps stable. Field data tells you which templates need the most love.
Structured Data
Add schema only where the page actually shows that info. Keep it in sync with the visible content. Fix warnings and errors before release.
Content Review That Matches Search Intent
Start with the query behind each page. If the searcher wants a step-by-step guide, give clear steps and visual cues. If they want a price range, put the numbers near the top and back them with sources. Cut filler, merge overlapping pages, and refresh stats and screenshots that age.
Template-Level Fixes
- Put the core answer near the top in plain text.
- Use headings that promise what’s below them.
- Write short paragraphs and helpful bullets.
- Keep one h1 per page and a clean h2–h3 flow.
- Add descriptive alt text to images and compress media.
Proof And Deliverables
Stakeholders want fixes that stick. Your audit packet should include a clear task list, before-and-after snapshots, and test URLs. Keep changes grouped by template or system so teams can ship them in tidy batches.
| Symptom | Likely Cause | Quick Fix |
|---|---|---|
| Pages Dropped From Results | Conflicting canonicals or soft 404 template | Set self-canonicals, fix status codes, tighten copy |
| Good Content, Weak Impressions | Thin internal links, deep crawl depth | Add hub links, surface in nav and related blocks |
| Intermittent CLS Spikes | Late-loading ads or images without dimensions | Reserve slots, set width/height, delay non-critical tags |
| Mobile Bounce On Top URLs | Heavy scripts, render-blocking CSS | Split bundles, load CSS critical path inline |
| Duplicate Sets In Index | Params and sort pages open to crawlers | Consolidate with canonicals and param handling |
| Old Screenshots In Guides | Stale updates, mixed dates across pages | Refresh media, keep one visible date via template |
Step-By-Step Workflow You Can Reuse
1) Inventory The Site
Export URLs by template and section. Mark indexable status, canonical target, depth, and traffic. This gives you a live map of what exists and what matters.
2) Triage Technical Risks
Scan responses, directives, and redirects. Fix hard blockers first: 4xx/5xx on key URLs, noindex on live pages, wrong canonicals, or rules that stop crawls.
3) Measure Speed On Real Devices
Compare field and lab results. Focus on slow templates first. Ship image compression, caching, and script defers, then retest to confirm gains.
4) Align Pages To Intent
Rewrite intros so readers get what they came for in the first screen. Slice fluff. Merge thin pages that split the same topic across several URLs.
5) Strengthen Internal Links
From hubs and nav, add links that send clear signals to cornerstone pages. On long articles, add related links that match search intent and keep readers moving.
6) Ship, Measure, Iterate
Group changes, release in batches, and watch trends for two to four weeks. Track both traffic and user experience to prove the value of each batch.
FAQs To Skip And Checks To Keep
Don’t bloat pages with filler Q&A blocks that repeat the same answer. Put energy into the main copy, the structure, and the speed of the page. Keep a short checklist for each new release so regressions don’t creep back in.
When To Re-Audit
Run a light pass after large code deploys, theme changes, or content migrations. Do a deeper pass each quarter for big sites and twice a year for smaller sites. Refresh screenshots and figures when products or rules change.
Practical Takeaways
- Lead with access, indexability, and speed. Those wins often land in days.
- Match pages to the searcher’s intent and trim duplication.
- Use clean internal links to lift the pages that matter most.
- Document everything: the issue, the fix, the proof, and the owner.
- Re-test on real devices and in the field to confirm lasting gains.
Helpful Extras While You Work
If you need to adjust crawler access during maintenance or to steer bots away from low-value paths, confirm your robots.txt rules are clean and placed at the root. When speed changes are on deck, pair template changes with live checks against the Core Web Vitals thresholds so fixes stick for real users.