Technical SEO Audit Checklist: 50 Checks for a Healthy Site

Technical SEO issues are invisible until they're expensive.

A page buried behind a noindex tag, a redirect chain adding 2 seconds to load time, a canonical pointing to the wrong URL — none of these show up in your content or design. They show up months later as rankings that plateau or drop without explanation.

After running technical audits across hundreds of sites, we've found that most teams have the same 15-20 recurring issues. The checklist below covers every one of them, organized by category so you can work through it systematically — not just poke at random settings hoping something improves.

This is not a theoretical checklist. Every check here has a direct impact on crawlability, indexation, or ranking performance.

---

How to use this checklist#

Work through categories in order. Crawling and indexation issues take precedence — there's no point optimizing page speed on a page that isn't indexed. Within each category, checks are ordered from highest to lowest impact.

For each issue you find, note it in a spreadsheet with: the affected URL(s), the severity (blocks indexation / hurts performance / low priority), and who owns the fix. That triage step saves more time than the audit itself.

---

Crawling and indexation#

These are the most critical checks. Crawl errors and indexation problems directly prevent pages from appearing in search results.

1. Verify your robots.txt isn't blocking important pages

Request yourdomain.com/robots.txt directly. Look for Disallow: rules that inadvertently block CSS, JavaScript, or important URL patterns. A misconfigured robots.txt after a site migration is one of the most common causes of sudden ranking drops.

2. Check for unintentional noindex tags

Use a crawler to scan every page for <meta name="robots" content="noindex"> and X-Robots-Tag: noindex HTTP headers. Staging environments often get deployed with noindex tags still on. In Google Search Console, check Index Coverage for "Excluded by noindex tag" to see what Google has discovered.

3. Confirm canonical tags are correct

Every page should have a self-referencing canonical, or a canonical pointing to the preferred version. Check for: canonical tags pointing to redirected URLs, canonical tags pointing to 404 pages, rel=canonical on paginated pages incorrectly pointing to page 1 when the content is different, and inconsistent canonical usage (HTTP vs HTTPS, trailing slash vs no trailing slash).

4. Audit redirect chains

A redirect chain (A → B → C → D) loses link equity and adds latency. Use a crawler to find redirect chains longer than one hop. Fix by updating the source URL to point directly to the final destination.

5. Find and fix 404 errors with internal links pointing to them

A 404 that gets no internal links is a minor issue. A 404 that has 50 internal links pointing to it is wasting crawl budget and losing link equity on every page that links to it. In Google Search Console under Index > Coverage, filter for "Not found (404)" and cross-reference with which pages link to those URLs.

6. Check for duplicate content without canonicals

Common sources: HTTP vs HTTPS versions, www vs non-www, trailing slash vs no trailing slash, URL parameters creating duplicate pages. Each pair of duplicates should have a canonical designating the preferred version, and a 301 redirect for non-canonical variants where practical.

7. Verify XML sitemap is accurate and submitted

Your sitemap should only include URLs that: are canonicalized to themselves, return 200 status codes, and are indexable (no noindex). Remove redirected URLs, 404s, and noindexed pages from the sitemap. Submit the sitemap in Google Search Console if you haven't.

8. Check crawl depth for priority pages

Use a crawler to measure how many clicks separate your most important pages from the homepage. Priority pages (category pages, pillar content, key landing pages) should be within 3-4 clicks. Pages at depth 5+ are at risk of infrequent crawling.

---

On-page fundamentals#

9. Audit title tags for uniqueness and length

Each page needs a unique title tag. Duplicate titles are a content signal problem — they suggest the pages cover the same topic. Target 50-60 characters. Titles truncated in SERPs lose their message; titles too short miss keyword opportunities.

10. Check meta descriptions

According to Ahrefs' 2024 study of 1 million domains, 72.9% of sites are missing meta descriptions on at least some pages. Google rewrites meta descriptions frequently, but a well-written description that matches search intent improves CTR on queries where Google does use it. Target 150-160 characters.

11. Audit H1 tags

Every page should have exactly one H1. Pages with no H1 miss a clear topical signal. Pages with multiple H1s send conflicting signals. The H1 should contain or closely match the primary keyword.

12. Check for missing or duplicate title tags

Duplicate title tags are often a sign of template issues — CMS configurations that generate the same title across category/tag pages. Identify duplicates with a crawler and fix at the template level.

13. Verify canonical self-referencing on indexable pages

Every page intended for indexation should have a self-referencing canonical (pointing to itself). This closes the loophole where syndication or parameter variants might be assigned as the canonical unintentionally.

14. Check heading hierarchy

H2s and H3s should form a logical outline of the page content. Pages with a single H1 and then no H2s (just H3s, H4s, and paragraphs) have a heading structure that looks broken to crawlers. Heading tags don't directly affect rankings, but they improve crawlability of page structure and user navigation.

15. Audit image alt text

Alt text is both an accessibility requirement and an SEO signal — it tells Google what an image depicts. According to Ahrefs' 2024 domain study, missing alt text is one of the most common technical issues across the web. Every meaningful image should have descriptive alt text with a natural keyword reference where relevant. Decorative images can have empty alt attributes (alt="").

16. Verify open graph tags for social sharing

OG tags (og:title, og:description, og:image) control how pages appear when shared on social platforms. Missing OG tags don't affect Google rankings, but pages with no OG image get low-quality previews that reduce click-through on social shares.

---

Site performance and Core Web Vitals#

Core Web Vitals became a ranking factor in 2021. As of 2024, only about 56% of websites pass all Core Web Vitals thresholds — meaning a CWV failure is still a meaningful differentiator.

17. Check Largest Contentful Paint (LCP)

LCP measures how long the largest visible content element takes to load. The threshold for "good" is under 2.5 seconds. Common causes of poor LCP: unoptimized hero images, render-blocking JavaScript, slow server response times, and missing preload hints for critical images.

18. Check Interaction to Next Paint (INP)

INP replaced First Input Delay in March 2024 and measures responsiveness throughout a page session, not just the first interaction. The threshold is under 200ms. Poor INP is usually caused by heavy JavaScript execution, large layout recalculations, or third-party scripts blocking the main thread.

19. Check Cumulative Layout Shift (CLS)

CLS measures visual stability — how much page elements shift unexpectedly as the page loads. The threshold is under 0.1. Common causes: images without specified dimensions, ads that expand into content, dynamically injected content above the fold.

20. Test server response time (TTFB)

Time to First Byte should be under 800ms. High TTFB points to server-side issues: slow database queries, no server-side caching, or geographic distance from the server to the user. A CDN addresses the geographic issue. Server-side caching addresses query performance.

21. Audit render-blocking resources

JavaScript and CSS that block rendering delay how quickly the browser can display page content. In PageSpeed Insights, check the "Eliminate render-blocking resources" audit. Defer non-critical JavaScript; inline critical CSS where possible.

22. Check image compression and modern formats

Images are the largest contributor to page weight on most sites. Verify all images are compressed and served in modern formats (WebP or AVIF) rather than JPEG/PNG. A CDN with automatic image optimization handles this without manual effort for each image.

23. Enable browser caching

Returning visitors should load cached assets from their browser rather than re-downloading them. Check that your server or CDN sets appropriate Cache-Control headers for static assets (CSS, JS, images). Assets that rarely change should have long cache TTLs (1 year for versioned files).

---

Mobile usability#

Mobile now accounts for approximately 59% of global web traffic. Google uses mobile-first indexing — it crawls and indexes the mobile version of your site, not the desktop version.

24. Verify mobile-first indexing isn't causing content gaps

If your desktop site has content that's hidden on mobile or not present at all, Google won't see it during indexation. Use Google Search Console's URL Inspection tool on mobile rendering mode to confirm key content is visible on mobile.

25. Check tap target sizing

Buttons and links should be large enough to tap accurately on a touchscreen — Google's recommendation is at least 48×48 pixels with adequate spacing between elements. Small tap targets generate "Tap targets too small" issues in PageSpeed Insights.

26. Audit viewport configuration

Every page needs the <meta name="viewport" content="width=device-width, initial-scale=1"> tag. Without it, mobile browsers render the page at desktop width and scale it down, which creates the zoomed-out appearance that fails mobile usability checks.

27. Test font legibility on mobile

Text smaller than 12px renders as unreadable on mobile without zooming. Google flags this as a mobile usability issue. Minimum body text is 16px; anything smaller for secondary content should be at least 12px.

28. Check for mobile-specific interstitials

Full-screen interstitials that appear immediately on page load on mobile (email capture popups, app download banners) trigger Google's intrusive interstitial penalty. Banners that occupy a reasonable portion of the screen and are dismissible are fine. Full-screen popups on mobile are not.

---

Schema and structured data#

According to the HTTP Archive 2024 Web Almanac, only about 30% of pages use Schema.org structured data — despite rich results generating a 58% click-through rate versus 41% for non-rich results.

29. Validate existing schema with Google's Rich Results Test

Use Google's Rich Results Test on key pages to confirm existing schema parses correctly and doesn't have validation errors. Schema errors don't cause ranking penalties, but they do prevent the page from being eligible for rich results.

30. Add Article or BlogPosting schema to blog content

Blog posts and editorial content should have Article or BlogPosting schema with datePublished, dateModified, author (with @type: Person and optionally sameAs pointing to a credible profile), and publisher fields. This helps Google accurately surface authorship and freshness signals.

31. Add FAQPage schema where applicable

Pages with genuine FAQ sections can include FAQPage schema. Note that Google deprecated FAQ rich results for most sites in August 2023 — they no longer appear in SERPs for most websites, only for authoritative health and government sources. However, FAQ schema still helps AI models parse and cite Q&A content.

32. Implement BreadcrumbList schema

Breadcrumb schema helps Google understand page hierarchy and often appears in search results below the URL. Implement it on all pages that use breadcrumb navigation. This is a low-effort addition with consistent SEO benefit.

33. Add Organization schema on the homepage

Organization schema on the homepage with your name, url, logo, and sameAs links (to social profiles, Wikipedia, Wikidata if applicable) establishes entity identity for your brand. This is foundational for Knowledge Graph eligibility and AI visibility.

34. Check for conflicting or duplicate schema

Multiple schema blocks on the same page that define the same entity can create conflicting signals. Use a single, complete schema block per entity rather than fragmenting schema across multiple scripts.

---

Internal linking and site architecture#

35. Find orphaned pages

Orphaned pages have no internal links pointing to them. They receive zero link equity and may not be crawled at all. Export your URL list from a crawler and cross-reference it with your internal link data to find pages with zero inlinks.

36. Audit anchor text distribution

Anchor text is a relevance signal for the linked page. Check that your most important pages receive internal links with descriptive, keyword-containing anchor text — not generic "click here" or "read more" anchors.

37. Identify internal links pointing to redirected URLs

Links pointing to URLs that 301 redirect waste a redirect hop and lose a small amount of equity. Update internal links to point directly to the final destination URL.

38. Check for broken internal links

Internal links pointing to 404 pages create a dead end for users and crawlers. A crawler run will surface these immediately. Fix by either restoring the linked page, pointing the link to a replacement, or removing the link.

39. Verify hub pages link to all cluster content

In a pillar/cluster content architecture, the pillar page should link to every cluster page in the topic group. Missing links in this structure leave cluster pages disconnected from the authority signal the pillar page accumulates. Audit pillar pages manually to confirm all cluster posts are linked.

40. Check that cluster content links back to pillar pages

The link should flow both ways: pillar → clusters and clusters → pillar. A cluster post that doesn't link back to its pillar page breaks the topical authority loop that hub-and-spoke architecture depends on.

---

HTTPS and security#

41. Confirm site-wide HTTPS with correct redirect

All HTTP requests should 301 redirect to HTTPS. The redirect should go from HTTP to HTTPS in a single hop — not HTTP → HTTPS → WWW or any other multi-hop chain.

42. Check for mixed content

Mixed content occurs when an HTTPS page loads resources (images, scripts, stylesheets) over HTTP. Browsers block or warn on mixed content; Google uses HTTPS as a ranking signal. Check Chrome DevTools console on key pages for mixed content warnings.

43. Verify SSL certificate validity and renewal

An expired SSL certificate causes browser warnings that kill traffic instantly. Confirm your certificate is valid and set up auto-renewal. Certificate expiry rarely gives advance warning in analytics.

---

Advanced crawl checks#

44. Audit hreflang implementation (international sites)

For sites targeting multiple languages or regions, each page should have hreflang annotations listing all language/region variants including the x-default fallback. Common errors: hreflang pointing to pages that don't exist, bidirectional hreflang links missing (if page A points to page B, page B must point back to page A).

45. Check pagination handling

For paginated content (blog archives, product category pages), confirm paginated pages are indexable if they contain unique content, or use canonical to page 1 if content is consolidated. Don't use rel="prev" / rel="next" — Google deprecated support for these in 2019.

46. Identify thin or low-word-count pages

Pages under 300 words often have quality signals that hurt crawl quality scores across the site. Audit pages below a word count threshold. Some legitimately warrant short treatment (contact pages, privacy policies) — others should be expanded or consolidated into longer posts.

47. Check for parameter-based URL duplication

URL parameters (?sort=price&color=blue) create near-duplicate pages that fragment indexation and waste crawl budget. Use canonical tags on parameter URLs to consolidate onto the clean URL, and configure Google Search Console's URL parameter tool if applicable.

48. Verify site speed on real devices

Lab data from tools like Lighthouse is useful but doesn't match real-user experience. Check Google Search Console's Core Web Vitals report for field data from actual Chrome users — it often reveals mobile performance issues that don't show up in lab tests.

49. Audit broken external links

Broken outbound links don't hurt your rankings directly, but they create bad user experiences and signal content neglect. Tools like Screaming Frog will surface 404 responses from external links. Fix by updating to a working URL or removing the link.

50. Confirm Google Search Console coverage matches expectations

Go to Index > Pages in Google Search Console and review the breakdown: indexed, not indexed, and excluded. "Crawled - currently not indexed" and "Discovered - currently not indexed" are both concerning at scale — they suggest Google is finding pages but choosing not to index them, often a content quality signal.

---

Prioritizing what to fix#

Not every issue above deserves the same urgency. Use this framework:

Fix immediately (blocking traffic):

• Pages you intend to rank are noindexed or blocked by robots.txt
• HTTPS certificate expired or mixed content causing browser warnings
• Sitemap returning errors or pointing to 404 pages
• Redirect loops

Fix within 2 weeks (hurting performance):

• Core Web Vitals failures on high-traffic pages
• Redirect chains on pages with significant external links
• Orphaned pages that should be receiving traffic
• Canonical tags pointing to wrong URLs

Fix in next audit cycle (clean-up):

• Missing meta descriptions on low-traffic pages
• Missing alt text on image-heavy pages
• Thin content on cluster pages
• Minor schema validation warnings

---

How often to audit#

Run a full audit every 3-6 months. For large sites (10,000+ pages), monthly crawls are worth the investment.

Trigger an immediate audit after:

• A CMS migration or redesign
• A significant drop in organic traffic (check for newly introduced noindex or robots.txt blocks first)
• Adding a major new section to the site
• A domain migration or HTTPS move

Between audits, keep Google Search Console's Coverage and Core Web Vitals reports open. Both surface new issues continuously and don't require a full crawl to catch problems.

---

How Climer supports technical monitoring#

Climer monitors crawl errors, broken internal links, and Core Web Vitals data on a continuous basis — surfacing issues as they appear rather than requiring manual quarterly audits. When writing new content, Climer's agent flags orphaned pages and suggests internal link placements to keep your link graph intact as the site grows.

---

Related guides#

• Technical SEO Audit: The Complete Guide — deeper explanation of each audit category and how to run the full process
• Site Architecture for SEO: How to Structure a Website That Ranks — the structural decisions that determine crawlability
• Internal Linking Strategy: How to Build a Link Equity Framework — the execution layer for checks 35-40 above
• Schema Markup for SEO: Which Types Actually Matter — complete guide to implementing structured data