Published March 19, 2026
Every popular schema validation tool answers the same question: is your structured data valid JSON? Google's Rich Results Test, the Schema.org Validator, Yoast, and others all check whether the markup on your page follows the correct syntax and conforms to the schema.org specification.
None of them answer the question that actually matters for AI visibility: what is missing?
A page can pass every validation tool with a green checkmark and still be invisible to AI. Valid schema is not the same as complete schema. The AIFDS validator was built to close that gap — checking not just validity, but whether the schema contains the fields AI systems actually need.
Google's Rich Results Test checks whether schema qualifies for rich result features — featured snippets, knowledge panels, product carousels. If valid for Google's purposes, you get a green checkmark.
The Schema.org Validator checks syntax, types, and properties against the specification.
CMS tools like Yoast generate basic schema automatically and confirm it is technically correct.
All answer the same question: is this valid JSON-LD? The problem is that valid JSON-LD can be completely useless for AI.
A homepage with Organization schema that includes only a business name and URL is technically valid. It passes every tool.
It is also missing the contact information, hours, service area, and business classification AI needs to recommend the business. Every question AI needs answered — what does this business do, can the user reach them, are they open now — remains unanswered.
No existing tool flags this. The schema is valid. But from AI's perspective, the page is barely visible. A business owner who sees a green checkmark and assumes the work is done may be missing every field that drives AI citation.
The AIFDS validator asks a different question: "what is missing and why does it matter?" Enter a URL and it checks against the fields documented in the pillar research and built into every AIFDS blueprint. The output is a field-by-field report.
Google's tool asks: does this qualify for rich results? The AIFDS validator asks: does this give AI what it needs to recommend the business? A page can qualify for rich results and still be missing the fields AI uses. The two systems are evaluating different signals for different purposes.
Most business owners who check schema use Google's tool. If it says valid, they assume the work is done. That creates a false sense of completeness — the schema may be missing every field that matters for AI citation.
The audit process should include both types of validation:
Step 1: Check validity. Use Google's Rich Results Test or the Schema.org Validator to confirm the JSON-LD is well-formed and free of syntax errors.
Step 2: Check completeness. Use the AIFDS validator to see what fields are present and what is missing.
Step 3: Fill the gaps. Send the validator output and the matching AIFDS blueprint to your developer — the output as the brief, the blueprint as the template.
Schema is eligibility. Validity is a technical requirement — the code has to work. Completeness is the visibility requirement — the data has to be there. Only one determines whether AI recommends your business.
The tools the industry has relied on for years check validity. The AIFDS validator checks both.
David Valencia writes about how AI systems find, parse, and cite websites.
The gap between what you think AI sees and what it actually sees.
Read →