✓ Free to Use • No Signup • Live Check — We Fetch the URL for You
Enter any public URL and this tool fetches the page and runs around 30 on-page checks on it: title and description, canonical, headings, image alt coverage, link counts, Open Graph tags, schema and indexing directives. You get a weighted score out of 100 and every check marked pass, warning or fail — with the actual value found, so the report reads as a fix list, not a grade to guess at.
An SEO audit is a measurement pass over everything on a page that affects whether search engines can find it, parse it and trust it. This tool runs that pass on a single page: our server fetches the URL, and the checks run against the HTML exactly as served — the same starting point a crawler sees before rendering.
The score is weighted, not a flat count. Core items (title, canonical, indexing) cost more than cosmetic ones, because that is how their real impact ranks. The audit is deliberately honest about its limits: it does not render JavaScript and it does not measure real-user speed — for lab speed scores from Google itself, use the Website Speed Test alongside it.
This audit reads one page exactly as a crawler first receives it: the raw HTML your server sends back. That view covers a lot of ground. The tool checks your title tag and meta description, the canonical URL, your H1 and the order of the headings below it, how many images carry alt text, and how links split between internal and external destinations. It also reads your Open Graph and Twitter tags, any JSON-LD schema, the viewport setting and robots directives, then groups the results into categories with a weighted score out of 100.
The limits matter just as much. Because the audit works on served HTML, it does not execute JavaScript, so content injected later by scripts may never appear in the results. It is also a snapshot of a single URL, not a crawl of your whole site, and it holds no backlink data, no search console figures and no view of whether the page is actually indexed. Performance is deliberately left out as well; load speed belongs to the separate speed test tool. Treat the score as a technical health check for one page, never as a verdict on your whole site.
Start at the top with failures that stop a page from being understood at all. A missing or duplicated title tag, a robots directive that blocks indexing, a canonical pointing at the wrong URL, or a page with no H1 are not cosmetic issues; they decide whether the page can compete in the first place. Fix those before anything else, then re-run the audit to confirm each fix actually reached the live page. It is common to correct a template, publish it, and find the cached or staged version is what the checker still sees.
Move to the warnings next: titles and descriptions at awkward lengths, images without alt text, heading levels that skip, or thin internal linking from the page. These rarely block a page outright, but they waste the space and signals you already have. Leave the polish for last: complete Open Graph and Twitter tags so shares look deliberate, and structured data where it honestly describes the page. Finally, remember the score is a guide to technical tidiness, not a target in itself. A page can score in the nineties and still say nothing worth ranking, so pair every audit with an honest read of the content itself.
Privacy: to run this check, our server fetches the public URL you enter — the same request any browser or crawler makes. The URL and its results are not stored; close the tab and they are gone.
Title tag and its length, meta description, canonical URL, H1 and heading structure, image alt coverage, internal and external link counts, Open Graph and Twitter Card tags, JSON-LD schema, viewport, language and indexing directives (robots meta and X-Robots-Tag).
Usually one heavy failure: a missing or duplicated title, a noindex directive, or images without alt text fail on a large share of real sites. Read the failed checks in order — the top of the list is where the score is hiding.
No. It checks the HTML as served, which is what crawlers start from. If your site injects its title or content with JavaScript, compare the result with the <a href="/seo-tools/page-crawl-test/">Page Crawl Test</a> to see exactly what a bot receives.
After every significant change — a redesign, a migration, a new template — and monthly on an active site. A fix is not done when it is deployed; it is done when the check passes.
Tools handle the technical setup. Rankings come from authority — browse 1,502 real publisher sites with live metrics and fixed prices, or see our packages.