Most technical SEO guides read like an engineering manual. You open them, see 60 line items, and close the tab. This technical SEO audit checklist is built differently: it is a sequence of 14 checks you can run from start to finish in a single afternoon, even if you have never opened a crawler before.

By the end you will have a prioritized list of fixes ranked by impact, so you know exactly what to hand to your developer first and what can safely wait until next quarter. cognitiveseo.com published something useful on the subject.

What a Technical SEO Audit Actually Does

A technical SEO audit answers three questions, in this order:

1. Can search engines reach my pages? (crawlability)
2. Are they allowed and willing to store them? (indexation)
3. Is the experience good enough to compete? (speed, mobile, structured data)

That order matters. A perfect Core Web Vitals score on a page blocked by robots.txt is worth exactly nothing. Work top down and you never waste effort. An in-depth look at it is worth the time.

One thing has changed in 2026: crawlers are no longer just Googlebot and Bingbot. AI assistants pull from the same infrastructure, and a site that is hard to crawl is also invisible in AI-generated answers. The good news is that the fixes are identical. Clean HTML, fast responses and clear signals serve both.

Tools You Need Before You Start

You can complete this entire checklist with free tools. Paid tools mostly save time and add monitoring.

Job	Free option	Paid option
Crawling the site	Screaming Frog (500 URLs free)	Screaming Frog licence, Sitebulb, Semrush Site Audit, Ahrefs Site Audit
Indexation data	Google Search Console, Bing Webmaster Tools	Index monitoring in Ahrefs or Semrush
Speed and Core Web Vitals	PageSpeed Insights, Chrome Lighthouse, CrUX dashboard	DebugBear, SpeedCurve, Calibre
Mobile checks	Chrome DevTools device mode, GSC mobile report	BrowserStack, LambdaTest
Structured data	Rich Results Test, Schema Markup Validator	Schema App, crawler schema reports
Log file analysis	Server logs plus a spreadsheet	Screaming Frog Log Analyser, Botify, JetOctopus

Set aside roughly four hours. Start the crawl first and let it run while you work through the Search Console checks.

The 14-Point Technical SEO Audit Checklist

1. Confirm your access and baselines

Before touching anything, make sure you own the data:

• Verify the site in Google Search Console using the domain property, not just the URL prefix. The domain property captures http, https, www and all subdomains.
• Add Bing Webmaster Tools. It is free, takes two minutes with the GSC import, and its crawl data is often more generous.
• Note your current numbers: indexed pages, clicks over the last 28 days, and average position. You need a before picture to prove the audit worked.

2. Run a full crawl of the site

Open Screaming Frog (or your crawler of choice), enter your homepage URL, and start the crawl. While it runs, configure two things:

• Enable JavaScript rendering if your site is built on React, Vue, Next.js or a similar framework. Crawl it twice, once with rendering and once without, then compare the number of discovered links. A big gap means content depends on JavaScript.
• Connect the Search Console and Analytics APIs so the crawl shows impressions and sessions next to each URL. This is how you later sort fixes by traffic impact.

Sites with more than 500 URLs will need a paid licence, or you can crawl section by section using include rules.

3. Check what is actually indexed

Go to Search Console > Indexing > Pages. This report splits your URLs into indexed and not indexed, with reasons. Look for:

• Crawled – currently not indexed: usually a quality or duplication signal, not a technical bug.
• Discovered – currently not indexed: crawl budget or server response issues, common on large sites.
• Excluded by noindex tag: verify each one is intentional.
• Alternate page with proper canonical tag: fine if deliberate, a problem if your money pages are in here.

Then compare three numbers: URLs in your sitemap, URLs found in your crawl, and URLs indexed in GSC. Large gaps between these three are the single fastest way to find a structural problem.

4. Audit your robots.txt file

Visit yourdomain.com/robots.txt and read it line by line. Check that:

• No Disallow: / rule is blocking the whole site (it happens more often than you would think after a staging push).
• CSS and JavaScript directories are not blocked. Google needs them to render pages.
• Your XML sitemap URL is declared at the bottom of the file.
• Admin, cart, internal search and faceted URLs are blocked where appropriate.

Remember: robots.txt controls crawling, not indexing. A blocked URL can still appear in results without a snippet. To remove a page from the index, use a noindex tag and let it be crawled.

5. Validate your XML sitemap

A clean sitemap contains only canonical, indexable, 200-status URLs. Run the sitemap through your crawler in list mode and remove:

• Redirected URLs (3xx)
• Broken URLs (4xx and 5xx)
• Noindexed pages
• Non-canonical duplicates
• Parameter and filter URLs

Split sitemaps by content type (products, blog, categories). When Search Console reports coverage per sitemap, segmentation tells you instantly which template has the problem.

6. Fix status codes and broken links

In your crawl results, filter by response code:

Code	What it means	Action
200	Page loads normally	Nothing
301	Permanent redirect	Fine, but update internal links to point to the destination
302	Temporary redirect	Switch to 301 if the move is permanent
404	Not found	Redirect if it has backlinks or traffic, otherwise leave it and remove internal links
5xx	Server error	Highest priority, escalate to hosting or dev immediately

Pay special attention to broken links inside your main navigation and footer. They appear on every page and burn crawl budget site wide.

7. Clean up redirect chains and loops

Redirect chains slow down crawling and dilute signals. In Screaming Frog use Reports > Redirects > Redirect Chains to export every hop.

• Aim for one hop maximum from old URL to final destination.
• Fix any redirect loop immediately. Those pages are completely inaccessible.
• Check that http redirects to https and that one hostname version (www or non-www) redirects to the other. Test all four variants by typing them into a browser.
• Never redirect mass 404s to the homepage. Google treats that as a soft 404. Map them to the closest relevant page instead.

8. Review canonical tags and duplicate content

Every indexable page should have a self-referencing canonical tag unless you deliberately want it consolidated elsewhere. In your crawl, check the Canonicals tab for:

• Pages with missing canonicals
• Pages with multiple conflicting canonicals
• Canonicals pointing to redirects or 404s
• Canonicals using relative or http URLs on an https site

Then hunt duplicates: identical title tags, identical H1s, and near-identical content across paginated pages, tag archives, printer versions or URL parameters such as ?sort= and ?utm_.

9. Verify meta robots and noindex directives

This is where accidental traffic loss hides. Export every URL carrying a noindex or nofollow directive and confirm each one is intentional. Classic mistakes:

• A staging-wide noindex that survived the launch
• Category pages noindexed by a plugin default setting
• An entire blog section set to noindex by a template variable

Also check the HTTP headers for X-Robots-Tag. It is invisible in the page source and blocks indexing just as effectively.

10. Assess site architecture and internal linking

Use your crawler’s Site Structure view to check crawl depth, the number of clicks from the homepage to any page.

• Important pages should sit within three clicks of the homepage.
• Find orphan pages (in the sitemap or analytics but with zero internal links) and link to them from relevant content.
• Check for pages with only one internal link. Those signal low priority to crawlers.
• Make sure navigation links are real <a href> elements, not JavaScript click handlers.

Strong internal linking also multiplies the value of external links you earn. If you are actively building authority through backlink campaigns, poor internal structure means that authority stops at the landing page instead of flowing through the site.

11. Measure Core Web Vitals and page speed

Open Search Console > Core Web Vitals for field data (real users), then run PageSpeed Insights on one URL per template: homepage, category, product, article.

Metric	Good threshold	Most common cause of failure
LCP (Largest Contentful Paint)	Under 2.5s	Oversized hero images, slow server response, render-blocking CSS
INP (Interaction to Next Paint)	Under 200ms	Heavy third-party scripts, chat widgets, tag managers
CLS (Cumulative Layout Shift)	Under 0.1	Images without width and height, injected banners, web fonts
TTFB (Time to First Byte)	Under 800ms	Cheap hosting, no caching, uncached database queries

The three quickest wins on almost every site: compress and convert images to WebP or AVIF, enable server-side caching and a CDN, and defer non-critical third-party scripts. Those three usually move LCP more than any code refactor.

12. Test mobile usability properly

Google indexes the mobile version of your site, so the mobile rendering is the version that counts. Open Chrome DevTools, switch to device mode, and check:

• Text is readable without zooming (16px body minimum)
• Tap targets are at least 48px and well spaced
• No horizontal scrolling on a 375px viewport
• The viewport meta tag is present
• Mobile and desktop serve the same content, the same headings, the same internal links and the same structured data

That last point is the one people miss. Hiding content behind mobile accordions is fine. Removing it from the mobile HTML entirely is not.

13. Validate your structured data

Structured data will not rank you higher on its own, but it wins rich results, which win clicks. Run key templates through the Rich Results Test and the Schema Markup Validator, then check Search Console > Enhancements for site-wide errors.

Priority schema by site type:

• Ecommerce: Product, Offer, AggregateRating, BreadcrumbList
• Blog or media: Article, Author, Organization, BreadcrumbList
• Local business: LocalBusiness, opening hours, geo data
• Service sites: Organization, Service, FAQPage where genuinely relevant

Two rules: use JSON-LD, and never mark up content that is not visible on the page. Mismatches lead to manual actions. For the wider picture, see Ultimate SEO Audit Checklist to Use in 2026.

14. Check HTTPS, security and rendering

Final sweep:

• SSL certificate valid and not expiring within the next 30 days
• No mixed content (https pages loading http images, scripts or stylesheets)
• HSTS header enabled
• Use the URL Inspection tool in GSC on three important pages and view the rendered HTML. If your main content is missing there, Google is not seeing it either
• Confirm no unwanted hreflang errors if you run multiple languages, and that every hreflang tag is reciprocal

How to Prioritize Fixes Before Touching Any Code

You will finish the audit with a list of 40 to 100 issues. Do not send all of them to your developer. Score each issue on two axes: impact on traffic and effort to fix.

Priority	Issue type	Typical timeline
P1 Critical	Site-wide noindex, robots.txt blocking, 5xx errors, redirect loops, expired SSL	Same day
P2 High	Broken internal links on money pages, canonical conflicts, dirty sitemap, failing LCP on top templates	Within 2 weeks
P3 Medium	Redirect chains, orphan pages, crawl depth over 4, missing schema	Within 1 to 2 months
P4 Low	Minor CLS on low-traffic pages, image alt text gaps, cosmetic markup warnings	Backlog

Two shortcuts that keep you honest:

1. Weight by traffic, not by count. One broken canonical on a page with 8,000 monthly visits beats 300 warnings on pages nobody visits.
2. Group by template, not by URL. If 1,200 product pages share one bug, that is one ticket, not 1,200. Developers fix templates.

Your Afternoon Schedule

Time	What you do
0:00 to 0:20	Steps 1 and 2: access checks, launch the crawl
0:20 to 1:10	Steps 3 to 5: indexation, robots.txt, sitemap (while the crawl runs)
1:10 to 2:20	Steps 6 to 10: status codes, redirects, canonicals, meta robots, architecture
2:20 to 3:20	Steps 11 to 14: speed, mobile, schema, HTTPS and rendering
3:20 to 4:00	Build the prioritized fix list and write the dev ticket

Five Mistakes Beginners Make

• Chasing a 100 Lighthouse score. Field data in Search Console is what Google uses. Lab scores are diagnostics, not targets.
• Redirecting every 404 to the homepage. It creates soft 404s and confuses users.
• Auditing once and never again. Run a light version monthly and the full checklist quarterly, plus always after a migration or redesign.
• Fixing technical issues on thin content. A fast, crawlable, schema-rich page with nothing to say still will not rank.
• Skipping the before and after snapshot. Without baseline numbers you cannot prove the work paid off.

After the Audit: What Comes Next

Technical SEO clears the road. It rarely creates demand on its own. Once your site crawls cleanly, indexes correctly and loads fast, the growth levers become content depth and off-page authority. A technically flawless site with no external links will still lose to a slightly messier competitor with a stronger link profile.

The efficient sequence is: fix the technical blockers first, then publish content that deserves to rank, then build links to it. Doing the last step before the first two simply sends authority into a leaky bucket.

FAQ

How long does a technical SEO audit take?

A small site of up to 500 URLs takes around three to four hours with this checklist. A mid-size site of 5,000 to 50,000 URLs usually takes one to two days, mainly because crawls and log analysis take longer. Enterprise sites need a week or more and segmented crawling.

How often should I run a technical SEO audit?

Run the full 14-point checklist quarterly. Between audits, check Search Console indexing and Core Web Vitals reports monthly. Always run a complete audit immediately before and after a site migration, redesign or CMS change.

Can I do a technical SEO audit for free?

Yes. Google Search Console, Bing Webmaster Tools, PageSpeed Insights, Chrome DevTools, the Rich Results Test and the free tier of Screaming Frog cover every item on this list. Paid tools mainly add scale, scheduling and automated monitoring.

What is the single most important technical SEO check?

Indexation. If your pages are not in the index, nothing else matters. Start with the Search Console Pages report and compare indexed URLs against the URLs you actually want ranking.

Do I need to know how to code?

No. Diagnosing issues requires reading, not writing, code. You need to recognize a canonical tag, a meta robots directive and a status code. Implementation can be handed to a developer, and on WordPress many fixes are plugin settings.

Does technical SEO matter for AI search and AI Overviews?

Yes, and increasingly so. AI systems rely on crawled and indexed content. Clean server-side HTML, fast responses, logical internal linking and accurate structured data make your content easier to parse and cite, whether the consumer is a traditional search engine or an AI assistant.

Should I fix everything my audit tool flags?

No. Tools flag issues without business context. Sort by traffic and revenue impact, group by template, fix the P1 and P2 items, and leave cosmetic warnings in the backlog. Chasing a green score in an audit tool is not the same as growing organic traffic.