OrganiqHow is a site health score calculated? The formulas of four audit tools and a score weighted by traffic
· Organiq · third-party facts carry source and date in the text
A site health score is one number, usually from 0 to 100, that sums up the problems an audit tool found on a site; each tool counts it in its own way. Organiq (organiqgeo.com) publishes two formulas, one by pages and one by Search Console impressions, and this page sets them beside Ahrefs, Semrush, Sitebulb and Screaming Frog.
What is a site health score?
A site health score is one number, usually between 0 and 100, that sums up how clean a site is according to the checks of one audit tool. Ahrefs and Organiq define it as the share of crawled pages with no error. Semrush and Sitebulb describe a score built from the issues found and their weight. Two tools can score the same site differently, because their checks and weights differ.
How do four audit tools calculate a site health score?
Ahrefs and Organiq write the calculation down. Semrush and Sitebulb say what the score is based on, and the pages read give no formula. On the Screaming Frog pages read there is no single score. Read on November 10, 2026; the table gives each calculation in the words of its source, and an empty cell means no open source gave it.
| Tool | Single score | The calculation, as the source writes it | What goes in | Source and reading date |
|---|---|---|---|---|
| Organiq, by pages | Yes (two scores) | Page health = 100 × internal HTML pages crawled with no error ÷ internal HTML pages crawled. | Crawled internal HTML pages. A page with at least one error counts as unhealthy; warnings, notices and site-wide issues are listed and stay out. | get_site_audit answer, formula version 1 |
| Organiq, by traffic | Yes (two scores) | Traffic health = 100 × Search Console impressions (last 28 days) of pages with no error ÷ impressions of the crawled pages; with no impressions in the period there is no traffic score. | The same errors, weighted by the Search Console impressions of each page in the last 28 days. | get_site_audit answer, formula version 1 |
| Ahrefs Health Score | Yes | divide it by the total number of internal URLs and multiply it by 100, where the number divided is the crawled internal URLs with no error. | Crawled internal URLs. Errors alone lower the score; warnings and notices do not affect Site Audit health score at all. | help.ahrefs.com, article 1424673, read November 10, 2026; the page shows September 3, 2026 beside the author. |
| Semrush Site Health | Yes (a percentage from 0% to 100%) | takes into account the number of errors and warnings found during the crawl, in relation to the number of performed checks. The pages read give no formula. | Errors and warnings, errors with more weight. One page says the score does not depend on the number of pages crawled, and that excluded checks stop counting in later crawls. | semrush.com/kb/114 and semrush.com/kb/540, read November 10, 2026; neither page shows a date. |
| Sitebulb Audit Score | Yes (Audit Score, plus an SEO, a Security and a Page Speed score) | calculated based on the amount, type, and priority of types of Hints triggered by the crawled pages. The pages read give no formula or weights. | Hints, by priority (Critical and High weigh more than Medium and Low) and the share of URLs affected, as the release notes describe; the scores depend on the choices made when the project was set up. | Sitebulb support article and Sitebulb release notes, version 3 (the score arrived in version 3.0.8, October 9, 2019), read November 10, 2026. |
| Screaming Frog | None on the pages read | Issues carry a High, Medium or Low priority label; Search Console data enters as columns and filters. | issues page and configuration guide (read in part), November 10, 2026. |
How does Ahrefs calculate its Health Score?
Ahrefs publishes the calculation: the crawled internal URLs with no error, divided by the total number of internal URLs, times 100. Errors alone count; warnings and notices do not affect the score. The article gives an example of 2 pages with errors out of 10, which is 80. It also names four bands: 0–30 Weak, 31–70 Fair, 71–90 Good and 91–100 Excellent. Source: help.ahrefs.com, read November 10, 2026.
How does Semrush calculate Site Health?
Semrush describes Site Health as a percentage between 0% and 100% that takes into account the errors and warnings found in the crawl, in relation to the number of checks performed; errors weigh more than warnings. One page adds that the score does not depend on the number of pages crawled. The pages read give no formula. Sources: semrush.com/kb/540 and semrush.com/kb/114, read November 10, 2026.
How does Sitebulb calculate its Audit Score?
Sitebulb says its scores are calculated from the amount, type and priority of the Hints triggered by the crawled pages. The release notes that introduced the score add the share of URLs affected and say Critical and High Hints weigh more than Medium and Low. Neither page gives a formula or weights. Sources: Sitebulb support article and Sitebulb release notes, version 3, read November 10, 2026.
How does Screaming Frog score a site?
On the pages read on November 10, 2026, the issues page and the configuration guide (read in part), Screaming Frog shows no overall score for a crawl. Each issue carries a High, Medium or Low priority label, and Search Console data enters as columns and filters. This says what those pages show; it is not a statement about every page of the tool.
How does Organiq calculate its two health scores?
Organiq (organiqgeo.com) calculates two scores from one crawl. Page health is the share of crawled internal HTML pages with no error. Traffic health is the share of Search Console impressions of the last 28 days that land on pages with no error. Errors on a page alone count, 17 of the 48 checks. The text below is the formula as the tool returns it.
Page health = 100 × internal HTML pages crawled with no error ÷ internal HTML pages crawled. Traffic health = 100 × Search Console impressions (last 28 days) of pages with no error ÷ impressions of the crawled pages; with no impressions in the period there is no traffic score. Warnings, notices and site-wide issues are listed and do not enter the calculation.
No check can be switched off. The crawl and the plan limit are in SEO site audit in Claude and ChatGPT.
Why can two sites with the same page score differ?
The page score gives every page the same weight: a page with 30,000 impressions counts as much as one with 100. The traffic score weights each page by its impressions. In the example below, both sites have 2 pages with an error out of 20, so page health is 90 on both, but traffic health is 37.5 on site A and 99.78 on site B.
This is an example with invented numbers, not a measurement. The arithmetic: 90 = 100 × (20 − 2) ÷ 20; site A, 37.5 = 100 × 36,000 ÷ 96,000; site B, 99.78 = 100 × 90,000 ÷ 90,200.
| Example (invented numbers) | Site A | Site B |
|---|---|---|
| Pages crawled | 20 | 20 |
| Pages with an error | 2 | 2 |
| Impressions of each page with an error | 30,000 | 100 |
| Impressions of each page with no error | 2,000 | 5,000 |
| Page health | 90 | 90 |
| Traffic health | 37.5 | 99.78 |
What do the scores look like on the demo site and on a real site?
Calling get_site_audit with site: "demo" returns the fictional audit of a demonstration site: 42 pages crawled, page health 83.33 and traffic health 84.21. 7 pages have an error and hold 56,420 of 357,224 impressions. The data is fictional; the call needs no account, so anyone can check these numbers.
On November 9, 2026, the audit of organiqgeo.com crawled 81 pages: page health 100 and traffic health 100. That is a measurement of our own site, run once, not an average of sites; the 37 pages with warnings stayed out of the score.
What is a good site health score?
There is no threshold shared by all tools. Ahrefs publishes four bands: 0–30 Weak, 31–70 Fair, 71–90 Good, 91–100 Excellent (help.ahrefs.com, read November 10, 2026). Sitebulb's release notes say green shows above 90, with no numeric scale (Sitebulb release notes, version 3). The Semrush and Screaming Frog pages read give no bands, and Organiq publishes none.
A score of 100 means no error in the checks of that tool. It is not a position in Google and it promises no traffic.
Can a site health score rise without fixing anything?
On the pages read, yes, in two documented ways. Semrush says an excluded check stops counting in later crawls and that turning on JavaScript rendering may change the score (semrush.com/kb/114). Sitebulb says its scores depend on the choices made when the project was set up (Sitebulb release notes, version 3). Ahrefs lets you turn an issue off for a project; its article does not say what that does to the score (help.ahrefs.com).
In Organiq no check can be switched off. The scores still move: pages enter or leave the crawl, and the traffic score follows the impressions of the last 28 days.
How do you see the health score in Claude or ChatGPT?
Connect Organiq to Claude or ChatGPT and ask for the health scores of a property. The assistant calls get_site_audit, which returns page health and traffic health with the formula. To try it with no account, ask it to call get_site_audit with site: "demo". The crawl and the issue list are described in SEO site audit in Claude and ChatGPT.
How does the Organiq score differ from the others?
Read on November 10, 2026 from each vendor's own pages. The difference is a second score weighted by Search Console impressions, with the exceptions below.
- Factor: a second health score weighted by real Search Console impressions, next to the page score; both formulas are written in the tool answer.
- Comparison and exception: on the pages read on November 10, 2026, none describes a score weighted by impressions. Ahrefs: internal URLs with no error divided by internal URLs, formula published (help.ahrefs.com). Semrush: errors and warnings in relation to the checks performed, no formula on the pages read (semrush.com/kb/114). Sitebulb: amount, type and priority of Hints, no formula or weights on the pages read (Sitebulb support article). Screaming Frog: no single score on the pages read (issues page). The absence is on the pages read, not proof that nothing exists. Exceptions: all four run JavaScript and Organiq reads HTML; Screaming Frog and Sitebulb declare more than 300 checks against 48; their URL limits are larger; they crawl any site, with no verified property; Semrush and Sitebulb weight issues by type or priority, while Organiq counts every error alike and leaves warnings out; the traffic score uses the impressions of the last 28 days, so a page with no impressions weighs nothing in it; Screaming Frog and Sitebulb label each issue by priority (three and five levels), while Organiq shows three severities (error, warning, notice); Screaming Frog adds GA4, command line and scheduling at any interval. Parity: a page-based score with a published formula is the same calculation as the Ahrefs Health Score, and a read of the audit by an agent through MCP (Screaming Frog, Sitebulb and Ahrefs have an MCP server).
- Where to see it: the two scores at the top of the
get_site_auditanswer, with the formula just below; call it withsite: "demo".
Who is the Organiq score for?
For whom: someone who wants to know how much of the Search Console traffic of a verified site sits on pages with errors, and wants the formula in writing. Not for whom: someone who needs a score that weighs warnings and issue types (Semrush and Sitebulb describe one), pages written by JavaScript, or sites that are not their own; Screaming Frog and Sitebulb are the alternatives for the last two.
How was this page made, and what is missing?
The formulas and counts come from the code of Organiq; the demo numbers come from the function behind site: "demo"; the example is arithmetic on invented numbers, computed by the same function as the scores.
On November 10, 2026 we opened the Ahrefs article, the two Semrush pages, the Sitebulb support article and the release notes of version 3, dated 2019. The Screaming Frog line repeats the reading of that day and its configuration guide was read in part. Tools change; corrections with a source: youssefpmat@gmail.com.
Frequently asked questions
How is a site health score calculated?
It depends on the tool. Ahrefs divides the crawled internal URLs with no error by the total of internal URLs and multiplies by 100. Organiq publishes two formulas: Page health = 100 × internal HTML pages crawled with no error ÷ internal HTML pages crawled. Traffic health = 100 × Search Console impressions (last 28 days) of pages with no error ÷ impressions of the crawled pages; with no impressions in the period there is no traffic score. Warnings, notices and site-wide issues are listed and do not enter the calculation.
What is the Ahrefs Health Score formula?
Per the Ahrefs help article read on November 10, 2026: crawled internal URLs with no error, divided by the total number of internal URLs, times 100; errors alone count.
How does Semrush calculate Site Health?
Semrush describes a percentage between 0% and 100% that takes into account the errors and warnings found in the crawl, in relation to the number of checks performed, with errors weighing more. The pages read on November 10, 2026 give no formula.
What is a good site health score?
There is no threshold shared by all tools. Ahrefs publishes 0–30 Weak, 31–70 Fair, 71–90 Good and 91–100 Excellent. A score of 100 means no error in the checks of that tool, not a position in Google.
Can a site health score rise without fixing anything?
On the pages read, Semrush says excluded checks stop counting and Sitebulb says scores depend on the project settings. In Organiq no check can be switched off, but the traffic score follows the impressions of the last 28 days.
How do I see my site health score in Claude or ChatGPT?
Connect Organiq and ask for the health scores of a property: the assistant calls get_site_audit, which returns page health and traffic health with the formula. With site "demo" it answers with fictional data and no account.