Technical SEO Audit Checklist for 2026 (Free Template Included)
SEO · 13 MIN READ

Technical SEO Audit Checklist for 2026 (Free Template Included)

The audit I run on every new client site, in the order I run it, with the parts that actually change outcomes marked.

By Tariq Sallam·September 2026

Most technical SEO audits are too long to be useful.

I have been sent hundred-page PDFs full of severity ratings where the top item was a missing alt attribute on a decorative icon, and the actual problem, an entire template blocked from indexing, was on page sixty-three.

So this is the shorter version. It is the sequence I genuinely work through, front-loaded with the things that have ever fixed a real traffic problem for me.

The order matters. There is no point optimising a page's structure if a robots directive means nobody can see it.

Quick Info

Best for
Site owners and marketers auditing their own site or a new client's
Difficulty
Moderate. A few items need developer help
Time to see movement
Crawl and index fixes can move within days. Everything else, weeks
Tools you'll need
Search Console, a crawler such as Screaming Frog, PageSpeed Insights, the Rich Results Test
Skills used
Technical SEO, a little HTML, patience with server settings
Last updated
September 2026

Stage One: Can It Be Crawled

Every audit starts here because everything downstream depends on it.

—Fetch robots.txt manually and read every line. Look for a Disallow that catches more than intended, and check whether staging rules were ever removed.
—Confirm the XML sitemap exists, returns 200, lists only canonical indexable URLs, and is referenced in robots.txt.
—Crawl the site and compare the URL count against the sitemap count. A large gap in either direction is your first real finding.
—Check for orphan pages. Anything important that no internal link points to is being crawled on charity.
—Review internal link depth. Anything more than three clicks from the home page gets crawled less often.
—Look at server response codes in bulk. Chains of redirects, soft 404s and 5xx spikes all waste crawl budget.

One addition for 2026: check whether you are inadvertently blocking AI crawlers. If your robots.txt or firewall blocks the user agents behind AI answer engines, you have quietly removed yourself from a growing share of visibility. Some sites do this deliberately. Very few do it deliberately and knowingly.

Stage Two: Is It Indexed, and the Right Version

Crawled and indexed are different states and conflating them causes most of the confusion I see.

—Work through the Search Console indexing report by reason, not by count. Crawled but not indexed usually means quality or duplication, not a technical fault.
—Check canonical tags across templates. Self-referencing on canonical pages, pointing correctly on variants, and never pointing at a redirect.
—Hunt duplicate content from parameters, pagination, trailing slashes, http and https, www and non-www, and uppercase URLs.
—Verify noindex is where you want it and nowhere else. Search your rendered HTML for it in bulk rather than trusting the CMS.
—Confirm hreflang if you run multiple languages, including the return tags. This is the single most commonly broken piece of markup I encounter.

A page can rank without a backlink. It cannot rank without being indexed.

Stage Three: Does It Render

This is where JavaScript-heavy sites tend to fall over, and where the audit stops being something you can do by reading source.

Use the URL Inspection tool and look at the rendered HTML, not the raw response. The question is simple: does the main content, the internal links and the structured data exist after rendering?

Common failures I keep finding. Content loaded only on scroll or on click. Navigation built entirely in JavaScript with no anchor tags. Pagination that works by state change and produces no crawlable URLs. Product content injected from an API that times out under crawler conditions.

If your framework renders client-side only, the fix is server-side rendering or static generation for anything you want found. Every other workaround is a workaround.

Stage Four: Speed and Core Web Vitals

Field data first, lab data second. The Core Web Vitals report in Search Console tells you what real users experienced. PageSpeed Insights tells you why.

Check the three metrics by URL group rather than by page, because failures are almost always template-wide.

—Largest Contentful Paint. Usually an unoptimised hero image, a slow server response, or render-blocking resources.
—Interaction to Next Paint. Usually too much JavaScript on the main thread, and very often a third-party script nobody remembers adding.
—Cumulative Layout Shift. Usually images and ad slots without dimensions, or a web font swapping late.

I go into the fixes in detail in my Core Web Vitals piece. For audit purposes you just need to know which template fails and why.

Stage Five: Structured Data and Machine Readability

This section has grown in importance faster than any other part of the audit, because it is now doing double duty for classic rich results and for AI source selection.

—Validate every template through the Rich Results Test and the schema validator. Errors, not just warnings.
—Confirm Organization schema on the site and Person schema for authors, wired together with sameAs links.
—Confirm Article schema names an author entity rather than a text string.
—Add FAQ and HowTo schema where the content genuinely contains those things, and remove it where it does not.
—Check Product, LocalBusiness and Breadcrumb markup where relevant, and make sure prices and availability are accurate rather than stale.

Then read your own heading structure as a machine would. One H1, no skipped levels, headings that describe the section rather than decorate it.

Stage Six: The Boring Essentials

Quick to check, occasionally catastrophic.

—HTTPS everywhere, valid certificate, no mixed content.
—One canonical domain, with everything else redirecting to it in a single hop.
—A genuine 404 status on missing pages, not a 200 with an apology.
—Mobile rendering that matches desktop content, since mobile is the version that counts.
—Image formats and dimensions specified, with meaningful alt text on content images.
—No accidental index bloat from tag archives, search result pages or filter combinations.

How to Prioritise the Findings

An audit that lists everything equally is a to-do list nobody will finish. I sort findings into three buckets and hand over nothing else.

01Blocking. Anything preventing crawl, indexation or rendering of pages that should earn traffic. Fix this week.
02Compounding. Duplication, internal linking, structured data, template-level speed failures. Fix this quarter, in that order.
03Hygiene. Everything else. Fix as it comes up, or never, and be honest that never is often the right answer.

If a finding cannot be traced to a plausible effect on traffic or conversions, it belongs in bucket three no matter how alarming the tool made it look.

Frequently Asked Questions

How often should I run a full technical audit?

Once a year for a stable site, once a quarter if you publish heavily or change templates often, and immediately after any migration or redesign.

Do I need a paid crawler?

Not to start. The free tier of Screaming Frog covers five hundred URLs, which is enough for many small sites, and Search Console covers the rest of the essentials.

Is technical SEO still worth it if content matters more?

Yes, because technical faults set a ceiling on what content can achieve. You cannot out-write a noindex tag.

What is the most common serious problem you find?

Indexation problems caused by duplication and thin archive pages, followed closely by client-side rendering hiding content and links.

Should I block AI crawlers in robots.txt?

For most businesses no. Blocking removes you from AI answers without returning the traffic. Decide it deliberately rather than inheriting it from a plugin default.

Where is the free template?

In the resources section linked at the end of this article, as a spreadsheet with the six stages and the priority buckets already set up.

Before You Go

The point of an audit is not to find problems. Any tool can find problems. The point is to find the two or three that are actually holding the site back, and to say so plainly enough that someone will fix them.

The spreadsheet version of this checklist, with the priority buckets built in, is in my resources section. The tools page lists what I use for each stage.

If you would rather have the audit done and handed to you with the findings already prioritised, that is a service I offer.

Fix the blockers first, Tariq

WRITTEN BY TARIQ SALLAM
Marketing Consultant. Entrepreneur. Content Creator.

I'm a marketing consultant, entrepreneur and content creator. I help businesses grow through practical marketing, websites, SEO, content and AI.

More About Tariq →

Keep reading