Schema Markup and Structured Data for AI: Technical Guide to Help LLMs Understand and Cite Your Brand

Structured data states basic facts about your brand in a standard, machine-readable format. Search engines, and the AI products built on them, need to understand what your brand is, what it offers, where it operates and who stands behind it, and schema markup is where those facts are declared.

Some industry studies report that many pages cited by AI products carry schema markup. Those figures describe their own samples and dates, and they show correlation: well-maintained sites tend to have schema and good content at the same time. Schema has not been shown to cause citations on its own.

This guide explains which schemas are most useful, how to implement them with copy-paste code and what they can and can't do for your AI visibility.

What Is Schema Markup and Why It Matters

Schema markup is code you add to your website's HTML to explain to machines — search engines and AI models — what each element on your page means. It uses the Schema.org vocabulary, backed by Google, Bing, Yahoo, and Yandex.

Without schema, systems have to infer these facts from your text. With schema, you state them explicitly: "this is a company, it operates in these markets, offers these services, and this is its founder."

Schema has long been used for rich results in Google (stars, prices, breadcrumbs). It also helps search systems, including those that feed AI answers, interpret a page's entities and facts without ambiguity.

As our AI SEO guide explains, clear, consistent facts about your brand reduce the room for errors. Schema is one way to state them, alongside visible text; it doesn't guarantee that an AI product will prefer your page.

What the Evidence Says: Does It Affect AI Citations?

Published analyses of AI citations, such as an AccuraCast study of about 2,000 queries across ChatGPT, Google AI Overviews and Perplexity, report which schema types appear on cited pages. Read them with care:

Presence is not preference. If a large share of cited pages carry Person or Organization schema, that may simply reflect that established publishers use schema widely. It doesn't show that ChatGPT chose them because of it.

Common types on cited pages include BreadcrumbList, WebSite, Organization and WebPage — the types many CMSs add automatically. Their frequency tells you what is widespread, not what drives citations.

Each product works differently. Perplexity, ChatGPT search and Google each use their own retrieval systems, and none of them documents schema as a requirement for being cited. Google states that no special schema is needed to appear in AI Overviews.

The practical conclusion: modern systems can understand well-written content without schema. Schema is still worth adding because it states key facts unambiguously and supports eligible rich results in Google.

7 Useful Schemas for AI Visibility

You don't need every schema type. These are the most useful ones for describing your brand and content:

1. Organization — Who You Are

Describes the company: name, website, logo, contact and official profiles (sameAs).

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://yourcompany.com",
  "logo": "https://yourcompany.com/logo.png",
  "description": "Clear description of what you do and for whom",
  "foundingDate": "2020",
  "areaServed": ["United States", "United Kingdom", "Spain", "Mexico"],
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "[email protected]",
    "contactType": "customer service"
  },
  "sameAs": [
    "https://www.linkedin.com/company/yourcompany",
    "https://twitter.com/yourcompany"
  ]
}

For local businesses (restaurants, clinics, hotels), use LocalBusiness or a more specific subtype instead of Organization, with a full address and geo coordinates, which help match the business to local searches.

2. Person — Who Writes

Person schema links your content to a real author with verifiable profiles.

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Author Name",
  "jobTitle": "Marketing Director",
  "worksFor": {
    "@type": "Organization",
    "name": "Your Company"
  },
  "url": "https://yourcompany.com/team/name",
  "sameAs": [
    "https://www.linkedin.com/in/name"
  ]
}

It makes authorship explicit, which supports the E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness) that readers and Google's quality guidelines look for. It's a description of the author, not a ranking factor on its own.

3. Article / BlogPosting — Your Editorial Content

For articles: headline, author, publication and update dates, publisher.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Title",
  "author": {
    "@type": "Person",
    "name": "Author Name"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Company",
    "logo": {
      "@type": "ImageObject",
      "url": "https://yourcompany.com/logo.png"
    }
  },
  "datePublished": "2026-04-02",
  "dateModified": "2026-04-02",
  "description": "Clear article description",
  "image": "https://yourcompany.com/article-image.jpg"
}

Key point: update dateModified when you substantially revise an article, and show the same date on the page. It helps systems that care about freshness tell whether the information is current; don't change it without real changes.

4. FAQPage — Questions and Answers

It describes visible questions and answers. Google now shows FAQ rich results only for a limited set of sites (mainly authoritative government and health sites), so for most sites the benefit is a clear description of content, not a rich result.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is AI visibility for brands?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "AI visibility is the frequency and quality with which language models like ChatGPT, Gemini, and Perplexity mention and recommend your brand when a user asks questions relevant to your industry."
      }
    }
  ]
}

Write each answer so it fully answers the question; there's no ideal word count. The markup must match the FAQ visible on the page.

5. HowTo — Step-by-Step Guides

Step-by-step procedures are easy to follow and quote. You can describe them with HowTo schema, but note that Google no longer shows HowTo rich results; its value is descriptive.

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Measure Your AI Visibility",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Define your reference questions",
      "text": "Think about the questions your customers would ask ChatGPT about your industry."
    },
    {
      "@type": "HowToStep",
      "name": "Query multiple LLMs",
      "text": "Test at least ChatGPT, Gemini, and Claude to get a representative picture."
    }
  ]
}

6. Product / Service — What You Sell

Important for ecommerce. Google uses Product markup for shopping results, and AI shopping features generally rely on product feeds (for example Merchant Center or the ChatGPT product feed) as well as page data. Keep both consistent.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Product Name",
  "description": "Clear product description",
  "brand": {
    "@type": "Brand",
    "name": "Your Brand"
  },
  "offers": {
    "@type": "Offer",
    "price": "29",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://yourcompany.com/product"
  }
}

Use the appropriate priceCurrency for your market: "USD" for the US, "EUR" for Europe, "GBP" for the UK, so prices are interpreted correctly.

7. BreadcrumbList — Your Site Structure

It's very common on websites. It doesn't describe your content directly, but it shows how your site is organized and the hierarchy of your pages.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {"@type": "ListItem", "position": 1, "name": "Home", "item": "https://yourcompany.com"},
    {"@type": "ListItem", "position": 2, "name": "Blog", "item": "https://yourcompany.com/blog"},
    {"@type": "ListItem", "position": 3, "name": "Schema Markup for AI", "item": "https://yourcompany.com/blog/schema-ai"}
  ]
}

How to Implement Schema Step by Step

Step 1: Audit What You Already Have

Check what you already have with the Schema Markup Validator (validator.schema.org) or Google's Rich Results Test. WordPress (with Yoast or Rank Math), Shopify and Wix often add basic markup; verify it is correct and matches the visible page.

Step 2: Prioritize by Business Type

You don't need all 7 schemas from day one. Prioritize like this:

All businesses: Organization (or LocalBusiness) and BreadcrumbList.

Blogs and editorial content: Article/BlogPosting and Person; FAQPage only where the page shows real Q&A (Google shows FAQ rich results only for a few authoritative government and health sites).

For ecommerce: add Product with prices and availability.

Professional services: Service and, where relevant, LocalBusiness subtypes. HowTo no longer produces rich results in Google.

Step 3: Generate Code with AI Help

You don't need to be a programmer. You can use ChatGPT or Claude to generate JSON-LD: "Generate an Organization schema in JSON-LD for my company [name], which operates in [countries], offers [services], and is located at [address]." Then validate it with the tools from step 1.

Step 4: Implement on Your Website

Add the JSON-LD code inside a script tag in your HTML head or body. On WordPress, plugins like Rank Math or Yoast handle it without code. On builders like Lovable, Webflow or Wix, use the custom code section or the platform's SEO settings.

Step 5: Validate and Monitor

After implementation, check the relevant reports in Google Search Console to confirm Google reads your structured data without errors. Processing can take days or weeks.

To look for an effect on AI visibility, analyze your brand with Mentio before and after implementing schema and compare mention rate and position. Other changes happen at the same time, so treat any difference as a correlation to investigate. Our guide on how to measure your AI visibility explains which metrics to track.

3 Common Mistakes to Avoid

Fake or inflated data: don't mark up ratings or reviews you don't have. Markup that misrepresents the page breaks Google's structured data guidelines and can lead to a manual action that removes rich results, and it contradicts other public sources. Only include verifiable data.

Vague geographic information: putting just "United States" or "London" for a local business, without a full address or coordinates. Include a complete address with latitude and longitude.

Generic FAQs: answers that don't actually answer the question. Each answer should give useful, specific information, and the markup must match the visible text. These are some of the common mistakes that make AI ignore your brand.

What Schema Does Not Do

Structured data makes your facts clearer, but it's not a shortcut to citations. Without quality content, presence in external sources (see our post on Reddit, LinkedIn and forums as AI sources) and a good reputation, schema only describes who you are — not why you're the best option.

Schema is one technical part of a GEO strategy. It works together with content, authority, external presence and measurement. As the comparison of how each LLM chooses sources shows, each product relies on different signals.

5 Copy-Paste Schema Blocks

Five JSON-LD blocks that cover most sites. Copy them into your <head>, replace the bracketed values and delete any field you can't fill with real data. Include aggregateRating only if the page shows genuine reviews.

1. Organization (on your homepage)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "[Your brand name]",
  "alternateName": ["[Old name if rebranded]", "[Name variants]"],
  "url": "https://[yourdomain.com]",
  "logo": "https://[yourdomain.com]/logo.png",
  "description": "[1-2 sentence description of your company]",
  "sameAs": [
    "https://linkedin.com/company/[your-company]",
    "https://twitter.com/[your-company]",
    "https://crunchbase.com/organization/[your-company]"
  ],
  "foundingDate": "[YYYY-MM-DD]",
  "founder": {
    "@type": "Person",
    "name": "[Founder name]"
  }
}

2. Product (on each product page)

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "[Product name]",
  "description": "[Product description]",
  "brand": {
    "@type": "Brand",
    "name": "[Your brand name]"
  },
  "offers": {
    "@type": "Offer",
    "price": "[price]",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "[4.5]",
    "reviewCount": "[123]"
  }
}

3. FAQPage (on posts and landings with FAQ)

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "[Question 1]",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Answer 1]"
      }
    },
    {
      "@type": "Question",
      "name": "[Question 2]",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Answer 2]"
      }
    }
  ]
}

4. Article (on each blog post)

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "[Post title]",
  "description": "[Post meta description]",
  "author": {
    "@type": "Organization",
    "name": "[Your brand]"
  },
  "publisher": {
    "@type": "Organization",
    "name": "[Your brand]",
    "logo": {
      "@type": "ImageObject",
      "url": "https://[yourdomain.com]/logo.png"
    }
  },
  "datePublished": "[YYYY-MM-DD]",
  "dateModified": "[YYYY-MM-DD]",
  "image": "https://[yourdomain.com]/image.jpg"
}

5. Service (on service landing pages)

{
  "@context": "https://schema.org",
  "@type": "Service",
  "serviceType": "[Service type]",
  "provider": {
    "@type": "Organization",
    "name": "[Your brand]"
  },
  "areaServed": {
    "@type": "Country",
    "name": "[Country]"
  },
  "description": "[Service description]",
  "offers": {
    "@type": "Offer",
    "price": "[price or range]",
    "priceCurrency": "USD"
  }
}

How to Test the Effect of Schema

Instead of relying on anecdotes, test on your own site:

1. Record a baseline. Before changing anything, record mentions, position and the facts answers state about you (for example, with the same prompt set in Mentio), plus Google impressions and clicks for the affected pages.

2. Change one thing. Add or fix the schema on a defined set of pages and note the date. Avoid publishing other large changes to the same pages at the same time.

3. Compare after several weeks. Re-run the same prompts and reports. If results improve, check whether other factors (new content, links, model updates) could explain it before crediting schema.

Page markup and feed ingestion are different layers. If you sell products, review the ChatGPT product feed too: a passing schema test does not prove that a catalog upload was accepted.

Describing entities and executing tasks are different problems. Complement your markup with an AI-agent navigation and form audit that checks controls, visible state and verifiable outcomes.

Compare AI Visibility Separately

Validate the markup itself with the Google testing tools described above. With Mentio you can run a before-and-after analysis of your visibility, position and sentiment in the models included in your plan and compare the results; it is an observational comparison, not a schema validator.

Markup works alongside the content it describes; see how to organize that content in a GEO content cluster.

Before writing schema, define the identity it will represent with an AI brand entity audit: canonical names, hierarchy, aliases and verified facts.

Measure your visibility before and after →

Want to know if AI mentions your brand?

Discover your visibility in ChatGPT, Claude and Gemini in minutes.

Related articles