In this article
Technical SEO is the foundation that everything else sits on. Content quality, link authority, and keyword targeting only produce results when the underlying infrastructure works properly. A single misconfigured robots.txt file can undo months of optimization work.
This checklist covers 50 items organized into six categories. Each item includes a brief explanation of why it matters. Use it as a reference for your own audits, or as a benchmark to evaluate the thoroughness of an audit you have received. For a deeper look at technical audits, see our technical SEO audit service.
Crawling and Indexing (Items 1 through 10)
If search engines cannot crawl and index your pages, nothing else matters. These items ensure that search engine bots can discover, access, and process your content.
Crawling & Indexing
01
Robots.txt validation
Confirm that robots.txt exists at the root domain, is accessible (200 status), and does not accidentally block important pages or directories. A single misplaced Disallow rule can prevent entire sections from appearing in search results.
02
XML sitemap availability
Verify that an XML sitemap exists, is referenced in robots.txt, and is submitted to Google Search Console. The sitemap should list all indexable pages and exclude non-canonical URLs, paginated pages, and error pages.
03
Sitemap accuracy
Cross reference the sitemap against actual site pages. Sitemaps that list URLs returning 404, 301, or noindex directives send mixed signals to crawlers and waste crawl budget.
04
Crawl budget efficiency
For large sites, monitor crawl stats in Search Console. Look for patterns where bots spend time crawling low value pages (faceted navigation, session parameters, duplicate filters) instead of important content.
05
Index coverage report
Review Search Console's indexing report for errors, warnings, and excluded pages. Identify any valid pages that are not indexed and investigate the cause: noindex tags, canonical conflicts, or crawl blocks.
06
Meta robots directives
Audit all meta robots tags and X-Robots-Tag headers. Ensure noindex is applied intentionally, not by default (some CMS configurations noindex staging or development pages and carry that setting to production).
07
JavaScript rendering
Test whether critical content is accessible without JavaScript. Use the URL Inspection tool in Search Console to see how Google renders the page. Content that requires JS to display may be invisible to crawlers.
08
Orphan pages
Identify pages that exist on the site but are not linked from any other page. Orphan pages are difficult for crawlers to discover and typically receive very little search visibility.
09
Crawl error monitoring
Check for server errors (5xx), soft 404s, and access denied (403) responses. Persistent crawl errors degrade the overall crawl efficiency for your site.
10
Log file analysis
Review server log files to understand actual bot behavior. Logs reveal which pages bots visit, how often, and which pages they ignore. This data is more reliable than any third party crawl simulator.
Site Architecture (Items 11 through 20)
How your site is structured determines how search engines understand relationships between pages, how link equity flows, and how users navigate your content.
Site Architecture
11
URL structure
URLs should be clean, descriptive, and consistent. Avoid excessive parameters, session IDs, or deeply nested paths. Flat, readable URLs perform better in search and are easier for users to understand.
12
Canonical tags
Every indexable page should have a self-referencing canonical tag. Duplicate content (www vs non-www, HTTP vs HTTPS, parameter variations) should point to the preferred version.
13
Internal linking depth
Important pages should be reachable within three clicks from the homepage. Deep pages receive less crawl attention and less link equity from internal links.
14
Internal link distribution
Audit how internal links are distributed across the site. Look for important pages that have few internal links pointing to them, and low value pages that receive disproportionate linking.
15
Breadcrumb navigation
Implement breadcrumbs on all pages below the homepage level. Breadcrumbs help users understand where they are, help bots understand site hierarchy, and can appear as rich results in search listings.
16
Pagination handling
Paginated content (category pages, product listings) should be handled properly. Use self-referencing canonicals on each paginated page, ensure bots can crawl through all pages, and consider "view all" alternatives for smaller sets.
17
Redirect chains
Identify and resolve redirect chains (A redirects to B, which redirects to C). Each hop in a chain adds latency and can dilute link equity. Aim for direct, single-hop redirects.
18
Broken internal links
Crawl the site for internal links that return 404 or other error codes. Broken links waste crawl budget, degrade user experience, and interrupt the flow of link equity.
19
Navigation consistency
Ensure the primary navigation is consistent across all pages and is implemented in crawlable HTML, not solely through JavaScript or CSS hover states that bots may not trigger.
20
Faceted navigation controls
For e-commerce and directory sites, review how faceted navigation (filters, sorting) creates URLs. Uncontrolled faceted navigation can generate thousands of low value, duplicate pages.
Performance (Items 21 through 30)
Page speed and user experience directly affect rankings. Google's Core Web Vitals are confirmed ranking signals, and slow sites lose users before content even loads.
Performance
21
Largest Contentful Paint (LCP)
Measure the time it takes for the largest visible element to render. Target under 2.5 seconds. Common culprits: unoptimized hero images, render-blocking resources, slow server response.
22
Interaction to Next Paint (INP)
INP replaced First Input Delay in 2024 and measures responsiveness across the full page lifecycle. Target under 200 milliseconds. Long-running JavaScript tasks are the most common cause of poor INP scores.
23
Cumulative Layout Shift (CLS)
Measure visual stability. Target a CLS score under 0.1. Images without dimensions, dynamically injected ads, and web fonts that cause layout reflow are common offenders.
24
Server response time (TTFB)
Time to First Byte should be under 800ms. Slow TTFB indicates hosting infrastructure issues, inefficient database queries, or lack of server-side caching.
25
Image optimization
Check that images are served in modern formats (WebP, AVIF), properly sized for display dimensions, and use lazy loading for below-the-fold images. Images are often the largest payload on any page.
26
Render-blocking resources
Identify CSS and JavaScript files that block the initial render. Inline critical CSS, defer non-essential scripts, and load third party resources asynchronously where possible.
27
Mobile performance
Test performance specifically on mobile networks and devices. Mobile users often have slower connections, and Google's index is mobile-first. A page that scores well on desktop may fail on mobile.
28
Third party script impact
Audit all third party scripts (analytics, chat widgets, ad networks, social embeds). Each script adds load time and can cause layout shifts. Quantify their performance cost and remove any that are not essential.
29
Resource compression
Ensure GZIP or Brotli compression is enabled for all text-based resources (HTML, CSS, JavaScript). Compression typically reduces file sizes by 60 to 80 percent.
30
Browser caching
Verify that static resources have appropriate cache headers. Returning visitors should not need to re-download assets that have not changed. Set long cache durations for versioned files.
Need a professional audit?
Our team covers all of this and more in every Central Audit engagement.
Start your auditSecurity (Items 31 through 38)
Security affects both rankings and user trust. Google has confirmed HTTPS as a ranking signal, and browsers actively warn users about insecure sites.
Security
31
HTTPS implementation
Every page should be served over HTTPS. Verify that the SSL certificate is valid, not expired, and covers all subdomains in use.
32
HTTP to HTTPS redirects
All HTTP URLs should redirect to their HTTPS equivalents with 301 redirects. Test both www and non-www variants to ensure no redirect loops exist.
33
HSTS headers
HTTP Strict Transport Security headers tell browsers to always use HTTPS. Once implemented, this prevents downgrade attacks and eliminates the initial HTTP request before the redirect.
34
Mixed content
Scan for pages served over HTTPS that load resources (images, scripts, stylesheets) over HTTP. Mixed content triggers browser warnings and can prevent pages from being fully secure.
35
Security headers
Check for recommended security headers: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy. These protect against common web attacks.
36
Safe Browsing status
Verify that Google's Safe Browsing database does not flag your site. Malware or phishing flags will severely impact search visibility and display prominent warnings to users.
37
Access control
Ensure admin areas, staging environments, and internal tools are properly restricted. Accidentally indexing an admin login page or staging server is more common than most site owners realize.
38
SSL certificate chain
Verify the complete certificate chain, including intermediate certificates. Incomplete chains cause validation failures in some browsers and can prevent search engines from crawling your site.
Structured Data (Items 39 through 45)
Structured data helps search engines understand your content and can unlock rich results in search listings, increasing click-through rates significantly.
Structured Data
39
Organization schema
Implement Organization or LocalBusiness schema on your homepage. Include name, logo, contact information, and social media profiles. This helps Google's Knowledge Graph understand your brand.
40
BreadcrumbList schema
Add BreadcrumbList markup to match your visual breadcrumb navigation. Breadcrumb rich results improve how your site appears in search and help users understand page context.
41
Article schema
Blog posts and articles should use Article, NewsArticle, or BlogPosting schema with headline, author, date published, date modified, and publisher information.
42
FAQ schema
If your pages contain question and answer content, implement FAQPage schema. Validate that each question-answer pair is visible on the page, as Google penalizes hidden or misleading FAQ markup.
43
Product schema (if applicable)
E-commerce sites should implement Product schema with name, description, price, availability, and review data. This enables product rich results including pricing and star ratings.
44
Schema validation
Test all structured data using Google's Rich Results Test and Schema Markup Validator. Look for errors, warnings, and missing recommended fields. Invalid schema provides no benefit.
45
Structured data consistency
Ensure that the data in your schema matches what is visible on the page. Discrepancies between schema and visible content can result in manual actions or loss of rich result eligibility.
International SEO (Items 46 through 50)
For sites that serve multiple countries or languages, proper internationalization ensures that the right content reaches the right audience.
International SEO
46
Hreflang implementation
If your site has content in multiple languages or targets multiple countries, implement hreflang tags. Each language/country variation should reference all other variations, including itself (self-referencing).
47
Hreflang return links
Verify that hreflang tags are reciprocal. If page A references page B as the Spanish version, page B must reference page A as the English version. Missing return links invalidate the entire hreflang setup.
48
Language and country codes
Use correct ISO 639-1 language codes and ISO 3166-1 Alpha 2 country codes. Common mistakes include using "en-UK" instead of "en-GB" or confusing language with country targeting.
49
Geo-targeting in Search Console
For country specific subdomains or subdirectories, verify that geographic targeting is correctly set in Search Console. This signal helps Google serve the right version to users in each region.
50
Content localization quality
Verify that translated content is genuinely localized, not just machine translated. Auto-translated content without human review often reads unnaturally and can harm user engagement signals.
Using This Checklist Effectively
This checklist is a reference, not a linear process. Start with the areas most relevant to your site and your current challenges. If a sudden decline brought you here, our guide on why your website traffic dropped covers how to diagnose the cause methodically. A local business with a single language site can skip the internationalization section entirely. An e-commerce site with millions of pages should prioritize crawl budget and faceted navigation over most other items.
If working through this list feels overwhelming, that is normal. A professional technical audit covers all of these areas systematically and delivers prioritized, actionable findings rather than a raw checklist. The value of an audit is not just in identifying problems. It is in understanding which problems matter most for your specific situation.
M
Central Audit
SEO Service
SEO strategist with experience auditing sites across ecommerce, SaaS, healthcare, and local business verticals. Every Central Audit engagement is backed by a structured, multi-phase methodology built to surface real revenue impact.
Learn more about our team →