Technical SEO Audit Checklist for 2026

A technical SEO audit checks whether search engines can crawl, understand and index your site, and whether pages load and work properly for visitors. This checklist covers the checks that matter most, in the order to do them, and points to a free tool for each one. Work from the top: nothing else matters if search engines cannot reach your pages.

Want to do the whole process step by step? Follow How to Run a Free Technical SEO Audit.

1. Crawling and indexing

• robots.txt is not blocking important pages. Open yoursite.com/robots.txt and check that no rule blocks pages or resources you want crawled. See Google’s introduction to robots.txt.
• A sitemap exists and lists the pages you want indexed. Submit it in Google Search Console and reference it in robots.txt.
• No important page has a noindex tag by mistake. This is common after a site launch or redesign.
• Key pages appear in the index. Use the URL Inspection tool in Search Console on your most important URLs.
• Your firewall or security plugin is not blocking crawlers. Pages that work in your browser can still return errors to bots.

2. Status codes and redirects

• No important page returns a 4xx or 5xx error. Google’s documentation explains how it treats each status code.
• Redirects are 301s (permanent) where the move is permanent.
• No redirect chains. A to B to C wastes time. Point the first URL straight at the last.
• Internal links point to final URLs, not redirected ones. This includes the trailing-slash version if your site uses it.
• Deleted pages return a proper 404 or 410, not a normal page that says “not found” with a 200 status.

Crawl your site with the Page Audit Checker to see the status of every page it finds, and use the Errors and Redirects filters.

3. Titles, descriptions and headings

• Every page has a unique title. Keep them descriptive and not much longer than about 60 characters. Details in Title Tag Length.
• Every page has a unique meta description that summarizes the page.
• Each page has one clear H1 that matches its topic, followed by a logical heading order.
• No duplicate titles or descriptions across pages.

The Page Audit Checker flags missing, duplicate, short and long titles and descriptions, and shows character counts and estimated pixel widths.

4. Canonicals and duplicate content

• Indexable pages have a canonical tag pointing to the preferred URL, usually the page itself.
• Canonicals do not point to redirected, blocked or noindexed URLs.
• Only one version of the site is live. http redirects to https, and the www and non-www versions redirect to one.
• URL parameters and filters do not create endless duplicates of the same content.

Google explains how it picks a canonical in its guide to consolidating duplicate URLs.

5. Internal links

• Every important page is linked from at least one other page. Pages with no internal links, called orphan pages, are hard for crawlers to find.
• Navigation and footer links are real links that work without JavaScript.
• Anchor text is descriptive, not “click here”.

6. Images and accessibility

• Meaningful images have descriptive alt text, and decorative images have an empty one. Learn the rules in What Is Alt Text? and find problems with the Alt Text Checker.
• Images are compressed and use modern formats where sensible. Try the Image to AVIF Converter.
• Images have width and height attributes to prevent layout shift.

7. Structured data

• Key pages carry accurate structured data that matches the visible content: Organization, Article, Product, LocalBusiness and so on.
• Markup passes testing in the Rich Results Test and the Schema Markup Validator.
• No conflicting duplicate blocks from a plugin and hand-written code.

New to it? Start with What Is Schema Markup?, then build your markup with the Schema Markup Generator.

8. Mobile and speed

• Pages work on a phone: a viewport tag, no sideways scrolling, readable text and tappable buttons. Google indexes the mobile version of your pages, so see Mobile-First Indexing Explained and test with the Mobile Friendly Test.
• Core Web Vitals are in a healthy range in PageSpeed Insights and Search Console.
• No render-blocking or oversized resources slowing the first screen.

9. HTML and security

• The site uses HTTPS everywhere, with no mixed-content warnings.
• HTML is free of serious errors, such as unclosed elements and duplicate IDs. Check pages with the HTML Validator.
• A real 404 page helps visitors who land on a broken link.

10. Monitoring

• Search Console is set up and checked regularly for indexing and crawl problems.
• You re-crawl after major changes, such as a redesign, migration or new template.
• You keep a record of what you fixed and when.

How to prioritize what you find

Not every issue deserves the same attention. Sort what you find like this:

1. Blocks crawling or indexing (robots.txt, noindex, server errors on key pages): fix first.
2. Affects many pages (a template with duplicate titles, a redirect loop): fix next, since one change fixes a lot.
3. Affects important pages (your services, top articles, products): fix before low-traffic pages.
4. Polish (a few long titles, minor HTML warnings): fix when time allows.

What an audit cannot tell you

A technical audit finds problems that stop good content from performing. It does not write that content, build links or guarantee rankings. Treat it as the foundation, then build on it.

If you would rather have a specialist review everything, see our technical SEO audits, or ask about help with indexing and crawl fixes.

Frequently asked questions

What is a technical SEO audit?

A review of the technical factors that affect how search engines crawl, index and render your site, such as status codes, redirects, canonicals, sitemaps, structured data and page speed.

How often should I run a technical SEO audit?

At least a couple of times a year, and after any big change such as a redesign, platform move or URL restructure.

Can I do a technical SEO audit for free?

Yes. Google Search Console, PageSpeed Insights and the free SeckRates tools cover most of the basics for a small or medium site.

How long does a technical SEO audit take?

For a small site, a few hours. For a large site with many templates, it can take days, mostly in reviewing and prioritizing the results.

What should I fix first?

Anything that stops pages being crawled or indexed, then problems that affect many pages, then problems on your most important pages.