JSON-LD and Structured Data: Why They Are Not Enough for ChatGPT, Perplexity, and Gemini

Structured Data Is Not Read the Same Way by Generative AIs

JSON-LD and structured schemas (Schema.org) have allowed Google to understand your content for years. However, ChatGPT, Perplexity, Gemini, and Claude process them differently. These AI engines analyze raw HTML, extract semantic context, but do not necessarily prioritize structured markup the way the traditional SEO algorithm does. Many brands discover too late that their impeccable structured data generates no citation or recommendation from AI assistants. The reason: these models give more weight to readable textual content, surrounding context, and domain authority than to isolated JSON-LD tags.

Why AI Engines Ignore or Misinterpret Your JSON-LD

JSON-LD Is Often Ignored If It Contains Partial or Inconsistent Data

Generative AIs do not rely on structured tags in an absolute way. If your JSON-LD contains an address, a phone number, or prices, but the visible text on the page contains contradictory or more detailed information, the models tend to prioritize the readable text. They apply a kind of internal consistency check: if the tag and the content do not align, they become skeptical.

Textual Context Takes Precedence Over Metadata

Unlike Google, which extracts structured data and indexes it in separate fields, generative AIs operate on the principle of contextual understanding. They read your page as a human user would: title, paragraphs, lists, then tags. If your JSON-LD declares that you are a restaurant with a 4.8-star rating, but nowhere in the visible text do you mention that rating, the AI may ignore the structured data and invent an answer or not cite it at all.

Formats Vary by AI: Some Do Not Parse Standard JSON-LD

Perplexity and Claude sometimes use crawlers that prioritize textual HTML content. Gemini, being a Google product, takes JSON-LD more into account, but even at Google, structured data does not influence response generation the same way it influences search ranking. ChatGPT, if it does not have direct web access (depending on the version), receives pre-processed content excerpts where structured markup may be partially lost.

How ChatGPT, Perplexity, Gemini, and Claude Actually Process Your Structured Tags

ChatGPT: Bing Integration and Priority to Readable Content

ChatGPT with internet access relies partly on Bing for content sources. JSON-LD is not used systematically to extract answers. Instead, ChatGPT indexes the main text and establishes logical connections. If you explicitly mention in your text "Our product costs 49 euros" and you also tag this price in JSON-LD, ChatGPT will likely cite your page. But if there is only structured markup without clear textual context, the AI will not understand your content well and will not recommend it.

Perplexity: Importance of Textual Density and Clear Citations

Perplexity builds its answers by explicitly citing sources. It analyzes accessible content and looks for passages that the user can verify. JSON-LD alone never appears in a Perplexity response, because this tool is designed to show tangible evidence. On the other hand, a well-written and informative paragraph, even without structured markup, will be cited. This means that for Perplexity, it is more important to have clear, well-organized, and detail-rich text than a perfect JSON-LD.

Gemini: Better JSON-LD Support, but Not Automatic

Gemini, being a Google product, benefits from Google Search integration and takes structured data more into account. However, this does not automatically activate citations. Gemini always reads the content as a whole. A correctly implemented LocalBusiness schema helps Gemini better understand your context, but does not force its recommendation. Consistency between your metadata and your content remains crucial.

Claude: Deep Text Analysis, Little Reliance on Metadata

Claude functions like a very attentive reader of raw text. It does not crawl pages directly, but receives content via integrations. Its content providers (such as Anthropic's API or integration sources) generally provide formatted text rather than raw HTML with JSON-LD. Therefore, Claude depends entirely on the clarity and structure of the visible text.

When JSON-LD Is Actually Useful for AIs

For Well-Defined Entities (Businesses, Events, Products)

JSON-LD remains effective when it describes a clear entity and the text confirms it. For example, if you are an SEO agency based in Paris and you include an Organization schema with your address, phone, and website, AIs more easily recognize your field of activity. This improves the chances that Gemini or a future AI recommendation system will point to you as an authority on the subject.

For Enriching Voice and Visual Search Results

Conversational AIs integrated into voice assistants (Alexa, Google Assistant, Siri) rely more on structured data. If you are targeting these platforms in addition to ChatGPT, JSON-LD becomes strategic. But for text-based answer engines like Perplexity or Claude, the impact is limited.

For Disambiguation and Cross-Validation

When an AI encounters an ambiguous query (for example, "Paris" can be the city or the mythological character), structured data helps with disambiguation. A correctly formatted JSON-LD tells the system: "We are talking about the city of Paris, with this latitude and longitude." This improves the relevance of responses.

GEO-Specific Adjustments to Make Your Data More Attractive to AIs

1. Enrich Your Visible Text with Information Complementary to JSON-LD

Do not rely on JSON-LD alone. Every important piece of data (address, hours, prices, specialties) must appear clearly in the readable content. Create dedicated sections: "Our Opening Hours" (with text), "Our Rates" (with details), "Our Location" (with geographic context). AIs will read these sections and associate them with the structured markup for dual understanding.

2. Use Nested Schemas for Geographic and Sectoral Context

Instead of a simple LocalBusiness schema, nest specialized schemas: LocalBusiness + ProfessionalService for a medical practice, LocalBusiness + Restaurant for an establishment. Add geo properties like GeoShape or Place to precisely define your coverage area. This helps AIs contextualize your offering geographically.

3. Validate Consistency Between JSON-LD and Visible Content

Regular audit: verify that the information in JSON-LD corresponds exactly to the visible content. If your schema says "Monday-Friday 9am-6pm" but your page mentions "Open 8am-7pm," AIs detect the inconsistency and trust your content less. Use tools like Google's Rich Results Test to verify that your markup is valid, then manually compare it with the text.

4. Create Unique Content Around Your Structured Data

Writing a 300-500 word article that details your local offering is more effective than an isolated JSON-LD. For example, if you are a plumber in Lyon, do not only tag your service as a LocalBusiness. Also write: "Emergency service in Lyon: we cover all 9 arrondissements, available 24/7" with concrete details. This gives AIs rich context to recommend you.

5. Include Citations and Social Proof in the Visible Text

Generative AIs value evidence. Instead of relying on a Schema Review rating, explicitly mention: "Our clients give us an average of 4.8 stars on Google (150+ reviews)" or "See our projects in our portfolio." Link to reliable external sources. This strengthens your credibility for AI engines.

6. Structure Your FAQs with a FAQPage Schema + Detailed Content

The FAQPage schema in JSON-LD is ignored by some AIs, but Perplexity and Gemini actively look for FAQ sections. Tag your FAQ in JSON-LD for Google, but also structure your questions and answers in a very readable and detailed way. AIs will read the visible text and cite your answers as sources.

Real Use Case: How AIs Process LocalBusiness Markup

Consider a dental practice in Marseille. Its JSON-LD includes: name, address, phone, hours, rates, services offered. Here is what each AI does:

Perplexity: Crawls the page, entirely ignores the JSON-LD, looks for readable text mentioning dental services, rates, or reviews. It will cite a paragraph such as "Dr. Martin offers cleanings for 80 euros" but will never mention the structured markup.

Gemini: Uses the JSON-LD to enrich its understanding of the domain (dentist, Marseille, services). Generates a response that combines this understanding with the textual content. If the text and markup align, generates a more precise response.

ChatGPT: Mainly reads the visible text. Recognizes that it is a dental practice in Marseille by reading the content. Could mention the address or phone if they are clear in the text. Does not cite the JSON-LD.

Claude: Depends on how the content is transmitted to it. If provided as raw HTML, it parses the text and ignores the JSON-LD. If provided as pre-processed text, it has never seen any trace of it.

Summary of Key Differences: JSON-LD in SEO vs. in GEO

In traditional SEO, Google uses JSON-LD intensively to index structured data in separate fields. Your Review schema directly influences rich snippets in results. Markup is an official component of ranking.

In GEO (generative AIs), JSON-LD is a secondary precision tool. Generative AIs operate on the model of textual understanding and context. Structured markup helps with disambiguation and improves the model's internal confidence, but does not automatically activate citations or recommendations. Readable, clear, and detailed textual content remains the key.

Checklist to Optimize Your Structured Data for Generative AIs

• Validate your JSON-LD with Google's Rich Results Test. Fix any errors.
• Duplicate key information in the visible and readable text of your page.
• Create unique content around your local or sectoral area of expertise (at least 300 words).
• Strict consistency: ensure that every piece of data in JSON-LD also exists in the text with the same information.
• Show evidence: explicitly mention reviews, certifications, achievements, not only in tags.
• Organize hierarchically: use clear headings (H2, H3) so that AIs segment your content well.
• Test in Perplexity and Gemini: ask questions related to your business and check how you are recommended (or not).
• Monitor changes: AIs constantly adjust their approach. Revisit your strategies every quarter.