Structured data validated against the official schema.org vocabulary
Structured data is a block of code, usually JSON-LD, that describes a page to search engines and AI assistants: who the company is, what the page offers and what it costs. Path Ranker reads the schema.org markup on every crawled page, in JSON-LD, microdata or RDFa, and checks types, properties and values against the official vocabulary file. Each item shows what is missing and whether it passes the check for Google rich results. When markup is missing or incomplete, the JSON-LD block comes ready to paste.
How it works
Every page is read
The HTML of every crawled page is read and the JSON-LD, microdata and RDFa markup is extracted. Microdata and RDFa are converted to the same shape and judged the same way.
Checked against the vocabulary
Each item is compared with the current schema.org release, named in the report, and with the required and recommended properties of its type. The logo and the declared images are opened to check that they exist and how big they are.
Results item by item
For each item: the page, the type, what is missing, the invalid values and whether it passes the rich result check, with links to the Rich Results Test and the Schema Markup Validator for that URL.
What it checks
Three formats, every page
JSON-LD, microdata and RDFa on every crawled page, with the count per format and the pages with no markup at all. A JSON-LD block with a syntax error is reported as an error.
The official vocabulary
Types and properties checked against the official schema.org file: 939 types and 1,538 properties. It flags what does not exist, with the suggested spelling, a property used on a type that does not accept it and terms the vocabulary has replaced.
Properties by type
Required and recommended property rules for 28 types, such as Organization, LocalBusiness, Product, Article, Event, FAQPage, BreadcrumbList and JobPosting. A subtype follows the rule of its closest parent type.
Rich result eligibility
An item of a Google rich result type passes when it has the required properties, valid values and types that exist. Organization and WebSite are left out of this count: they describe the entity and do not produce a rich result.
Values and dates
Absolute URLs, ISO 8601 dates and a schema.org @context. It flags expired offers, events that already happened, offers without a price or currency, breadcrumbs with wrong positions and FAQs without an answer.
Logo and images
It opens the logo and up to four declared images. It flags a logo that is down or smaller than 112 × 112 px, Google’s minimum. Answers of 401, 403 and 429 are marked as not verifiable, not as a broken image.
Graph and page consistency
@id references that lead nowhere, the same entity declared with different @id values across pages, an Organization name that differs from the site name, a url on another domain and a sameAs missing the profiles the site itself shows.
What is not declared yet
Organization, WebSite, BreadcrumbList, Person and the offer (Service, Product or Course); FAQPage where the page has an FAQ, VideoObject where there is video, Review where there are testimonials and SearchAction when the site has a search box.
Ready to paste
For what is missing or incomplete, the report writes the JSON-LD already filled in with what it read on the site: name, phone, address, logo, social profiles, FAQs with their answers, breadcrumb trail, articles, the author and the offer. It writes Organization or LocalBusiness, WebSite with search, FAQPage, BreadcrumbList, Article or BlogPosting, Person and Product or Service blocks, and completes any published item that lacks a required property. What only you know is marked FILL IN.
What it does not do
- It does not publish the markup: whoever runs the site pastes the ready block after replacing each FILL IN with the real value.
- Passing the check does not guarantee a rich result: Google decides case by case. Since 2023, FAQ rich results show only for well-known government and health sites, and HowTo rich results are no longer shown.
- Item-by-item validation uses the HTML the server delivers. Markup inserted only by JavaScript, such as through a tag manager, becomes a finding of its own, because many AI and search crawlers do not run JavaScript.
- It checks only the pages the crawl reached: on Free, just the home page.
Which plans include it
Free: one analysis per sign-up, home page only; it shows the problems and why they matter, not how to fix them. Starter, Pro and Enterprise: every crawled page, up to 60, 200 and 500 per domain, with how to fix each issue; the Semantics and structured data group can run on its own. The ready-to-paste JSON-LD is on paid plans, in the full report and on the analysis screen, with a copy button; it does not appear in the client version of the report. Scheduled analyses: monthly on Starter, weekly on Pro and daily on Enterprise (for up to 25 domains; the rest weekly).
See pricingFrequently asked questions
- All three are read and judged the same way. Google accepts all three but recommends JSON-LD, which is the easiest to maintain. When there is microdata or RDFa, the report suggests moving it to JSON-LD and removing the old markup.
- Path Ranker reads every crawled page in the same analysis and, beyond the rich result check, verifies the full schema.org vocabulary, the @id graph and the consistency with the page. Every finding links to the Rich Results Test and the Schema Markup Validator for that URL so you can confirm it.
- Not necessarily. Since 2023, Google shows FAQ rich results only for well-known government and health sites. Keep the FAQPage with the questions and answers visible on the page: it helps search engines and AI assistants understand the content.
- The current release published by schema.org. The report shows which version was used in each analysis.
- Yes, on paid plans. When Organization or LocalBusiness, WebSite, FAQPage, BreadcrumbList, Article, Person, Product or Service is missing, or a published item lacks a required property, the full report and the analysis screen show the block put together from what was read on the site, with a copy button. Replace each FILL IN with the real value and check it in the Schema Markup Validator before you publish.
Other features
Bing analysis
Your business on Bing Maps and your site in Bing search, which also feeds Copilot
Core Web Vitals
Real Chrome users and Lighthouse on mobile and desktop, side by side
E-E-A-T and trust
28 experience, expertise, authority and trust signals, each with the page it came from
SEO and AI goals
Ten adjustments that tend to bring clients, each with the number, the goal and its state
Monitoring and alerts
Scheduled analyses, regression alerts, downtime, and expiring certificates or domains
Keyword research
Search ideas with volume, difficulty, cost per click and intent, ready to track
Google Business Profile
A 0-100 score, local competitors, a geogrid and an alert when a profile detail changes
Google rankings
Where your site shows up in Google for the keywords that matter, and how that changes
Privacy and security
LGPD and GDPR, consent, headers, certificate, DNS and exposed credentials
AI readiness
GEO, AEO, per-page citability, an agent journey and AI citations
Reports
PDF, PIN-protected links, your own brand and the company report, in 3 languages
AI and search bots
18 AI and search bots tested live, with what each one receives
Search Console and GA4
Google clicks, indexing and sessions in the report, including visits from AI assistants
Semantic SEO
Subjects, pillar pages, entities and passages that stand on their own
Technical SEO
Crawl, status codes, canonical, robots.txt, sitemaps, hreflang and JavaScript rendering
Validate the structured data on your site
Paste the address and see, item by item, what is complete, what is missing and what the official schema.org vocabulary does not recognize.
Try it free