A website has several jobs. It needs to explain your business, work smoothly, and help visitors take the next step.
It also needs to communicate with the systems that discover and interpret its content.
People can usually tell whether a webpage is a blog post, a product listing, or an event announcement. Schema markup helps search engines identify those details too.
It adds information to your page’s code, such as who wrote a post, how much a product costs, or when an event takes place.
Schema helps search engines understand your content. But adding it does not guarantee that your website will rank higher or appear in AI answers.
Let’s look at how schema works and how to use it on your website.
What Is Schema Markup?
Schema markup is structured data that describes the information on a webpage using a shared vocabulary, usually from Schema.org.
A visitor might recognise a page as a blog post because it has a headline, an author, and a publication date. Structured data explicitly labels those details for systems that support it.
For example, it can describe:
- The person who wrote an article.
- The organisation behind a website.
- A product and its current offer.
- An event and its location.
Google uses structured data to help understand page content and support eligible search features. Google recommends JSON-LD when the site’s setup allows it.
Clarity first. Markup second.
Schema Markup and WebSite Schema Are Different
“Website schema” is often used as a general term, but WebSite is one specific Schema.org type.
A complete implementation might describe several connected things:
| Type | What it describes |
|---|---|
WebSite | The website itself |
WebPage | An individual page |
Person | An author or individual |
Organization | A company or organisation |
BlogPosting | A blog article |
Product | A product |
Event | An event |
The right choice depends on what the page actually contains. A service landing page should not be labelled as a blog post simply because the website also has a blog.
Schema.org defines the vocabulary; individual search engines decide which types and properties support their features.
What Does Schema Look Like?
Here is a simplified example describing a blog article:
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Schema Markup in the AI Search Era",
"author": {
"@type": "Person",
"name": "Prathamesh Bhagat",
"url": "https://prathameshbhagat.com/"
}
}This example illustrates the structure. It is not a complete implementation or a guarantee of eligibility for a Google feature. A production setup should reflect the published article and follow the applicable feature documentation.
What Schema Can—and Cannot—Do
Correct markup can make a page eligible for supported rich results.
However, eligibility does not guarantee display. Google may choose a standard result even when the markup passes validation.
The details must also reflect the visible page. Invented ratings, misleading business information, or markup for unrelated content create inconsistencies and can violate Google’s structured data policies.
From a business perspective, I would treat schema as part of accurate website maintenance. It helps describe what exists; it cannot compensate for an unclear offer or an unhelpful page.
Does Schema Help You Appear in AI Search?
This is where careful wording matters.
Google says there is no special Schema.org markup required for AI Overviews or AI Mode. Its existing SEO fundamentals still apply.
Those include crawlable pages, useful text, internal links, and structured data that matches the content.
Google also states that eligibility does not guarantee inclusion. Its guidance should not be treated as proof of how every other AI platform selects sources.
My practical approach is to make a website understandable first:
- Explain the service clearly.
- Answer real customer questions.
- Show who is responsible for the content.
- Support claims with evidence.
Then use structured data to describe that information consistently.
Two Pieces of Advice That Need Updating
FAQ markup no longer produces Google FAQ rich results
Google’s documentation records that FAQ rich results stopped appearing from May 7, 2026.
A useful FAQ section still helps visitors understand pricing, timelines, or your process. Its value should come from answering those questions—not an expectation of expandable Google results.
SearchAction does not restore Google’s sitelinks search box
Google retired the sitelinks search box in November 2024.
Its announcement clarified that WebSite markup for site names remained supported. These are separate uses, so an old tutorial’s search-box example should not be mistaken for a current Google feature.
A Practical WordPress Workflow
Before adding custom code, inspect what your website already outputs.
Your SEO plugin, theme, or another plugin may already generate structured data.
Here is the workflow I recommend:
- Identify the page’s purpose. Is it an article, product, profile, or something else?
- Inspect the existing output. Search the page source for
application/ld+json. - Check the facts. Review names, URLs, authors, dates, images, and business details.
- Resolve conflicting output. Avoid separate implementations describing the same item differently.
- Validate the result. Use the Schema Markup Validator for vocabulary checks and Google’s Rich Results Test for supported Google features.
- Maintain it. When the underlying content changes, review its structured data too.
Treat validation as a technical check, not a promise of search visibility. Correct implementation and guaranteed rich-result display are different things.
Start With the Information, Then Add the Markup
For a developer’s portfolio, I would prioritise clear services, identifiable authorship, and project pages that explain the work honestly.
For a business website, I would begin with accurate business details and pages that answer customers’ questions.
The implementation should follow those needs.
A website becomes more useful when people can understand what it offers and systems can interpret its information consistently.
That is the role I see for schema in modern development: a practical layer of clarity, supported by accurate content and regular maintenance.