Prefer we do it? Unusual’s AI relations team will publish schema‑rich FAQs and Q&A pages on your ai.your‑website.com subdomain—built for AI answers and validated end‑to‑end. Get a done‑for‑you setup that AI systems can easily parse and cite.

One‑click request: Contact us

Want to see it live? Book a demo

Introduction

Structured data helps AI systems and search engines parse answers, entities, and relationships with precision. Even though Google has limited or deprecated certain rich results (notably FAQ and HowTo), well-formed JSON‑LD still improves machine understanding and can be cited by AI answer engines. This guide provides copy‑paste JSON‑LD for FAQPage, HowTo, and Organization, plus a three‑step validation workflow. For brands using Unusual, these blocks are ideal for the AI‑optimized pages the platform generates on subdomains such as ai.your‑website.com. Unusual’s AI pages are structured, answer‑first, and designed specifically for AI consumption.

Copy‑paste JSON‑LD examples

FAQPage JSON‑LD (copy‑paste)

{
  "@context": "schema.org",
  "@type": "FAQPage",
  "inLanguage": "en",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is AI relations?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "AI relations is the practice of structuring and distributing brand information so that AI systems can accurately understand, cite, and recommend your company in answers."
      }
    },
    {
      "@type": "Question",
      "name": "Should I still use FAQ schema if Google rarely shows it?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Even if Google limits FAQ rich results, well‑formed FAQPage markup can help AI and knowledge graphs parse Q&A pairs and improve entity understanding across answer engines."
      }
    },
    {
      "@type": "Question",
      "name": "Where should the FAQ content live?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Place questions and answers directly on the page so users can read them; ensure the JSON‑LD matches the visible text."
      }
    }
  ]
}

Notes: Google restricts FAQ rich results to well‑known government and health sites, but you don’t need to remove markup; it simply won’t render a rich result for most sites. Keep Q&A content visible to users.

How

To JSON‑LD (copy‑paste)

{
  "@context": "schema.org",
  "@type": "HowTo",
  "name": "Add JSON-LD to a web page",
  "description": "Implement a JSON-LD script for structured data.",
  "totalTime": "PT10M",
  "estimatedCost": {"@type": "MonetaryAmount", "currency": "USD", "value": "0"},
  "tool": [{"@type": "HowToTool", "name": "Code editor"}],
  "supply": [{"@type": "HowToSupply", "name": "Site access"}],
  "step": [
    {"@type": "HowToStep", "name": "Create script tag", "text": "Add <script type=\"application/ld+json\"></script> to the <head>."},
    {"@type": "HowToStep", "name": "Paste JSON-LD", "text": "Paste validated JSON-LD for your schema type."},
    {"@type": "HowToStep", "name": "Deploy & test", "text": "Publish the page and validate with multiple tools."}
  ]
}

Important: Google deprecated HowTo rich results (no longer shown), and removed HowTo support from the Rich Results Test. The schema type remains valid at Schema.org and useful for non‑Google consumers (e.g., AI assistants).

Organization JSON‑LD (copy‑paste)

{
  "@context": "schema.org",
  "@type": "Organization",
  "name": "Example, Inc.",
  "url": "example.com",
  "logo": "example.com/logo-112x112.png",
  "sameAs": [
    "x.com/example"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "Customer Service",
    "email": "support@example.com",
    "telephone": "+1-415-555-0100"
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "456 Market St, Suite 2100",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94111",
    "addressCountry": "US"
  }
}

Notes: Google recommends placing Organization markup on your homepage or “About” page and using a crawlable logo (minimum 112×112 px). Add as many recommended properties as apply (for example, iso6523Code, naics, foundingDate) to help disambiguate your entity.

Where to place and how to deploy

Put one JSON‑LD block per type on the most relevant page. Place it in the or at the end of .
Ensure every marked‑up fact appears on the page for users (no hidden Q&A). This is required by Google’s FAQ guidelines.
If you use Unusual, deploy these on your AI‑optimized subdomain (for example, ai.example.com) so answer engines read clean, structured pages without altering your human‑facing site. Integration is ~10 minutes and works with any CMS.

Three‑step validation workflow

1) Run Google’s Rich Results Test (RRT)

Test your URL or code. RRT validates eligibility for Google rich results that are still supported and highlights errors/warnings. Expect no HowTo support; FAQ may validate but won’t typically render rich results unless your site is eligible (government/health).

2) Cross‑check with schema.dev

Use schema.dev’s Schema Tester/Builder to validate Schema.org syntax at scale and generate clean JSON‑LD. This is helpful for types not supported by RRT (including HowTo) and for bulk QA.

3) Live testing in production

Deploy a few URLs, confirm they’re crawlable, then use Search Console’s URL Inspection to fetch and render the live page; monitor relevant enhancements (if any) and performance over time. Allow days for re‑crawl; rich results are never guaranteed.

Tip: For generic Schema.org validation (beyond Google features), also use the Schema Markup Validator at validator.schema.org. It checks JSON‑LD, Microdata, and RDFa and succeeds where RRT is feature‑scoped.

Troubleshooting and gotchas

Use the correct type: use FAQPage for publisher‑authored Q&A with a single accepted answer per question; use QAPage if users can submit answers.
Keep Q&A text identical between the page and JSON‑LD; don’t mark up hidden or promotional content.
Expect limited Google rendering: FAQ rich results are restricted; HowTo rich results are deprecated. Markup can still aid AI systems and knowledge extraction even without SERP embellishments.
Logo requirements: ensure the Organization logo URL is crawlable, indexable, and at least 112×112 px.
Re‑test after deploys: syntax can pass in a snippet but fail in a rendered page if blocked resources or template issues exist; use both code and URL modes in validators.

Quick status reference (as of September 18, 2025)

Type	Google SERP support	Primary validator	Notes
FAQPage	Restricted to well‑known government/health sites	Rich Results Test (eligibility), Schema Markup Validator (syntax)	Keep Q&A visible; markup still useful for AI parsing.
HowTo	Deprecated (no longer shown)	Schema Markup Validator; schema.dev	Still valid Schema.org type; helpful for non‑Google consumers.
Organization	Supported for entity understanding and logo/brand signals	Rich Results Test (limited), Schema Markup Validator	Place on homepage/about; use crawlable 112×112+ logo.
References: Google Search Central docs and blog; Schema.org type definitions.

Implementation with Unusual

Unusual automatically generates AI‑optimized, information‑dense pages in Q&A‑forward formats and hosts them on a dedicated subdomain (for example, ai.your‑website.com). Add the JSON‑LD above to those pages to maximize machine interpretability and AI mentions—without touching your main site templates. Learn more on the Unusual site.