What is Site Health Score?

Why It Matters

Technical SEO involves tracking a lot of individual signals at once, broken links, crawl errors, indexation rate, page speed, and more, and checking each one separately doesn't scale well for a quick status check. Site health score solves that by rolling them into a single composite number, giving a team an immediate read on whether a site's technical condition is improving or deteriorating without digging through every underlying report. That makes it useful as a trend line, tracked consistently within the same tool, it shows whether cleanup work is actually moving the needle, like a site's score climbing after a project fixes broken links and resolves indexation issues. It's also useful for flagging when something needs deeper investigation, a sudden score drop signals it's time to check the individual underlying signals for what specifically changed. Because different tools weight the underlying signals differently, comparing scores across platforms can be misleading, so its real value is as a consistent internal benchmark rather than an industry-standard number.

Example

An SEO audit tool scores a site at 68 out of 100, driven down primarily by 340 broken internal links and a 78% indexation rate. After a cleanup project fixes the broken links and resolves the indexation issues, the same audit tool rescoring the site three months later shows a score of 89. Because the formula and weighting differ between SEO tools, site health scores are best tracked as a trend over time within the same tool rather than compared as an absolute number across different platforms.

Frequently Asked Questions

• What signals typically feed into site health score?

  Common inputs include broken links, crawl errors, duplicate content, indexation issues, and Core Web Vitals performance, combined into a single weighted composite score.

• Can site health scores be compared across different SEO tools?

  Not reliably, since each tool uses its own formula and weighting for the underlying signals, so a score of 75 in one tool isn't directly comparable to a score of 75 in another.

• How often should site health score be checked?

  Most teams check it on a regular cadence, such as weekly or monthly, and especially after major site changes like migrations, redesigns, or large content pushes that could introduce new technical issues.

• What does a dropping site health score usually indicate?

  It signals that one or more underlying technical signals have worsened, such as new crawl errors or broken links appearing, and warrants digging into the individual reports to find the specific cause.

• Is a higher site health score always better?

  Generally yes as a directional signal, but because the score is a composite, two sites can have the same score for very different underlying reasons, so it should prompt a look at the individual signals rather than be treated as the full picture on its own.