One number for your whole site

What an SEO health score can tell you

There is no official Google SEO score. Third-party scores summarize selected checks using each tool’s own formula, so the number is not comparable across products unless their inputs and weights match. A score can help you track whether a set of technical findings improved over time. It cannot predict rankings, traffic or Merchant Center approval.

Shipwork’s score runs the same bounded audit used by its site audit and summarizes findings as a number from 0 to 100, an A–F grade, must-fix and warning counts, checks run, pages checked and leading errors. The score depends on which checks apply to the site and what the crawl could inspect. Read the underlying findings before deciding what work matters.

• 100 points minus 5 per must-fix finding, with that penalty capped at 80 points.
• Minus 1.5 per warning, with that penalty capped at 20 points.
• The score is bounded between 0 and 100; a site with no findings scores 100.
• The grade and score summarize this audit’s findings, not Google’s assessment.

How to check your SEO score and understand the result

Enter the public domain and choose Score my site. Review the resulting score alongside the counts and top findings. A lower score means this run found more or higher-penalty issues under the formula; it does not mean Google assigned that number. Two websites can have the same score but different problems, so use the findings to choose a fix rather than optimizing the number by itself.

The audit samples a bounded set of pages and runs checks that apply to the site. A high score can miss an issue outside the sampled pages or in a system the audit cannot observe. Search Console shows Google-specific indexing and search performance data; analytics shows visitor behavior. Use those sources for their own questions.

• Fix the highest-priority errors that affect pages important to your business.
• Review warnings and decide whether each matters for your site.
• Rescan after changes and compare the findings as well as the score.
• The share page and badge display the snapshot; another scan is needed to refresh it.

Turn score findings into a work list

Start with the error count and top error cards. Each issue includes a description and fix; group repeated findings by likely source. If many URLs share a canonical or noindex issue, the cause may be a template or app rather than separate page edits. If only one URL is affected, inspect that page and its response. Then rerun the score to see whether the finding cleared and whether other work remains.

Do not remove a warning just to raise the score if the underlying setting is intentional. For example, not every page belongs in a sitemap, and some sites deliberately block training crawlers. Choose fixes that improve your actual crawl and customer experience while preserving intentional policies.

• Example: an unintended site-wide noindex should be fixed at the template or response-header source, not one URL at a time.
• Example: a blocked AI training agent may be an intentional choice; review agent-by-agent access before changing robots.txt.
• Use the focused site audit to inspect full findings and individual checkers when you want more detail.

Score snapshots, sharing and limits

The score page creates a shareable result and an embeddable badge for the scan. The badge displays the stored snapshot and does not start a new crawl when someone views it. The score is refreshed only when the site is scanned again; it is not a live reading of current pages. If you publish a badge, remember that anyone who can access its public image can see the displayed score snapshot.

A one-time result is a point-in-time technical summary. Deployments, inventory changes, search engine decisions and content edits can change after the scan. Use Search Console for Google’s reports, Merchant Center for product diagnostics, and analytics for visits and conversions. Treat the score as a triage aid, not a substitute for those records.

• Site audit: inspect the detailed checks behind a score.
• Compare sites: view audit results side by side.
• Printable report: prepare a document-style version of findings.

What is a good SEO score, and how to check yours

There is no official Google SEO score. A score is useful as a consistent summary of technical findings, not as a ranking prediction or a substitute for Search Console, analytics, or content review. Shipwork’s score summarizes findings from the checks that apply to a site.

On Shipwork, 90–100 is an A, 80–89 a B, 70–79 a C, 60–69 a D, and below 60 an F. A high score means fewer issues in the checks that ran; it does not measure whether the page answers a search well.

1. Enter your site’s public domain on the score page and choose Score my site.
2. Review the 0–100 result together with the must-fix and worth-fixing counts, the number of checks and pages covered, and the highest-priority findings.
3. Work through the concrete fixes shown for errors first, then address warnings that matter to your site. The score subtracts 5 points per must-fix finding (up to 80 points) and 1.5 per warning (up to 20 points), with a floor of zero.
4. Treat the number as a technical health snapshot: an A or high number is not a guarantee of rankings, traffic, or Google approval, and the score is not a Google metric.
5. Re-scan after changes to compare the snapshot. The share page shows the scan date, and the badge reflects the latest stored score after another scan.