← Back to Insights

Technical SEO Checklist 2026: 47 Points That Actually Matter

Skip the fluff. This is the technical SEO checklist we use for every audit — focused on issues that actually impact rankings.

Technical SEO Checklist 2026: 47 Points That Actually Matter

Why another technical SEO checklist?

Every SEO blog has a technical checklist. Most of them list 100+ items, half of which don't matter for 90% of sites. You end up overwhelmed, checking boxes that have zero impact on rankings.

This checklist is different. It's what I actually check during audits — focused on issues that actually impact rankings. I've prioritized by impact, so you can focus on what matters first.

Fair warning: this is comprehensive. Use it as a reference, not something to implement in one afternoon.


Critical issues (fix immediately)

These issues can tank your rankings or prevent indexing entirely. Check these first.

1. Indexability

  • Robots.txt blocking important pages? — Check for Disallow rules that might accidentally block key content. Common mistake: staging site rules left in production.
  • Noindex tags on pages that should rank? — Search for noindex in page source. CMS plugins sometimes add these automatically.
  • Crawl budget being wasted? — Large sites: check if Googlebot is spending time on low-value pages (filters, sorts, internal search results).

2. Site architecture

  • Important pages more than 3 clicks from homepage? — Deep pages get crawled less frequently and pass less authority.
  • Orphan pages? — Pages with no internal links. Find them in Screaming Frog or Sitebulb.
  • Crawl traps? — Infinite URL patterns (calendars, filters) that waste crawl budget.

3. Technical errors

  • 5xx errors on important pages? — Server errors prevent indexing. Check Search Console's Coverage report.
  • Soft 404s? — Pages that show "not found" content but return 200 status. Google sees these as low-quality.
  • Redirect chains longer than 2 hops? — A → B → C → D loses PageRank and slows crawling.

4. Core Web Vitals failures

  • LCP over 2.5s on mobile? — Largest Contentful Paint. Usually caused by slow servers, large images, or render-blocking resources.
  • CLS over 0.1? — Cumulative Layout Shift. Usually caused by images without dimensions, dynamic content, or late-loading fonts.
  • INP over 200ms? — Interaction to Next Paint (replaced FID). Heavy JavaScript is usually the culprit.

High priority (fix this week)

5. Duplicate content

  • HTTP/HTTPS versions both accessible? — Should redirect to one version (HTTPS).
  • www and non-www both accessible? — Pick one, redirect the other.
  • Trailing slash consistency? — /page and /page/ should not both work (or use canonical).
  • Parameter URLs creating duplicates? — ?sort=price, ?color=blue creating duplicate content?
  • Pagination properly handled? — Use rel="canonical" to the main page or self-referencing canonicals.

6. Canonical issues

  • Every indexable page has a canonical? — Self-referencing if original, pointing to original if duplicate.
  • Canonicals are absolute URLs?https://example.com/page not /page
  • Canonical matches the preferred URL version? — If you prefer non-trailing slash, canonical should too.
  • No redirect to canonical URL? — Canonical + redirect = unnecessary. Pick one.

7. Mobile optimization

  • Mobile-friendly test passes? — Use Google's Mobile-Friendly Test tool.
  • Same content on mobile and desktop? — Google uses mobile-first indexing. Hidden content on mobile = hidden from Google.
  • Tap targets large enough? — Buttons at least 48px, with 8px spacing.
  • No horizontal scrolling? — Content fits viewport width.

8. HTTPS security

  • SSL certificate valid and not expiring soon? — Check expiration date.
  • No mixed content? — HTTPS page loading HTTP resources.
  • HSTS enabled? — Forces HTTPS connections. Nice to have, not critical.

Medium priority (fix this month)

9. URL structure

  • URLs are human-readable? — /products/blue-widget not /p?id=12345
  • URLs are concise? — Under 75 characters is ideal.
  • Lowercase URLs? — /Page and /page are technically different URLs.
  • No special characters? — Avoid &, %, #, etc. in URLs.
  • Keywords in URLs? — Minor ranking factor, but helps CTR.

10. Internal linking

  • Important pages have many internal links? — More internal links = more importance signal.
  • Anchor text is descriptive? — "Click here" tells Google nothing. Use descriptive anchors.
  • No broken internal links? — 404s from internal links waste crawl budget.
  • Related content linked? — Topical clusters should interlink.

11. XML sitemap

  • Sitemap exists and is submitted to Search Console? — Basic requirement.
  • Sitemap only includes indexable pages? — No 404s, redirects, or noindexed pages.
  • Sitemap is up to date? — Auto-generated is best.
  • Sitemap under 50MB / 50,000 URLs? — Split into multiple if larger.
  • Sitemap in robots.txt?Sitemap: https://example.com/sitemap.xml

12. Page speed optimization

  • Images compressed and properly sized? — Don't serve 2000px images for 400px containers.
  • Using modern image formats? — WebP or AVIF instead of PNG/JPG where supported.
  • Images lazy loaded below the fold? — But NOT lazy loading the LCP image.
  • CSS and JS minified? — Remove whitespace and comments.
  • Render-blocking resources minimized? — Defer non-critical CSS/JS.
  • Using a CDN? — Especially for static assets.

13. Structured data

  • Schema markup implemented where relevant? — Article, Product, FAQ, LocalBusiness, etc.
  • Schema validates without errors? — Use Google's Rich Results Test.
  • Schema matches visible content? — Don't add FAQ schema for hidden FAQs.

Lower priority (ongoing maintenance)

14. Crawl optimization

  • Log files analyzed regularly? — See what Googlebot actually crawls.
  • Crawl budget not wasted on low-value pages? — Block faceted navigation, search results, etc.
  • Fresh content crawled quickly? — Important pages should be crawled within days of updates.

15. International SEO (if applicable)

  • Hreflang implemented correctly? — Bidirectional references required.
  • x-default set? — Fallback for users not matching any hreflang.
  • No conflicts between hreflang and canonical? — Canonical should be to self or language equivalent.

16. JavaScript SEO (if JS-heavy site)

  • Content visible without JavaScript? — Test in browser with JS disabled.
  • Critical content not lazy loaded? — Google might not scroll/interact.
  • Internal links are crawlable?<a href="..."> not JS click handlers.
  • URL changes update the actual URL? — SPAs should use History API.

17. Log-based checks

  • Googlebot crawl frequency healthy? — Decreasing crawls can signal issues.
  • Important pages getting crawled? — Not just homepage and categories.
  • Error spikes in logs? — 5xx or 4xx errors correlating with traffic drops.

Tools for technical audits

You don't need all of these. Pick based on your needs and budget.

Free tools

  • Google Search Console: The essential tool. Coverage, performance, Core Web Vitals.
  • PageSpeed Insights: Core Web Vitals testing.
  • Mobile-Friendly Test: Quick mobile check.
  • Rich Results Test: Schema validation.
  • Chrome DevTools: Network, performance, rendering issues.

Paid tools

  • Screaming Frog: Best desktop crawler. Free up to 500 URLs.
  • Sitebulb: Great visualization and prioritization.
  • Ahrefs Site Audit: Cloud-based, good for ongoing monitoring.
  • Semrush Site Audit: Similar to Ahrefs, integrates with their suite.
  • Lumar (DeepCrawl): Enterprise-level crawling.

Audit workflow I use

Here's my actual process for technical audits:

Phase 1: Quick health check (30 min)

  1. Check Search Console for critical errors
  2. Review Core Web Vitals status
  3. Run PageSpeed Insights on 3-5 key pages
  4. Check robots.txt and XML sitemap
  5. Quick mobile test on homepage

This catches the most urgent issues quickly.

Phase 2: Full crawl (2-4 hours)

  1. Run Screaming Frog or Sitebulb on full site
  2. Export and analyze: status codes, canonicals, titles, meta descriptions
  3. Check for duplicate content patterns
  4. Review internal link distribution
  5. Identify crawl traps or orphan pages

Phase 3: Prioritization (1 hour)

  1. Score issues by impact and effort
  2. Group into: Critical / High / Medium / Low
  3. Create actionable tickets for dev team
  4. Estimate timeline for fixes

Phase 4: Monitoring setup

  1. Set up Search Console alerts
  2. Schedule monthly re-crawls
  3. Create dashboard for Core Web Vitals tracking

Common mistakes I see

Obsessing over minor issues

Missing alt tags don't tank rankings. H1 in wrong order doesn't tank rankings. Focus on issues that actually matter: indexability, speed, mobile, duplicates.

Fixing symptoms, not causes

Manually redirecting 100 broken links when the real problem is a CMS generating bad URLs. Fix the system, not just the output.

No prioritization

Spending days optimizing images while critical pages are noindexed. Always start with indexability and crawl issues.

Audit once, never again

Sites change. Developers push code. CMSs update. Technical SEO requires ongoing monitoring, not one-time audits.


Summary: what actually matters

If you remember nothing else, remember this:

  1. Can Google crawl and index your important pages? (Robots.txt, noindex, crawl budget)
  2. Is your site fast enough? (Core Web Vitals)
  3. Is your site mobile-friendly? (Mobile-first indexing)
  4. Is your site free of duplicate content issues? (Canonicals, redirects)
  5. Is your site architecture logical? (Internal linking, hierarchy)

Everything else is optimization on top of these fundamentals. Get these right first.

Start your audit today:

  1. Open Search Console → Coverage. Any critical errors?
  2. Run PageSpeed Insights on your homepage. Core Web Vitals passing?
  3. Check robots.txt. Anything blocked that shouldn't be?
  4. Run a mobile-friendly test on your top landing page.

These four checks take 15 minutes and catch the most common critical issues.


FAQ

How often should I do a technical audit?

Full audit: quarterly or after major site changes. Quick health check: monthly. Search Console monitoring: weekly. Critical sites should have automated monitoring alerting on issues.

Which issues should I fix first?

Always prioritize indexability issues first (pages being blocked or noindexed). Then critical errors (5xx, Core Web Vitals failures). Then duplicates and canonicals. Everything else comes after.

Do I need expensive tools?

For small sites (<500 pages), Screaming Frog free version + Google Search Console is enough. For larger sites, you'll want paid crawling tools. The ROI is usually worth it.

How long does it take to see results from technical fixes?

Depends on the fix. Removing a noindex can show results in days. Core Web Vitals improvements might take a few weeks to reflect in rankings. Broader improvements typically show within 1-3 months.