Technical SEO Checklist: The Checks That Actually Move Rankings

What is technical SEO?

Technical SEO is the work of making a website easy for search engines to crawl, render, and index. It covers site speed, mobile display, URL structure, redirects, duplicate content, sitemaps, robots rules, and structured data. It does not cover the words on the page or the links from other sites.

The technical SEO basics matter because Google works in stages. First it discovers a URL. Then it crawls it, renders it like a browser, and decides whether to index it. Only indexed pages can rank. A technical problem at any stage blocks everything that comes after it.

That is also why technical SEO comes before an on-page SEO checklist. Great content on a page Google cannot index earns nothing. Technical fixes are also cheap. One redirect rule can recover hundreds of pages at once.

The technical SEO checklist

Work through the groups below in order. The first groups fix problems that hide whole pages from Google. The later groups make pages that already rank do a little better. Tick each item and fix the fails from the top down.

1. Indexing: can Google show your pages?

• Search site:yourdomain.com in Google. The count should be close to the number of pages you want indexed.
• Open the Pages report in Google Search Console. Read every reason under "Not indexed" and make sure each one is intentional.
• Check that no important page has a noindex tag. Look in the HTML head and in the X-Robots-Tag HTTP header.
• Confirm that only one version of the site is indexed: https, one hostname (www or not), and one trailing slash style.
• Check that staging, test, and dev sites are not indexed. Password protect them instead of relying on robots.txt.
• Use the URL Inspection tool on your five most important pages. The live test should say "URL is available to Google."

2. Crawling: can Google reach every page?

• Open /robots.txt. Make sure it does not block CSS, JavaScript, images, or any section you want ranked.
• Submit an XML sitemap in Search Console. It should list only canonical, indexable, 200 status URLs.
• Remove redirected, 404, and noindex URLs from the sitemap. Google treats a dirty sitemap as a weak signal.
• Check that every important page is reachable within three clicks of the homepage.
• Find pages with no internal links pointing to them. These orphan pages are rarely crawled and rarely rank.
• Crawl the site and list every internal link that returns 404 or 500. Fix or remove them. See how to fix broken links.

3. Redirects and status codes

• Every redirect should be a single hop. Chains of two or more redirects waste crawl budget and slow users down.
• Use 301 for permanent moves. Avoid 302 unless the move really is temporary.
• Remove redirect loops. A loop returns an error to both users and Googlebot.
• Make sure deleted pages return 404 or 410, not a 200 "page not found" message. Google calls those soft 404s.
• Redirect the http version to https and the non-preferred hostname to the preferred one.

4. Duplicate content and canonicals

• Every indexable page has a self-referencing canonical tag with the full, absolute URL.
• URL parameters for sorting, filtering, and tracking point their canonical to the clean URL.
• Paginated pages each have their own canonical. Do not point page 2 to page 1.
• Title tags and meta descriptions are unique per page. Duplicate titles usually mean duplicate pages.
• Trailing slash, uppercase, and index.html variants all redirect to one version. Our post on canonical URLs covers the edge cases.

5. Speed and Core Web Vitals

• Largest Contentful Paint (LCP) is under 2.5 seconds for at least 75 percent of visits.
• Interaction to Next Paint (INP) is under 200 milliseconds.
• Cumulative Layout Shift (CLS) is under 0.1.
• Images are compressed, sized to their container, and served in WebP or AVIF where possible.
• The largest image or hero element is not lazy loaded. Lazy loading above the fold delays LCP.
• Check the Core Web Vitals report in Search Console, not just a lab test. It uses real visitor data.

6. Mobile

• The site uses responsive design, and the mobile version has the same content and links as desktop.
• Tap targets are large enough and text is readable without zooming.
• No interstitials or pop-ups cover the main content on page load.

7. Structured data and site structure

• Add schema markup that matches the page: Article, Product, FAQ, Organization, BreadcrumbList, or LocalBusiness.
• Validate it with the Rich Results Test. Fix every error. Warnings are optional.
• URLs are short, lowercase, and use hyphens between words.
• Breadcrumbs are visible on the page and marked up with schema.
• International sites use correct hreflang tags that point to indexable URLs and reference themselves.

How to do a technical SEO audit step by step

The checklist tells you what to look for. The steps below tell you how to run the technical SEO audit in a repeatable way. Budget half a day for a site with fewer than 1,000 pages.

1. 1

   Set up your tools

   You need three things: Google Search Console, a site crawler, and PageSpeed Insights. Verify the domain property in Search Console so you see every hostname and protocol. Pick a crawler that reports status codes, canonicals, and indexability for every URL.

2. 2

   Crawl the whole site

   Run a full crawl and export the results. Include the XML sitemap as a seed so orphan pages show up. On a large site, crawl by section first so the job finishes and you can start fixing.

3. 3

   Compare crawl, sitemap, and index

   You now have three lists: pages the crawler found, pages in the sitemap, and pages Google indexed. Pages in one list but not the others are your first leads. A page in the sitemap that Google skipped needs a reason.

4. 4

   Fix indexing blockers first

   Look for noindex tags, robots.txt blocks, canonicals pointing elsewhere, and soft 404s on pages that should rank. These are the highest value fixes. One wrong rule can hide a whole directory.

5. 5

   Clean up redirects and broken links

   Sort the crawl by status code. Fix 4xx and 5xx links at the source. Shorten redirect chains to one hop. Update internal links so they point straight to the final URL.

6. 6

   Run the speed checks on your templates

   Do not test every page. Test one page per template: homepage, category, product or article, and blog post. Fix the template and every page built on it gets faster.

7. 7

   Validate structured data and mobile

   Run the Rich Results Test on the same template pages. Then load them on a phone and check text size, tap targets, and pop-ups. Note anything that fails.

8. 8

   Write the report and schedule the recrawl

   List every issue with the affected URLs, the fix, and a priority. Our SEO audit report template has the structure. Recrawl after each fix ships so you can prove it worked.

Common technical SEO issues and how to fix them

These are the technical SEO issues we find most often, with the usual fix for each.

The 80/20 rule for technical SEO

The 80/20 rule in SEO says that about 80 percent of your results come from 20 percent of the work. For technical SEO, that 20 percent is indexing and crawling. If Google can find and index the right pages, and only those pages, you have most of the value already.

In our experience, the next best return comes from fixing template-level speed issues and duplicate URLs. Structured data and URL cosmetics sit at the bottom. They are worth doing, but they rarely move traffic on their own.

Tools for a technical SEO audit

You do not need a big budget. Five tools cover everything on this list.

• Google Search Console. Free. Shows indexing status, crawl stats, Core Web Vitals from real users, and manual actions. Start here.
• PageSpeed Insights. Free. Runs a lab test and shows field data for Core Web Vitals on one URL.
• A site crawler. Crawls every URL and reports status codes, canonicals, titles, and links. Zutrix Site Audit does this in the cloud. Desktop crawlers like Screaming Frog are another option.
• Rich Results Test. Free from Google. Validates structured data and shows which rich results a page qualifies for.
• A rank tracker. Not an audit tool, but it tells you whether the fixes worked.

For a longer comparison, see our post on the best SEO audit tools. If you only want to check how a page looks in Google right now, the free SERP checker shows live results for any keyword and location.

How often to run the checklist

Run the full technical SEO audit checklist once a quarter. Run the indexing and crawling sections after every release that touches templates, navigation, or URLs. Set up alerts for new 404s and new noindex pages.

Technical SEO checklist template

Copy the seven groups above into a spreadsheet. Give each item three columns: status (pass, fail, or not applicable), affected URLs, and owner. Add a date column so you can compare quarters. That is the whole technical SEO checklist template. It does not need to be pretty. It needs to be used.

If you report to a client or a manager, pair the sheet with a one-page summary. Say what you found, what you fixed, and what changed in traffic.