An SEO audit score is a way of collapsing dozens of separate findings into one number you can put in front of a client, a board, or your future self three months from now. The problem with almost every scored audit on the market is that the scoring model is hidden. You get a "68/100" and no way to know which pillar dragged it down, how much each pillar was worth, or whether the tool's opinion of "importance" matches your business at all. This calculator inverts that: you enter the six pillar scores, and you also enter the weight of each one.
Arb Digital built this because we kept rebuilding the same spreadsheet for every audit. A weighted score is genuinely useful for prioritisation and for tracking progress across quarters, but only when everyone can see the arithmetic. Nothing on this page is a Google-published metric. Google does not release a site score, does not publish ranking-factor weights, and has said repeatedly that its systems consider many signals in ways that do not reduce to a single public number. What follows is an explicit, editable model — useful precisely because it is transparent about being a model.
What This SEO Audit Score Calculator Does
You supply a 0–100 score for six audit pillars: technical health, on-page optimisation, content quality, off-page authority, page experience, and local or entity signals. You also supply the percentage weight you believe each pillar deserves for this specific site. The calculator multiplies each score by its weight, sums the results, and normalises by the total weight entered — so the score stays valid even if your weights add up to 90% or 115% rather than exactly 100.
Alongside the headline score, it reports the total weight you entered (so you can spot a typo immediately), names the weakest pillar by raw score, tells you how many weighted points you are short of your target, and — the most useful output — identifies the single pillar where a fix would move the overall score most. That last figure is weight-aware: a mediocre pillar carrying 20% weight is a bigger opportunity than a terrible pillar carrying 5%.
How to Use It
- Score each pillar 0–100 from your own audit findings. Use whatever rubric you already trust — a percentage of checks passed, a manual judgement, or a crawler's own sub-score. Consistency between audits matters far more than precision within one.
- Set the weights to match the site. An ecommerce catalogue with 40,000 URLs should weight technical health heavily. A ten-page local service site almost certainly should not, and should push weight into local and entity signals instead.
- Zero out anything irrelevant. If the business has no physical location or service area, set the local weight to 0 rather than inventing a score for it. The calculator renormalises automatically.
- Set your target score. Pick the number you want to reach by the end of the engagement, not a theoretical 100.
- Read the "biggest single win" figure before you write your recommendations. It tells you where effort converts into score fastest under your own weighting.
The Formula / How It's Calculated
The maths is a standard weighted mean. For each pillar i with score Si and weight Wi:
Audit score = Σ(Si × Wi) ÷ Σ(Wi)
With the default weights, a site scoring 72 technical, 65 on-page, 58 content, 41 authority, 80 page experience and 35 local produces (72×20 + 65×20 + 58×20 + 41×20 + 80×10 + 35×10) ÷ 100 = (1440 + 1300 + 1160 + 820 + 800 + 350) ÷ 100 = 58.7. Round to 59. The dividing step by total weight is what makes the tool forgiving: if you set weights of 30/30/30/30/10/10 — 140 in total — the score still comes out on a 0–100 scale, because every weight is expressed as a share of the total rather than as an absolute.
"Points to target" is simply target minus current score, floored at zero. The "biggest single win" is computed by asking, for each pillar in turn, how much the overall score would rise if that pillar alone were lifted to 100 — which equals (100 − Si) × Wi ÷ ΣW. The pillar with the largest value wins. This is why a pillar at 41 with 20% weight (11.8 points available) beats a pillar at 35 with 10% weight (6.5 points available), even though the second one looks worse in isolation.
Why the Weights Have to Be Yours
Every scored audit product on the market has baked-in weights, and every one of them is a guess dressed as authority. There is no published table of ranking-factor weights. Google's own Search Essentials and SEO starter guide describes practices, not point values, and Google has been consistent that the relative importance of signals is context-dependent and query-dependent. So when a tool tells you technical SEO is worth exactly 25% of your site's health, that number came from a product manager, not from Search.
The honest response is not to abandon scoring — clients and stakeholders genuinely need a trend line — but to make the weighting an explicit, defensible choice. If you weight content at 30% for a publisher, you should be able to say why in a sentence: organic traffic on that site is driven by breadth of topic coverage, not by fixing 40 redirect chains. That sentence is worth more than the score itself, and it survives scrutiny in a way a vendor's hidden default never does.
Choosing Weights for Four Common Site Types
These are starting points from Arb Digital's own practice, not benchmarks. Adjust them freely.
Large ecommerce catalogue. Technical health carries the most weight because faceted navigation, parameter handling, and crawl waste can suppress thousands of URLs at once. On-page matters at template level rather than page level. Content weight drops because most URLs are product pages with structurally similar copy. Pair this with the crawl budget calculator to see whether crawl waste is a real constraint or a theoretical one.
Content publisher. Content depth and off-page authority dominate. Technical health still matters but usually as a hygiene floor rather than a growth lever. If you are tracking whether older articles are losing ground, the content decay calculator gives you the decline curve to feed into your content pillar score.
Local service business. Local and entity signals should carry real weight — often 25% or more — because map-pack visibility can outweigh classic organic for high-intent queries. Off-page weight shifts toward citations and local relevance rather than raw domain strength. Score the local pillar with our local SEO ranking calculator and the profile-completeness side with the GMB optimization score calculator.
SaaS or B2B site. Content and on-page usually carry the load, because the winning pages are comparison, integration, and use-case pages that live or die on how well they match query intent. Feed intent classification in with the keyword intent classifier before scoring the content pillar.
The Trap of Scoring the Same Thing Twice
The most common error in a weighted audit model is double-counting. Page speed is a page-experience issue, but slow rendering also affects crawl efficiency, which is a technical issue. Thin content is a content problem, but it usually also shows up as a weak on-page score because the page lacks headings and internal links. If you let the same underlying defect depress three pillars, your score punishes it three times and your prioritisation gets distorted — you will over-invest in the loudest problem.
The fix is to define each pillar by the artefact it covers rather than by the outcome. Technical health covers what a crawler can reach and render. On-page covers what is in the HTML of a given URL. Content covers whether the page satisfies the query. Page experience covers measured field performance. Write those definitions down once and reuse them across every audit, because the score is only comparable over time if the rubric is stable.
Scoring the Same Site Twice: Making the Trend Line Honest
A single audit score is nearly meaningless. A score measured the same way in January, April, July and October is one of the most useful reporting artefacts an agency can produce, because it turns a long list of completed tickets into a movement anyone can read. Three rules make the trend line honest.
First, freeze the weights for the duration of the engagement. Changing weights mid-programme changes the score without changing the site, and it will look — reasonably — like moving the goalposts. Second, freeze the rubric behind each 0–100 pillar score. If "technical health" meant "percentage of crawler checks passed" in January, it cannot quietly become a subjective judgement in July. Third, record the raw pillar scores, not just the total. When the total moves from 59 to 67, the interesting question is always which pillar moved, and a stored total cannot answer it.
It is also worth logging what changed on the site between measurements. A score that jumps six points the same month a migration completed is telling you something different from a score that climbs steadily over two quarters of content work. Without that context, the number invites the wrong conclusion.
What This Score Cannot Tell You
An audit score measures the state of the site. It does not measure demand, competition, or revenue, and it will not predict traffic. A site can score 85 in a market where every competitor scores 90, and a site can score 45 and dominate a niche nobody else has bothered to enter. Score movement is a leading indicator of effort, not a guarantee of outcome.
It also cannot price the work. Lifting off-page authority from 41 to 70 is a fundamentally different investment from lifting on-page from 65 to 90, even if the two produce a similar score gain. Before committing budget on the strength of a score, model the commercial side separately with the SEO ROI calculator and the traffic side with the SEO traffic forecast calculator. The audit score tells you what to fix; those tools tell you whether fixing it is worth the money.
Finally, the score is only as good as the inputs. If your technical pillar score comes from a crawl that missed a whole subdomain, or your authority score comes from a metric that has not been refreshed in six months, the weighted average inherits every one of those flaws and hides them behind a confident-looking two-digit number.
Arb Digital's SEO team runs weighted audits with the rubric and weights agreed up front, re-scores on a fixed cadence, and reports pillar-level movement rather than a single opaque number.
SEO Services Talk to Arb DigitalCommon Mistakes to Avoid
- Presenting the score as a Google metric. It is a model. Say so on the slide, every time — it protects your credibility when someone eventually asks where the weights came from.
- Changing weights between audits and then reporting the score as improvement. Freeze the model, or restate both audits under the new weights.
- Weighting local signals on a site with no local presence, which drags the total down for a pillar that cannot be fixed and should not exist.
- Chasing the lowest pillar instead of the highest weighted opportunity. The calculator's "biggest single win" exists to stop exactly this.
- Scoring a pillar from a partial crawl — a crawl that stopped at 5,000 URLs on a 60,000-URL site produces a technical score about a site you did not actually audit.
Related Free Tools From Arb Digital
Score the individual pillars with the Core Web Vitals score calculator for page experience and the topical authority calculator for content coverage. If a replatform is on the roadmap, run the site migration risk calculator before you re-score anything, since a migration can move every pillar at once. The full free online tools hub has the rest.
Frequently Asked Questions
No. Google does not publish a site-level SEO score or a table of ranking-factor weights. Any scored audit, including this one, is a model built by whoever made the tool. That is why every weight here is editable and labelled as Arb Digital's default rather than a Google figure.
There is no universal threshold, because the score depends entirely on the rubric and weights you chose. The useful comparison is against your own previous score under identical settings, or against a competitor scored by you using the same rubric. A number compared across two different models means nothing.
The calculator divides by the total weight you entered, so each weight is treated as a share of the total. Weights of 30, 30, 20, 20, 10 and 10 behave identically to 25, 25, 17, 17, 8 and 8. It only matters that the ratios between them reflect your priorities.
Quarterly suits most sites, because meaningful technical and content work rarely completes faster than that. Re-scoring monthly tends to produce noise rather than signal unless you are mid-migration or actively shipping large changes every week.
Almost never. The last fifteen points usually cost more than they return, and some findings are deliberate trade-offs rather than defects. Setting a realistic target — the field in this calculator exists for that — makes the remaining gap actionable instead of permanently red.
Only if you scored both yourself, with the same rubric and the same weights, in the same period. Comparing your score against a number produced by another vendor's hidden model is comparing two different questions and calling the answers equivalent.
Any consistent source works: percentage of automated checks passed, a manual scoring sheet, or Search Console data for indexation and performance issues. Google's Search Console Help documents the reports most teams use for the technical and indexation pillars.
This score is a planning and reporting model produced by Arb Digital, not a metric published or endorsed by any search engine, and it does not predict rankings or revenue.
