Site Health Score: Turning a Technical Audit Into a Fix List

Search Architect and Founder at SEO AI Regent. Engineering dual-axis content scoring and AI answer-engine optimization for enterprise content teams.

Introduction

A site health score is a severity-weighted summary of technical audit findings, usually starting at 100 and losing 8, 5, 3, or 1 points for critical, high, medium, or low issues. It turns a noisy crawler report into an ordered fix list by showing which defects cost the most visibility.

What is a site health score?

• A site health score is not a vanity grade. It is a compressed view of technical debt: every detected issue removes points according to severity, so the final number reflects both count and business risk. A page with one critical crawl block can score lower than a site with twenty low-priority metadata gaps.
• The useful part is explainability. If a report says 78, stakeholders need to see whether that came from 8-point critical defects, 5-point high issues, or many 1-point notices. Without that breakdown, the score becomes a leaderboard instead of a work queue.
• How the 8/5/3/1 deduction model works
• Start at 100. Critical issues deduct 8 points because they can stop crawling, indexing, or rendering. High issues deduct 5, medium issues deduct 3, and low issues deduct 1. The model is intentionally coarse: it rewards fixing blockers before polish, and it prevents a hundred tiny notices from outranking one broken canonical.
• A good implementation also caps duplicate issue types or groups them by template. Otherwise one bad CMS pattern can create 400 identical deductions and make the score look unrecoverable. Grouping keeps the fix list tied to root causes, not URL counts.
• SeverityDeductionTypical examplesOwnerCritical8Blocked crawling, noindex on key templates, server errorsEngineeringHigh5Redirect chains, canonical conflicts, broken internal linksEngineering or SEOMedium3Duplicate titles, missing structured data, slow templatesContent or SEOLow1Missing alt text, minor metadata, image compressionContent or design

How do I turn audit findings into a prioritized fix list?

• Export findings with severity, affected URL count, template, and owner. Then sort by points lost, not by issue name. A 5-point redirect chain affecting 12,000 URLs usually beats a 3-point missing alt attribute on 40 images, even if the latter is easier to explain in a meeting.
• Next, convert each issue into a ticket with acceptance criteria: expected status code, canonical target, schema validation result, or Core Web Vitals threshold. This is where an audit methodology matters; see the documented approach at audit methodology.
• Severity buckets and owner handoff
• Critical and high issues go to engineering or platform owners because they usually involve templates, server rules, or rendering. Medium issues often belong to content operations. Low issues can be batched into quarterly cleanup. The score improves fastest when ownership follows severity, not department politics.
• Track points recovered per sprint. If a fix removes a critical issue across a template, the score should move by the grouped deduction, not by one URL. That makes progress visible and prevents teams from gaming the metric with one-off edits.

The 20-issue taxonomy behind an explainable score

• A 20-issue taxonomy is small enough to audit consistently and large enough to cover the failure modes that affect discovery. The exact labels vary by crawler, but the categories should be stable: crawl, index, canonicalization, redirects, status codes, robots, sitemaps, internal links, orphan pages, duplicates, titles, meta descriptions, headings, structured data, images, performance, mobile, security, internationalization, and rendering.
• Stability matters more than comprehensiveness. If every release renames issues, historical score trends become meaningless. A fixed taxonomy lets you compare March and September without translating vendor language.
• #Issue familyTypical severityWhy it matters1Crawl accessCriticalPrevents discovery of important URLs2IndexabilityCriticalRemoves pages from search results3CanonicalizationHighConsolidates or splits ranking signals4RedirectsHighWastes crawl budget and link equity5Status codesCriticalReturns errors to users and crawlers6Robots directivesHighAccidentally blocks important content7XML sitemapsMediumOmits or mislabels crawl candidates8Internal linksMediumDistributes authority and discovery9Orphan pagesMediumHides pages from crawl paths10Duplicate contentMediumSplits relevance across URLs11Title tagsMediumWeakens snippet relevance12Meta descriptionsLowAffects click-through, not ranking directly13Heading structureLowClarifies page topic hierarchy14Structured dataMediumEnables rich results and entity clarity15ImagesLowAffects accessibility and page weight16PerformanceHighImpacts Core Web Vitals and UX17Mobile usabilityHighAffects mobile-first indexing18HTTPS and securityCriticalProtects users and trust signals19InternationalizationMediumPrevents wrong-language results20JavaScript renderingHighHides content from crawlers

What is a good health score number?

• There is no universal good number because crawlers weight issues differently. As a working benchmark, 90 or above usually means no critical blockers and few high-severity defects. 70 to 89 often means important issues remain. Below 70, expect crawl waste, index bloat, or rendering problems that can suppress visibility.
• A score of 92 is good if the missing 8 points are low-severity notices. It is not good if those 8 points come from one critical issue that the tool capped or grouped. Always read the deduction list before celebrating the headline.

Site health score calculator and free checks

• A site health score calculator applies the same deduction logic to a crawl. Free tools can be useful for a first pass, but check whether they expose severity, affected URLs, and exportable evidence. A number without evidence is a marketing widget, not an audit.
• Best free website audit tools
• Google Search Console is free and authoritative for indexing, but it is not a full crawler. Lighthouse covers performance and accessibility. Screaming Frog's free tier crawls 500 URLs. Ahrefs Webmaster Tools offers site audit features for verified sites. Use one broad crawler plus Search Console, then reconcile differences instead of trusting one score.
• For provenance and change tracking, a product such as provenance tracking can help teams record which fix changed which metric. That matters when a score drops after a deployment and nobody knows which template changed.

How do I find my SEO score?

• You can find an SEO score by running a crawl in a site audit tool, connecting Google Search Console, or using a website checker that reports technical issues. Start with your own domain verification so the tool can crawl authenticated or blocked areas and report accurate status codes.
• If you need a repeatable pipeline, validate crawl output before scoring it. A pipeline such as pipeline validation illustrates the idea: collect raw signals, normalize them, then score. The same discipline prevents a health score from changing because a crawler's default settings changed.

Does a perfect 100 mean you are done?

• No. A perfect score only means the audited issue set is clean. It does not prove content quality, search intent match, link equity, or conversion performance. Treat 100 as a cleared runway, not a destination.
• The contrarian take: chasing 100 can be wasteful. If the last 5 points require rewriting alt text on 3,000 archived images, the engineering time may produce less value than one new indexable template or one fixed canonical. Score is triage, not a KPI.

Frequently asked questions

• What is a good health score number? A good site health score is usually 90 or above when no critical or high-severity issues remain. The exact threshold depends on the crawler's deduction model, so read the issue breakdown before relying on the headline.
• Is an SEO score of 92 good? An SEO score of 92 is good if the missing points come from low-severity notices rather than one critical defect. Always check whether the deduction is grouped by issue type or counted per URL.
• How do I find my SEO score? Run a verified site audit in a crawler or connect Google Search Console to see indexing and technical signals. Use a tool that exports affected URLs and severity so the score can be turned into tickets.
• How can I check the health of my website for free? You can check website health for free with Google Search Console, Lighthouse, and limited crawlers such as Screaming Frog's 500-URL tier. Combine at least two sources because free tools measure different parts of technical SEO.
• How is a site health score calculated? A site health score usually starts at 100 and deducts 8, 5, 3, or 1 points for critical, high, medium, or low issues. Grouping duplicate issues by template keeps the score explainable and prevents one CMS bug from dominating it.
• What is the 20-issue taxonomy? The 20-issue taxonomy is a stable set of technical audit categories covering crawl, index, canonical, redirect, status, robots, sitemap, links, duplicates, metadata, headings, schema, images, performance, mobile, security, internationalization, and rendering. Stable names make score trends comparable over time.
• Does a 100 site health score guarantee rankings? No, a 100 site health score only means the audited technical issue set is clean. Rankings also depend on content relevance, authority, user signals, and competition.
• Should I fix low-severity issues before critical ones? No, fix critical and high-severity issues first because they can block crawling, indexing, or rendering. Low-severity issues can be batched after blockers are resolved.
• {"@context":"https://schema.org","@graph":[{"@type":"Article","headline":"Site Health Score: Turning a Technical Audit Into a Fix List","author":{"@type":"Person","name":"seoairegent"},"datePublished":"2026-11-03T19:25:55.915Z","description":"Learn how a site health score turns technical audit findings into a prioritized fix list using 8/5/3/1 severity deductions and a 20-issue taxonomy."},{"@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is a good health score number?","acceptedAnswer":{"@type":"Answer","text":"A good site health score is usually 90 or above when no critical or high-severity issues remain. The exact threshold depends on the crawler's deduction model, so read the issue breakdown before relying on the headline."}},{"@type":"Question","name":"Is an SEO score of 92 good?","acceptedAnswer":{"@type":"Answer","text":"An SEO score of 92 is good if the missing points come from low-severity notices rather than one critical defect. Always check whether the deduction is grouped by issue type or counted per URL."}},{"@type":"Question","name":"How do I find my SEO score?","acceptedAnswer":{"@type":"Answer","text":"Run a verified site audit in a crawler or connect Google Search Console to see indexing and technical signals. Use a tool that exports affected URLs and severity so the score can be turned into tickets."}},{"@type":"Question","name":"How can I check the health of my website for free?","acceptedAnswer":{"@type":"Answer","text":"You can check website health for free with Google Search Console, Lighthouse, and limited crawlers such as Screaming Frog's 500-URL tier. Combine at least two sources because free tools measure different parts of technical SEO."}},{"@type":"Question","name":"How is a site health score calculated?","acceptedAnswer":{"@type":"Answer","text":"A site health score usually starts at 100 and deducts 8, 5, 3, or 1 points for critical, high, medium, or low issues. Grouping duplicate issues by template keeps the score explainable and prevents one CMS bug from dominating it."}},{"@type":"Question","name":"What is the 20-issue taxonomy?","acceptedAnswer":{"@type":"Answer","text":"The 20-issue taxonomy is a stable set of technical audit categories covering crawl, index, canonical, redirect, status, robots, sitemap, links, duplicates, metadata, headings, schema, images, performance, mobile, security, internationalization, and rendering. Stable names make score trends comparable over time."}},{"@type":"Question","name":"Does a 100 site health score guarantee rankings?","acceptedAnswer":{"@type":"Answer","text":"No, a 100 site health score only means the audited technical issue set is clean. Rankings also depend on content relevance, authority, user signals, and competition."}},{"@type":"Question","name":"Should I fix low-severity issues before critical ones?","acceptedAnswer":{"@type":"Answer","text":"No, fix critical and high-severity issues first because they can block crawling, indexing, or rendering. Low-severity issues can be batched after blockers are resolved."}}]}]}

FAQ