Technical SEO Checklist 2026: 12 Checks, Tools and Pass Criteria to Demand From Your Agency

• Amol Ghemud
• Technical SEO Checklist 2026: 12 Checks, Tools and Pass Criteria to Demand From Your Agency
• Published: February 19, 2026

Contributors: Amol Ghemud
Published: February 19, 2026

Summary

A technical SEO checklist confirms Google can crawl, render, index and understand your site. This 2026 version maps 12 checks to the tool to run and the pass criteria, using Google’s own thresholds: LCP 2.5 seconds or less, INP 200 milliseconds or less, CLS 0.1 or less, and sitemaps capped at 50,000 URLs or 50MB uncompressed. Run it monthly, quarterly and annually so small issues don’t compound.

If your site isn’t technically sound, your marketing budget is leaking.

Your team just published a brilliant, GEO-optimized piece targeting a keyword your competitors rank for. 60 days later, it’s not indexed. Or it takes 6 seconds to load on mobile. Or Google can’t read it because the markup is broken. That’s why every business needs a technical SEO checklist.

Technical SEO isn’t glamorous. Nobody builds a career posting LinkedIn updates about fixing canonical tags. But poor technical foundations silently undermine every rupee you spend on content, ads and strategy.

This guide is for founders, CMOs and beginners who need to know what to ask and which answers are unacceptable. Every Google threshold below was checked against the specific Google Search Central or web.dev page in September 2026.

What Is a Technical SEO Checklist? (Quick Answer for 2026)

A technical SEO checklist is a repeatable set of checks that confirms Google can crawl, render, index and understand your site. The 12 checks that matter in 2026 cover Core Web Vitals, robots.txt, XML sitemaps, indexation, status codes, canonical tags, mobile-first parity, JavaScript rendering, structured data, internal links, HTTPS and hreflang.

Use this table as your SEO technical checklist. Rows marked “upGrowth benchmark” are our working standards, not Google rules.

What Changed Since the 2025 Checklist

• FAQ rich results are gone. Google’s documentation changelog says the feature would “no longer appear in Google Search starting May 7, 2026.”
• llms.txt does nothing for Google Search. Google’s AI optimization guide says Google Search ignores these files.
• INP is the responsiveness metric. It replaced First Input Delay (FID) as a Core Web Vital in March 2024, so reports quoting FID are out of date.

Why Agencies Ignore Technical SEO (and What It Costs You)

Most agencies report rankings and traffic, not the infrastructure behind both, so technical problems grow unseen until traffic drops. It’s like a contractor showing you the paint job while the foundation cracks.

Technical issues compound. Google’s ranking systems generally evaluate content page by page, but most sites run on a handful of templates, so 1 slow template or broken canonical rule repeats across every URL that uses it. 1 bad robots.txt rule can hide entire sections. Missing schema markup costs you rich result eligibility. And a JavaScript rendering bug can leave Google indexing a near-empty page while your team sees a perfect site.

The uncomfortable reality: many agencies have content people who can run a Screaming Frog crawl and flag the obvious issues. That covers the surface, not rendering, canonical conflicts or template-level performance problems.

Crawl and Index Checks: robots.txt, XML Sitemaps and Indexation

If Google can’t crawl a URL, or chooses not to index it, nothing else on this list matters. Start with robots.txt, sitemaps, the Page indexing report and your status codes.

robots.txt: Crawl Control, Not Index Control

What to ask: “Has our robots.txt blocked anything we want in search?”

Acceptable answer: The file sits at the root of each host, shows as fetched in the robots.txt report, stays under Google’s 500 KiB limit and blocks only low-value areas like internal search results.

Red flag answer: “We blocked those pages in robots.txt so they won’t show in Google.” Google says robots.txt “is not a mechanism for keeping a web page out of Google”. Blocked URLs can still appear without a description. Use noindex, and don’t block that page, because Google must crawl it to see the rule.

Also note: Google treats a 4xx robots.txt response (except 429) as if no file exists, and it generally caches the file for up to 24 hours.

XML Sitemaps: Stay Under 50,000 URLs and 50MB

What to ask: “Do our sitemaps list only canonical, indexable URLs?”

Acceptable answer: Each file holds 50,000 URLs or fewer and is 50MB or less uncompressed, per Google’s sitemap guidelines. Bigger sites split files under a sitemap index. Entries are absolute canonical URLs with accurate lastmod dates.

Red flag answer: “We set priority to 1.0 on key pages.” Google ignores <priority> and <changefreq>. And redirects or 404s in a sitemap muddy the signal.

A sitemap index can list up to 50,000 sitemaps, and Search Console accepts up to 500 sitemap index files per site, so the limits rarely bite.

Indexation Ratio: Find the Pages Google Is Leaving Out

What to ask: “How many canonical pages have we published, and how many are indexed?”

Acceptable answer: Within 10% (upGrowth benchmark), with every exclusion explained. Google’s Page indexing report help says to expect indexing for “only the canonical pages,” not every URL.

Red flag answer: “I’ll need to check.” If your team doesn’t know the ratio, crawl issues can hide content for months.

500 published pages with 300 indexed means 200 pages you paid for are invisible. Usual causes: robots.txt rules blocking crawlers, orphan pages with no internal links, stray noindex tags and duplicates that lead Google to pick another URL as canonical.

Status Codes, Redirects and Crawl Budget

Googlebot follows up to 10 redirect hops, but aim for single-hop 301s (upGrowth benchmark). 4xx URLs drop out of the index, persistent 5xx errors slow crawling, and soft 404s (error pages returning 200) waste crawls. Crawl budget only matters for big sites: Google’s guide targets 1 million+ pages changing weekly or 10,000+ changing daily.

Core Web Vitals, Mobile-First Indexing and HTTPS Checks

A page passes Core Web Vitals when LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less at the 75th percentile of page loads. Google indexes your mobile version, so watch mobile first.

Core Web Vitals: LCP, INP and CLS

What to ask: “What are our mobile Core Web Vitals for our top 20 pages by traffic?”

Acceptable answer: All 3 metrics show Good in PageSpeed Insights field data or the Core Web Vitals report, both based on real-user data, at the 75th percentile. PageSpeed Insights covers the previous 28 days.

Red flag answer: “Our Lighthouse score is 95” or “desktop looks good.” Lab scores aren’t field data, and mobile is reported separately.

Poor means LCP above 4 seconds, INP above 500 milliseconds or CLS above 0.25. Still, Google says good scores don’t guarantee top rankings; relevance wins. Our Core Web Vitals fixes guide covers common causes.

Mobile-First Indexing: Content Parity

What to ask: “Does mobile show the same content, structured data and meta tags as desktop?”

Acceptable answer: Yes, confirmed in URL Inspection. Google uses “the mobile version of a site’s content” for indexing and ranking, so titles, descriptions and robots tags must match. See our mobile-first indexing guide.

Red flag answer: “We hide some sections on mobile.” Google may not index them, and it won’t load content that needs a click or swipe.

Then compare mobile and desktop conversion rates. A wide gap is usually UX friction: slow pages, small tap targets, painful forms and pop-ups.

HTTPS and Security

What to ask: “Any HTTP pages or mixed content warnings?”

Acceptable answer: 100% HTTPS, no mixed content, auto-renewing certificate. Secure serving is part of Google’s page experience self-assessment.

Red flag answer: Anything else. Browsers warn users on non-HTTPS pages, so this is table stakes.

Also Read: what mobile-first indexing means for your site

Rendering, Canonical, Structured Data and Linking Checks

These checks decide whether Google sees the page you built, picks the URL you want and understands the page. In our audits, this is where the expensive problems hide.

JavaScript SEO: Check the Rendered HTML

What to ask: “If our JavaScript failed, what would Google see?”

Acceptable answer: Main content and <a href> links appear in rendered HTML. Google’s JavaScript SEO basics describe 3 phases (crawling, rendering, indexing) and call server-side or pre-rendering “still a great idea.”

Red flag answer: “We add noindex by default and remove it with JavaScript.” Google may skip rendering once it sees noindex.

Single-page apps need 2 more checks. For missing content, redirect to a URL that returns a real 404 or add noindex dynamically, so you don’t create soft 404s. And route between views with the History API, not URL fragments.

Canonical Tags and Duplicate Content

What to ask: “Does Google’s selected canonical match ours, and do pages compete for keywords?”

Acceptable answer: Absolute rel=”canonical” URLs, internal links to canonicals, and URL Inspection showing matching declared and Google-selected canonicals.

Red flag answer: “We block duplicates in robots.txt.” Google’s canonicalization guide says not to; redirects and rel=”canonical” are the strong signals.

And “cannibalization isn’t a priority” is wrong. When 2 pages chase 1 query, Google has to pick 1, and it may not be the page you want. Consolidate them.

Structured Data in 2026: Rich Results, Not AI Shortcuts

What to ask: “Which schema types run across our site, and do they validate?”

Acceptable answer: JSON-LD (Google’s recommended format): Article, Organization and Product or Service markup passing the Rich Results Test and matching visible content.

Red flag answer: “We added FAQ schema everywhere for rich results.” Those stopped showing on May 7, 2026, and valid markup doesn’t guarantee any feature.

For AI search, Google says structured data isn’t required for its generative AI features, there’s no special schema to add and Google Search ignores llms.txt. Schema still earns rich result eligibility. As our SEO vs GEO guide explains, AI visibility on Google starts with crawlable, indexable pages and clear, text-based content.

Internal Linking Architecture

What to ask: “How many contextual links and clicks from the homepage do our key pages have?”

Acceptable answer: No orphans. Google can only crawl <a> links with an href and wants every important page linked from another page. Our upGrowth benchmark: key pages within 3 clicks of the homepage, with 10+ contextual links.

Red flag answer: “Our navigation links to everything.” Navigation is the minimum, not the strategy.

Hreflang for International Sites (If Applicable)

What to ask: “Is our hreflang reciprocal?”

Acceptable answer: Every version lists itself and all alternates with full URLs, using valid codes: an ISO 639-1 language plus an optional ISO 3166-1 Alpha 2 region, such as en-IN or en-AE, plus x-default. See our hreflang guide.

Red flag answer: “We tagged the UAE pages with just the country code.” Google says you can’t specify a country code by itself, and missing return links can get tags ignored. For India and GCC sites, that means the wrong market sees the wrong page.

How Often to Run a Technical SEO Audit (2026 Cadence)

Check Search Console monthly, crawl quarterly and run a deep technical SEO audit yearly. Developers ship updates, plugins conflict and content goes live without markup.

Monthly: Search Console Review

Scan the Page indexing, Core Web Vitals and robots.txt reports for new errors. About 15 minutes.

Quarterly: Full Site Crawl

Crawl with Screaming Frog or Sitebulb for broken links, redirect chains, canonicals, schema and orphan pages. Budget 2 to 4 hours (upGrowth estimate).

Annually: Deep Technical Audit

Review server response, CDN, JavaScript rendering, hreflang, sitemap structure and security.

What Expert Technical SEO Looks Like in Your Agency Relationship

If your agency can’t answer this technical SEO checklist with data, you have a capability gap. That doesn’t always mean a new agency; a specialist hire or 1-time audit may do. Expert teams answer with numbers from Search Console and a crawler, not reassurance.

Don’t assume all is fine because rankings haven’t dropped yet. Technical debt accumulates silently, and by the time it shows in traffic reports, you’ve lost months.

Technical SEO Checklist FAQs

Your Next Move: Run 2 Checks This Week

Open Search Console and check 2 reports before you spend more on content or paid media. First, Page indexing: are your canonical pages indexed? Second, Core Web Vitals: do mobile URLs pass? If both are green, you have a solid foundation. If either shows issues, that’s your top fix.

Want a full audit covering crawlability, schema, speed and GEO readiness? Book a technical SEO audit with our team for a prioritized fix list, or book a strategy call with upGrowth.

---

About the Author

Amol Ghemud

Optimizer in Chief

Amol has helped catalyse business growth with his strategic & data-driven methodologies. With a decade of experience in the field of marketing, he has donned multiple hats, from channel optimization, data analytics and creative brand positioning to growth engineering and sales.