GEO Course
Structured Data and Schema for AI and Search Visibility
By Sanita | Generative Engine Optimization Specialist
Which schema.org types to use for AI and search visibility: Organization, Article, Product, LocalBusiness and more, with JSON-LD examples and honest limits.
Updated 11 November 2026 · Part of the GEO guide series
Short answer: Structured data, usually written as schema.org markup in JSON-LD, describes what a page is about in a form that machines can read: who published it, who wrote it, what the product costs, where the business is. It can help search engines and other systems understand your pages and may make some pages eligible for rich results. It does not guarantee rankings, rich results or AI citations, and Google says it does not require any special markup for its AI features. Use it to describe visible content accurately, keep it consistent with the page and validate it.
What Structured Data Does and Does Not Do
- It does: label entities and facts in your content, such as an organization, a person, an article, a product or a local business, in a format that is easy to parse.
- It can: make pages eligible for certain rich results in Google, and help systems connect your pages to the right entity.
- It does not: replace good content, improve rankings by itself or guarantee that an AI tool will cite you. Google states that you do not need to create special files or markup to appear in AI Overviews and AI Mode, and no AI company has published a promise that schema increases citations.
Think of schema as removing ambiguity, not adding a boost. The visible page remains the most important thing.
Schema.org and JSON-LD in Brief
Schema.org is a shared vocabulary of types (such as Organization, Article, Product) and properties (such as name, author, price). JSON-LD is the format Google recommends for adding it: a script tag that holds the data and does not change how the page looks.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Analytics Ltd",
"url": "https://www.example.com",
"logo": "https://www.example.com/images/logo.png",
"sameAs": [
"https://www.linkedin.com/company/example-analytics",
"https://www.crunchbase.com/organization/example-analytics"
]
}
</script>
(Example values.) Put the markup in the page's HTML, ideally in the server-rendered or prerendered HTML so that crawlers that do not run JavaScript can read it. Only mark up information that is visible on the page.
Which Types to Prioritize
| Type | Where | Why it is useful |
|---|---|---|
| Organization | Home page or About page | Names the business and links its official profiles with sameAs |
| Person | Author and team pages | Connects content to real people and their credentials |
| Article or BlogPosting | Posts and guides | States headline, author, dates and publisher |
| Product with Offer and review data | Product pages | Describes price, availability and ratings, and supports product rich results where eligible |
| LocalBusiness (or a more specific subtype) | Location pages | States address, hours and phone for each location |
| BreadcrumbList | Pages in a hierarchy | Shows page position within the site |
| FAQPage, HowTo | Pages with visible Q&A or steps | Describes content, but Google no longer shows these rich results for most sites |
Order matters. Start with Organization, then Article on content pages, then Product or LocalBusiness if they apply. Add the rest only when you can maintain them.
Organization and Person
Google says Organization markup can help it understand your administrative details and disambiguate your organization. Include your official name, URL, logo and a short description, plus sameAs links to profiles that you really run, such as LinkedIn, Crunchbase or an app store listing. For people, add a Person node on author pages with the name, job title, a short bio and links to professional profiles, and connect articles to that person. Keep names and descriptions identical to what you use elsewhere. See entity clarity and E-E-A-T for GEO.
Article and BlogPosting
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Write Content for AI Retrieval",
"author": { "@type": "Person", "name": "Jane Doe" },
"publisher": { "@type": "Organization", "name": "Example Analytics Ltd" },
"datePublished": "2026-03-01",
"dateModified": "2026-10-15",
"mainEntityOfPage": "https://www.example.com/blog/ai-retrieval/"
}
</script>
Match the headline to the visible title, use real dates and keep dateModified honest: change it only for meaningful updates. Do not invent authors or credentials.
Product and Review Markup
For product pages, mark up the name, image, description, brand, price, currency and availability, and ratings only if they come from real, visible reviews of that product. Keep prices and stock in step with the page and the feed, because mismatches cause problems in search and Shopping. Never copy ratings from another source, or mark up reviews you wrote yourself. If your platform adds Product markup automatically, check what it outputs and fix gaps rather than adding a second conflicting block.
LocalBusiness
Use the most specific subtype that fits, such as Dentist or VeterinaryCare, and include the address, phone, opening hours, geo coordinates and the URL of the location page. For several locations, give each its own page and its own markup, not 1 block with the head office address. Make sure details match your Google Business Profile. See local SEO.
FAQPage and HowTo
These types describe visible questions and answers or steps. Google announced in 2023 that FAQ rich results would be limited to well-known government and health sites and that it would stop showing HowTo rich results, so for most sites they no longer produce visible results in Google. They can still describe the content accurately, but do not add them for the dropdowns, and do not mark up content that is not on the page. See FAQ schema and structured answer markup.
Example: A Small Store Cleans Up Its Markup
(Illustrative.) An outdoor gear store runs its pages through the Rich Results Test and the Schema Markup Validator and finds:
- Product pages have 2 conflicting Product blocks, one from the theme and one from an app.
- Some prices in the markup are months old.
- Rating markup appears on products with no visible reviews.
The fix: keep the platform's block, add the missing properties to it, remove the app's duplicate, connect prices to the live price field and show rating markup only where real reviews appear. The store then re-tests, and checks Search Console's enhancement reports after Google recrawls.
Validation and Maintenance
- Test with Google's Rich Results Test for eligible rich results and the Schema Markup Validator for general schema.org checks.
- Compare the markup with the visible page. Every fact in the markup should be visible or accurate.
- View the rendered and the raw HTML to make sure that the markup is present for crawlers that do not run JavaScript.
- Monitor Search Console reports for errors and warnings.
- Update markup when prices, hours, authors or products change.
A free SEO audit reports whether structured data is detected on a page, which makes a quick first check. To see whether AI crawlers can reach the page at all, use the AI crawler access check, and see how assistants describe your brand with the AI visibility checker.
Common Mistakes
- Marking up information that is not visible on the page.
- Duplicate or conflicting blocks from a theme, plugin and manual code.
- Fake or copied reviews and ratings.
- Out-of-date prices, hours and dates.
- Using the wrong type, such as FAQPage for sales copy.
- Expecting markup to fix weak content or to guarantee AI citations.
- Markup added only by JavaScript that crawlers may not run.
Action Checklist
- Add Organization markup to the home page, with accurate
sameAslinks. - Add Article or BlogPosting with author and dates to content pages.
- Add Product or LocalBusiness markup where relevant.
- Validate each template, not just 1 page.
- Re-check after site updates and set a quarterly review.
Related Guides
- Structured Data and Rich Results
- FAQ Schema and Structured Answer Markup
- What Is GEO?
- AI Search and Modern SEO
FAQs
Does Schema Markup Help Me Get Cited by AI Tools?
There is no public confirmation that it does. It helps systems understand your pages, which is useful, but AI tools do not publish how they choose sources. Treat it as a description of your content, not a ranking trick.
Is JSON-LD Better Than Other Formats?
Google recommends JSON-LD because it is easy to add and maintain without changing the visible HTML. Microdata and RDFa are also valid.
Which Schema Type Should I Add First?
Organization on your home page, then Article on content pages, then Product or LocalBusiness if they apply to your site.
Can Wrong Schema Hurt Me?
Misleading markup can cause Google to ignore it or to take manual action against it. Accurate markup that matches the page is safe. Remove anything that you cannot keep correct.
Do I Need a Plugin?
Not necessarily. Many CMS plugins generate markup, but check what they output and avoid duplicates. Hand-written JSON-LD in a template works well for simple sites.