A technical SEO audit checklist is a fixed list of checks that confirm search engines can crawl, render, index, and rank your site, separate from content or link quality. This checklist covers 62 checks across ten areas: crawlability, indexation, JavaScript rendering, Core Web Vitals, structured data, site architecture, XML sitemaps and robots.txt, international SEO, log files, and mobile. Work through it in order, because each layer depends on the one before it.
If you want the full-site version that also covers content and off-page authority, our SEO audit checklist walks through all six areas of a complete audit. If you would rather hand this off, our technical SEO audit service breaks down what a paid audit delivers and what it costs.
A technical SEO audit checklist is a structured list of checks limited to the machine-facing side of a website: whether search engines can crawl it, render its content, index it, and treat it as fast and trustworthy enough to rank. Google's own developer documentation treats crawling and indexing as prerequisites, not ranking bonuses, so every item on this list protects that foundation. It deliberately excludes content quality, keyword targeting, and backlinks, which belong to a broader SEO audit instead.
A general SEO audit usually gives technical health a single section with ten or so items, which is fine for a quick health check but too shallow once a site has any real scale, a recent migration, or a JavaScript framework. This checklist exists for that gap: developers, in-house SEOs, and agencies who need to go deep on crawling, rendering, and indexing without wading through content and backlink checks that do not apply to the problem in front of them.
Work top to bottom, because the order matches dependency, not importance. A page cannot be indexed if it cannot be crawled, and it cannot rank on speed or schema if it is not indexed in the first place. Record every failed check before fixing anything, then use the prioritization framework near the end to decide what to fix first.
| Tool | What it tells you | Cost |
|---|---|---|
| Google Search Console | Indexing status, Core Web Vitals field data, crawl stats | Free |
| Screaming Frog or Sitebulb | Site-wide crawl: redirects, status codes, duplicate tags | Freemium (free up to 500 URLs) |
| Chrome DevTools + Rich Results Test | What actually renders, plus schema validation | Free |
| PageSpeed Insights / CrUX | Lab and real-user Core Web Vitals data | Free |
| Screaming Frog Log File Analyzer or JetOctopus | What Googlebot actually crawled, from raw server logs | Freemium / paid |
| Ahrefs or Semrush Site Audit | Large-scale crawling with historical tracking | Subscription |
If Googlebot cannot reach a page, nothing else on this list matters, so start here every time.
Google's own documentation frames crawl budget as capacity plus demand: how many connections your server can handle, and how much Google wants to crawl based on a page's popularity and how often it changes. That framing matters most on large sites, which is why crawl budget checks belong on every enterprise technical audit even when they can be skipped on a 50-page brochure site.
Indexation checks decide which of your crawlable pages are actually eligible to show up in search results at all.
site:yourdomain.com search shows your key pages are indexed.noindex tag.Google typically indexes a page in two passes: it reads the raw HTML first, then queues a second render pass once resources are available to execute the JavaScript, according to Google's own Search Central documentation on how rendering works. A page can look complete in a browser and still be missing content, links, or schema in what Google actually indexed, which is why rendering gets its own section instead of hiding inside "technical health."
<a href> tags Google can follow, not JavaScript-only onclick handlers.Google, through its web.dev developer resource, defines a "good" page as one where Largest Contentful Paint happens in 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift stays at 0.1 or less, all measured at the 75th percentile of real visits.
Schema does not write your rankings for you, but it is one of the highest-leverage technical fixes because it is fast to ship and immediately testable.
Ahrefs analyzed hreflang tags across 374,756 domains and found that 67% of them contain at least one error, most often a missing x-default tag or a missing reciprocal (return) link between language pairs. Hreflang fails quietly: Google simply ignores the broken signal and falls back to its own judgment about which version to show, so a site can carry the tags for years without anyone noticing they never worked.
Log file analysis reads your server's raw request logs to see exactly what Googlebot crawled, when, how often, and what response code it received, which is ground truth that Search Console's sampled reports do not fully show. It earns its place mainly on large sites, thousands of URLs or more, where crawl budget is a real constraint; a small brochure site rarely needs it.
A full pass once or twice a year is enough for most sites, paired with a lighter monthly glance at Search Console's crawl stats and Core Web Vitals reports. Run an unscheduled audit immediately after any migration, replatform, or major redesign, since those events are the single most common cause of new crawl blocks, broken redirects, and lost indexation.
A raw list of 62 checks is only useful once it is sorted by what actually blocks rankings versus what merely helps at the margins.
| Priority | What it covers | Examples |
|---|---|---|
| P0: fix immediately | Anything blocking crawling or indexing outright | Stray noindex tags, robots.txt blocking key paths, broken canonical chains |
| P1: fix this quarter | Rendering, speed, and schema issues that cap competitiveness | Failing Core Web Vitals, JS-only content, invalid or missing schema |
| P2: plan and monitor | Slower, compounding structural work | Hreflang cleanup, site architecture, crawl budget on large sites |
Clear the P0 column before touching anything else, since fixing schema or Core Web Vitals on a page Google cannot index wastes the effort. Once the P0 list is empty, P1 items usually deliver the fastest visible movement, while P2 work compounds over months rather than weeks.
Clean technical fundamentals are also what let AI answer engines cite a page with confidence, since a crawlable, well-structured page is easier for both Google and language models to verify. We saw this directly with LiveHelpNow, where technical and content work together added roughly 3,000 organic visits a month and got the site cited in AI Overviews, a result that depends on Google being able to crawl, render, and understand the page cleanly in the first place. You can read the full breakdown in our case studies.
What is a technical SEO audit checklist? It is a fixed, ordered list of checks limited to the parts of a website that decide whether search engines can crawl, render, index, and rank it: crawlability, indexation, JavaScript rendering, Core Web Vitals, structured data, site architecture, sitemaps, robots.txt, international SEO, and log files. It leaves out content quality, keyword research, and backlinks, which belong to a full SEO audit instead.
What is the difference between a technical SEO audit checklist and a full SEO audit checklist? A technical checklist only covers the machine-facing layer: crawling, rendering, indexing, speed, and structured data. A full SEO audit adds content quality, on-page optimization, keyword intent, and backlinks on top of that. Our broader SEO audit checklist walks through both layers if you need the complete picture.
How many checks should a technical SEO audit include? This checklist runs 62 checks across ten areas, which is enough depth for most small and mid-sized sites. Enterprise sites with millions of URLs often expand it further, especially around log file analysis and international SEO, where a single missed hreflang pair can affect thousands of pages at once.
Do I need to check log files for a technical SEO audit? Small sites usually do not need it, since Search Console's crawl stats are close enough to reality. Sites with thousands of URLs, a history of crawl budget problems, or a recent migration benefit most, because log files are the only source that shows exactly what Googlebot requested and when, rather than a sampled summary.
How do I know if Google can render my JavaScript? Run the page through Search Console's URL Inspection tool, then compare the rendered HTML it shows against your raw server response. If key content, links, or schema only appear in the rendered version, they still count, but if they are missing from both, Googlebot never saw them at all.
What is the most common technical SEO mistake? A stray noindex tag or an overly broad robots.txt disallow rule left over from a staging environment or migration, which can silently deindex an entire section of a site. It rarely announces itself, which is exactly why crawling and indexing come first on every audit checklist.
How often should you run a technical SEO audit? Once or twice a year covers most sites, with a lighter monthly check of Search Console for new crawl errors or indexing drops. Run an extra pass immediately after any migration, redesign, or CMS change, since those are the moments most likely to introduce crawl blocks or broken redirects.
Can I run a technical SEO audit without paid tools? Yes, for small sites. Google Search Console, Chrome DevTools, the Rich Results Test, and PageSpeed Insights are free and cover most of this checklist. Paid crawlers like Screaming Frog, free up to 500 URLs, or Ahrefs become worth it once a site grows past a few hundred pages or needs ongoing tracking.
What is crawl budget and does it matter for small sites? Crawl budget is the combination of how much Google's servers are willing to fetch from your site, its crawl capacity, and how much Google wants to, based on popularity and how often content changes. Google's own documentation notes that crawl budget is mainly a concern for sites with millions of URLs, so a small site with a few hundred pages rarely needs to worry about it.
Does structured data affect rankings? Google states that structured data does not directly move rankings on its own, but it does make pages eligible for rich results like star ratings, FAQ snippets, and how-to steps, which can lift click-through rate. It also helps Google and AI systems understand what a page is about, which supports rankings indirectly.
Work through all ten sections, sort your findings into the P0, P1, and P2 buckets above, and clear the P0 column first. If your site is complex enough that this checklist raises more questions than it answers, our technical SEO company page explains what ongoing technical support looks like, or you can book a free technical SEO audit call and we will walk through your crawl, index, and speed issues together.
Get a free, no-obligation SEO audit and a 30-minute strategy session. We'll show you exactly where the growth is hiding.
Fill out the form and we'll get back to you within one business day. Prefer email? Write to us directly at contact@rankite.com.