Schema Markup for AEO: FAQ, Product and Organization Setup

For answer engine optimization, three schema types cover most businesses: Organization to define who you are, Product with Offer to describe what you sell, and FAQPage for pages built around real questions. Implement them in JSON-LD, keep every value identical to the visible page, validate them and generate them from the same data that produces your content.

Set expectations first. Google states that you do not need special markup to appear in AI Overviews or AI Mode, and an Ahrefs study of 1,885 pages that added schema found no clear effect on AI citations. Schema is not an AI visibility shortcut. It is a consistency and eligibility layer: it supports search features, helps search engines understand entities, and, according to Microsoft, helps Bing's language models understand content. This guide shows how to set it up correctly.

The current state of these schema types

Type	Google rich result status in 2026	Main value for AEO
Organization	Supported for logo and knowledge panel understanding	Entity definition, links to official profiles
Product and Offer	Supported for product snippets and merchant listings	Accurate price, availability and reviews
FAQPage	Rich results removed from Google Search in May 2026	Consistency with visible Q&A; no Google search feature

Google stopped showing FAQ rich results on May 7, 2026, and removed the related Search Console report and Rich Results Test support in June 2026. Existing FAQ markup causes no problems, but it no longer produces a Google search feature.

Organization schema

Organization schema tells search engines what your company is and connects your site to your official profiles. Place it on the homepage or About page.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com/#organization",
  "name": "Example Analytics",
  "legalName": "Example Analytics, Inc.",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/images/logo.png",
  "description": "Example Analytics provides product analytics software for mobile app teams.",
  "foundingDate": "2019",
  "sameAs": [
    "https://www.linkedin.com/company/example-analytics",
    "https://www.crunchbase.com/organization/example-analytics",
    "https://github.com/example-analytics"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@example.com"
  }
}

Implementation notes:

• The description should match your approved one-sentence company description, word for word, across your site and profiles.
• sameAs should only list official profiles you control or that represent you, such as LinkedIn, Crunchbase, GitHub, Wikipedia or Wikidata where they exist.
• Use a stable @id so other markup, such as Product or Article, can reference the organization.
• Use a more specific type where accurate, for example LocalBusiness for location-based businesses.

Product and Offer schema

Product schema describes items you sell. For ecommerce, it supports product snippets and merchant listings in Google. For software, consider SoftwareApplication instead.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Trailhead 40L Hiking Backpack",
  "image": "https://www.example-outdoor.com/images/trailhead-40.jpg",
  "description": "A 40-liter hiking backpack with a ventilated back panel and rain cover.",
  "sku": "TH40-GRN",
  "gtin13": "0123456789012",
  "brand": { "@type": "Brand", "name": "Example Outdoor" },
  "offers": {
    "@type": "Offer",
    "url": "https://www.example-outdoor.com/trailhead-40",
    "priceCurrency": "USD",
    "price": "149.00",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": "212"
  }
}

All values are illustrative. Use real, current data.

Implementation notes:

• Price and availability must match the visible page and your product feed at all times. Generate all three from the same product database.
• Include GTINs where products have them. Google Merchant Center and many shopping systems rely on product identifiers.
• Only include ratings that reflect genuine reviews shown on the page. The FTC's rule on fake reviews allows civil penalties for fake or misrepresented reviews.
• For AI shopping, product feeds matter as much as markup. Google's AI shopping experiences draw on Merchant Center data, and Google introduced new Merchant Center attributes for conversational commerce in January 2026. OpenAI's Agentic Commerce Protocol covers purchasing in ChatGPT.

SoftwareApplication for SaaS

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Example Analytics",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Web, iOS, Android",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD",
    "description": "Free plan for up to 10,000 monthly events"
  },
  "publisher": { "@id": "https://www.example.com/#organization" }
}

FAQPage schema

FAQPage markup describes a page containing a list of questions with answers written by the site owner.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does Example Analytics work with React Native apps?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Example Analytics provides an SDK for React Native versions 0.72 and later. Setup takes about 15 minutes using the installation guide."
      }
    }
  ]
}

Should you still use it? It is optional. It no longer produces Google rich results, and there is no strong evidence it increases AI citations. If you already have it, you can leave it. If you add FAQ content, invest in the quality of the visible answers, which is what readers and AI systems actually read. Tests reported in early 2026 suggest some assistants may read JSON-LD as text, so markup and visible text must say the same thing.

Implementation steps

1. Inventory existing markup. Crawl your site and list every structured data type in use, including markup added by plugins or themes.
2. Remove conflicts. Multiple plugins often output duplicate or contradictory Organization or Product markup.
3. Define the data source. Decide where each value comes from, such as your product database, CMS fields or brand fact base.
4. Template the markup. Generate JSON-LD from templates populated by that source rather than hand-editing.
5. Validate. Use Google's Rich Results Test for supported features and the Schema.org validator for general syntax.
6. Monitor. Check Search Console enhancement reports for errors and warnings, and re-validate after template changes.
7. Audit consistency quarterly. Compare markup, visible content, feeds and third-party profiles.

Common mistakes

Markup that contradicts the page. A different price in schema than on the page undermines trust and can violate Google's structured data guidelines.

Hand-maintained JSON-LD. It drifts out of date. Generate it from your data.

Marking up invisible content. Google's guidelines require markup to represent content visible to users.

Plugin sprawl. Several SEO plugins each adding Organization markup creates duplicates.

Expecting AI citations from markup alone. Current evidence does not support it.

A hypothetical example

A hypothetical outdoor gear retailer finds three problems in its markup audit: two plugins output different Organization names, Product schema shows prices from before a sale, and 40% of products lack GTINs. The fix is to remove one plugin, generate Product markup and the Merchant Center feed from the same product database, and add GTINs from supplier data. The benefit is not a special AI ranking boost. It is that every system reading the site, the feed and the markup sees the same facts.

How Bob Builds AI helps

Bob Builds AI's integrations include a GitHub integration that opens pull requests for schema and technical GEO fixes, and Brand Memory holds the approved facts that markup should reflect. For an industry example, see schema markup for law firms.

---

FAQ

Which schema types matter most for AEO?

Organization, Product with Offer, and SoftwareApplication cover most businesses, with Article for editorial content and LocalBusiness for location-based companies. What matters most is that values are accurate and match the visible page, feeds and third-party profiles.

Is FAQ schema still worth adding in 2026?

It is optional. Google stopped showing FAQ rich results in May 2026, and there is little evidence FAQ markup increases AI citations. Existing markup does no harm. Focus effort on writing strong visible answers to real questions.

Does schema markup help ChatGPT or Perplexity?

Neither OpenAI nor Perplexity has published guidance saying they use Schema.org markup. Tests suggest some assistants may read JSON-LD as page text, while other research indicates some extract only visible HTML. Keep all important facts in visible content.

Where should Organization schema go?

Place it on your homepage or About page, with a stable @id so other markup on the site can reference it. The name, description and logo should match your approved brand facts and official profiles.

How do I validate schema markup?

Use Google's Rich Results Test for features Google supports and the Schema.org validator for general syntax. Then monitor Search Console enhancement reports and re-validate whenever templates change.

Should product schema match my Merchant Center feed?

Yes. Price, availability, identifiers and titles should be identical across your product pages, structured data and Merchant Center feed. Generating all three from the same product database is the most reliable way to prevent mismatches.

Can wrong schema hurt my site?

Markup that misrepresents page content can lead Google to ignore it or take manual action under its structured data guidelines. Contradictory data across markup, pages and feeds can also contribute to inaccurate information in search and AI answers.

---

Conclusion

Schema markup is a consistency layer, not an AI ranking lever. Organization, Product and, optionally, FAQPage markup help search engines understand your entities and products, as long as every value matches what your pages, feeds and profiles say.

Start with an inventory: remove duplicate plugin markup, connect Product markup and feeds to one data source and align your Organization description with your approved brand facts. Bob Builds AI can help you keep those facts consistent and route technical fixes into your development workflow.