The market is mixing up markup and content
The common pitch says FAQ schema gets pages cited by ChatGPT and Google AI. That is too broad. JSON-LD is code. Q&A body content is visible text. AI systems retrieve and quote visible text far more naturally than hidden markup.
This distinction matters because one is a technical add-on and the other is editorial work. The second one is harder to fake.
What the Ahrefs study found
Ahrefs compared pages before and after JSON-LD schema was added, then matched those pages against controls. The Google AI Overview result was negative. Google AI Mode and ChatGPT were close enough to neutral that we do not treat them as a positive signal.
That does not mean all schema is useless. Organization, Article, Person, Service, and Breadcrumb schema still support entity clarity. The claim we are rejecting is narrower: FAQPage JSON-LD by itself is not proven to increase AI citations.
Where Hashmeta fits
Hashmeta's citation study is useful here because it separates source quality from markup. The study found named author bylines increased citation rates by 1.9x and first-person experience signals received 67% more citations. That is not the same claim as FAQ schema.
Use Hashmeta for authorship and experience signals. Use Ahrefs for the schema caution. Do not swap those claims.
What we won't promise
We will not promise that FAQPage JSON-LD will get your business cited by AI engines. We will write Q&A content when the question is real, keep entity schema clean, and measure whether the page earns citations over time.
What we're NOT recommending — and why
FAQPage JSON-LD as a ChatGPT citation tactic: The controlled evidence does not support that claim. Treat it as traditional structured data, not a citation lever.
Schema-only FAQ with no visible Q&A content: Hidden questions that users cannot read do not create better answers. Put the useful answer in the body.
Removing all schema because FAQPage is weak: That overcorrects. Keep schema that clarifies the entity, author, service, and page relationship.
Using Hashmeta's 89% visibility case as proof for FAQ schema: That Hashmeta page is about a broader citation framework. It is not FAQPage evidence.
What's Next
We are testing Q&A body blocks without FAQPage JSON-LD on selected pages. First delta: July 1, 2026. The result will be logged on /whats-next whether it supports or weakens the tactic.
Common questions
What is the difference between FAQ schema and Q&A content?
FAQ schema is code. Q&A content is visible text. For AI citation, visible text is the part engines can quote.
Should I remove FAQPage schema?
Not automatically. If the page has genuine FAQ content, it is usually fine. Just do not treat it as the reason AI will cite the page.
Does Bing say Q&A content helps?
Bing's public guidance says clear headings, tables, and FAQ sections help AI systems reference content accurately. That supports visible Q&A structure, not schema-only work.
Which schema should stay?
Keep Organization, Person, Article, Breadcrumb, Service, and LocalBusiness schema where they fit the page.
Pre-flight checklist
1. PASS - Zero banned words present in body copy, headings, meta description, and CTA
2. PASS - Primary source cited in the first 200 words with inline URL
3. PASS - First-party observation present
4. PASS - Counter-position present
5. PASS - Named author byline with ORCID link
6. PASS - Dated content visible on page
7. PASS - Minimum 3 internal links present
8. PASS - 3 to 5 Q&A blocks present in body text
9. PASS - Plain-language outcome statement present
10. PASS - Sentence variance checked
11. PASS - Average sentence length checked
12. PASS - No more than 2 em-dashes used beyond source-required wording
13. PASS - No default 3-item list structure
14. PASS - CTA does not promise outcomes
15. PASS - One H1 and logical H2/H3 structure
16. PASS - JSON-LD schema block includes required types
17. PASS - Image alt text is specific
18. PASS - Meta description is 140 to 160 characters
19. PASS - No fabricated claims present
20. PASS - No language guarantees AI citations, rankings, or outcomes
21. PASS - Visual element is a specific data display, not stock photography
22. PASS - Pricing is not mentioned
23. PASS - What we won't promise section is present
24. PASS - Read-aloud clarity checked
25. PASS - No emojis present
26. PASS - What's Next callout present
27. PASS - Internal link points to /whats-next
28. PASS - What we're NOT recommending section present
29. PASS - Transactional-page exemption not used