Free Technical SEO Checklist Template [2026]
A 160-point technical SEO checklist covering crawlability, indexation, site architecture, Core Web Vitals, mobile rendering, and structured data. Every checkpoint tells you how to verify it, so you are auditing against evidence rather than memory.
Download Free Template
Get instant access - no signup required
8-tab Excel workbook with 160 checkpoints, priority levels, and status dropdowns
Free to use. No signup required. Attribution appreciated but not required.
What's Included
8 organized worksheets
📋 Instructions Tab: How to run the checklist and what order to work in
🌐 Site Setup Tab: Stack, tooling, access, and explicit audit scope
🔍 Crawlability & Indexation Tab: robots.txt, sitemaps, canonicals, status codes, crawl budget, HTTPS
🏛️ Architecture & URLs Tab: Click depth, orphan pages, internal links, URL patterns, redirects, duplication
⚡ Speed & Core Web Vitals Tab: LCP, INP, CLS with the render-blocking causes behind each
📱 Mobile & Rendering Tab: Mobile-first parity, JavaScript rendering, viewport, images
🧩 Structured Data & Intl Tab: Schema coverage, validation, hreflang reciprocity
🚦 Priority Fix List Tab: Every failure ranked by impact and effort, with owner and target date
Use Cases
How SEO professionals use this template
Key Features
Template Preview
Excel Worksheet Tabs (8 Tabs Total)
🔍 Crawlability
Robots, sitemaps, canonicals, status codes
This is a preview. Download the full template for every row across all 8 tabs.
📊 Template by PikaSEO.com
How to Use This Template
Crawl the site first
Run Screaming Frog, Sitebulb, or our free Technical SEO Audit tool before you open the checklist. Every checkpoint has a 'How to Check' column that assumes you have crawl data in front of you.
Set the scope
Use the Site Setup tab to record the stack, your tooling, and which areas are in scope. Marking log file analysis or international SEO as Phase 2 up front prevents scope arguments later.
Work top to bottom, not by interest
The tabs are ordered by impact. Indexation problems outrank speed problems — finish Crawlability before you spend a sprint on Core Web Vitals.
Turn failures into a plan
Copy every Fail and Warning into the Priority Fix List, then sort by Impact descending and Effort ascending. That ordering is your sprint plan, and the Owner column is what makes it happen.
Frequently Asked Questions About the Technical SEO Checklist Template
What is a technical SEO checklist?
A technical SEO checklist is a structured list of the infrastructure-level checks that determine whether search engines can crawl, render, and index your site properly. It covers robots.txt and sitemaps, indexation, canonicalisation, site architecture, page speed and Core Web Vitals, mobile rendering, JavaScript execution, structured data, and international targeting. It deliberately excludes content quality and link building, which are separate disciplines with separate workflows.
How many checkpoints should a technical SEO audit cover?
This template contains 160 checkpoints spread across five dimensions: 29 for crawlability and indexation, 22 for architecture and URLs, 22 for speed and Core Web Vitals, 19 for mobile and rendering, and 18 for structured data and international, plus scope and fix-tracking rows. A small brochure site will legitimately mark many as N/A. A large e-commerce or multi-locale site will need all of them.
What order should I work through a technical SEO audit in?
Crawlability and indexation first, always. A page that is not indexed cannot benefit from any other fix, so a noindex tag on a money page outranks a 3.5-second LCP every time. After indexation, work through architecture, then speed, then mobile rendering, then structured data. The tabs in this template are ordered that way deliberately.
What are the current Core Web Vitals thresholds?
LCP (Largest Contentful Paint) should be 2.5 seconds or less, INP (Interaction to Next Paint) 200 milliseconds or less, and CLS (Cumulative Layout Shift) 0.1 or less. All three are judged at the 75th percentile of real user field data, not lab scores. Lab tools like Lighthouse tell you why a metric is bad; only field data from Search Console or CrUX tells you whether it is bad.
Why does my page rank when Lighthouse gives it a low score?
Because Lighthouse is a lab test run on a simulated device, and Google ranks on field data from real Chrome users. A page can score 45 in Lighthouse and still pass Core Web Vitals if actual visitors are on fast connections and modern devices. Use the Search Console Core Web Vitals report as the source of truth, and use Lighthouse only to diagnose the cause once field data says there is a problem.
How often should I run a technical SEO audit?
Run a full audit quarterly, and a focused re-run of the Crawlability tab after any migration, CMS upgrade, theme change, or major release. Technical regressions almost always arrive with a deployment rather than appearing spontaneously, so tying a short audit to your release cycle catches far more than a calendar reminder does.
What are the most common technical SEO mistakes this checklist catches?
The recurring ones are: lazy-loading the LCP hero image, which is the single most common speed mistake; canonical tags pointing at redirected or 404 URLs, which silently leaves pages uncanonicalised; a trimmed mobile navigation that removes internal links from indexing entirely under mobile-first indexing; non-reciprocal hreflang, which Google ignores completely; and staging environments that are noindexed but not password-protected.
Do I need Screaming Frog to use this checklist?
No, but you need some crawler. The 'How to Check' column names the tool for each checkpoint, and most can be done with free options: Google Search Console for indexation, coverage, and Core Web Vitals; PageSpeed Insights for speed diagnosis; the Rich Results Test for structured data; and our free Technical SEO Audit tool for a crawl. A paid crawler mainly saves time on large sites.
What is the difference between a technical SEO checklist and a full SEO audit?
A technical SEO checklist covers only infrastructure — whether search engines can access and understand your site. A full SEO audit adds content quality, keyword targeting, on-page optimisation, backlink profile, and competitive positioning. Most agencies run both: this checklist for the engineering-facing work, and a broader audit template for the strategy-facing findings.
How do I hand technical SEO fixes to a development team?
Use the Priority Fix List tab rather than sending the whole checklist. Developers need a ranked list with an owner, an effort estimate, and a definition of done — not 160 rows where 140 are passing. Sorting by Impact descending then Effort ascending produces a list that maps naturally onto sprint planning, and it makes the trade-offs visible when capacity is tight.
Should I fix every warning?
No, but you should date every warning. A checkpoint marked Warning is a decision you deferred, not a checkpoint you passed. Copy warnings into the Priority Fix List with a target date, then genuinely deprioritise the low-impact ones. What causes problems is warnings that quietly stay warnings across four consecutive audits.
Is this technical SEO checklist template really free?
Yes. The Excel file downloads immediately with no signup, no email capture, and no watermark. You can white-label it by deleting the PikaSEO branding row at the top of each tab, and agencies are welcome to use it with clients.