Log in

Sign up

Webmaster's panel

How to Do an SEO Audit: A Practical 2026 Checklist

Author

Anna Pawłowska

8 minutes 10 seconds

16 September 2026

Somewhere on your hard drive is an SEO audit spreadsheet nobody has opened since March. Forty tabs, three hundred rows, a traffic-light system that made sense at 11pm and means nothing now. Everyone who does this for a living has one. The good news is that a proper audit doesn't need to look like that, and it doesn't need three weeks either.

An SEO audit is really just a health check for your site: is Google able to find it, understand it, trust it, and load it fast enough that people stick around? In 2026 there's a fifth question stapled to the front of that list — can AI Overviews, ChatGPT, and Perplexity read it too? — but the core exercise hasn't changed. You crawl, you measure, you fix the things that matter first.

This checklist walks through it in the order we'd actually do it, from the technical plumbing nobody sees to the AI-visibility work everybody's suddenly asking about. Keep it open in one tab and work down it; by the end you'll have a prioritized list instead of a folder of screenshots.

Try out WebWave

Keep Reading

What's actually different about auditing a site in 2026

AI Overviews now show up on roughly half of Google searches, which means a meaningful slice of your "impressions" in Search Console never turn into a click at all — the answer is already on the results page. That's not a reason to panic, and it's definitely not a reason to abandon classic SEO. It's a reason to widen the audit. We wrote a longer breakdown of how SEO and GEO actually differ and where they overlap if you want the full picture, but the short version for this checklist is: the sites Google ranks highly are, for the most part, the same sites AI models pull from. Clean structure, real internal linking, and content that earns trust still do most of the work. You're just now optimizing for two readers instead of one — a person, and a language model skimming your page for a fact it can cite.

Part 1 — Can search engines even find you?

Start here, because nothing else in this checklist matters if the page isn't indexed.

Check indexation status. Search site:yourdomain.com and compare the count to your actual page total. Open Google Search Console and look at the Pages report — anything sitting under "Crawled, not indexed" or "Discovered, not indexed" is worth investigating before you touch anything else.

Validate robots.txt. It should block staging environments and pointless faceted URLs, not your CSS, your images, or (increasingly relevant) the AI crawlers — GPTBot, PerplexityBot, ClaudeBot — that decide whether your content ever gets cited in an AI answer. Blocking them isn't a safety default anymore; it's an invisibility switch you may be flipping without noticing.

Submit and clean up your XML sitemap. It should list only canonical, indexable URLs — no redirects, no 404s, no noindex pages hiding in there. We go into sitemap structure in more depth in this piece on building one that actually helps your rankings.

Hunt down redirect chains and broken links. A→B→C redirect chains waste crawl budget and dilute link equity at every hop. Any decent crawler (Screaming Frog, Ahrefs, Semrush) will surface these in a few minutes.

Check canonical tags. Every indexable page needs exactly one canonical, pointing to itself unless there's a genuine duplicate elsewhere. Self-referencing canonicals on every page is the safest default.

Part 2 — Speed and Core Web Vitals

Google measures three things here, and the thresholds are specific enough to test against directly:

LCP (Largest Contentful Paint) — under 2.5 seconds is "good"
INP (Interaction to Next Paint) — under 200 milliseconds is "good"
CLS (Cumulative Layout Shift) — under 0.1 is "good"

To officially "pass," 75% of your real visitors (measured through Chrome's field data, not a lab test) need a good score on all three, on a given URL. Run your key pages — homepage, top landing pages, your best-performing blog posts — through PageSpeed Insights and note which metric is failing, because the fix depends entirely on which one it is. A slow LCP is almost always a heavy hero image or a sluggish server response. INP usually traces back to too much JavaScript firing the moment someone taps a button. CLS is the odd one out: it's rarely code at all, just an image or an ad loading without a reserved size and shoving the text down mid-read.

Practical fixes that move the needle fastest: compress and convert images to WebP or AVIF, lazy-load anything below the fold, defer non-critical scripts, and get a CDN in front of static assets if you don't have one. We've written more on why page speed affects rankings and what to fix first if this section turns up more red than green.

Part 3 — Mobile-first, because it's the only "first" that counts

Google has indexed the mobile version of your site by default for years now, so test on mobile, not desktop-with-a-narrower-window. Run Google's Mobile-Friendly Test, but also actually open the site on a real phone: tap targets that are too close together, text that requires pinch-zooming, and menus that cover half the screen are the kind of thing an automated tool shrugs off but a real visitor bounces over. If you're rebuilding rather than patching, this rundown of responsive design done properly is worth a read before you start.

Create your website, your way

Start for free

Part 4 — On-page SEO, the part everyone half-remembers

This is the section people think they know, then discover three pages with duplicate title tags they forgot about.

Title tags: unique per page, 50–60 characters, primary keyword near the front
Meta descriptions: 140–160 characters, written to earn the click rather than stuff the keyword
One H1 per page, containing the primary keyword naturally
A logical heading hierarchy — H2s and H3s that actually nest under the right H1, not a flat wall of bold text pretending to be structure
Descriptive alt text on every meaningful image (not just for accessibility scores — AI crawlers use it too)
Visible freshness signals on evergreen content: a "last updated" date does more for trust than people give it credit for

If keyword placement and jargon like "search intent" or "topical authority" still trip you up mid-audit, our glossary of SEO and content terms is a faster reference than another ten-tab Google session.

Part 5 — Site architecture and internal linking

This is the part most audits rush through, and it's usually where the easiest wins are hiding.

Map how many clicks it takes to reach every important page from your homepage — anything past three or four clicks deep is effectively invisible to both users and crawlers. Then look at your internal linking itself: every important page should have at least one contextual link pointing to it from somewhere else on the site, with descriptive anchor text rather than "click here." A pillar page on a broad topic, linking out to detailed spoke articles that link back to it, does more for topical authority than a dozen isolated posts ever will. If you're auditing landing pages specifically, these SEO elements that get skipped on landing pages more than anywhere else is a good companion checklist.

Part 6 — Structured data

Schema markup is how you hand search engines and AI models a structured, unambiguous version of what's on the page, instead of making them infer it. At minimum, check for:

Organization schema sitewide
Article schema on blog posts
Product schema on anything sellable
FAQPage schema wherever you already have a Q&A section

Run pages through Google's Rich Results Test and the Schema.org validator, and make sure the markup actually matches what's visible on the page — mismatched schema is a trust signal in the wrong direction. The mistake we see most often in audits isn't a missing schema type at all. It's three different schema blocks on one page, each describing a slightly different version of the same product or article, left behind by three separate edits nobody cross-checked. Where you do have several schema types on one page, nesting them into a single @graph with proper @id references is cleaner than stacking separate script tags.

Part 7 — Answer Engine Optimization (AEO)

This is the newer half of the checklist, and it's less about technical fixes and more about how you write.

Lead with the answer. Put the direct answer to the implied question in the first sentence or two of a section, then explain. AI systems (and skimming humans) reward content that front-loads the point instead of building up to it across three paragraphs.

Add real FAQ sections. Five to eight genuine questions per key page, marked up with FAQPage schema, phrased the way a person would actually type them.

Write self-contained sections. Each H2 or H3 block should make sense if it's the only paragraph an AI model ever pulls out and quotes — which means restating the subject rather than leaning on "it" and "this" from three sentences up.

Build topical authority through interlinking, not just individual great pages — a cluster of ten genuinely connected articles on a subject outperforms one exhaustive post with no support around it.

Part 8 — Generative Engine Optimization (GEO)

GEO is AEO's sibling, aimed specifically at the AI Overviews and chat-based answer engines that summarize rather than link.

Make sure your content is actually renderable by AI crawlers — if your key content only appears after client-side JavaScript runs, server-side rendering (or at least pre-rendering) is worth the engineering time
Use real HTML tables for comparisons, not screenshots or image-based infographics — a model can't extract data from a picture
Back claims with specific numbers and sources rather than vague superlatives — "reduces load time by 40%" survives being quoted; "significantly faster" doesn't
Keep dates and stats current — GEO rewards freshness more aggressively than classic SEO ever did

If you're building or rebuilding with this in mind from the ground up, it's worth knowing what a genuinely AI-first website builder handles for you automatically versus what you'll be patching in by hand afterward.

Part 9 — Content quality and keyword coverage

Pull your top pages by traffic and impressions from Search Console and Analytics, and ask three questions of each one: does it still match what people are actually searching for, is it competing with another page on your own site for the same query (keyword cannibalization is more common than most audits catch), and does it say anything that isn't already said better somewhere else on the internet. Thin, outdated, or overlapping pages are usually better merged or rewritten than left alone.

This is also the point where a proper SEO analyzer earns its keep instead of a dozen browser tabs — WebWave's built-in SEO analyzer flags exactly this kind of thing (missing meta data, duplicate titles, thin content) as you're editing the page, not three months later in an audit like this one. If SEO tooling is genuinely a gap in how your site is built, the SEO, blog, and branding features overview is worth ten minutes.

Part 10 — Local SEO, if it applies to you

Skip this section if you're not a local business — but if you are, and your audit doesn't check your Google Business Profile, NAP (name, address, phone) consistency across directories, and local landing pages, it's an incomplete audit. We covered the specifics in this guide to ranking for local search, and most of it applies well beyond the market in the title.

Part 11 — Put it all in order

An audit that ends in a wall of findings with no priority is just a longer version of the problem it was meant to solve. Sort what you found into three buckets before you close the laptop:

Fix today — broken indexing, blocked AI crawlers, missing HTTPS, a homepage failing Core Web Vitals
Fix this month — on-page gaps, missing schema, thin content, weak internal linking
Ongoing — content freshness, new FAQ sections, monitoring dashboards

And build a rhythm around it rather than waiting for the next fire: a quick health check on your most important pages weekly, a fuller crawl monthly, and a proper deep audit like this one quarterly — plus an unscheduled one any time you migrate platforms or Google ships a core update.

Choose one of the free templates and create your website effortlessly