The largest score group measures whether crawled URLs and preferred page signals remain reachable and consistent.
- Server-error and client-error rates
- Missing canonical targets
- Canonical mismatches
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.
TL;DR
Too Long; Didn't Read
Show summary Hide summary
TL;DR
Too Long; Didn't Read
How Is the Technical SEO Score Calculated?
Screpy Technical SEO Score is a 0–100 summary calculated from the latest completed website crawl. It uses affected rates and capped penalties inside four weighted groups, reports crawl coverage and confidence, and keeps the issue counts and affected records available for investigation.
Score result
- Screpy shows the current score, formula version, change from the previous successful crawl, and the score of each weighted group.
- Screpy keeps crawled pages, critical issues, warnings, notices, broken links, missing metadata, and average response time beside the summary.
Current weights
- Screpy weights crawlability at 40% and on-page content at 30%.
- Screpy weights links and images at 20% and selected security headers at 10%.
Coverage and confidence
- Screpy calculates a score only when the crawl has a successful page and completed link and image inventories.
- Screpy lowers confidence when crawl coverage is limited by page capacity or a meaningful blocked share.
Responsible interpretation
- Screpy compares health and issue trends across successful crawls, but teams still verify equivalent scope and inspect the affected records.
- Screpy keeps PageSpeed, Core Web Vitals, uptime, and search performance outside the current score formula and does not treat the score as a ranking guarantee.
See exactly what contributes to the Technical SEO Score.
Screpy uses affected rates and capped penalties inside four weighted groups. The formula summarizes the latest crawl without pretending that every issue has equal impact or that unrelated monitoring metrics belong in the same number.
On-page content · 30%
The on-page group measures repeated content and metadata conditions across eligible successful pages.
- Missing titles, descriptions, and H1 headings
- Duplicate metadata
- Thin content, low content ratio, and language mismatch
Links and images · 20%
This group evaluates link destinations and image implementation relative to the links and images collected in the crawl.
- Broken and invalid links
- Missing image alt text or dimensions
- Large and non-lazy-loaded images
Security headers · 10%
The security group checks whether successful pages return a focused set of browser protection headers.
- Strict-Transport-Security
- Content-Security-Policy
- X-Frame-Options and X-Content-Type-Options
Read the score together with its coverage.
Start with the latest completed crawl, current 0–100 score, change from the previous successful crawl, coverage, confidence, and formula version. These details show whether the number is available and comparable before the team reacts to it.
- See the health score and previous-crawl delta
- Check score coverage and confidence before comparison
- Keep the crawl date, status, and page total in view
See which measured category lowered the result.
Open the crawlability, on-page content, links and images, and security breakdown. Screpy calculates every group from the affected share of eligible records, caps each signal penalty, and applies the published group weight.
- Compare the four group scores and weights
- Connect a penalty with its affected and eligible records
- Separate score inputs from unrelated monitoring metrics
Compare score and issue direction across successful crawls.
Review health score, critical issues, warnings, notices, fixed issues, and crawled pages on one timeline. A changed page total or crawl scope remains visible so an apparent improvement is not accepted without context.
- Follow score direction after releases and fixes
- Compare added, fixed, and remaining issues
- Keep the crawled-page total beside every trend
Move from the summary to the affected website records.
Use Metadata, Headings, Indexability, Content, Links, Images, Schema, and Crawl health issue groups to find the condition behind a change. Then open the relevant Pages, Links, or Images inventory and identify the shared cause.
Learn more about issue evidence- Review severity, current count, and previous-crawl delta
- Open the affected URLs, destinations, or assets
- Export a focused queue and recrawl after the fix
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.
- 01
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.
- 02
Read coverage and confidence first
Check whether the score is available and whether crawl coverage is high, medium, or low. A crawl that reaches its page limit or encounters a meaningful blocked share may not represent the same website surface as another crawl.
- 03
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.
- 04
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.
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.
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.
GEO
Why Does AI Search Cite Third-Party Sites Instead of Your Website?
AI search citations often favor trusted third-party sites, reviews, and expert sources; strengthen your brand signals, authority, and citation-ready content.
Read article GEO
Why Do AI Assistants Cite Different Sources for the Same Query?
AI assistants cite different sources when retrieval systems interpret context, rank fresh evidence, and select passages differently across queries and runs.
Read article GEO
Does AI Search Traffic Convert Better Than Organic Search Traffic?
AI search traffic may convert at a higher rate than organic visits, but limited volume and attribution gaps mean GA4 data should guide practical channel decisions.
Read article GEO
How Do You Calculate AI Visibility ROI?
AI visibility ROI connects citations, share of voice, branded search, assisted conversions, and revenue to costs for a practical, defensible ROI model.
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.
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.
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.
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.
Why is my Technical SEO Score unavailable?
The score needs at least one successful page and completed link and image collection. If the crawl did not reach usable pages or those inventories are incomplete, Screpy shows the score as unavailable instead of calculating it from partial inputs.
What do score coverage and confidence mean?
Coverage describes how completely the crawl represented the configured scope. Confidence is derived from that coverage. Reaching the crawl page capacity or encountering a substantial blocked share can lower confidence, which should be reviewed before comparing scores.
Why did my score change after a new crawl?
The website may have changed, but the crawl may also have discovered a different number or mix of pages, links, and images. Compare crawl settings, successful pages, blocked share, coverage, score version, group scores, and affected rates before attributing the change to one release.
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.
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.
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.
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.
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.