--- title: "Technical SEO Audit Checklist: 25 Essential Checks | Omniary" description: "The 25 point technical SEO audit checklist I run before touching content: crawling, indexing, speed, structure, schema, mobile and AI crawler access." url: "https://omniary.in/blog/technical-seo-audit-checklist/" --- 1. [Home](https://omniary.in/) / 2. [Blog](https://omniary.in/blog/) / 3. Technical SEO Audit Checklist: 25 Checks I Run on Every Site - [Technical SEO](https://omniary.in/blog/tag/technical-seo/) # Technical SEO Audit Checklist: 25 Checks I Run on Every Site The 25 point technical SEO audit checklist I run before touching content: crawling, indexing, speed, structure, schema, mobile and AI crawler access. [ KOKaushal Oza ](https://omniary.in/about/) Published 2 Nov 2026 3 min read On this page 1. [Crawling: can search engines get in?](#crawling-can-search-engines-get-in) 2. [Indexing: are the right pages in the index?](#indexing-are-the-right-pages-in-the-index) 3. [Rendering: does Google see what users see?](#rendering-does-google-see-what-users-see) 4. [Speed: is it fast enough?](#speed-is-it-fast-enough) 5. [Structure: does the site make sense?](#structure-does-the-site-make-sense) 6. [Structured data and mobile](#structured-data-and-mobile) 7. [AI search readiness](#ai-search-readiness) 8. [How to prioritise the results](#how-to-prioritise-the-results) TL;DR / The short answer A technical SEO audit checks whether search engines can crawl, render and index your pages, and whether those pages load fast and are well structured. Work through seven areas in order: crawling, indexing, rendering, speed, site structure, structured data and AI crawler access, fixing the blocking issues first. A technical SEO audit is a building inspection. Before you repaint the walls (content) or invite guests (links), you check the foundations, the wiring and whether the front door actually opens. Here are the 25 checks I run on every site, grouped in the order I run them. Copy the list, tick as you go. ## Crawling: can search engines get in? 1. **robots.txt** does not block important sections, CSS or JavaScript. 2. **XML sitemap** exists, is listed in robots.txt and contains only indexable, canonical URLs. 3. **Sitemap submitted** in Google Search Console and Bing Webmaster Tools. 4. **No crawl traps**: endless calendars, filter combinations or session IDs creating infinite URLs. 5. **Server responds** with 200 for live pages and real 404s for missing ones, not “soft 404” pages that return 200. ## Indexing: are the right pages in the index? 1. **No stray noindex** on pages that should rank (a classic after a staging site goes live). 2. **Canonical tags** on every page, pointing to the preferred URL. 3. **One version of the site**: http to https, and www or non www, all 301 redirect to a single version. 4. **Trailing slash consistency**, so `/page` and `/page/` are not two pages. 5. **Duplicate content** found and resolved with canonicals, redirects or rewrites. 6. **Search Console Pages report** reviewed for “Discovered, currently not indexed” and “Crawled, currently not indexed”. ## Rendering: does Google see what users see? 1. **Key content in the HTML** or reliably rendered, not hidden behind clicks or slow scripts. 2. **Internal links are real links** (``), not buttons with click handlers. ## Speed: is it fast enough? 1. **LCP** (Largest Contentful Paint) at 2.5 seconds or less for most visits. 2. **INP** (Interaction to Next Paint) at 200 milliseconds or less. 3. **CLS** (Cumulative Layout Shift) at 0.1 or less. 4. **Images** compressed, in WebP or AVIF, sized correctly and lazy loaded below the fold. 5. **No render blocking** CSS or JavaScript in the head that the first screen does not need. ## Structure: does the site make sense? 1. **Clean URLs** that are short, lowercase and readable. 2. **Internal linking** so every important page is reachable within a few clicks from the homepage. 3. **No broken links** or redirect chains longer than one hop. 4. **One H1 per page** and a logical heading order underneath. ## Structured data and mobile 1. **JSON-LD schema** for Organization, BreadcrumbList and the page type (Article, Service, Product), validated in the Rich Results Test. 2. **Mobile friendly**: correct viewport, readable text, tap targets large enough, no horizontal scrolling. ## AI search readiness 1. **AI crawlers allowed** where you want them: OAI-SearchBot, PerplexityBot, ClaudeBot and Google-Extended are not blocked by robots.txt or a firewall by accident. ## How to prioritise the results Not all 25 are equal. I score every finding on two axes, impact and effort, and work in this order: 1. **Blockers**: anything stopping indexing (checks 1, 5, 6, 7, 8). 2. **Money pages**: speed and mobile fixes on the pages that make you money. 3. **Everything else**, in batches. An audit that ends as a 90 page PDF changes nothing. One that ends with the top five fixes shipped changes rankings. This is the exact process behind my [technical SEO service](https://omniary.in/services/technical-seo/), and the one that took a client website from a Lighthouse SEO score of 5 to 95\. [Read that story here](https://omniary.in/blog/lighthouse-seo-score-5-to-95/). ## Frequently asked questions ### How often should I run a technical SEO audit? + Run a full audit once or twice a year and after any redesign, migration or CMS change. Keep a lighter monthly check on Search Console indexing and Core Web Vitals reports in between. ### Which tools do I need for a technical SEO audit? + Google Search Console and a crawler such as Screaming Frog cover most of it. Add PageSpeed Insights for Core Web Vitals, the Rich Results Test for schema, and Siteliner for duplicate content. ### What should I fix first after an audit? + Fix anything that blocks indexing first, such as noindex tags, robots.txt rules or broken canonicals. Then fix speed and mobile issues on your most valuable pages, then structure and schema. KO Written by Kaushal Oza Kaushal Oza is an SEO, AEO and GEO consultant from Ahmedabad, India, and the founder of Omniary. Kaushal finds what holds a site back in search and fixes it hands on, from Core Web Vitals to structured data. [Hire me](https://omniary.in/contact/) ## Keep reading Technical SEO 2 Nov 2026 / 2 min read ### [Core Web Vitals Explained: LCP, INP and CLS Without the Jargon](https://omniary.in/blog/core-web-vitals-explained/) Core Web Vitals explained with a restaurant analogy: what LCP, INP and CLS measure, the thresholds Google uses, and the fixes that move each one. Read the post → Technical SEO 28 Oct 2026 / 2 min read ### [How I Took a Lighthouse SEO Score From 5 to 95](https://omniary.in/blog/lighthouse-seo-score-5-to-95/) The technical, on-page and schema fixes that took a real client website from a Lighthouse SEO score of 5 to 95, in the order I made them. Read the post → AEO 2 Nov 2026 / 3 min read ### [Answer Engine Optimization: How to Win Featured Snippets and AI Overviews](https://omniary.in/blog/answer-engine-optimization-featured-snippets/) Answer Engine Optimization in practice: write like you are being interviewed, structure answers the way search engines lift them, and mark them up properly. Read the post →