Scans a single page for common on-page SEO issues
Checks one page at a time (not a full-site crawl): title, meta description, headings, images, canonical, viewport, robots, Open Graph, favicon, content length, load time, HTTPS.
An SEO audit tool checks a webpage against a list of common on-page SEO factors — things like title length, meta description, headings, and image alt text — and reports what's missing or worth fixing.
Enter a URL.
Press "Run Audit."
Review the score and each check below it.
Yes — there's no paywall, no watermark, and no sign-up required.
Each of the 13 checks has a weight based on how much it typically matters. A pass earns its full weight, a warning earns half, and a fail earns none — the score is the total earned as a percentage of what was possible.
No — it checks one page per run, the exact URL you enter. Run it again on each page you care about (homepage, key landing pages, blog posts) rather than expecting one run to cover the whole site.
No — it reads the raw HTML that comes back from the server, the same way a basic crawler would. If your page builds its title, meta tags, or main content with client-side JavaScript after the page loads, this audit won't see that content and may report it as missing.
Any time you change a page's title, meta tags, or content — it's a quick way to confirm nothing regressed, especially right before or after a deploy.
Yes — the page is fetched and checked for that one request and isn't saved anywhere. No account or sign-up is required to use it.
A fast way to catch obvious on-page gaps without a full SEO platform subscription.
Check a post before publishing to catch a missing meta description or title issue.
Run through key pages on a new site before it goes live.
Confirm meta tags and headings survived a template or theme change.
Yes — there's no paywall, no watermark, and no sign-up required.
No, it checks one page per run, the exact URL you enter. For a full site, run it separately on each important page.
No, it reads the raw HTML that comes back from the server. If your page builds its title, meta tags, or content with client-side JavaScript, this audit won't see that content.
Each of the 13 checks has a weight. A pass counts its full weight, a warning counts half, and a fail counts zero — the score is the weighted total as a percentage.
Any time you change a page's title, meta tags, or content — it's a quick way to confirm nothing regressed before or after a deploy.
No. The page is fetched and checked for that one request and isn't saved anywhere.