TECHNICAL SEO CHECKLIST
Technical SEO checklist: crawl, index, render, load
A technical SEO checklist verifies the plumbing that lets search engines crawl, render and index your pages: robots.txt, status codes, noindex tags, canonicals, redirects, sitemaps, mobile parity, Core Web Vitals and structured data. Fix crawl and index blockers first. Digimetrics Technical SEO Crawler checks these across your pages in 30 seconds to 2.5 minutes.
- Free for 7 days
- Every tool unlocked
- No card needed
Updated 23 October 2026 · Digimetrics editorial team
The short answer
- Technical SEO is everything between your server and Google's index: access, status codes, duplicates, rendering and speed.
- robots.txt controls crawling, not indexing; to keep a page out of Google, use noindex and leave the page crawlable.
- Google indexes the mobile version of your pages, so content missing on mobile is content missing from Google.
- Core Web Vitals pass at LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less.
- A sitemap file is limited to 50,000 URLs or 50MB uncompressed; split larger sites with a sitemap index.
What is technical SEO?
Technical SEO is the work that makes a site crawlable, renderable and indexable, so the content you write is eligible to rank. It does not make weak content rank; it removes the reasons strong content cannot.
Think of it as three questions Google asks about every URL. Can I fetch it? (robots.txt, server status, login walls). Can I understand it? (rendering, JavaScript, mobile content, structured data). Should I index this version? (noindex, canonicals, duplicates, redirects). Speed and page experience sit on top: they affect how people experience the page once it is found.
That is also what is included in technical SEO and what is not. Keyword choice, copywriting and link building are separate disciplines covered in our guides to keyword research and on-page SEO. If you want the broad audit that ties all of them together, start with the SEO audit checklist.
The full technical SEO checklist
Here is the website technical SEO checklist grouped by layer, with the pass condition taken from Google's documentation and the tool that checks each item.
Use it as a technical SEO checklist template: add owner and date columns and re-run it after every release that touches templates, navigation or hosting.
| Layer | Check | Pass condition | How to check |
|---|---|---|---|
| Crawl | robots.txt allows important sections | No Disallow on pages you want found, CSS and JS not blocked | Technical SEO Crawler |
| Crawl | Pages return HTTP 200 | Linked pages do not return 404 or server errors | Technical SEO Crawler |
| Crawl | Internal links are crawlable | Every key page is reachable through links | Google Crawler Simulator |
| Index | noindex only where intended | Key pages carry no noindex tag or X-Robots-Tag header | Technical SEO Crawler, URL Inspection |
| Index | One canonical URL per piece of content | HTTP and HTTPS, www and non-www resolve to one version | Technical SEO Crawler |
| Index | Permanent moves use permanent redirects | 301 or 308 for moved pages, no long chains | Technical SEO Crawler |
| Index | No soft 404s | Missing pages return a real 404 status | Search Console Page indexing report |
| Index | XML sitemap is clean | Only canonical, indexable URLs; under 50,000 URLs or 50MB per file | Search Console Sitemaps report |
| Render | Mobile content equals desktop content | Same text, headings, links and robots meta tags | Google Crawler Simulator |
| Render | Primary content does not need a click to load | Text present without swiping, clicking or typing | Google Crawler Simulator |
| Speed | LCP | Within 2.5 seconds | Page Speed Check |
| Speed | INP | 200 milliseconds or less | Page Speed Check |
| Speed | CLS | 0.1 or less | Page Speed Check |
| Enhance | Structured data valid and matches visible content | No errors in the Rich Results Test | Schema Generator |
| Enhance | HTTPS everywhere | Valid certificate, no mixed content | Page Technical & Domain Analysis |
Crawling vs indexing: the mistake that hides pages
robots.txt decides whether Google may crawl a URL; noindex decides whether Google may index it. Blocking a page in robots.txt can stop Google from ever seeing its noindex tag.
Google's documentation is explicit on both points. A robots.txt file is mainly for managing crawler traffic and is not a mechanism for keeping a page out of Google: a disallowed URL can still be indexed if other sites link to it, just without a description. And for noindex to work, the page must not be blocked by robots.txt, because the crawler has to fetch the page to see the rule. Google also does not support noindex inside robots.txt.
The practical rule: to hide a page, allow crawling and add noindex. To save crawl effort on unimportant URLs, use robots.txt. Never do both on the same URL. For large sites, our glossary entry on crawl budget explains when crawl efficiency starts to matter.
| Goal | Use | Do not use |
|---|---|---|
| Keep a page out of Google results | noindex meta tag or X-Robots-Tag header, page left crawlable | robots.txt Disallow alone |
| Stop crawlers wasting requests on filters or search pages | robots.txt Disallow | noindex (Google still has to crawl to see it) |
| Merge duplicate URLs | 301 redirect, or rel=canonical if you cannot redirect | noindex on the duplicates |
| Move a page permanently | 301 or 308 redirect | 302, which tells Google the move is temporary |
How to fix technical SEO issues, in the right order
Fix issues that stop indexing first, then issues that affect every page through a shared template, then one-off page issues. A crawler that marks severity does this sorting for you.
Most technical problems live in templates, so one fix often repairs hundreds of URLs. When the crawl shows the same issue on many pages, find the template rather than editing pages one by one.
In the official tutorial's sample (fictional brand Brightpath), the Technical SEO Crawler checked 10 pages and the first fix was missing meta descriptions on 6 of 10 pages: one template change. The Page Speed Check sample scored 68, and its top fix, serving images in modern formats, saved about 420 KB. Both examples show the pattern: one change, many pages.
- High severity first: noindex on key pages, blocked resources, server errors, redirect loops.
- Template issues next: missing titles or descriptions, slow shared scripts, layout shift from ads or banners.
- Page issues last: a single broken link, one oversized image, one orphan page.
- Re-crawl after each batch so you can confirm the issue count fell.
Advanced technical SEO checks for larger sites
Once the basics pass, larger sites should check JavaScript rendering, faceted navigation, crawl efficiency, international versions and site moves.
These items rarely matter on a 20-page site and often matter a lot on a store or publisher with thousands of URLs. Google notes that how you organise content in directories can affect crawling on sites with more than a few thousand URLs, because it can learn how often each directory changes.
- JavaScript: Google can process JavaScript content that is not blocked, but confirm key text appears in the rendered HTML.
- Lazy loading: content that only loads after a user interaction will not be seen by Google.
- Faceted navigation: sorting and filtering can create many near-duplicate URLs; canonicalise or block the low-value ones.
- Site moves: map every old URL to its new home with permanent redirects before launch.
- AI crawlers: decide whether GPTBot and similar bots may crawl; our guide on AI crawlers covers the trade-off.
What tools help with a technical SEO checklist?
Google Search Console is the free source of truth for indexing. Add a crawler for site-wide issues, a speed test for Core Web Vitals and a renderer to see what Googlebot reads.
Digimetrics covers each layer with a dedicated tool, all included in the 7-day free trial:
| Job | Digimetrics tool | Time |
|---|---|---|
| Crawl pages for issues and severity | Technical SEO Crawler | 30 seconds to 2.5 minutes |
| Core Web Vitals and speed fixes | Page Speed Check | 10 seconds to a minute |
| Whole-site health score and fix list | Full Site Audit (SEO + AI) | 1 to 3.5 minutes |
| Valid JSON-LD structured data | Schema Generator | a few seconds |
| Indexing and search data | Search Console | loads on its own |
HOW IT WORKS
How to check technical SEO in five passes
- 1
Pass 1: access
Confirm robots.txt allows the sections you want found and that key pages return HTTP 200. Use Search Console's URL Inspection tool on your homepage.
- 2
Pass 2: indexing signals
Crawl the site with the Technical SEO Crawler and list every noindex tag, canonical tag and redirect chain.
- 3
Pass 3: rendering
Check what Google actually reads on the page, including JavaScript-loaded content, with the Google Crawler Simulator.
- 4
Pass 4: speed
Test one page per template on mobile with the page speed test and fix the slowest template first.
- 5
Pass 5: enhancements
Validate structured data, confirm HTTPS and review the sitemap in Search Console. Re-crawl to confirm every fix.
QUESTIONS PEOPLE ASK
Frequently asked questions
Still unsure? Email support@digimetrics.ai and a person will reply.
What is included in a basic technical SEO checklist?
At minimum: robots.txt access, HTTP 200 status on key pages, no accidental noindex, one canonical URL per page, permanent redirects for moved pages, a clean XML sitemap, mobile content parity, passing Core Web Vitals and valid structured data.
How do I learn technical SEO?
Start with Google's own documentation: Search Essentials, the SEO Starter Guide and the crawling and indexing guides. Then crawl a real site, read the issue list and look up each issue type. Fixing a live site teaches faster than reading.
How often should I run a technical SEO audit?
After every redesign, migration, CMS change or template release, and monthly in between. The Technical SEO Crawler and Full Site Audit can be scheduled so problems surface before traffic drops.
Do Core Web Vitals affect rankings?
Yes, Google says Core Web Vitals are used by its ranking systems, but there is no single page experience signal and good scores do not put a page at the top on their own. Fix them once indexing issues are solved, and do not chase a perfect score purely for SEO.
Is schema markup technical SEO?
Yes, it sits in the enhancement layer. It helps Google understand the page and makes it eligible for rich results, but it does not fix crawling or indexing problems. See our schema markup guide.
Should I hire a technical SEO agency?
For a site move, a large JavaScript application or a store with thousands of URLs, specialist help can pay for itself. For a small business site, a crawler plus this checklist usually covers it; ask any agency which of the checks above they run and how they prioritise.
Find the technical issues holding your pages back.
Crawl your site, see every issue ranked by severity, and fix the template behind it. Free for 7 days, no credit card.