Free tool
Website SEO Checker
A site-level snapshot of metadata, indexability, links, robots.txt, and sitemap discovery across a sample of pages.
The check could not be completed
Website check results
What was checked
| Field | Value |
|---|
Findings
Pages sampled
| Page | Status | Title | Words |
|---|
This is a snapshot of a sample of pages, not a full audit. Response time is measured as the time this server waited for the page, which is not a Core Web Vitals measurement and does not reflect what a visitor on a phone experiences. For a full crawl, use the Technical SEO Audit.
What This Tool Does
The website checker takes a small, honest sample of a site rather than crawling all of it. It fetches the address you give it, optionally follows a handful of internal links from that page, looks for robots.txt and an XML sitemap, and reports what it found across the pages it actually reached.
It is built for the first five minutes with a site you do not know yet: is it reachable, is it on HTTPS, does it have titles and descriptions, are they duplicated across templates, is anything accidentally blocked from indexing. When you need coverage rather than a snapshot, the Technical SEO Audit crawls further and tracks progress as it goes.
How to Use It
Enter the site address. Leave the follow-links box ticked to sample a few internal pages, or untick it to check the single page only, which is faster and uses less of your allowance.
- Read the errors first. A missing title on the page a site links to from every template is worth more than a dozen notices about lengths.
- Check duplicate titles and duplicate descriptions carefully. Across a small sample, duplication usually means a template is writing them, which means it affects every page built from that template rather than only the two you can see.
- Confirm the sitemap and robots.txt lines. A missing sitemap is not fatal, but a robots.txt that blocks something you want indexed is the sort of problem that costs months.
- Treat the score as an index of the findings below it, not as a verdict. It is only useful for noticing that something changed between runs.
How the Tool Calculates or Retrieves Data
Every page is fetched from this website's server. Each address is validated before the request and again after each redirect, so a link that redirects towards a private network is refused rather than followed. Crawling stays on the domain you entered, obeys robots.txt by default, and stops at the page limit you chose.
Response time is the time this server waited for the page, measured from here. It depends on the distance between the two servers and says nothing about how the page performs in a browser, so it is never presented as a Core Web Vitals measurement.
The score is arithmetic you can check: it starts at one hundred and subtracts eight for each error and three for each warning, floored at zero. The rule set version is stored with the result, and the deductions are printed under the score, so a change in the number can always be traced to a change in the findings.
Understanding Your Results
Findings are grouped as errors, warnings, passes, notes, and checks that were skipped. The skipped group matters: it tells you what the sample could not establish, which is more useful than a pass that was never really tested.
A duplicate-title warning across two sampled pages is a strong signal and a small piece of evidence at the same time. It proves duplication exists; it does not tell you how many other pages share the same title. That question needs a full crawl.
Mixed-content notes list plain http links found on pages served over https. Browsers block or downgrade some of these, and they are usually left over from an old migration rather than deliberate.
Frequently Asked Questions
Because a fast snapshot is what this tool is for, and because a full crawl of someone else's site from a shared server is a request you should make deliberately. When you want depth, the Technical SEO Audit crawls in batches, shows progress, and can be cancelled.
Exactly the arithmetic printed underneath it: one hundred less eight per error and three per warning. It is not a prediction of how a site will rank, and no such prediction is available from a page fetch. It is useful for comparing two runs of the same site.
No. It is how long this server waited for a reply, which is affected by the distance between the two machines. Real user performance needs measurements taken in a browser, which this tool does not do.
Yes, within the limits above. The crawler identifies itself honestly, respects robots.txt, keeps the number of requests small, and never sends form data or credentials.