Technical SEO
SEO Audit Operating System
A repeatable SEO audit workflow for diagnosing crawl, index, rendering, content, authority, local, AI visibility, and conversion constraints in order.
An SEO audit should follow the path a page must travel before it can create business value: discovery, crawling, indexing, rendering, understanding, ranking, trust, clicks, and conversion.
The operating system is simple: diagnose the earliest constraint first, then move downstream. A conversion audit cannot fix a page that is blocked from indexing, and more backlinks rarely solve a page that does not match search intent.
The audit sequence
| Step | Question | Evidence To Collect | Common Output |
|---|---|---|---|
| 1. Discover | Can search systems find the important URLs? | Internal links, XML sitemaps, backlinks, crawl exports. | Link important orphaned pages, clean sitemap inclusion. |
| 2. Crawl | Can crawlers request the URLs and resources? | Status codes, robots.txt, server errors, blocked assets. | Fix blocks, errors, redirect loops, and unavailable templates. |
| 3. Index | Are pages eligible and worth storing? | Meta robots, canonicals, duplicate patterns, Search Console index data. | Fix noindex mistakes, canonical conflicts, thin duplicates. |
| 4. Render | Does the rendered page expose meaningful content and links? | Rendered HTML, screenshots, JavaScript dependency checks. | Make primary content and links available reliably. |
| 5. Understand | Is the page purpose and entity context clear? | Titles, headings, schema, breadcrumbs, author/source context. | Clarify page type, topic, entity, and hierarchy. |
| 6. Match intent | Does the page satisfy the query task? | SERP patterns, competitor formats, query modifiers, user needs. | Change page type, depth, structure, proof, or CTA. |
| 7. Build authority | Is there enough trust to compete? | Backlinks, mentions, reviews, citations, expert proof, original assets. | Build citation-worthy pages and external corroboration. |
| 8. Convert | Does visibility produce qualified action? | CTA placement, form starts, tool completions, lead quality, calls. | Align next steps with searcher intent and business value. |
| 9. Measure | Can the team tell whether work helped? | GSC, analytics, rank tracking, logs, CRM notes, annotations. | Track page groups, not isolated vanity metrics. |
Use this order as a guardrail, not a ritual. If a site has a known migration issue, start there. If a local business has perfect indexation but no reviews or local proof, local trust may be the real constraint.
Intake questions
Before crawling anything, collect enough context to avoid a generic audit:
- What changed recently: migration, redesign, CMS change, content deletion, tracking change, product change, or algorithm update?
- Which page groups matter most: services, products, categories, locations, guides, tools, or comparison pages?
- Which outcomes matter: impressions, clicks, leads, calls, bookings, revenue, local actions, or brand demand?
- Which markets, languages, or locations matter?
- Who can fix issues: engineering, content, design, local operations, leadership, or an outside vendor?
- What tools are available: Search Console, analytics, rank tracking, crawl data, server logs, CRM data, GBP insights?
Good intake narrows the audit. A small, focused review with the right evidence beats a broad issue dump that nobody can execute.
Evidence map
| Audit Lane | Strong Evidence | Weak Evidence |
|---|---|---|
| Crawlability | Crawl exports, server responses, robots rules, rendered HTML samples. | Tool warnings without affected URL examples. |
| Indexability | Search Console URL inspection, canonical tags, noindex directives, duplicate clusters. | Assuming a page is indexed because it appears in a sitemap. |
| Intent | SERP format patterns, query modifiers, competitor page types, user task analysis. | Keyword volume without page-type analysis. |
| Content quality | Original examples, freshness, author/source clarity, useful depth, visible proof. | Word count targets alone. |
| Authority | Relevant links, mentions, citations, reviews, expert profiles, digital PR assets. | Domain metrics without source review. |
| Local trust | GBP data, NAP consistency, reviews, local page proof, citation quality. | Directory count alone. |
| Measurement | GSC trends, analytics, conversion data, annotations, page-group reporting. | One-day rank movements. |
Every finding should include affected URLs, business relevance, likely cause, recommended fix, owner, risk, and how to measure the result.
Priority logic
Use a priority score after evidence is collected:
| Factor | Question |
|---|---|
| Impact | Would fixing this affect important pages, leads, revenue, crawl/index quality, or trust? |
| Confidence | Is the evidence strong enough to act? |
| Effort | Can the team realistically ship the fix soon? |
| Risk | Could the fix break traffic, UX, tracking, or existing rankings? |
Then apply decision rules:
- Fix crawl and index blockers before polishing visible snippets.
- Fix high-value templates before isolated low-value URLs.
- Fix pages tied to business outcomes before low-intent archives.
- Prefer reversible fixes when evidence is incomplete.
- Batch similar issues when one owner can solve them together.
- Document what is deferred and why.
Audit outputs
A useful audit should produce three views:
| Output | Audience | Purpose |
|---|---|---|
| Executive summary | Owner, founder, marketing lead | Names the main constraint and top actions. |
| Priority map | SEO, content, engineering, local ops | Converts findings into ordered work. |
| Evidence appendix | Implementers and reviewers | Shows URLs, screenshots, exports, and source data. |
Avoid sending only a spreadsheet. The spreadsheet is useful evidence, but the priority map is the decision layer.
Page-group thinking
Most SEO problems are template or page-group problems. Review pages by role:
- Homepage and brand pages.
- Core service or product pages.
- Category and collection pages.
- Location and service-area pages.
- Guides, blog posts, and resource pages.
- Topic definitions and glossary pages.
- Tools, calculators, templates, and research assets.
- Thin archives, tags, filters, search results, and parameter URLs.
For each group, decide whether the page type should be indexed, what search intent it serves, how it is discovered, what canonical rules apply, and what action it should create.
Key supporting topics include Robots.txt, XML Sitemap, Redirects, Canonical URL, and JavaScript SEO.
Measurement plan
Measure the page group changed by the work. If internal links were improved for service pages, track service-page crawling, impressions, clicks, rankings, assisted conversions, and leads. Do not judge the work only by total site sessions.
Useful reporting fields:
| Field | Why It Matters |
|---|---|
| Page group | Keeps analysis tied to the affected template or cluster. |
| Change shipped | Connects movement to actual work without overclaiming causation. |
| Date shipped | Helps compare before and after windows. |
| Primary metric | Keeps the team honest about the intended outcome. |
| Secondary signals | Shows early movement before conversions change. |
| Next decision | Turns reporting into prioritization. |
Common audit mistakes
- Starting with tool warnings instead of business-critical page groups.
- Treating every issue as equal.
- Recommending more content before fixing indexation, intent, or internal links.
- Reporting rankings without clicks, leads, or page purpose.
- Overreacting to one day of data.
- Ignoring implementation risk.
- Leaving stakeholders with findings but no sequence.
Use this system
Start with the SEO Audit Checklist for a directional score. Then use the SEO Audit Prioritization Template to turn findings into an action plan.
For a real-world scenario, review the Example SEO Audit Priority Map. If the site is losing traffic, use the Traffic Drop Diagnosis workflow before changing pages. For evidence collection, use the SEO Audit Evidence Checklist.