Templates
Technical SEO checklist template, ten parts to tick off
Short answer
A technical SEO checklist is a list of checks on the technology behind your website. That way you know for sure that Google can find, read and include every important page. It goes one layer deeper than the general SEO checklist and covers ten parts, from crawling and indexing to status codes and structured data. Print it or put it in a file of your own.
The technical SEO checklist to tick off
Get three things ready, namely Search Console, access to your robots.txt and a crawler that goes through your whole site. Tick off what is right and fill in the orange parts with what you find.
Technical SEO checklist for [your website address]
Checked by [name], crawl run on [date].
1. Crawling
- Have a crawler go through your whole site. Found [number] addresses, of which [number] with status 200.
- Is every important page within three clicks of the homepage? Buried deeper [pages].
- Are all internal links ordinary anchor (a) elements with an href? Exceptions in [menu, footer or filter].
- Do filters, sorting or search parameters create endless series of addresses? Parameters [parameters].
2. Indexing
- Read in Search Console why addresses stay out of the index. Main reason [reason], for [number] addresses.
- Is noindex only on pages that may stay out of Google? With noindex [pages].
- Does URL Inspection show the full text in the rendered HTML for your three busiest pages? Checked on [date].
3. robots.txt
- Does robots.txt load with status 200? Status [code].
- Does robots.txt allow the CSS, JavaScript and images Google needs to build a page? Blocked [files].
- Is a page listed in robots.txt that needs to come out of the index? Remove the rule and put noindex on that page. Adjusted [pages].
- Does a Sitemap line in robots.txt point the way to your XML sitemap?
4. XML sitemap
- Does the sitemap contain only canonical addresses with status 200? Exceptions [number].
- Does each sitemap file stay under 50,000 addresses and 50 MB? Files [number].
- Does the lastmod date match the last real change to the page?
5. Canonicals
- Does every indexable page have a canonical with an absolute URL? Missing on [number] pages.
- Does every canonical point to a page with status 200 that is itself indexable? Wrong on [pages].
- Do the canonical, internal links and sitemap name the same address as the main version? Conflicting on [pages].
6. Status codes and redirects
- Does every moved page get a permanent redirect, 301 or 308? Temporary (302 or 307) on [number].
- Does every redirect reach the final address in one step? Chains [number], longest chain [number] steps.
- Does a deleted page really return status 404 or 410, instead of 200 with an error message? Soft 404 on [number].
- How many server errors (5xx) does the Crawl stats report show? Number [number] in [period].
7. HTTPS and domain
- Does an http address go to https in one step via a 301? Tested on [address].
- Do all images, scripts and fonts load via https? Still via http [files].
- Choose one main form of your domain, with www or as a bare domain. Does the other form redirect? Main form [address].
- Does the certificate renew automatically? Valid until [date].
8. Mobile
- Do the mobile and desktop versions have the same structured data and the same robots tags?
- Does important text only appear after a click, tap or swipe? Put that text directly in the HTML. Found on [pages].
- Does a pop-up on mobile cover the main content on arrival? On [pages].
9. Speed
- Do images and embedded videos have a fixed width and height, so the layout stays in place?
- Do images load in a light format such as WebP or AVIF? Heaviest image [kB] on [page].
- How long does the browser wait for the first response from the server? Measured [milliseconds].
- Which third-party scripts load on every page? Number [number], to remove [scripts].
10. Structured data
- Is your structured data in JSON-LD? Types [for example Organization or Product].
- Does the markup describe only what a visitor can also see on the page?
- Does the Rich Results Test show 0 errors? Errors [number], tested on [date].
- Are there messages under Enhancements in Search Console? Open messages [number].
Fix plan, first [point], then [point], to be carried out by [developer or own team].
How to work through the technical checklist
Technical issues are connected. An error at the top of the list can hide an error further down, which is why you stick to this order.
Start with the crawl and the crawl stats
A crawler shows what Google comes across when it follows your links. The Crawl stats report shows per status code and file type how often Google visited your site. According to Search Console Help, that report is meant for advanced users and you rarely need it with fewer than 1,000 pages.
Remove blocks before you go further
A noindex only works if Google is allowed to crawl the page. If robots.txt blocks the address, the crawler never sees the noindex, according to Google's documentation on noindex. So choose one signal per page and use robots.txt only for crawling.
Set the main version for each page
Google weighs several signals when it chooses a main version. A redirect and a canonical count as strong signals and a listing in the sitemap as a weak signal, according to Google's explanation of duplicate URLs. So make all three name the same address.
Clean up chains and error codes
By default, Googlebot follows up to 10 redirects in a row. The page on status codes says addresses with a 4xx code stay out of the index. Server errors and code 429 make Google crawl more slowly for a while, so fix those first.
Test the structured data last
Markup builds on a page that already loads well. Google's structured data guidelines ask you to describe only what visitors see on the page. Even with an error-free test, Google decides for itself whether to show a rich result.
Do it yourself or hand it over?
You can go through a large part of the list yourself. For the fixes you often need access to the code or the server.
Do it yourself
Read the sitemap and robots.txt, run URL Inspection, use the Rich Results Test and keep track of the messages in Search Console. Set aside a fixed hour for this every month.
With a developer
Redirect chains, server errors, mixed content and canonicals in your site's templates call for work in the code. Give your developer this list with the orange parts filled in, so they know exactly where to look.
Frequently asked questions about the technical SEO checklist
What is the difference from the regular SEO checklist?
The SEO checklist goes through your whole website in five parts, from technical to measuring. This technical list covers only the technical side and goes one layer deeper per part. Start with the general list and add this one as soon as a technical point stays open.
Does technical SEO also matter for a small website?
Yes. A block in robots.txt or a forgotten noindex hits a 20-page site just as hard. As Google explains, crawl budget mainly matters for sites with more than a million pages, or more than 10,000 pages that change daily.
How big can an XML sitemap be?
A single sitemap file holds at most 50,000 addresses or 50 MB uncompressed, Google writes in its sitemaps guide. If your site is bigger, split the sitemap. Google ignores the priority and changefreq values.
Can Google follow links in JavaScript?
Google generally only crawls a link if it is an anchor (a) element with an href, according to its guidelines for links. The crawler often skips a button with a click function or a span with an address.
Do I need a paid crawler?
For a small site, a free version or URL Inspection in Search Console is enough. With hundreds of pages, a crawler saves you a lot of time, because it puts all status codes, canonicals and redirects in one list.
Have the technology behind your site fixed
Next step
Still have points open after ticking everything off that are hard to solve yourself? With technical SEO, our team finds the cause, fixes the errors and then measures whether Google reads your pages properly. Dominic keeps you up to date. Want a full picture of your site first? Then read about the SEO audit.
HOW TECHNICAL SEO WORKS


