About the Technical SEO Checklist
Technical SEO decides whether search engines can reach, render and index your pages at all. This technical SEO checklist groups the essential checks into crawling, indexing controls, site architecture, redirects and HTTPS, and sitemaps with performance. Every item explains the risk in plain language and gives a concrete way to verify it, usually with one of our free crawlers or checkers.
Work top to bottom on a new audit: crawl and indexing problems can hide every other improvement, so fix those first. Then tidy redirects and internal links, and finish with Core Web Vitals and rendering. Your ticks are saved in your browser, so you can audit over several sessions and export the finished list as Markdown for a developer ticket or client report.
How to use it
- Open the checklist and start with the Crawling & robots.txt section.
- Use the linked tool on each item to check your site, then tick it off.
- Note failures and assign fixes to the developer or content owner.
- Export the list as Markdown or print it for your audit report.
Frequently asked questions
What is included in a technical SEO checklist?
A technical SEO checklist covers how search engines crawl and index a site: robots.txt rules, noindex and canonical tags, HTTP status codes, redirects, HTTPS, XML sitemaps, internal linking and crawl depth, JavaScript rendering, mobile signals and Core Web Vitals. Content and keyword work usually sits in a separate on-page checklist.
How often should I run a technical SEO audit?
Run a full audit at least every quarter and after any major change such as a redesign, CMS update, migration or new template. Large or frequently changing sites benefit from a monthly crawl. Between audits, keep an eye on Search Console's Page indexing and Crawl stats reports for sudden changes.
Does Google still use priority and changefreq in sitemaps?
No. Google ignores priority and changefreq values in XML sitemaps. It does use lastmod when the dates are consistently accurate, so update lastmod only when the main content of a page changes. Keep sitemaps limited to canonical, indexable URLs that return a 200 status.