free_tool
SEO & Structured-Data Auditor
Enter a URL and get a graded read on the on-page basics search engines actually use: title and description, canonical, indexability, Open Graph and Twitter cards, a single clear H1, mobile viewport, and the JSON-LD structured data that earns rich results. Plain checks, with what to fix first.
Enter a public URL. The page is fetched server-side and parsed in your browser; nothing is stored.
The page is fetched server-side and parsed in your browser. It reads the HTML as served, so a site that renders its content with client-side JavaScript may look emptier here than it does to a rendering crawler. That gap is itself a finding worth knowing about.
why_it_matters
The basics are still where pages lose
Most pages don't lose ranking to something exotic; they lose it to a stray noindex left over from staging, a missing canonical splitting their authority, or an absent og:image that makes every share look broken. These are quick to fix once you can see them.
Structured data is the part most sites skip and the part that earns the richer listing: ratings, breadcrumbs, FAQs, article bylines. This flags whether you ship any JSON-LD at all, which is the first step to those upgraded results.
faq
Questions & answers
- What on-page signals does the SEO and Structured-Data Auditor check?
- It scores eleven signals: indexability, title length, meta description, canonical, a single H1, Open Graph tags, Twitter card, mobile viewport, HTML lang, JSON-LD structured data, and HTTPS. Each is weighted and the total maps to a letter grade from A to F.
- Does my browser fetch the page directly?
- No. Your browser sends the URL to a server route that fetches the page with SSRF protections and returns the HTML, which your browser then parses and scores. The audited site never sees your IP.
- Why does my page look emptier here than in Google?
- It reads the HTML exactly as served, without running client-side JavaScript. A site that renders its content with React or similar will show fewer headings, meta tags and structured data here than a rendering crawler would see.
- Can it catch a stray noindex left over from staging?
- Yes. It checks both the robots meta tag and the X-Robots-Tag response header and shows which one carries the directive. A live page accidentally shipped with noindex gets a hard fail on indexability, which is the worst kind of SEO mistake to miss.
- Does it validate that my JSON-LD is correct?
- Not fully. It checks whether any JSON-LD type is present and flattens @graph to find them, but it does not verify the schema is valid or complete. Use it to confirm structured data exists, then validate the shape elsewhere.
Want the SEO done properly, not just checked?
This grades the basics. I'll go deeper: rendering and crawlability, Core Web Vitals, internal linking, and structured data that actually earns rich results. Book a call, or leave your email.
Prefer proof first? See how this plays out in real case studies →