Technical SEO Checklist: 30+ Items to Audit in 2026

If search engines can't find and index your pages, nothing else in SEO matters. Crawlability is the single most critical category in any technical audit because it determines whether your site even exists in search results.

Robots.txt Configuration CRITICAL

What to check: Verify your robots.txt file at yourdomain.com/robots.txt. Confirm it is not blocking important pages, CSS files, JavaScript, or images that Google needs to render your site. Check that it references your XML sitemap.

Why it matters: A misconfigured robots.txt can prevent Google from crawling your entire site or critical sections. We have seen businesses lose 80% of their organic traffic overnight because a developer accidentally pushed a staging robots.txt to production with Disallow: /.

How to fix: Only block pages that genuinely should not be crawled (admin panels, staging environments, duplicate filter pages). Use Google Search Console's robots.txt tester to validate rules. Never block CSS or JavaScript files that are needed for rendering.

Tools: Google Search Console (robots.txt tester), Screaming Frog, Ahrefs Site Audit.

XML Sitemap CRITICAL

What to check: Confirm your sitemap exists, validates against the XML sitemap protocol, includes all important pages, excludes noindexed or redirected URLs, and has been submitted to Google Search Console. Check that <lastmod> dates are accurate.

Why it matters: Sitemaps tell search engines which pages exist and when they were last updated. A sitemap with incorrect URLs, broken pages, or outdated dates sends confusing signals to crawlers. Google has confirmed that sitemaps help with discovery, especially for new or large sites.

How to fix: Generate a dynamic sitemap from your CMS or use a sitemap plugin. Remove any URL that returns a non-200 status code. Keep the sitemap under 50,000 URLs (use sitemap index files for larger sites). Submit via Search Console and reference it in your robots.txt.

Tools: Google Search Console, Screaming Frog, Yoast (WordPress), next-sitemap (Next.js).

Canonical Tags HIGH

What to check: Every indexable page should have a self-referencing canonical tag. Pages with URL parameters (sorting, filtering, pagination) should canonical back to the primary URL. Check for conflicting canonicals where the canonical URL itself has a different canonical.

Why it matters: Without canonical tags, search engines may treat URL variations as separate pages, splitting your ranking signals across duplicates. This dilutes your authority and can cause the wrong version of a page to rank.

How to fix: Add <link rel="canonical" href="..." /> to every page. Use absolute URLs (not relative). Ensure canonicals point to the preferred version (usually the cleanest URL without parameters). Audit for chains where page A canonicals to B, and B canonicals to C.

Noindex Directives CRITICAL

What to check: Crawl your site and check every page for <meta name="robots" content="noindex"> or X-Robots-Tag: noindex HTTP headers. Verify that only pages you intentionally want hidden from search are noindexed.

Why it matters: Accidental noindex tags are one of the most common and damaging technical SEO mistakes. They silently remove pages from search results. If your traffic suddenly drops, check noindex tags before anything else.

How to fix: Remove noindex directives from any page that should appear in search. For staging environments, use password protection or IP blocking instead of noindex to prevent accidental deployment to production. Audit regularly with Screaming Frog.

Crawl Budget Optimization MEDIUM

What to check: Review your crawl stats in Google Search Console (Settings > Crawl Stats). Look for wasted crawl budget on low-value pages: parameter URLs, tag pages, archive pages, or internal search results. Check for excessive redirect chains.

Why it matters: For sites with over 10,000 pages, crawl budget determines how quickly Google discovers and re-indexes your content. Wasting budget on thin or duplicate pages means important content gets crawled less frequently.

How to fix: Block low-value pages from crawling via robots.txt (but do not noindex and block simultaneously). Consolidate thin content. Fix redirect chains (every hop in a chain wastes crawl budget). Improve server response time so Google can crawl more pages per visit.

Google has been clear: page experience matters. Core Web Vitals are not just nice-to-have metrics. They are ranking signals that affect where your pages appear in search results. Slow sites lose visitors, conversions, and rankings.

Largest Contentful Paint (LCP) CRITICAL

What to check: Measure LCP in PageSpeed Insights using both lab and field data. Identify the LCP element on your key pages (usually a hero image, heading, or large text block). Check if server response time, render-blocking resources, or large images are slowing it down.

Why it matters: LCP measures how fast the largest visible content element loads. Users perceive this as page load speed. Pages with LCP over 4 seconds have significantly higher bounce rates. Google recommends 2.5 seconds or faster.

How to fix: Optimize the LCP element first (compress hero images, use WebP/AVIF format, add width/height attributes). Reduce server response time (TTFB under 800ms). Eliminate render-blocking CSS and JavaScript. Use preload hints for critical resources: <link rel="preload">.

Interaction to Next Paint (INP) HIGH

What to check: INP replaced First Input Delay (FID) in March 2024 as the official responsiveness metric. Test interactive elements (buttons, dropdowns, forms) with Chrome DevTools Performance panel. Check for long JavaScript tasks that block the main thread.

Why it matters: INP measures how quickly your page responds to user interactions throughout the entire visit, not just the first click. Poor INP means buttons feel sluggish, forms feel laggy, and users leave frustrated.

How to fix: Break long JavaScript tasks into smaller chunks. Defer non-critical JavaScript. Minimize DOM size (aim for under 1,500 elements). Remove unused third-party scripts. Use requestIdleCallback for non-essential work.

Cumulative Layout Shift (CLS) HIGH

What to check: Observe your pages loading on both desktop and mobile. Do elements jump around as the page loads? Check for images without dimensions, dynamically injected ads, web fonts causing text to reflow, or banners pushing content down.

Why it matters: Layout shifts frustrate users. Imagine clicking a "Read More" link and accidentally hitting "Buy Now" because an ad loaded and pushed the button. A CLS score above 0.1 signals a poor user experience to Google.

How to fix: Always include width and height attributes on images and videos. Reserve space for ads and embeds with CSS aspect-ratio or min-height. Preload web fonts and use font-display: swap. Avoid inserting content above existing content dynamically.

Image Optimization HIGH

What to check: Audit image file sizes across your site. Look for images over 200KB on mobile pages. Check if you are serving modern formats (WebP or AVIF). Verify images use responsive sizing (srcset) and lazy loading for below-the-fold images.

How to fix: Convert images to WebP (30-50% smaller than JPEG with similar quality). Resize images to the maximum display dimension, not larger. Implement lazy loading with loading="lazy". Use a CDN for image delivery. Compress with tools like Squoosh, ShortPixel, or Imagify.

Code Minification & Caching MEDIUM

What to check: Verify CSS and JavaScript files are minified (no unnecessary whitespace or comments in production). Check browser caching headers: static assets should have a cache lifetime of at least one year. Look for unused CSS and JavaScript that loads on every page.

How to fix: Use build tools (Webpack, Vite, esbuild) to automatically minify code. Set Cache-Control: max-age=31536000 headers for static assets. Use code splitting to load only what each page needs. Remove unused CSS with PurgeCSS or similar tools.

Google uses mobile-first indexing for all websites. That means the mobile version of your site is the primary version Google crawls and ranks. If your mobile experience is broken, your desktop rankings suffer too.

Responsive Design CRITICAL

What to check: Test your site at multiple screen sizes: 375px (iPhone SE), 390px (iPhone 14), 412px (Pixel/Android), and 768px (tablet). Look for horizontal scrolling, overlapping text, images breaking out of containers, or content hidden behind other elements.

Why it matters: Over 60% of Google searches happen on mobile devices. A site that does not work properly on phones will lose the majority of its potential traffic. Google demotes non-mobile-friendly pages in mobile search results.

How to fix: Use a responsive CSS framework or design system. Set max-width on containers and images. Use relative units (%, rem, vw) instead of fixed pixel widths. Test with Chrome DevTools device emulation and real devices.

Viewport Configuration CRITICAL

What to check: Every page must have <meta name="viewport" content="width=device-width, initial-scale=1"> in the <head>. Without it, mobile browsers render the page at desktop width and zoom out, making text unreadable.

How to fix: Add the viewport meta tag to your HTML template or layout component. Do not set maximum-scale=1 or user-scalable=no as these prevent users from zooming, which is an accessibility violation.

Touch Targets MEDIUM

What to check: Buttons, links, and interactive elements should be at least 48x48 pixels with at least 8px of spacing between them. Run the Mobile Usability report in Google Search Console to identify pages with touch target issues.

Why it matters: Small or crowded touch targets cause accidental taps, frustrating mobile users. Google flags this in the Mobile Usability report and it affects your page experience signal.

How to fix: Set minimum padding on links and buttons. Use CSS min-height: 48px; min-width: 48px; on interactive elements. Add margin between adjacent clickable elements. Test by tapping elements on a real phone.

Mobile Content Parity HIGH

What to check: Verify that your mobile site shows the same content as your desktop site. Content hidden behind "Read more" toggles, tabs, or accordions on mobile should still be in the source code. Check that images, videos, and structured data are present on mobile.

Why it matters: With mobile-first indexing, content that only appears on desktop may not be indexed. If your mobile version hides half your content behind JavaScript-dependent interactions, Google may not see it.

How to fix: Use responsive design instead of separate mobile sites. Ensure all content is in the DOM on mobile (even if visually collapsed). Verify with the URL Inspection tool's "rendered page" view in Search Console.

How your pages connect to each other determines how search engines understand your site's hierarchy, how link authority flows, and how quickly new pages get discovered and indexed. Poor architecture wastes crawl budget and buries important pages. The best marketing agencies fix architecture issues before touching anything else.

URL Structure HIGH

What to check: URLs should be short, descriptive, and use hyphens to separate words. Avoid dynamic parameters when possible. Use a logical hierarchy: /services/seo-agency/ not /page?id=372&cat=seo. Check for duplicate content caused by URLs with and without trailing slashes, or www and non-www variants.

How to fix: Establish URL conventions and enforce them in your CMS. Choose trailing slash or no trailing slash and redirect the other. Pick www or non-www and redirect the other. Keep URLs under 75 characters when possible. Use lowercase only.

Internal Linking CRITICAL

What to check: Every important page should be reachable within 3 clicks from the homepage. Use descriptive anchor text (not "click here"). Ensure links point to the canonical version of URLs. Look for pages with very few internal links pointing to them.

Why it matters: Internal links are one of the strongest signals you can control. They tell Google which pages are important, establish topical relationships, and distribute ranking authority. Pages with more internal links from relevant pages tend to rank higher. A solid internal linking strategy is central to effective SEO for any industry.

How to fix: Audit your internal link distribution with Screaming Frog or Ahrefs. Add contextual links from related content. Create hub pages that link out to cluster content. Aim for 10-20 internal links per long-form article.

Breadcrumbs MEDIUM

What to check: Verify breadcrumbs display on every page below the homepage level. Check that the breadcrumb trail matches the site hierarchy. Implement BreadcrumbList schema markup so breadcrumbs appear in search results.

How to fix: Add breadcrumb navigation to your page templates. Use structured data (BreadcrumbList schema) that matches the visible breadcrumbs. Ensure each breadcrumb level links to the correct parent page.

Site Depth & Orphan Pages HIGH

What to check: Run a crawl and check the click depth of every page. Pages more than 3 clicks from the homepage receive less crawl priority and less link authority. Identify orphan pages (pages in your sitemap that have zero internal links pointing to them).

How to fix: Flatten your site architecture by adding category or hub pages. Link to deep pages from higher-level pages. Add orphaned pages to relevant navigation, category pages, or related content sections. Remove or consolidate truly unnecessary pages.

On-page technical elements bridge the gap between content and infrastructure. These are the code-level signals that help search engines understand what your pages are about and how to display them in search results.

Schema Markup (Structured Data) HIGH

What to check: Test your pages with Google's Rich Results Test or Schema.org validator. Key schema types to implement: Organization (homepage), LocalBusiness (local businesses), Article (blog posts), FAQPage (FAQ sections), BreadcrumbList (breadcrumbs), and Product or Service pages.

Why it matters: Schema markup helps Google understand your content and can earn rich results (FAQ dropdowns, star ratings, breadcrumbs, how-to steps) that dramatically increase click-through rates. Pages with rich results can see 20-30% higher CTR.

How to fix: Add JSON-LD structured data in the <head> or <body> of your pages. Use Google's Structured Data Markup Helper to generate the code. Validate every schema implementation with the Rich Results Test before deploying.

Heading Hierarchy HIGH

What to check: Every page should have exactly one H1 tag that includes the primary keyword. Headings should follow a logical hierarchy: H1 > H2 > H3 > H4 with no skipped levels. Do not use heading tags for visual styling (use CSS classes instead).

Why it matters: Heading hierarchy helps search engines understand content structure and topic organization. It also improves accessibility for screen readers. Google uses headings to identify subtopics and match content to specific queries.

How to fix: Audit headings with Screaming Frog (H1 tab shows missing, duplicate, or multiple H1s). Restructure headings to reflect a clear outline. Use H2 for major sections, H3 for subsections within those sections.

Meta Tags HIGH

What to check: Every indexable page needs a unique title tag (50-60 characters, primary keyword front-loaded) and meta description (120-160 characters, includes CTA). Check for duplicate titles and descriptions across your site. Verify Open Graph tags for social sharing.

How to fix: Write unique, keyword-targeted titles and descriptions for every page. Use your CMS or framework's metadata features. Audit with Screaming Frog to identify duplicates, missing tags, or tags that are too long/short.

Hreflang Tags MEDIUM

What to check: If your site targets multiple languages or regions, verify hreflang tags on every page. Each language version should reference all other versions (including itself). Check for return tag errors where page A references page B but B does not reference A.

How to fix: Implement hreflang tags in the HTML <head>, HTTP headers, or XML sitemap. Always include an x-default hreflang for the fallback version. Use the ISO 639-1 language codes and ISO 3166-1 Alpha 2 country codes.

Pagination MEDIUM

What to check: If your site uses paginated content (blog archives, product listings), verify that each paginated page has a self-referencing canonical (not pointing to page 1). Ensure Google can discover all paginated pages through internal links.

How to fix: Use self-referencing canonical tags on each paginated page. Link to the next and previous pages. Consider using "load more" or infinite scroll with proper implementation (ensure crawlable URLs exist for each page). Include all paginated URLs in your sitemap.

Security and server infrastructure form the bedrock of your site's trustworthiness. Google considers HTTPS a ranking factor, and server issues like slow response times or incorrect status codes can prevent your content from ranking altogether.

HTTPS Implementation CRITICAL

What to check: Every page should load over HTTPS. Check that HTTP URLs 301-redirect to HTTPS. Verify your SSL certificate is valid and not expired. Test with SSL Labs (ssllabs.com) for a comprehensive security grade.

Why it matters: HTTPS is a confirmed Google ranking signal. Browsers display "Not Secure" warnings on HTTP pages, which destroys user trust. HTTPS also protects user data and is required for many modern web features (service workers, geolocation, camera access).

How to fix: Install an SSL certificate (most hosts offer free Let's Encrypt certificates). Set up 301 redirects from all HTTP URLs to HTTPS. Update internal links to use HTTPS. Update your sitemap and canonical tags to use HTTPS URLs.

Mixed Content HIGH

What to check: After migrating to HTTPS, check for mixed content warnings where your HTTPS page loads resources (images, scripts, stylesheets) over HTTP. Use Chrome DevTools Console to identify mixed content errors and warnings.

How to fix: Update all resource URLs to HTTPS or use protocol-relative URLs (//example.com/image.jpg). Check embedded iframes, third-party scripts, and CDN URLs. Use the Content-Security-Policy header with upgrade-insecure-requests as a safety net.

404 Errors & Broken Links HIGH

What to check: Crawl your site and identify all URLs returning 404 status codes. Check Google Search Console's Pages report for "Not found (404)" errors. Look for internal links pointing to 404 pages and external links pointing to your 404 pages.

Why it matters: Broken links waste crawl budget and create dead ends for users and search engines. Internal 404s pass zero link authority. External backlinks pointing to 404 pages are wasted ranking signals.

How to fix: 301 redirect broken URLs to the most relevant existing page. Fix internal links to point directly to working pages. Create a custom 404 page that helps users find what they need. For expired content with backlinks, redirect to a relevant alternative.

Redirect Chains & Loops HIGH

What to check: Identify redirect chains (A redirects to B, B redirects to C, C redirects to D). Check for redirect loops (A redirects to B, B redirects to A). Verify that all redirects use 301 (permanent) status codes, not 302 (temporary), unless the redirect is genuinely temporary.

How to fix: Update all redirect chains so A redirects directly to the final destination. Fix loops by removing one of the circular redirects. Convert 302 redirects to 301 when the move is permanent. Update internal links to point directly to the final URL (skip the redirect entirely).

Server Response Codes MEDIUM

What to check: Verify that all live pages return 200 status codes. Removed pages should return 404 or 410 (gone). Moved pages should return 301. Check for soft 404s (pages that return a 200 status but display a "Page not found" message). Monitor server errors (500, 502, 503) in Search Console.

How to fix: Configure your server to return appropriate status codes. Fix soft 404s by either restoring the content or returning a true 404/410 status code. Investigate and resolve recurring 5xx errors. Set up uptime monitoring to catch server issues quickly.

You do not need every tool on this list. Start with Google Search Console (free) and one crawler. Add specialized tools as your needs grow.

For most small-to-mid-sized businesses, Google Search Console combined with Screaming Frog covers 90% of what you need. If you want ongoing monitoring with automated alerts, Ahrefs or Semrush Site Audit tools are worth the investment.

Not every technical SEO item carries equal weight. Here is how to prioritize your audit based on impact. Fix Critical items first because they can prevent your site from appearing in search results entirely. Then move through High, Medium, and Low priority items. Understanding how long SEO takes helps set realistic expectations for when fixes translate to ranking improvements.

A common mistake is trying to fix everything at once. Start with the Critical items. If you are not sure how to choose an SEO agency to help, look for one that can explain their technical audit process and prioritization framework clearly.