Skip to content

A technical SEO score that shows real progress

One number from 0 to 100 summarizes the health of your site. It rises as you fix issues, so you can show clients and managers that the work is paying off.

TL;DR

Too long; didn't read
Show summary

What is a technical SEO score?

A technical SEO score condenses the results of a site audit into one number. In BigRank it starts at 100, subtracts a penalty for each issue based on its severity, and is normalized by page count so large and small sites are comparable.

How is the score calculated?
It is 100 minus weighted issue penalties, normalized by the number of pages crawled.
Where do I see it?
On the project Overview, with a trend over crawls, and in your reports.
Why does the score change between crawls?
Fixing issues raises it, and new issues on new or changed pages lower it. Each crawl is a snapshot, so you can see when it moved.
Does a bigger site score lower?
Not because of size alone. Penalties are normalized by page count.

How the score is built

The score starts at 100 and subtracts a penalty for each issue, weighted by severity and normalized by page count. The formula never changes between crawls, so a rise or a drop reflects the site, not the method.

  • Severity weights

    Critical issues cost more than warnings, and warnings cost more than notices, so serious problems move the score the most.

    • Critical, warning and notice levels
    • A penalty for each issue found
    • Same weights on every crawl
  • Page-count normalization

    Penalties are divided by the number of pages, which keeps the score fair across small blogs and large stores.

    • Pages counted from the latest crawl
    • 100 means no weighted issues
    • Crawl page limit set by plan
  • Category breakdown

    The Overview shows issue counts by severity, so you can see what is pulling the score down.

    • Critical issue count
    • Warning and notice counts
    • Affected URLs behind each issue
  • Trend chart

    The score is plotted across crawls, so progress and regressions are easy to spot.

    • One point per crawl
    • Each drop tied to a crawl
    • Manual runs add a point too
  • New and fixed issues

    Switch between crawl snapshots to see which issues appeared and which were resolved.

    • Snapshot kept for every crawl
    • Date selector for past crawls
    • Issue counts per snapshot
  • Score in reports

    Add the health score section to a white-label PDF report for clients and stakeholders.

    • One of nine report sections
    • Alongside an audit issues section
    • Your logo and brand colors

A number your team can rally around.

The score sits on the project Overview next to issue counts by severity, so everyone sees the same picture of site health.

  • Score from 0 to 100
  • Issue counts by severity
  • Search Console summary alongside

See the trend, not just the snapshot.

Every crawl is stored, so the score becomes a line you can read: when it dropped, when it recovered and which release caused the change.

  • Trend across crawls
  • Date selector for past snapshots
  • Scheduled recrawls keep the line current

Proof for clients.

Include the health score and fixed issues in a branded report, so the value of technical work is visible without a long explanation.

  • Overview and health score section
  • Completed fixes section
  • Workspace logo and brand colors

SEO MCP

Ask your AI assistant about Technical SEO Score.

Ask your assistant what the health score is today, how it moved over recent crawls, or how many errors and warnings the latest audit found.

Sample conversation

From baseline to better score

The score moves only when issues change, so the routine is simple: set a baseline, remove the heaviest penalties first, and let the next crawl show the result.

  1. Run the first crawl

    Your first crawl sets the baseline score for the project.

  2. Fix the heaviest issues

    Start with critical issues, since they carry the largest penalties.

  3. Recrawl

    Run the crawl again or wait for the scheduled recrawl.

  4. Check the trend

    Confirm the score moved and note the change in your report.

When teams watch the score

The score is the right tool when someone needs one number instead of an issue list: a monthly report, a check after a release, an agreed client target or a quick read across several sites.

  • Monthly reporting

    Show the score trend and the issues fixed since the last report.

  • Release monitoring

    Spot a drop after a release and trace it to the crawl where it first appeared.

  • Agency goals

    Set a target score with a client and track progress toward it.

  • Portfolio comparison

    Compare health across projects and see which sites need attention first.

One number, the full issue list or the next fix?

Use Technical SEO Score to follow site health as one number over time, Website Audit to see every issue and the pages behind it, and Quick Wins to find the changes most likely to bring traffic.

  • Technical SEO Score

    Track a 0 to 100 health score weighted by issue severity and normalized by page count, with a trend line across crawls.

  • Website Audit

    Open every issue from the latest crawl, grouped by severity, with the list of affected URLs to hand to developers.

  • Quick Wins

    Work through 19 reports that join Search Console and crawl data, with every item ranked by impact and ease.

Keep going

Raise the score with less guesswork

The score tells you how much is wrong, not what to fix. Open the issues behind it, start with broken links, and add the trend to your client reports.

Start free trial

Technical SEO Score FAQ

Answers about what counts as a good score, how severity sets the penalty, Core Web Vitals, client reports, when the score updates and whether small fixes count.

What counts as a good score?

Higher is better, and 100 means no weighted issues. Use your own trend as the benchmark rather than chasing a fixed number.

What makes one issue cost more than another?

Its severity. Penalties are weighted by severity, so a critical issue costs more than a notice.

Does the score include Core Web Vitals?

The score is built from weighted crawl issues. Core Web Vitals have their own Overview card and their own history charts.

Can I put the score in a client report?

Yes. The overview and health score is one of the sections you can pick for a PDF report.

When does the score update?

After every crawl. Recrawls run weekly by default and daily on higher plans, and you can start one at any time.

Does fixing a notice change the score?

Yes. Penalties are weighted by severity, so a notice moves the score least.

SEO that fits your budget

Plans start at $19/month with a 7-day free trial. Every plan includes the site audit, Search Console insights and white-label reports.

See pricing