Warning: Trying to access array offset on false in /home/crystalm/public_html/wp-content/plugins/pro-elements/modules/dynamic-tags/tags/post-featured-image.php on line 39

Warning: Trying to access array offset on false in /home/crystalm/public_html/wp-content/plugins/pro-elements/modules/dynamic-tags/tags/post-featured-image.php on line 39

Warning: Trying to access array offset on false in /home/crystalm/public_html/wp-content/plugins/pro-elements/modules/dynamic-tags/tags/post-featured-image.php on line 39

Warning: Trying to access array offset on false in /home/crystalm/public_html/wp-content/plugins/pro-elements/modules/dynamic-tags/tags/post-featured-image.php on line 39
Technical SEO Checklist: A Complete Audit Guide - Crystal Media

Technical SEO Checklist: A Complete Audit Guide


Warning: Trying to access array offset on false in /home/crystalm/public_html/wp-content/plugins/pro-elements/modules/dynamic-tags/tags/post-featured-image.php on line 39

Technical SEO is the infrastructure that allows search engines to discover, crawl, understand, and rank your content. Without a solid technical foundation, even the most well-written, thoroughly researched content will underperform its potential.

This checklist covers every major technical SEO element  organised by category and prioritised by impact. Use it as a systematic audit framework, whether you are reviewing a site for the first time or conducting a quarterly technical health check.

For context on how technical SEO fits within a broader strategy, see our guide on How to Increase Website Traffic.

How to Use This Checklist

Work through each category in order. Categories earlier in the list (crawlability, indexability) affect everything downstream. Fixing a page speed issue on a page that is not indexed is wasted effort. Prioritise the checklist from top to bottom.

For each item:

  •  Pass — no action required
  •  Needs attention — monitor or schedule improvement
  •  Fail — address as a priority before moving on

Tools referenced throughout this checklist:

For a guide to choosing and using these tools, see our article on SEO Tools for Website Growth.

Section 1: Crawlability

Crawlability determines whether search engines can access and navigate your website. If Googlebot cannot crawl your pages, they cannot be indexed or ranked.

1.1 Robots.txt File

  • Robots.txt file exists at yourdomain.com/robots.txt
  • Disallow directives are intentional — no important pages or sections are accidentally blocked from crawling
  • Sitemap is referenced in robots.txt ( Sitemap: https://yourdomain.com/sitemap.xml )
  • Googlebot is not blocked — ensure Disallow: / does not appear under User-agent: Googlebot or User-agent: *

How to check: Navigate directly to yourdomain.com/robots.txt in your browser and review the contents. Also check GSC > Settings > Robots.txt.

Common mistake: A staging environment robots.txt (which typically blocks all crawlers) accidentally carried over to a production site. This blocks Google from indexing the entire website.

1.2 XML Sitemap

  • XML sitemap exists at yourdomain.com/sitemap.xml (or as declared in robots.txt)
  • Sitemap is submitted in Google Search Console (GSC > Indexing > Sitemaps)
  • Sitemap is dynamically updated — new pages are automatically added
  • Sitemap contains only indexable pages — no noindex pages, redirect URLs, or error pages
  • Sitemap file is under 50MB and fewer than 50,000 URLs (use multiple sitemaps if needed)
  • Last modified dates are accurate — reflect genuine content updates, not automated false refreshes

1.3 Internal Linking and Crawl Depth

  • No orphaned pages — every published page is linked from at least one other page on the site
  • Crawl depth is reasonable — important pages are reachable within three clicks from the homepage
  • No broken internal links (404s) — use Screaming Frog to identify and fix
  • Redirect chains are minimised — A redirects to B, not A → B → C → D
  • Navigation menus link to key category and hub pages

How to check: Run a Screaming Frog crawl and filter by “Response Code 404” for broken links. Check crawl depth in the Crawl Depth report.

1.4 Pagination

  • Paginated pages are crawlable if they contain unique content (e.g. product category pages)
  • Self-referencing canonicals are used correctly on paginated series where appropriate
  • Rel=”prev” and rel=”next” implementation reviewed (deprecated by Google but still sometimes used)

Section 2: Indexability

Indexability determines whether pages Google crawls are eligible to appear in search results.

2.1 Noindex Tags

  • No important pages are accidentally set to noindex — check title tags, HTTP headers, and meta robots tags
  • Noindex is intentionally applied where appropriate: thank-you pages, admin pages, duplicate content pages, staging subfolders
  • Noindex is not applied to pages you want to rank — cross-reference with GSC > Indexing > Pages > “Excluded” to identify unexpected noindex tags

High-risk scenario: A CMS update, plugin change, or developer setting can apply sitewide noindex in minutes. Always check GSC after any major site update.

2.2 Canonical Tags

  • Every page has a canonical tag pointing to the preferred URL
  • Self-referencing canonicals are present on all pages (the canonical points to itself)
  • Canonical URLs use the correct protocol (https://, not http://)
  • Canonical URLs include or exclude trailing slashes consistently (match your preferred URL format)
  • No canonical conflicts — page A canonicals to page B while page B canonicals to page A
  • Paginated pages do not all canonical to page 1 (this prevents Google from indexing subsequent pages)

2.3 Duplicate Content

  • No significant duplicate content between pages on the same site
  • URL parameters that create duplicate pages are handled (via GSC parameter handling or canonical tags)
  • WWW vs non-WWW is canonicalised — choose one version and redirect the other consistently
  • HTTP vs HTTPS is consistent — HTTP should 301 redirect to HTTPS

How to check: Run a Screaming Frog crawl and review the “Duplicate Content” tab. Use GSC’s Coverage report to identify pages flagged as duplicate.

Section 3: Page Speed and Core Web Vitals

Page speed is a confirmed Google ranking factor. Core Web Vitals — the specific performance metrics Google uses — measure real-world user experience.

3.1 Core Web Vitals

  • LCP (Largest Contentful Paint) under 2.5 seconds — the time it takes for the largest visible element (usually a hero image or headline) to load
  • INP (Interaction to Next Paint) under 200ms — how quickly the page responds to user input (replaced FID in March 2024)
  • CLS (Cumulative Layout Shift) under 0.1 — how much the page layout shifts unexpectedly during loading

How to check: Google PageSpeed Insights provides both lab data (simulated) and field data (real users) for any URL. GSC > Experience > Core Web Vitals shows sitewide performance.

3.2 Page Speed Improvements

  • Images are compressed and in modern formats (WebP or AVIF preferred over JPEG/PNG)
  • Images have explicit width and height attributes (prevents CLS from layout shifts as images load)
  • Lazy loading is applied to images below the fold (loading=”lazy” attribute)
  • Render-blocking JavaScript and CSS are minimised — defer non-critical scripts
  • Browser caching is enabled — sets cache expiration headers for static assets
  • A Content Delivery Network (CDN) is in use for sites with geographically distributed audiences
  • Server response time (TTFB) is under 600ms
  • Unnecessary third-party scripts are removed or deferred (chat widgets, analytics, ad scripts)

Section 4: Mobile Usability

Google uses mobile-first indexing — the mobile version of your site is primary for ranking purposes.

4.1 Mobile Responsiveness

  • Site passes Google’s Mobile-Friendly Test (search.google.com/test/mobile-friendly)
  • Text is readable without zooming on a standard smartphone screen
  • Tap targets (buttons, links) are adequately sized — at least 48×48 CSS pixels, with sufficient spacing
  • Content is not wider than the screen — no horizontal scrolling required
  • Interstitials and pop-ups do not obstruct main content on mobile (Google penalises intrusive interstitials)

How to check: GSC > Experience > Mobile Usability shows all mobile errors across your site. Also review on actual devices across iOS and Android.

4.2 Mobile Page Speed

  • Core Web Vitals pass on mobile (often harder to achieve than desktop due to lower processing power)
  • Images are appropriately sized for mobile (do not serve desktop-sized images to mobile users)
  • Font sizes are legible without zooming (minimum 16px for body text is recommended)

Section 5: URL Structure and Redirects

5.1 URL Format

  • URLs are short and descriptive — include the target keyword, avoid unnecessary parameters
  • URLs use hyphens to separate words (not underscores or spaces)
  • URLs are lowercase — avoid mixed case which can create duplicate URLs
  • URL structure is logical and consistent — reflects site hierarchy where applicable

5.2 Redirects

  • 301 redirects are in place for all removed or changed URLs
  • No redirect chains (A → B → C should be consolidated to A → C)
  • No redirect loops (A → B → A)
  • 302 redirects are only used for genuinely temporary redirects
  • All redirects resolve correctly — use Screaming Frog’s Redirect Chains report to verify

Section 6: HTTPS and Security

6.1 SSL Certificate

  • Site is fully served over HTTPS — no mixed content (HTTP resources on HTTPS pages)
  • SSL certificate is valid and not expired
  • HTTP URLs 301 redirect to HTTPS equivalents
  • HSTS (HTTP Strict Transport Security) is implemented where appropriate

How to check: Click the padlock icon in your browser’s address bar. Use SSL Labs’ free SSL test at ssllabs.com/ssltest for a detailed certificate report.

Section 7: Structured Data (Schema Markup)

Structured data helps search engines understand your content type and can unlock rich results that increase click-through rates.

7.1 Schema Implementation

  • Appropriate schema types are implemented for your content:
    • Article or BlogPosting — for editorial content
    • FAQPage — for pages with Q&A sections
    • HowTo — for step-by-step guides
    • LocalBusiness — for location-based businesses
    • Product — for e-commerce product pages
    • BreadcrumbList — for navigation breadcrumbs
  • Schema is valid — test with Google’s Rich Results Test (search.google.com/test/rich-results)
  • No schema spam — only implement schema that accurately reflects the page content
  • Schema is implemented in JSON-LD format (Google’s preferred method)

Section 8: International SEO (If Applicable)

  • Hreflang tags are correctly implemented for sites targeting multiple languages or regions
  • Hreflang tags are reciprocal — if page A references page B, page B must reference page A
  • Language and country codes are correct in hreflang attributes (e.g. en-GB, fr-FR)
  • Correct URL structure is used for international content (subdomains, subdirectories, or ccTLDs)

Post-Audit Prioritisation

After completing the checklist, prioritise fixes using this framework:

Critical (fix immediately):

  • Sitewide noindex or robots.txt blocks
  • SSL certificate errors
  • Server errors (5xx) on key pages
  • Missing or broken XML sitemap

High priority (fix within 30 days):

  • Core Web Vitals failures on high-traffic pages
  • Broken internal links and redirect chains
  • Mobile usability errors
  • Missing canonical tags

Medium priority (fix within 90 days):

  • Schema markup implementation
  • Image compression and lazy loading
  • URL structure inconsistencies
  • Orphaned pages

Ongoing:

  • Monitor Core Web Vitals monthly
  • Review crawl stats quarterly
  • Rerun full technical audit twice yearly

For guidance on the broader SEO strategy these technical fixes support, see our article on How to Improve Website SEO. If you are conducting this audit as part of a broader site evaluation, our SEO Audit Checklist covers on-page and content dimensions alongside the technical elements here.

FAQ: Technical SEO Checklist

How often should I run a technical SEO audit? A full technical audit should run at least twice a year — and immediately after any major site change (migration, redesign, CMS update). Google Search Console should be reviewed weekly for new errors.

What is the most critical technical SEO issue to fix first? Any issue that prevents indexing — such as an accidental sitewide noindex tag, a robots.txt blocking Googlebot, or a broken SSL certificate — is the highest priority because it prevents all content from appearing in search results.

Do I need technical SEO skills to run an audit? Basic audits using Google Search Console and PageSpeed Insights are accessible to non-technical users. Deep technical audits involving crawl data, log file analysis, and server configuration typically require developer involvement or a specialist SEO tool.

How does technical SEO affect Core Web Vitals? Core Web Vitals are the performance dimension of technical SEO. They measure real-world user experience in terms of load speed, interactivity, and visual stability — all of which Google uses as direct ranking signals alongside traditional technical factors.

What happens if I have duplicate content? Duplicate content splits ranking signals between multiple URLs, potentially diluting the authority of each. It can also confuse search engines about which version to index and rank. Use canonical tags to consolidate signals to the preferred version.

Key Takeaways

  • Crawlability must be confirmed before any other technical fix — if Google cannot access your site, nothing else matters
  • The noindex tag is one of the most dangerous technical settings on any website — verify it is only applied intentionally
  • Core Web Vitals (LCP, INP, CLS) are confirmed ranking signals and should be monitored monthly
  • Mobile usability is evaluated on the mobile version of your site — which is also the primary version Google uses to rank pages
  • Canonical tags, redirects, and URL consistency prevent authority dilution from duplicate content
  • Structured data (schema markup) is an underutilised opportunity to unlock rich results and improve click-through rates

Conclusion

Technical SEO is not glamorous  but it is foundational. Every ranking achieved by your content, every backlink you earn, and every piece of optimization you apply delivers less value when technical problems are suppressing your site’s performance.

Work through this checklist systematically, prioritise critical fixes first, and build a habit of monthly and quarterly technical reviews. The sites that dominate organic search are rarely those with the best content alone — they are those where excellent content sits on top of a technically sound foundation.

For the broader strategic context, return to our hub guide on How to Increase Website Traffic. And if you are ready for a comprehensive review that covers on-page and content dimensions alongside technical elements, see our SEO Audit Checklist.

Facebook
Twitter
LinkedIn
Telegram

Leave a Reply

Your email address will not be published. Required fields are marked *

Join Our Newsletter

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.