Before and after a release
Capture a baseline before a migration, redesign, navigation change, or shared-template release, then compare the next successful crawl using equivalent settings.
Technical SEO Score Checker for Website Health
Turn the latest completed website crawl into a transparent 0–100 health score. Review the weighted crawlability, on-page content, links and images, and security groups; check coverage and confidence; then open the issues and affected records behind every change.
What makes up the score
Weighted health groups
Crawlability, on-page content, links and images, and security contribute to the 0–100 score.
Coverage and confidence
Check how much evidence the completed crawl covers before comparing scores.
Issue drilldown
Open critical issues and affected records to see which fixes can change the score.
Check Your Technical SEO Score
Screpy turns the latest successful website crawl into a 0–100 health score. Use it to spot changes in the measured technical conditions, then read the evidence behind the number.
- See the score beside the crawl completion date and crawled-page total.
- Review separate scores for crawlability, on-page content, links and images, and security.
- An unavailable result stays unavailable; it is not converted into a zero score.
example.comCompleted
Understand SEO Score Factors
The calculation uses the affected share of eligible pages, links or images and limits each signal’s penalty. Four weighted group scores form the total, so fixing ten issue instances does not always earn ten points.
- Crawlability, 40%: HTTP 4xx and 5xx responses, missing canonicals and canonical mismatches.
- On-page content, 30%: missing titles, descriptions and H1s, duplicate metadata, thin-content signals and language mismatches.
- Links and images, 20%: broken or invalid links, missing alt text or dimensions, and large or non-lazy images.
- Security, 10%: presence of HSTS, CSP, X-Frame-Options and X-Content-Type-Options headers.
Score weights
Σ100%
- Crawlability40%
- Content30%
- Links · Images20%
- Security10%
Check SEO Score Confidence
Read the high, medium or low confidence label before treating a score as representative. Confidence reflects page-limit and blocked-crawl signals; it is not a measured percentage of every URL on the website.
- Reaching the configured page capacity can lower confidence even when the crawl finishes successfully.
- A larger blocked share further reduces confidence; investigate access restrictions before drawing conclusions.
- Check discovered pages and crawl depth as well: high confidence cannot prove that unlinked pages were found.
Confidence
HighLowMediumHigh
Track SEO Health Changes
The audit chart follows health scores and issue counts across successful crawls. A release, a metadata edit or a different crawl scope can change the result; use the trend to choose what to investigate.
- See critical issues, warnings, notices, fixed issues and crawled pages alongside the health trend.
- The score delta appears only when both results are available and use the same scoring formula.
- Keep page capacity, depth and JavaScript mode comparable before reporting a before-and-after improvement.
Health score
87 / 100
Investigate Technical SEO Issues
Use the score as an entry point into Website Audit, then inspect affected records and the business value of the pages. A low group score can point to a shared template problem rather than dozens of unrelated fixes.
- Open page findings to check responses, metadata, headings, content, canonicals and relevant headers.
- Trace broken links to their source pages and destinations; review image findings where the assets are used.
- Filter and export the relevant records to give an SEO specialist or developer concrete evidence.
- Recrawl after the fix and confirm both the affected records and the score. PageSpeed, uptime and rankings remain separate signals.
/guides/seo200
Indexed
Talk about Technical SEO Score Tool. With SEO MCP.
Connect your AI assistant to Screpy’s SEO MCP server. Ask about your latest completed crawl, inspect affected pages and turn technical SEO findings into a clear order of work.
- Screpy: Hello! Let’s look at Technical SEO Score Tool for example.com. What would you like to know?
- You: Check Technical SEO Score Tool for example.com. What should I fix first?
- Screpy: The latest completed crawl shows missing titles and broken internal links. Start with the affected pages, then inspect the evidence before making changes. Crawl findings: Missing titles: 3 pages. Broken internal links: 1 link.
- You: Turn that into a short action plan.
- Screpy: I’ll keep the evidence and recommendations separate. Review the findings, choose one change and check the results afterward. Your next steps: Review: Check the source and date of each finding.. Decide: Choose the first change to make.. Verify: Compare the results after the change..
- You: Can you explain the evidence in plain language?
- Screpy: Yes. Ask about a supported result and I can explain what it shows, where it comes from and what is still uncertain. Missing data stays unavailable; recommendations are not automatic fixes.
Move from a score change to a verified technical fix.
A useful score review starts with crawl comparability and ends with affected-record verification. Coverage, confidence, group weights, and the website context matter more than chasing a number alone.
-
Create a trustworthy crawl baseline
Complete a crawl with enough page, link, and image coverage. Record the starting URL, page capacity, depth, JavaScript mode, access conditions, and site version so a later score can be compared fairly.
-
Read coverage and confidence first
Check whether a score is available, then read its high, medium or low confidence label alongside crawled-page totals. Page limits and blocked URLs can reduce confidence; the label does not measure what percentage of the entire website was discovered.
-
Open the group and affected records
Use the weighted score groups to find the largest opportunity, then review issue severity, affected URLs, links, or images. Confirm whether the cause is one record or a repeated template, route, content type, or component.
-
Fix the cause and recrawl consistently
Publish the smallest correct fix, inspect it on the live website, and run another crawl with comparable scope. Confirm the group score, issue count, affected rate, and health trend changed for the intended reason.
Use the score as a monitoring signal—not as the SEO strategy.
The score is most useful when a team has a baseline, an owner, and a reason to investigate. Pair the summary with the affected URLs and the business importance of the pages before scheduling work.
For recurring site maintenance
Use the score and issue trend as an early signal that routine publishing or engineering work changed the technical condition of the crawled site.
To choose the next investigation
Start with the weighted group and high-severity issue affecting valuable pages, then open the underlying records instead of optimizing the number in isolation.
For stakeholder progress reports
Pair the high-level score and delta with fixed, added, and remaining issues so clients and managers can see the work behind the direction of travel.
Choose the level of technical SEO evidence you need
Use Technical SEO Score for a high-level crawl-health signal, Website Audit for site-wide investigation and verification, and the free checker for one live page.
Summarize four weighted health groups, coverage, confidence, issue direction, and successful-crawl history in one project view.
Open the complete Pages, Links, and Images evidence, investigate repeated patterns, export focused records, and recrawl after the fix.
Review metadata, headings, canonicals, links, images, structured data, accessibility, and technical signals for one public URL.
Screpy documentation
Learn how to investigate the score inputs
Use the Screpy guides to configure a comparable crawl, review affected pages, links, and images, and verify technical fixes in a later crawl.
Related SEO guides
Learn the concepts behind this workflow and apply them with practical SEO guidance.
SEO
Do Google’s New CrUX Ad Metrics Affect SEO?
Do Google's new CrUX ad metrics affect SEO? Learn what ad count, density, CPU and network weight measure, where to find the data, and what to check next.
Read article SEO
14 Shopify Hydrogen SEO Checks for Storefront Routes
Run 14 Shopify Hydrogen SEO checks across product, collection and market routes. Verify metadata, variants, sitemaps, redirects and the actual public response.
Read article SEO
14 Sanity SEO Fields to Add to Your Content Schema
Plan 14 Sanity SEO fields with a reusable Studio schema, published-perspective GROQ and checks for slugs, image assets, authors and indexing controls.
Read article SEO
SI SEO: A Practical Guide to AI Search Visibility
Learn what SI SEO means, how to improve AI search visibility, and how to measure mentions, citations, visits, and business outcomes.
Read articleTechnical SEO Score FAQ
Understand the formula, category weights, eligible inputs, coverage, confidence, crawl comparison, prioritization, and what a website health score can—and cannot—prove.
What is a technical SEO score?
A technical SEO score is a 0–100 summary of selected crawl findings. Screpy calculates the score from the latest completed crawl and keeps the underlying groups, issue counts, and affected records available so the number remains an entry point—not the diagnosis.
Why is my Technical SEO Score unavailable?
The latest successful crawl needs at least one page with a 2xx response and link and image collection enabled. If these requirements are not met, the score is unavailable. A missing score is not zero, and an unavailable result cannot produce a score-change comparison.
What do score coverage and confidence mean?
The dashboard shows high, medium or low confidence. This estimate considers whether the crawl reached its page limit and how much of the crawl was blocked. It is not a measured percentage of every page on your website. Even high confidence cannot confirm that unlinked or undiscovered URLs were audited.
How should I prioritize work from the score?
Begin with a low-scoring weighted group, then identify the high-severity issue affecting valuable pages at meaningful scale. Inspect representative URLs and find the shared cause before changing templates, routes, metadata, links, images, or headers.
Can the issue total fall while the score also falls?
Yes. The score uses weighted groups and affected rates rather than treating every issue instance equally. A crawl can fix many low-impact records while adding a smaller number of heavily weighted problems, or it can cover a different website scope.
What is the difference between Technical SEO Score and Website Audit?
Technical SEO Score summarizes four weighted groups from the latest completed crawl. Website Audit is the investigation workflow: it exposes the Pages, Links, and Images inventories, issue details, source context, filters, exports, and later crawl evidence needed to understand and verify a fix.
What is the difference between Technical SEO Score and a one-page SEO checker?
A one-page checker reviews one live URL at one moment. Technical SEO Score summarizes eligible findings across a completed project crawl, so it can reveal repeated conditions and compare website health across successful crawls.
Which issues can lower the score?
The current formula includes HTTP client and server errors, canonical issues, missing or duplicated metadata, missing H1 headings, thin-content signals, language mismatch, broken or invalid links, image accessibility and loading findings, and selected security headers.
Why did my score change after a new crawl?
Website edits can change the score, but a new crawl can also discover a different mix of pages, links and images. Compare crawl settings, page totals, confidence, group scores and affected records before attributing a change to a release. The displayed score delta requires available results from both crawls using the same scoring formula.
Should every website aim for a score of 100?
A higher comparable score generally means fewer of the measured conditions affected the crawled scope, but 100 is not automatically the best business priority. Review page value, issue severity, scale, user impact, confidence, and implementation risk before choosing the next fix.
How does Screpy calculate the Technical SEO Score?
The current calculation combines four weighted groups: crawlability at 40%, on-page content at 30%, links and images at 20%, and security headers at 10%. Each signal applies a capped penalty based on the affected share of its eligible pages, links, or images, and the weighted group scores produce the final 0–100 result.
Do PageSpeed, Core Web Vitals, uptime, or rankings change this score?
No. Screpy provides those signals in separate monitoring and search workflows, but they are not inputs to the current Technical SEO Score formula. Keeping them separate prevents a performance, availability, or ranking metric from being presented as if it were a crawl-health calculation.
Does a higher Technical SEO Score guarantee better rankings or traffic?
No. The score measures a defined set of technical and on-page crawl conditions. Search performance also depends on relevance, content quality, authority, competition, demand, indexing decisions, SERP presentation, and user behavior.