English Version
Deploying JSON-LD for AI search visibility starts with picking the right schema type for each page, then validating to zero errors before considering the work done. This guide provides three copy-paste templates — Organization, Article, and FAQPage — plus a two-tool validation sequence.
1. Decide Which JSON-LD Type You Need First
Before copying any template, identify the role of the page you are marking up. Applying FAQPage to a homepage, or Organization to an article page, sends contradictory entity signals that AI engines cannot resolve into a coherent brand record.
Three page roles map to three schema types:
| Page role | Schema type | Where it lives |
|---|---|---|
| Site identity | Organization |
Homepage or global template |
| Page-level evidence | Article |
Each individual article or post |
| Visible Q&A | FAQPage |
Any page with user-visible question-answer pairs |
schema.org/Organization defines Organization as the structured type for describing an organizational entity — carrying brand name, canonical URL, logo, and contact information. It is the first identity layer that AI engines use to build a brand entity record. schema.org/Article records page-level evidence: headline, publish date, and author, giving AI systems the signals needed to assess content freshness and source credibility. schema.org/FAQPage is reserved exclusively for pages where the question-and-answer pairs are already visible to the user — it is not a content generation tool.
"Structured data must represent content that is visible to users on the page; marking up content that is hidden from users violates Google's structured data policies." — Google Rich Results Test
The deployment sequence that follows from this decision is: Organization first, Article per content page, FAQPage only where visible Q&A exists. Validate at each stage.
2. Copy the Organization Template: Define Site Identity First
Organization is the foundation of the entire structured data stack. Without a correctly deployed Organization block, subsequent Article and FAQPage markup lacks a verified entity anchor, and AI engines have no reliable way to attribute your content to a known brand.
Deployment rules:
- Place the block inside a
<script type="application/ld+json">tag in the<head>of your homepage. - If your CMS uses a global header template (for example, WordPress
header.php), insert it there for site-wide reuse. - Fill only fields you can verify. A missing field costs nothing; an inaccurate
sameAslink actively degrades the entity signal.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Brand Name",
"url": "https://www.yourwebsite.com",
"logo": "https://www.yourwebsite.com/logo.png",
"contactPoint": {
"@type": "ContactPoint",
"contactType": "customer support",
"email": "support@yourwebsite.com"
},
"sameAs": [
"https://www.linkedin.com/company/your-company",
"https://en.wikipedia.org/wiki/Your_Company"
]
}
Judgment criteria:
- Every URL in
sameAsmust be a real, accessible page that describes your brand. If a Wikipedia entry does not exist yet, leave the field out rather than guessing. - The
logoimage should be at least 112 × 112 pixels, in PNG or SVG format. urlmust match your canonical domain exactly — including whether it carrieswww.
schema.org/Organization lists over 40 supported properties, but the principle here is to fill only what is true and verifiable. Padding the block with empty or speculative values does not improve recognition; it introduces noise.
"The core value of Organization schema is to give search engines and AI systems an unambiguous entity anchor; inaccurate sameAs links actively harm brand entity signals rather than helping them." — schema.org/Organization
3. Copy the Article Template: Add Page-Level Evidence to Each Post
Article markup creates a verifiable provenance record for each piece of content. AI engines such as ChatGPT and Perplexity weight author credibility, content recency, and publisher attribution when deciding whether to cite a source. All three signals can be transmitted through a correctly deployed Article block.
Deployment rules:
- Deploy a separate Article block on each individual content page. Do not reuse one block across multiple pages.
headlinemust match the H1 on the page word for word.datePublishedanddateModifieduse ISO 8601 format (e.g.,2026-07-12) and must stay in sync with the dates displayed on the page.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article title, matching H1 exactly",
"author": {
"@type": "Person",
"name": "Author Name",
"url": "https://www.yourwebsite.com/author/name"
},
"publisher": {
"@type": "Organization",
"name": "Your Brand Name",
"logo": {
"@type": "ImageObject",
"url": "https://www.yourwebsite.com/logo.png"
}
},
"datePublished": "2026-07-12",
"dateModified": "2026-07-12",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://www.yourwebsite.com/your-article-url"
}
}
Common errors to avoid:
- A
headlinelonger than 110 characters may be truncated in Google rich results display. - The
authorURL should point to a dedicated author bio page, not the homepage. - If the content is institutional rather than by a named individual, change
author "@type"to"Organization".
schema.org/Article defines three sub-types — NewsArticle, BlogPosting, and TechArticle. For standard blog posts and guides, the base Article type is correct. Only news publishers should use NewsArticle. Using a mismatched sub-type does not produce an error, but it sends an inaccurate content classification signal.
4. Copy the FAQPage Template: Mark Up Only Visible Q&A
FAQPage is the most frequently misused of the three templates. Two errors appear consistently: marking up questions and answers that do not exist on the page, and adding FAQPage markup to pages that contain no visible Q&A at all. Both practices are flagged as content mismatches by the Google Rich Results Test and will cause the markup to be ignored or penalized.
Deployment rules:
- Compile the list of visible Q&A pairs on the page first. Write the markup second. The sequence cannot be reversed.
- Text in
acceptedAnswermust match the on-page answer closely enough that a user reading both would consider them identical in meaning. - Every
Questionand everyAnswermust be visible to users on that same page.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Full text of the first question",
"acceptedAnswer": {
"@type": "Answer",
"text": "Complete answer text, consistent with what is visible on the page."
}
},
{
"@type": "Question",
"name": "Full text of the second question",
"acceptedAnswer": {
"@type": "Answer",
"text": "Complete answer text, consistent with what is visible on the page."
}
}
]
}
Risk note:
schema.org/FAQPage specifies that this type applies to "a page that contains a list of frequently asked questions and their answers." If a page contains only a single Q&A pair, QAPage is the more precise type. If a page contains no Q&A content at all, adding FAQPage markup is a structured data misrepresentation — it erodes trust signals for the entire domain, not just that page. Accuracy is the goal, not volume.
5. Validate Step by Step Until You Reach Zero Errors
Generating the JSON-LD code is not the finish line. Markup that has never been validated is markup of unknown status — it may be recognized, ignored, or actively flagged. Validation uses two tools in sequence, each checking a different layer.
Step one: Google Rich Results Test — check eligibility
Open Google Rich Results Test and enter either the page URL or paste the raw HTML. The tool reports:
- Which schema types Google has detected on the page.
- Errors — these prevent rich result eligibility and must be fixed before anything else.
- Warnings — these do not block basic eligibility but reduce completeness; fix them progressively.
Target: zero errors. Warnings can be addressed iteratively, but no errors should remain when you consider a deployment complete.
Step two: schema.org Validator — check semantic integrity
Open schema.org Validator and paste your JSON-LD snippet directly. This tool checks semantic correctness independently of Google's specific rendering rules:
- Are field names recognized schema.org properties?
- Are required properties present?
- Are value types correct — for example, is
datePublisheda valid ISO date string?
Rechecking cadence:
Once both tools report zero errors, record the timestamp. Any subsequent change to page content or to the JSON-LD block requires repeating both validation steps. BrandGEO's Fix Center can generate JSON-LD, FAQ, and robots.txt artifacts and prompts users to verify deployment status — the generated files still require validation with these two tools to confirm that markup matches visible page content. Generation and deployment are two separate steps.
Recommended deployment order across the three templates: Organization → Article → FAQPage. Organization, as the site identity layer, should be deployed and validated first, and should maintain zero-error status throughout all subsequent work.
FAQ
Q1: What is the difference between JSON-LD and Microdata, and which do AI search engines prefer?
JSON-LD is embedded as a standalone <script> block in the page <head>, decoupled from the HTML structure, which makes it easier to maintain and update independently of content changes. Microdata writes attributes directly into HTML tags, coupling markup to layout. Google explicitly recommends JSON-LD. AI engines such as ChatGPT and Perplexity can extract structured signals more reliably from a self-contained code block than from attributes scattered across the DOM. For any new implementation, JSON-LD is the correct starting point.
Q2: Can a single page carry more than one JSON-LD type at the same time?
Yes. A page can contain multiple independent <script type="application/ld+json"> tags marking different types — for example, both an Article block and a FAQPage block on the same content page. Each block must be independently valid; they should not be nested inside one another incorrectly. When you run Google Rich Results Test, each type will be reported separately.
Q3: Does FAQPage markup directly affect citation rates in AI engines?
FAQPage markup allows AI engines to read your Q&A content in structured form, reducing the parsing cost and increasing the probability of accurate attribution. It is not a guarantee. Content quality, the completeness of brand entity signals across all three schema layers, and the volume of credible third-party references all contribute independently. FAQPage markup is a necessary condition for this class of recognition, not a sufficient one.
Q4: If page content is updated, does the JSON-LD need to be updated too?
Yes, it must be updated in sync. If Article's dateModified diverges from the actual revision date visible on the page, or if FAQPage answer text no longer matches what users see, Google Rich Results Test will flag the inconsistency and the rich result will be suppressed. Build JSON-LD updates into your standard content publishing workflow rather than treating them as a separate maintenance task.
Q5: Which platforms are most valuable to include in sameAs links?
For B2B brands: LinkedIn company page, Crunchbase, and Wikipedia (if an entry exists) carry high entity weight. For media and content brands, industry databases and established community pages add supporting signal. The governing rule is the same regardless of platform: include only pages that are real, stable, and publicly accessible, and that accurately describe your brand. Each inaccurate sameAs link dilutes the entity signal rather than reinforcing it.
Q6: Does Organization schema need to appear on every page?
No. Organization describes site-level brand identity and belongs on the homepage or in a global template that covers the entire site. Individual article pages do not need a separate Organization block — the publisher field inside the Article block already establishes the brand entity relationship by name reference. Duplicating Organization across every page produces no additional benefit and adds unnecessary markup weight.
Check your site's JSON-LD health now
BrandGEO provides an AI visibility audit based on your public URL — enter your domain to receive a structured data health report and actionable fix recommendations you can deploy immediately.
Start your free audit → BrandGEO
Who should use this guide?
It is for teams evaluating JSON-LD for AI Search: 3 Copy-Paste Templates who need clear steps, evidence, and risk boundaries.
What should I confirm before acting?
Confirm the target audience, public evidence, citable site pages, and the structured content that needs attention first.
How do I tell whether the work is effective?
Track brand mentions in AI answers, cited sources, indexed pages, structured-data status, and the content quality-gate results.
What common mistakes reduce reliability?
Do not present unverified claims as facts. Keep a reachable source for every material statement and re-check accessibility after publishing.
How often should I re-check?
After deployment, verify accessibility and structured data first, then track citations and indexing on a regular cadence.