What's the difference between robots.txt and noindex, and which should I use?

These directives operate at different layers of Google's crawling and indexing pipeline, and confusing them causes real problems. robots.txt is a crawling directive: it tells Googlebot not to fetch a URL. noindex is an indexing directive in the page HTML or HTTP header that tells Googlebot not to include the page in its search index. The critical misunderstanding: a page blocked by robots.txt can still appear in search results if Google discovers it from external backlinks. Google knows the page exists because links point to it, but it can't read the noindex tag because it's blocked from fetching the page. The practical rule: use robots.txt to prevent crawling of pages you want to keep private but don't care about indexation status (staging environments, internal tools). Use noindex for pages you want Googlebot to fetch but not index (thank-you pages, paginated archives beyond page 2, thin content you're keeping for UX reasons). Never use robots.txt as a substitute for noindex on pages you actively want removed from search results.

How do I check my real Core Web Vitals scores, not the PageSpeed lab data?

PageSpeed Insights lab scores are diagnostic tools for identifying performance issues. They're not what Google uses for rankings. The ranking-relevant scores come from the Chrome User Experience Report (CrUX), real performance data collected from actual Chrome users visiting your site. There are three ways to access your real CrUX data. First, Google Search Console: the Core Web Vitals report shows field data segmented by device type and status (good, needs improvement, poor). This is the most actionable view for technical SEO purposes. Second, the PageSpeed Insights API: when run with a real URL, PSI shows both lab and field data. Look at the 'Field Data' section at the top, not 'Lab Data.' Third, Ranking Lens monitoring: continuous automated tracking of your CrUX scores across your full URL inventory. The common mistake is optimizing based on lab scores while your field scores remain poor, which happens with JavaScript-heavy sites where real user performance differs significantly from controlled lab conditions.

What's the fastest way to fix CLS on my site?

CLS above 0.1 is almost always caused by one of four specific patterns. Pattern 1: images without explicit width and height attributes. The browser can't reserve space before the image loads, so content shifts when it arrives. Fix: always include width and height on img tags, or use CSS aspect-ratio. Pattern 2: late-loading web fonts causing text reflow. Text renders in a fallback font, then shifts when the custom font loads. Fix: use font-display: optional to prevent layout shift entirely, or font-display: swap with matching fallback font metrics. Pattern 3: dynamically injected content including ad slots, cookie banners, and newsletter bars that load after initial render. Fix: pre-allocate the space with min-height on the container before the content loads. Pattern 4: animations that affect layout properties like height, width, top, or left. Fix: animate transform and opacity instead, these are GPU-composited and don't trigger layout recalculation. Use Chrome DevTools' Performance panel and filter by Layout Shifts to identify exactly which elements are shifting and when.

Does page speed actually affect Google rankings, or is that overblown?

Based on our analysis across several hundred sites, Core Web Vitals are a significant ranking factor at the extremes and a marginal tiebreaker in the middle. A page with CLS above 0.25 will be demoted enough to lose meaningful position in competitive SERPs. A page with LCP above 4 seconds faces similar treatment. But the difference between LCP of 1.2 seconds versus 2.1 seconds? In our testing, the direct ranking impact is negligible if content quality and authority are equal. Where speed matters more than most technical SEO practitioners admit is in indirect signals: faster pages generate lower bounce rates, higher engagement, and more return visits, all of which feed into Google's user satisfaction signals. A page where users wait 3 seconds for content and immediately bounce is performing poorly on every signal Google can measure. Fix performance because it improves the user experience that generates ranking signals, not because a 0.3-second LCP improvement will directly move you from position 4 to position 1.

How should I handle JavaScript-rendered content for technical SEO?

Googlebot can render JavaScript, but with a delay, inconsistently, and with significant resource constraints compared to a standard browser. Content that requires JavaScript execution to appear in the DOM is typically indexed days to weeks after initial discovery, not immediately. Content critical for ranking, including your main article body, headers, and internal links, should be present in the initial HTML response, not dependent on client-side JavaScript. There are three viable approaches for technical SEO compliance. Server-Side Rendering: the server executes JavaScript and returns complete HTML, best for highly dynamic content. Static Site Generation: pages pre-built to complete HTML at build time, best for content that doesn't change per user. Hybrid with selective hydration: a static HTML shell with JavaScript progressively enhancing interactive elements, best for complex apps. The test: use URL Inspection in Google Search Console and compare the rendered page to what a user sees. If they diverge significantly, you have a rendering problem affecting your technical SEO.

What structured data should every blog post have in 2026?

For a blog article optimized for both Google search features and AI citation, three schema types are non-negotiable. First, Article or BlogPosting schema: include headline, datePublished, dateModified, author as a Person entity with name and URL, publisher as an Organization with logo, and the article's description. The author Person entity is particularly important for E-E-A-T since Google uses it to build a knowledge graph entity for the author. Second, FAQPage schema: if your article contains a FAQ section, wrap each question and answer pair in FAQPage schema. This unlocks FAQ rich results in Google search, which can more than double your SERP real estate on featured queries. Third, BreadcrumbList: provides Google with explicit navigation context and enables breadcrumb rich results. Validate everything with Google's Rich Results Test before deploying. The common mistake: implementing FAQPage schema on pages where the questions and answers aren't visible in the page content. Google will reject these.

What's the most commonly overlooked technical SEO issue in 2026?

Based on auditing dozens of sites, the single most overlooked issue is orphaned pages, meaning pages with no internal links pointing to them. These pages receive zero PageRank from your site's internal link distribution regardless of how strong your domain is externally. They're effectively invisible to Google's crawlers unless discovered through an XML sitemap or external backlinks. The insidious part: orphaned pages tend to be your weakest content, which is often why they weren't linked to, so they also drag down your site's overall content quality signal under the Helpful Content system. A secondary commonly missed issue is redirect chain accumulation on sites that have gone through multiple redesigns or CMS migrations. A chain of A to B to C is so common that most site owners don't realize they have it. Each additional hop adds latency and dilutes PageRank. Use Screaming Frog or Sitebulb to map your redirect graph and flatten everything to single-hop 301 redirects as part of your technical SEO maintenance routine.

Technical SEO Checklist 2026: 47 Checks That Actually Matter

A technical SEO checklist 2026 without specific thresholds is just a list of things to worry about. This one is different.

Every item below has a specific pass or fail condition. We've run this checklist across dozens of sites and know which issues actually move rankings versus which ones feel important but don't. We'll tell you both.

Best Technical SEO Checklist 2026

Here are the 47 technical SEO checks in our Technical SEO Checklist 2026, organized by the seven domains that cover everything.

Domain 1: Crawlability and Indexation (12 Technical SEO Checks)

Our Technical SEO Checklist starts with crawlability and indexation. If Google can't crawl and index your pages correctly, nothing else you do matters.

1. robots.txt is valid and not blocking critical pages Test: fetch yourdomain.com/robots.txt. Check that your main content directories aren't accidentally blocked. A single disallow rule blocking "/" has ruined more sites than any algorithm update. Tool: Google's robots.txt Tester in Search Console.

2. XML sitemap is submitted and error-free Your sitemap should contain only indexable URLs (no noindex pages, no 301 redirects, no 404s). Submit it in Search Console. Check it for errors weekly. Maximum recommended sitemap size: 50,000 URLs or 50MB uncompressed.

3. Canonical tags are correct and self-referencing Every page should have a self-referencing canonical tag in the head. Paginated pages should canonicalize to page 1 only if the content is near-identical. Check that dynamic parameter URLs (session IDs, tracking parameters) canonicalize to the clean URL.

4. No redirect chains longer than one hop A to B to C is a two-hop chain. Google follows up to 5 hops but loses PageRank at each step. Every redirect should go directly from the old URL to the final destination. Tool: Screaming Frog with "Response Codes" filter. Flatten everything to single-hop 301s.

5. HTTP to HTTPS redirects are in place Every HTTP URL should 301 to HTTPS. No exceptions. Check for mixed content (HTTP resources on HTTPS pages) with a tool like Why No Padlock.

6. No duplicate content without canonicalization The most common sources: www vs non-www, trailing slash vs no trailing slash, HTTP vs HTTPS, and print-friendly page variants. Each should have a canonical pointing to the preferred version.

7. Index coverage matches expected page count In Search Console, go to Pages and check "Not indexed" for unexpected reasons. "Discovered but not indexed" often means crawl budget issues or Google questioning content quality. "Crawled but not indexed" almost always means thin content.

8. Core pages are within 3 clicks of the homepage Run a crawl with Screaming Frog. Any page more than 3 clicks from the homepage receives dramatically less PageRank. Fix deep pages by adding them to relevant top-level navigation or improving internal linking from high-authority pages.

9. No orphan pages Pages with zero internal links pointing to them receive no internal PageRank. Run a crawl and export pages with 0 inlinks. Either link to them from relevant content or consolidate them into existing pages.

10. Hreflang is correctly implemented for multilingual sites Each language variant must reference all other language variants in its hreflang tags, including itself. Unconfirmed hreflang (where the referenced page doesn't have a reciprocal tag) gets ignored entirely.

11. JavaScript rendering doesn't hide critical content Test with Google's URL Inspection tool in Search Console. Compare the rendered HTML to what a user sees. Critical content including headings, article body, and internal links must be present in the initial server-rendered HTML.

12. Crawl budget is not being wasted on low-value pages If your site has more than 10,000 URLs, crawl budget matters. Block infinite parameter combinations, session ID URLs, and internal search results from crawling via robots.txt. Prioritize crawl budget for your content pages.

Domain 2: Core Web Vitals (8 Technical SEO Checks)

Domain 2 of our Technical SEO Checklist 2026 is about core web vitals of your page. This is where it actually get a little more technical. Again, if you are not familiar with terms, use AI to ask about this article.

Metric	Good	Needs Improvement	Poor
LCP	Under 2.5s	2.5s to 4s	Above 4s
INP	Under 200ms	200ms to 500ms	Above 500ms
CLS	Under 0.1	0.1 to 0.25	Above 0.25

Note: INP replaced FID in March 2024. Sites optimized for FID may be failing INP since the metrics measure fundamentally different things.

13. LCP is under 2.5 seconds in CrUX field data Check Search Console's Core Web Vitals report, not PageSpeed lab data. The most common LCP culprits: unoptimized hero images, render-blocking resources, and slow server response times. Fix: preload the LCP image, use WebP format, and add fetchpriority="high" to the LCP element.

14. INP is under 200ms in CrUX field data INP measures responsiveness across all user interactions, not just the first one. Main thread blocking JavaScript is the primary cause. Fix: defer non-critical JavaScript, use web workers for heavy computation, and break up long tasks above 50ms with scheduler.yield().

15. CLS is under 0.1 in CrUX field data Always provide explicit dimensions for images and video elements. Pre-allocate space for ads and dynamic content. Use font-display: optional or swap with matched fallback font metrics.

16. TTFB (Time to First Byte) is under 800ms While not a direct ranking factor, slow TTFB makes LCP harder to achieve. Fix with server-side caching, a CDN, and by moving to a faster hosting provider.

17. Images use next-generation formats WebP provides 25 to 35 percent smaller file sizes than JPEG at equivalent quality. AVIF provides 40 to 50 percent smaller sizes but has lower browser support (around 96% as of 2026). Use WebP for broad compatibility. All images should have explicit width and height attributes.

18. Render-blocking resources are minimized JavaScript and CSS that block page rendering delay LCP. Use defer or async for non-critical JavaScript. Move critical CSS inline for above-the-fold content. Use media queries on non-critical stylesheets.

19. Font loading doesn't cause layout shift Use font-display: swap with a matched system font fallback (same x-height and width). Or use font-display: optional to serve the system font if the web font isn't cached.

20. No significant third-party script impact Run PageSpeed Insights and check "Third-party code." Ad scripts, chat widgets, and analytics tools frequently contribute 0.5 to 2 seconds of main thread blocking. Audit each one for necessity.

Domain 3: Mobile-First (5 Technical SEO Checks)

Google indexes the mobile version of your site. Your mobile experience is your ranking experience and a major part of our Technical SEO Checklist 2026.

21. Viewport meta tag is correct Every page needs: . Missing this makes your page render at desktop width on mobile.

22. Touch targets are at least 44px by 44px Buttons and links smaller than 44px fail Google's mobile usability guidelines. This includes hamburger menus, footer links, and inline text links that are too small to tap reliably.

23. No horizontal scroll on mobile Content must fit within the viewport width without horizontal scrolling. Fixed-width elements and oversized images are the most common causes.

24. Text is readable without zooming Minimum readable font size is 16px for body text on mobile. Text below 12px is flagged as too small by Google's mobile usability testing.

25. Mobile and desktop content are equivalent Google uses the mobile version for indexing. If your mobile site hides content that's visible on desktop (via display:none or a mobile-specific template that removes sections), that content doesn't get indexed.

Domain 4: Structured Data (7 Technical SEO Checks)

26. Article schema is implemented correctly Include: headline, datePublished, dateModified, author (Person with name and URL), publisher (Organization with name and logo), and description. The author Person entity feeds Google's knowledge graph for E-E-A-T evaluation.

27. FAQPage schema matches visible FAQ content Questions and answers in your FAQPage schema must match the visible content on the page. Google will reject schema that doesn't correspond to visible page content.

28. BreadcrumbList schema is present Provides navigation context to Google and enables breadcrumb rich results in SERPs. Implement on every page with a clear content hierarchy.

29. Organization schema on the homepage Include: name, url, logo, sameAs (links to social profiles), and contactPoint. This establishes your organization entity in Google's knowledge graph.

30. Schema is validated with Rich Results Test Test every schema implementation at search.google.com/test/rich-results before deploying. Common errors: missing required fields, incorrect type hierarchies, and schema on pages where the corresponding content isn't visible.

31. No schema errors in Search Console Check Search Console's Enhancements section regularly. Schema errors can suppress rich results even when the page itself ranks well.

32. Schema is maintained after site updates Schema breaks most often during CMS updates, template changes, and migrations. Add schema validation to your deployment checklist.

Domain 5: Security and Trust (5 Technical SEO Checks)

33. SSL certificate is valid and not expiring soon Check your certificate expiry date. A lapsed SSL certificate takes your site offline instantly and causes significant ranking drops from link value loss during the downtime.

34. HTTPS is the default for all pages Every page, including images, scripts, and APIs, should serve over HTTPS. Mixed content (HTTP resources on HTTPS pages) triggers browser warnings and can suppress rankings.

35. HSTS header is configured HTTP Strict Transport Security tells browsers to always use HTTPS for your domain. Set a max-age of at least 31,536,000 seconds (1 year) once you're confident your HTTPS setup is stable.

36. No sensitive data exposed in public URLs Session tokens, API keys, and personal data should never appear in URLs. These get indexed by Google and appear in Search Console reports.

37. Security headers are configured Implement Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options headers. These protect users and signal to Google that your site takes security seriously.

Domain 6: Performance (5 Technical SEO Checks)

38. Brotli compression is enabled Brotli provides 15 to 25 percent better compression than gzip for HTML, CSS, and JavaScript files. Check with Chrome DevTools Network panel. Look for "content-encoding: br" in response headers.

39. Browser caching is configured Static assets (images, CSS, JavaScript) should have cache-control headers with at least 1 year max-age. Use content hashing in filenames for cache busting.

40. Server response time is under 200ms Measure TTFB with Chrome DevTools or WebPageTest. Slow TTFB is usually caused by slow database queries, no server-side caching, or under-provisioned hosting.

41. Resource hints are used for critical resources Use for the LCP image and critical fonts. Use for third-party domains. Use for origins your page will need immediately.

42. Unused CSS and JavaScript is removed Chrome DevTools Coverage panel shows what percentage of loaded CSS and JavaScript is actually used. Tree-shake unused code and lazy-load JavaScript that's needed only for specific interactions.

Domain 7: Internal Linking and Architecture (5 Technical SEO Checks)

The last domain of our Technical SEO Checklist 2026 is about internal linking and architecture.

43. Pillar pages link to all related cluster content Your most authoritative pages on a topic should link to every related piece of content. This distributes PageRank through your site and signals topical authority to Google.

44. Cluster content links back to the pillar page Every article on a sub-topic should link to the main pillar page on that topic. This creates a connected content cluster that Google evaluates as a unit.

45. Anchor text is descriptive, not generic "Click here," "read more," and "learn more" anchors pass PageRank but provide zero context about the linked page. Use descriptive anchors that include the target page's keyword naturally.

46. No pages have PageRank diluted by too many outbound links A page with 200 internal links per page distributes minimal PageRank per link. Keep footer links to essential navigation only. Move related content links to contextually relevant positions in the content body.

47. Internal link equity reaches your most important pages Run a crawl, export inlink counts, and identify your top 20 commercial or revenue pages. Each should have at least 10 internal links from topically relevant pages. If they don't, add contextual links from your highest-traffic content.

Key Takeaways of Ranking Lens Technical SEO Checklist 2026

The Technical SEO Checklist 2026 starts with crawlability: if Google can't crawl and index your pages, nothing else compounds
INP replaced FID in March 2024 and is harder to pass. Check CrUX field data in Search Console, never PageSpeed lab scores
Orphaned pages with zero internal links receive no PageRank regardless of your domain's external authority
FAQPage schema plus visible FAQ content unlocks rich results that can double your SERP real estate on featured queries
Redirect chains should be flattened to single-hop 301s. Each additional hop loses PageRank and adds latency
Mobile-first indexing means your mobile experience is your ranking experience. Equivalent content on both versions is non-negotiable
Use each domain and step of the Technical SEO Checklist 2026 to copy and insert into your favorite AI tool for any questions or direct improvements in your code.
Run this Technical SEO Checklist 2026 quarterly as part of your site maintenance routine, not just after migrations

Technical SEO Checklist 2026: 47 Checks That Actually Matter

Best Technical SEO Checklist 2026

Domain 1: Crawlability and Indexation (12 Technical SEO Checks)

Domain 2: Core Web Vitals (8 Technical SEO Checks)

Domain 3: Mobile-First (5 Technical SEO Checks)

Domain 4: Structured Data (7 Technical SEO Checks)

Domain 5: Security and Trust (5 Technical SEO Checks)

Domain 6: Performance (5 Technical SEO Checks)

Domain 7: Internal Linking and Architecture (5 Technical SEO Checks)

Key Takeaways of Ranking Lens Technical SEO Checklist 2026

Is your site cited by ChatGPT?

Frequently Asked Questions

Continue Reading

Framer SEO Guide 2026: Get Your Framer Site Found

Lovable HTML Indexing: Why Crawlers See Empty Pages in 2026

Pre-Rendering for Lovable Apps: Step-by-Step Guide 2026