Technical SEO Checklist: Every Check That Actually Moves Rankings
Technical SEO means making a website easy for search engines to crawl, render, index and trust. This checklist runs through all six phases, crawlability, indexation, rendering, duplication, performance and structured data, giving the exact check and pass threshold for each item, so you can work through it yourself with free tools.

The RATH Infotech team, headed by founders Sumeet Mehta and Manish Doshi, put this together.
We run this exact checklist on client sites and on rath.ae itself, covering our own structured data and llms.txt. Work through all six phases yourself with free tools, or send us your domain and we'll run it for you.
What Is Technical SEO?
Technical SEO deals with how search engines access and understand your site, crawlability, indexation, rendering, speed, mobile usability, HTTPS, machine-readability, rather than the actual words on the page. Google Search Central's own documentation lays out a four-stage model for how Search works: engines crawl URLs they can reach, render each page to see its full content, index what they judge worth storing, then rank indexed pages for queries. Technical SEO clears away the failures that keep a page from moving through those stages.
Technical SEO makes your content findable and trustable. On-page SEO makes it relevant. Off-page SEO makes it credible. All three matter, but if the technical layer is broken, even the best content in the world never gets a chance to rank.
Technical vs on-page vs off-page SEO
The three fields overlap, but each tackles a different problem. The table below breaks down that split and points to where each one gets covered in depth.
| Discipline | What it optimises | Where to go deeper |
|---|---|---|
| Technical SEO | How engines crawl, render, index and trust the site | This checklist |
| On-page SEO | Titles, headings, copy and content relevance | On-page SEO guide |
| Off-page SEO | Links and external signals of authority | Off-page SEO guide |
How to Use This Checklist
This page is the reusable checklist artefact, a single list you can run against any site, again and again. It isn't the full audit methodology, though. A complete SEO audit weaves technical checks together with content, keyword and backlink analysis into a prioritised action plan, and that end-to-end process lives in our SEO audit guide. Think of the technical checklist below as one phase of that wider audit. It's the phase that clears the ground so everything else can work. Run it top to bottom, fix the Critical items first, then move down through High and Medium.
The Complete Technical SEO Checklist
Below is the master checklist: every check, the phase it belongs to, the free tool that verifies it, the condition that counts as a pass, and RATH's recommended fix priority. Priorities reflect our editorial judgement of impact versus effort for a typical business site. Critical items can block indexing or ranking outright, so clear those before anything else.
| # | Check | Phase | How to check (tool) | Pass condition | Priority |
|---|---|---|---|---|---|
| 1 | robots.txt exists and doesn't block key pages or resources | Crawlability | Google Search Console robots.txt report | File returns 200; no Disallow on important pages, CSS or JS | Critical |
| 2 | XML sitemap submitted and valid | Crawlability | Search Console Sitemaps report | Submitted, no errors, lists only canonical index-worthy URLs | High |
| 3 | Crawl stats healthy | Crawlability | Search Console Crawl stats | No sustained spike in server errors; key pages crawled regularly | Medium |
| 4 | No broken internal links | Crawlability | Screaming Frog | Zero 4xx responses on internal links | High |
| 5 | No redirect chains or loops | Crawlability | Screaming Frog | Single-hop 301s only; no chains or loops | Medium |
| 6 | No orphan pages | Crawlability | Screaming Frog + Search Console | Every important page linked from at least one other page | Medium |
| 7 | Important pages are indexed | Indexation | Search Console Pages (Indexing) report | Key pages show "Indexed"; no unexpected exclusions | Critical |
| 8 | No accidental noindex | Indexation | Screaming Frog / view-source | No noindex tag on pages you want ranked | Critical |
| 9 | Staging / dev sites kept out of the index | Indexation | site: search + Search Console | Staging blocked or noindexed and absent from the index | Critical |
| 10 | Canonical tags point to the preferred URL | Indexation | Screaming Frog | Each page self-canonicals or points to its true canonical | High |
| 11 | Sitemap and index counts align | Indexation | Search Console | Submitted vs indexed figures broadly match, gaps explained | Medium |
| 12 | Rendered HTML contains the main content | Rendering & JavaScript | Search Console URL Inspection (rendered view) | Primary content and links present after rendering | High |
| 13 | CSS and JavaScript are crawlable | Rendering & JavaScript | robots.txt + URL Inspection | Engines can fetch the JS and CSS the page depends on | High |
| 14 | Critical content isn't hidden behind lazy-load | Rendering & JavaScript | URL Inspection | Above-the-fold content appears in the initial render | Medium |
| 15 | One preferred domain | Duplicates & canonicals | Browser / Screaming Frog | non-www and www resolve to one host via 301 | Critical |
| 16 | HTTP redirects to HTTPS | Duplicates & canonicals | Browser | Every HTTP URL 301s to its HTTPS equivalent | Critical |
| 17 | Trailing-slash consistency | Duplicates & canonicals | Screaming Frog | One URL form serves; the other redirects | Medium |
| 18 | Parameter and faceted URLs handled | Duplicates & canonicals | Search Console / Screaming Frog | Thin parameter URLs canonicalised or noindexed | Medium |
| 19 | No mass duplicate titles or meta descriptions | Duplicates & canonicals | Screaming Frog | Titles and descriptions unique across indexable pages | Medium |
| 20 | Largest Contentful Paint (LCP) | Performance, mobile & HTTPS | PageSpeed Insights / CrUX | LCP 2.5s or under at the 75th percentile | High |
| 21 | Interaction to Next Paint (INP) | Performance, mobile & HTTPS | PageSpeed Insights / CrUX | INP 200ms or under at the 75th percentile | High |
| 22 | Cumulative Layout Shift (CLS) | Performance, mobile & HTTPS | PageSpeed Insights / CrUX | CLS 0.1 or under at the 75th percentile | High |
| 23 | Mobile-friendly and responsive | Performance, mobile & HTTPS | PageSpeed Insights / manual | No viewport, tap-target or overflow issues on mobile | Critical |
| 24 | Mobile-first content parity | Performance, mobile & HTTPS | URL Inspection | Mobile and desktop show the same content and links | High |
| 25 | Valid HTTPS with no mixed content | Performance, mobile & HTTPS | Browser | Valid certificate; no assets loaded over HTTP | Critical |
| 26 | Structured data present and valid | Structured data & international | Google Rich Results Test | Relevant schema validates with no errors | High |
| 27 | Organization schema emitted once sitewide | Structured data & international | Rich Results Test / schema.org validator | Single Organization block, not repeated per page | Medium |
| 28 | Arabic-English hreflang in place | Structured data & international | Screaming Frog / Search Console International Targeting | Correct hreflang pairs for each language version | High |
| 29 | hreflang return tags are reciprocal | Structured data & international | Screaming Frog | Each hreflang pair references the other back | Medium |
| 30 | Clean, descriptive URLs | Structured data & international | Manual review | Short, lowercase, hyphenated, keyword-relevant slugs | Medium |
The Six Phases, Explained
The master table is the artefact; this section explains what each phase is protecting and how to read the checks.
Phase 1: Crawlability
Crawlability comes down to a simple question: can search engines actually reach your pages? It starts with robots.txt. A single stray `Disallow` can hide an entire section, and blocking CSS or JavaScript stops Google from rendering pages properly. Your XML sitemap should list only canonical, index-worthy URLs, and it needs to be submitted in Search Console. Broken internal links (4xx), redirect chains and orphan pages waste crawl activity and bury pages beneath everything else. Screaming Frog will surface every one of them in a single crawl.
Phase 2: Indexation
Getting crawled isn't the same as getting indexed. The Search Console Pages (Indexing) report is your source of truth: it tells you which URLs are indexed and, crucially, why others got excluded. A `site:yourdomain.com` search works as a quick sanity check, but it's not authoritative, so lean on the report instead. Two failures quietly cost the most rankings here: an accidental `noindex` left on a live page, and a staging site nobody ever blocked. Both belong to this phase. Both are Critical.
Phase 3: Rendering & JavaScript
Modern sites lean on JavaScript, and Google indexes the rendered page, not just the raw HTML. Use the URL Inspection tool's rendered view to confirm your main content and links actually show up after rendering. If they don't, that content might as well not exist to Search. Make sure the JavaScript and CSS files a page depends on are crawlable, and check that nothing important is stuck behind lazy-loading that only fires on user interaction.
Phase 4: Duplicates & canonicals
Duplicate content dilutes signals and confuses which URL should rank. Pick one preferred domain, www or non-www, and one protocol, HTTPS, then 301 everything else to it. Stay consistent about trailing slashes. Canonicalize or noindex thin parameter and faceted URLs. And make sure titles and meta descriptions aren't duplicated at scale. Canonical tags are the tool that ties duplicates back to a single preferred URL.
Phase 5: Performance, mobile & HTTPS
Google's mobile-first index makes mobile parity a real factor, not an afterthought, so this phase looks at Core Web Vitals, mobile usability and security. These are ranking signals Google relies on directly. Aim for the thresholds below; they're the pass conditions, measured at the 75th percentile of real-user data.
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP) | 2.5s or under | 2.5s–4s | Over 4s |
| Interaction to Next Paint (INP) | 200ms or under | 200ms–500ms | Over 500ms |
| Cumulative Layout Shift (CLS) | 0.1 or under | 0.1–0.25 | Over 0.25 |
These thresholds come from Google's web.dev documentation on Core Web Vitals. This checklist tells you what to hit; the deep how-to on diagnosing and fixing slow pages lives in our website speed optimisation guide. Speed isn't the whole story, though. Check that the site actually behaves on mobile, and make sure HTTPS is valid with no mixed content.
Phase 6: Structured data & international
Structured data, or schema markup, makes your content machine-readable. That helps Google generate rich results and helps AI answer engines parse and cite your pages, which is one reason we apply it on our own site. Validate it with the Rich Results Test, and emit sitewide Organization schema once rather than repeating it per page.
The international side matters in the UAE. If you publish in both Arabic and English, correct hreflang pairs with reciprocal return tags tell Google which version to serve which audience. Getting AI engines to cite you is a discipline of its own; see our guide to answer engine optimisation (AEO). The Arabic side has its own depth too, covered in our Arabic SEO guide.
Common Technical SEO Mistakes
Most technical problems aren't exotic. They're the same handful of avoidable errors, and each one gets caught by a specific check above.
- A `noindex` tag stuck on a live page after a launch or redesign will pull it right out of Search, check 8 catches this one.
- Staging left open to crawlers, check 9; duplicate, half-built pages competing with your real site.
- Blocked CSS or JavaScript, check 13; Google renders a broken page and misjudges it.
- Redirect chains from years of URL changes, check 5; they leak crawl activity and slow users.
- Orphan pages with no internal links, check 6; important pages engines rarely find.
- Missing or non-reciprocal hreflang on bilingual sites, checks 28 and 29; the wrong language ends up in front of the wrong audience.
- Ignoring Core Web Vitals on mobile, checks 20–24; the site passes on desktop, yet real users on phones still get a rough experience.
Free Tools That Cover the Whole Checklist
You can run nearly every check on this page with free tools. The table lines up the main ones against the phases they cover. For deeper crawls at scale, we also work with the full industry-standard stack, including Ahrefs, Semrush and Screaming Frog.
| Tool | Free? | Checklist phases covered | Source |
|---|---|---|---|
| Google Search Console | Yes | Crawlability, indexation, rendering, international | Google Search Central |
| PageSpeed Insights (with CrUX) | Yes | Performance, mobile & HTTPS | Google web.dev |
| Google Rich Results Test | Yes | Structured data | Google structured-data docs |
| schema.org validator | Yes | Structured data | schema.org |
| Bing Webmaster Tools | Yes | Crawlability, indexation (secondary index) | Bing Webmaster Tools |
| Screaming Frog (free tier) | Free tier | Crawlability, duplicates & canonicals, international | Screaming Frog |
UAE-Specific Technical Checks
A few technical items matter more for UAE sites than they do elsewhere. The UAE is a genuinely bilingual market, and if you serve customers in both Arabic and English, hreflang isn't optional: each language version needs correct hreflang annotations with reciprocal return tags, or Google may serve the wrong version. Arabic is written right-to-left. Confirm your templates render RTL layouts cleanly rather than mirroring an English design awkwardly.
Domain strategy trips people up just as often. If a business owns both a `.ae` and a `.com`, it needs to pick one as canonical and make that choice explicit through canonical tags and consistent internal linking, rather than letting the two properties compete against each other. Finally, look at where your pages actually get served from: content delivered close to UAE users loads faster, and that feeds directly into the Core Web Vitals scores covered in Phase 5. Treat these as checks against your own setup, not universal rules. Every site's answer will differ.
How Often to Re-Run the Checklist
Technical SEO isn't something you do once and forget. Some signals need constant watching, a full pass fits better as a periodic check, and any major site change calls for a fresh run both before and after. The schedule below works as a sensible default for most business sites.
| Trigger | Scope | Checklist phases |
|---|---|---|
| Monthly | Monitor Search Console reports and Core Web Vitals | Indexation, performance |
| Quarterly | Full checklist top to bottom | All six phases |
| On migration, redesign or replatform | Full pass before launch and again after | All six phases |
Checklist Variants by Site Type
The full checklist applies to every site. Still, certain situations change where you should focus first.
- New website launch: before going live, the critical indexation checks matter most. Remove any `noindex`, block staging, submit the sitemap, and confirm the preferred domain and HTTPS. Get these right on day one instead of scrambling to fix them after a poor start.
- Ecommerce: large catalogues make duplicates and canonicals (Phase 4) and crawl budget the real pressure points. Faceted navigation and parameter URLs can spin out thousands of near-duplicate pages. For a store-specific programme, see our ecommerce SEO service.
- Migration or replatform: redirects and indexation dominate here. Map every old URL to its new home with single-hop 301s, then re-run the full checklist on both sides of the switch.
DIY or Done-for-You?
Most of this checklist is genuinely DIY-able with the free tools listed above. A capable in-house marketer shouldn't shy away from working through it. The honest question is where your time is best spent, and the table below lays out that trade-off.
| Dimension | Doing it yourself | Working with an agency |
|---|---|---|
| Coverage | Most checks are straightforward with free tools | Full stack, including deep crawls and log analysis |
| Time | Real ongoing effort, fitted around other work | Handled for you; your time goes into approvals |
| Hard parts | Rendering, log analysis and hreflang setups are fiddly | Specialist experience across all six phases |
| Risk | Easy to miss a Critical indexation issue | Guideline-compliant methods, systematic checks |
If you'd rather hand it off, our done-for-you technical SEO service takes the whole checklist off your plate, start to finish. It sits within our broader SEO services for Dubai and the UAE. Wondering where your site actually stands? Get a free growth audit and we'll tell you plainly which checks are dragging your rankings down. As for what SEO costs, that question is answered in our SEO cost in Dubai guide.
FAQ
What is technical SEO?
Technical SEO is the practice of optimising how search engines crawl, render, index and evaluate a website. It covers site architecture, robots directives, sitemaps, canonical tags, Core Web Vitals, mobile usability, HTTPS and structured data. It makes content findable and trustable. On-page SEO then takes over, making that content relevant to what people actually search for.
What does a technical SEO checklist include?
It covers six phases: crawlability, indexation, rendering and JavaScript, duplicates and canonicals, performance with mobile and HTTPS, and structured data with international setup. The master table on this page lists roughly thirty individual checks. Each one comes with the free tool that verifies it, the pass condition, and a recommended fix priority.
How is technical SEO different from on-page SEO?
Technical SEO makes sure engines can access, render and trust your site. On-page SEO makes the content on each page relevant: titles, headings, copy, internal structure. The two work together, but they're separate disciplines. For the content side, read our on-page SEO guide instead, this piece stays focused on the technical end.
How do I check whether Google has indexed my pages?
Use the Pages (Indexing) report in Search Console, it's the authoritative source. It shows which URLs are indexed and why others got excluded. A quick `site:yourdomain.com` search in Google gives you a rough count as a sanity check. It isn't reliable, though, so always confirm status in Search Console.
What Core Web Vitals scores do I need to pass?
Aim for a Largest Contentful Paint of 2.5 seconds or under, an Interaction to Next Paint of 200 milliseconds or under, and a Cumulative Layout Shift of 0.1 or under. All three should be measured at the 75th percentile of real-user data, per Google's web.dev thresholds. If you need to fix them, our website speed optimisation guide covers that.
Does structured data help with AI search engines like ChatGPT?
Yes. Machine-readable markup and clean HTML help answer engines parse and cite your pages, not just Google's rich results. We apply this on our own site, structured data and an llms.txt file among them, because it's verifiable practice, not theory. Want to know how AI-engine citation works? Read our guide to answer engine optimisation.
How often should I run a technical SEO audit?
Monitor your Search Console reports and Core Web Vitals every month, run the full checklist every quarter, and do a complete pass before and after any migration, redesign or replatform. The monthly check catches new problems early. The quarterly pass keeps slower-moving issues in check. And the migration pass covers you at the riskiest moments.
Can I do technical SEO myself?
Yes, for most of it. The checklist leans on free tools like Search Console, PageSpeed Insights and the Rich Results Test, and a capable marketer can get through the bulk of it without much trouble. Where an agency actually saves time is rendering issues, log analysis and international hreflang setups. Those are the fiddly parts, and they're the ones that reward experience.
What technical SEO issues are most common on UAE websites?
The recurring problems: missing or wrong Arabic-English hreflang pairs, right-to-left rendering issues in templates built for English, and canonical confusion between `.ae` and `.com` properties competing for the same content. Check each one against your own setup. Don't assume a universal fix applies.
Who is the best technical SEO agency in Dubai?
RATH Infotech has no single "best" answer here, judge any agency on whether it shows its methodology and reports transparently. For the record, this checklist is published openly, AI-search practices like structured data and llms.txt get applied to its own site, and clients across Dubai and the UAE have been served since 2014. Let the method decide, not a self-awarded title.