How to Run a Complete SEO Audit in 2026, Step by Step

Step 1: make sure engines see what you see

Start here, because a mistake at this level cancels everything else.

Open yoursite.com/robots.txt. Check that it doesn’t block sections you want indexed, and that it references your sitemap. Then open the sitemap itself: it should contain only canonical, indexable URLs returning 200. A sitemap listing redirects or noindexed pages signals sloppiness to every crawler that reads it.

Next, run site:yoursite.com in Google and compare the count with the number of pages you actually have. A large gap in either direction always tells a story: orphan pages, indexed duplicates, or whole sections being ignored.

Three checks almost everyone skips:

• The www and apex versions must redirect to one another with a 301/308, and both must serve a valid TLS certificate. We’ve seen sites lose half their backlink value because www served a broken certificate for months.
• Every page should carry a canonical tag pointing to itself, except deliberate duplicates.
• Private pages (client area, admin) must be noindexed, and deleted pages must return a real 404, not a 200 with a “not found” message. Soft 404s waste crawl budget and pollute the index.

Step 2: on-page, tag by tag

For each important page, in this order: the title (unique, under 60 characters, main keyword early), the meta description (it doesn’t rank, but it earns the click), the heading structure (one H1, H2s that genuinely divide the content), and image alt attributes.

What separates a current audit from a 2023 checklist is structured data. Google removed seven rich result types in January 2026 (Course Info, Claim Review and Estimated Salary among them), then dropped FAQ rich results for nearly all sites in May 2026. Time spent on FAQPage markup today is time wasted. Focus on Organization, Article with a named author, Product if you sell, and BreadcrumbList. Validate with Google’s Rich Results Test, not by eye.

Step 3: does the content deserve to rank?

This is the most uncomfortable question in the audit, and the one tools automate worst.

The March and May 2026 core updates confirmed the direction Google has been pushing for two years: scaled content abuse gets punished. Sites publishing hundreds of generated pages without editorial supervision lost 50 to 80% of their traffic during the March update. What survives is content that adds something the currently ranking page doesn’t have: first-hand data, a client case, a clear opinion from an identifiable author.

For every strategic page, ask three questions:

1. If this page disappeared, would anyone go looking for it?
2. What does it contain that the top three Google results don’t?
3. Can a reader tell who wrote it, and why that person is credible?

Three noes means the page is a liability, not an asset. Merge it, rewrite it, or delete it.

Step 4: performance, with the real thresholds

Core Web Vitals are measured in the field, at the 75th percentile of real Chrome visits, over a rolling 28-day window. The official thresholds haven’t moved: LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1.

Two clarifications that prevent bad audit calls:

INP replaced FID in March 2024 and is now the vital that fails most often. It measures the responsiveness of every interaction on the page, not just the first one. A site can post an excellent lab Lighthouse score and still have poor field INP, usually because of third-party scripts.

Don’t mix lab and field data. Lighthouse simulates; the CrUX API reports what real users experienced. When they disagree, the field wins. If a page lacks the traffic to appear in CrUX, fall back to origin-level data first, and only then to lab numbers.

Step 5: GEO, the part 2023 checklists ignore

Your clients now ask ChatGPT and Perplexity directly, and Google inserts AI Overviews above its results. Pew Research measured in July 2025 that when an AI Overview is present, only 8% of users still click an organic result, versus 15% without one. You can dislike it; you can no longer leave it out of an audit.

Check three things:

• AI crawler access. GPTBot, ClaudeBot, PerplexityBot and OAI-SearchBot must be able to read the site. Blocking them in robots.txt means choosing never to be cited. Do distinguish training bots from search bots, though: blocking training is a defensible policy choice, blocking search is a commercial handicap.
• Quotability. Answer engines lift self-contained passages: a direct 40-to-60-word answer at the top of a section, dated and sourced figures, headings phrased the way people ask questions. A long paragraph that buries the point will never get quoted.
• E-E-A-T signals. A named author with Person schema, visible publication and update dates, a clear entity behind the site. AI engines cross-reference these signals with brand mentions elsewhere on the web.

Step 6: cross-check against real data

An audit that only looks at the page gets its priorities wrong. Open Search Console: queries sitting in positions 4 to 10 with decent impressions are your quick wins (striking distance). Pages with high impressions and an unusually low CTR have a title or snippet problem, not a content problem. Then cross with analytics: a business-critical page receiving nothing deserves more attention than a page already ranking first.

That cross-referencing is exactly what we ended up automating in PimpSEO: Search Console and analytics data re-prioritize the technical findings in the report. A mediocre title on a high-stakes page outranks a missing alt on a dead one.

Delivering the audit: action plan first

Always end with a single list, sorted by impact-to-effort ratio, and for each item: the problem, the evidence (the measurement, the screenshot), the recommended fix, and the estimated effort. Ten actions maximum on the first page. Everything else goes in an appendix.

If you’d rather skip the afternoon this compilation takes, that’s what our tool does: paste a URL on the home page and the report comes out sorted, exportable to PDF, ready to present. Auditing one page is free and needs no account.