Audit a page for SEO
Paste a URL and get a scored report across five categories, with the three fixes that recover the most score listed first. No signup, no card. It runs the same engine as the API.
What it scores
- Content
- Heading order, language declaration, image alternative text, and whether the page says enough for a crawler to know what it is about.
- Meta
- Title, description, canonical, hreflang, and duplicate meta — the tags that decide how the page is represented in a result, and which of your URLs is the one that counts.
- Social
- Open Graph and card metadata: what appears when someone pastes your link into a chat, which is often the first impression a page gets.
- Technical
- Structured data, robots directives, broken links, and the machine-readable signals that determine whether the page is eligible for anything beyond a plain blue link.
- Performance
- Render-blocking stylesheets, image dimensions and lazy-loading attributes, HTML weight — the page-level choices that shape how fast it can possibly be.
Checks are weighted rather than counted, so the score moves when something that matters is wrong — not when you accumulate a long tail of trivia. The report leads with the highest-value fixes for that reason.
What a single-page audit cannot see
- Anything rendered by JavaScript. We read the HTML your server sent. If your title and headings only exist after hydration, they are missing here — and that is worth knowing rather than working around.
- Real-world speed. Core Web Vitals come from field data gathered from your visitors. We can see what constrains speed on the page; we cannot see what your users experience.
- Your site's authority. Who links to you, and how much that is worth, is invisible from one fetch of one URL.
- Why you rank where you rank. A page can pass every check here and sit on page four because the query is competitive and the site is new. Technical correctness removes reasons to fail. It does not manufacture reasons to win.
Questions
Does it run JavaScript?
No. It fetches the URL and parses the HTML your server actually sent. That is a deliberate choice, because it is also roughly what a crawler sees on first contact — but it means a single-page app that renders its title, headings and meta tags on the client will look emptier here than it does in your browser. If your framework server-renders or pre-renders, what you see here is what a crawler sees. If it does not, that gap is itself the finding.
Is this a Core Web Vitals score?
No. The performance category looks at page-level choices that constrain speed — render-blocking stylesheets, missing image dimensions, HTML weight. Real Core Web Vitals come from field data collected from actual visitors on actual devices, which no scanner can synthesise from one fetch.
Does it crawl my whole site?
The public checker audits the one URL you give it. Site-wide crawling is what the bulk endpoint is for, and that needs a key — partly for quota, partly because crawling someone's whole site anonymously is not something to leave open to the internet.
Can it tell me why I am not ranking?
No, and be suspicious of anything that claims to. This audits what is on the page. Rankings are decided by that plus your site's authority, the competition for the query, intent match, and a great deal nobody outside the search engine can observe. A clean audit removes the technical reasons you might not rank. It does not supply the other ones.
Is there a limit?
The public checker is rate-limited per IP and protected against automated scraping. A free key gives you 10 audits a month with no card.
Auditing a site, not a page?
A free key gives you 10 audits a month with no card, and the bulk endpoint takes a list of URLs in one call.