What Website SEO Score Checker does
Website SEO Score Checker fetches one public page and applies ten published weights: successful HTTP status, HTTPS final URL, title length, description length, exactly one non-empty H1, canonical presence, mobile viewport, HTML language, absence of a noindex meta directive, and non-empty alt text for discovered images.
The score is a compact implementation checklist, not a search-engine grade. A page can score 100 while having weak content, poor performance, invalid structured data, blocked resources, or no external authority. Conversely, a deliberate implementation can fail a simplified threshold. Use the item-by-item evidence to guide review rather than optimizing for the total alone.
How to use Website SEO Score Checker
- Enter the full public URL of the page you want to audit.
- Select Check page SEO to fetch the server-visible HTML and run all ten checks.
- Review each rubric item, its weight, pass state, and evidence before looking at the total.
- Verify findings with rendered-page, performance, accessibility, structured-data, and crawl testing as appropriate.
Important details
The scoring thresholds are explicit
Title passes at 10–60 characters and description at 70–170. H1 passes only when exactly one non-empty H1 is found. These are this tool's review thresholds, not universal search-engine requirements.
Every point maps to a rubric item
The ten checks add to one hundred points with no hidden model or external score. Evidence such as status, character counts, canonical value, viewport text, and missing-alt count explains each outcome.
The fetch does not execute JavaScript
Metadata or content injected only on the client may be absent. The report reflects the bounded HTML response delivered to the PagesTools server after allowed redirects.
Practical uses
- Catch missing basic metadata after a template or CMS release.
- Create a repeatable ten-item prepublication checklist for public pages.
- Compare implementation evidence before and after a technical SEO change.
Privacy and limitations
The submitted URL is sent to PagesTools and fetched by its server. The target can log that request, so do not use private or token-bearing URLs. The JSON report is returned with no-store cache headers.
This is a single-page, non-JavaScript HTML audit. It excludes ranking, indexing confirmation, Core Web Vitals, backlinks, structured-data validity, robots.txt, sitemap coverage, accessibility, content quality, and a complete crawl.