Schema Markup

What is schema markup?

Schema markup is structured data that you add to a webpage to describe its content in a machine-readable format. It gives search engines more explicit information about what a page, organization, person, product, service, article, event, FAQ, or other entity represents.

Instead of relying only on visible copy and page structure, search engines can use structured data to interpret relationships between entities and attributes more precisely.

The vocabulary most commonly used for this is Schema.org, while JSON-LD is the format Google generally recommends for implementing structured data on webpages.

Why is schema markup important for SEO?

Schema markup helps search engines understand content more accurately. It can clarify who an organization is, what a page is about, which entity an author represents, how a product is described, or which information belongs to a particular content type.

Valid structured data can also make certain pages eligible for enhanced search-result features, often called rich results. Eligibility does not guarantee that Google will display a rich result, but schema provides the structured information required for supported result types.

Schema markup should therefore be viewed as a semantic and technical SEO layer rather than as a direct ranking shortcut.

Is schema markup a ranking factor?

There is no strong evidence that adding schema markup by itself directly improves organic rankings. Structured data is primarily useful because it gives search engines explicit information about a page and, for supported types, can make pages eligible for richer search-result features.

This distinction matters. Schema can improve how clearly information is represented to machines and can influence search appearance through eligible rich results, but that is different from demonstrating a direct ranking boost.

Its SEO value therefore comes from improving machine-readable context, reducing ambiguity, supporting entity understanding, and enabling supported search features rather than acting as a ranking shortcut.

What does the research say about schema and AI Search?

The evidence for a direct AI Search visibility benefit is currently limited. One of the largest recent studies was conducted by Ahrefs in 2026. Their initial analysis of approximately six million URLs found that pages cited by AI were almost three times more likely to contain JSON-LD than pages that were not cited. However, this showed correlation rather than causation.

Ahrefs then tracked 1,885 pages that added JSON-LD between August 2025 and March 2026 and compared them with approximately 4,000 control pages. They measured citation changes across Google AI Overviews, Google AI Mode, and ChatGPT. Adding schema produced no meaningful citation uplift in AI Mode or ChatGPT. The measured changes were +2.4% for AI Mode and +2.2% for ChatGPT, both statistically indistinguishable from zero. AI Overviews showed a small decline relative to controls, but the researchers cautioned against interpreting this as evidence that schema harms AI visibility.

This is important because websites using schema are often technically stronger websites overall. They may also have better content, stronger authority, more backlinks, and higher traditional search rankings. Schema can therefore correlate with AI citations without being the cause of those citations.

You can read the Ahrefs study on schema and AI citations for the full methodology and results.

Does schema markup help AI Search?

Schema markup can help create a clearer machine-readable representation of entities and relationships, but there is currently no strong evidence that adding schema by itself increases citations in ChatGPT, Google AI Mode, or other generative search experiences.

For that reason, schema should not be positioned as a direct AI Search ranking factor. It is better understood as part of the technical and semantic foundation of a website.

For B2B websites, a useful approach is to connect important entities such as the Organization, People, Services, Articles, Authors, and other relevant entities through accurate structured data. This should reinforce information that is already visible and consistent across the website.

AI Search visibility still depends on a broader set of factors including strong content, authority, external corroboration, internal linking, technical accessibility, traditional search visibility, and consistent entity information. Overflow's AI Search playbook focuses on this broader approach.

What is structured data?

Structured data is information written in a standardized format that software can parse consistently. Schema markup is one of the most common applications of structured data on websites.

For example, a normal page may state that Overflow Agency is a company. Organization schema can explicitly label the organization name, website, logo, and other relevant properties so machines do not have to infer every relationship from prose alone.

What is Schema.org?

Schema.org is a shared vocabulary for structured data. It defines types such as Organization, Person, Article, Product, Service, Event, BreadcrumbList, and many others, together with the properties that can describe those entities.

The vocabulary is broader than the specific schema types Google currently supports for rich results. A schema type can still be semantically useful even when it does not trigger a special search-result feature.

What is JSON-LD?

JSON-LD stands for JavaScript Object Notation for Linked Data. It is a structured data format that can be placed in a script element in the page's HTML.

JSON-LD separates structured data from visible page markup, which makes it relatively easy to manage and update. A simplified Organization example looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Company",
  "url": "https://example.com"
}
</script>

The values in structured data should match the actual content and entity information on the website. Schema should never be used to describe information that is misleading or absent from the page.

What are common types of schema markup?

The right schema depends on the type of page and the information actually present. Common examples include:

• Organization schema: describes a company or organization.
• Person schema: describes an identifiable person such as an author or expert.
• Article schema: describes editorial content such as articles or blog posts.
• Product schema: provides structured information about a product.
• Service schema: can describe services and the provider behind them.
• BreadcrumbList schema: describes the page's position within a site's hierarchy.
• Event schema: describes events, dates, locations, and related details.
• JobPosting schema: describes job vacancies.
• FAQPage schema: describes frequently asked questions where its use complies with current search-engine guidelines.

How do you choose the right schema type?

Start with what the page actually represents. Do not select a schema type simply because it looks likely to produce a more prominent search result.

A company homepage may use Organization schema. An editorial article may use Article schema and reference its author. A vacancy page may use JobPosting schema. A page can also contain multiple compatible entities when those relationships are accurate.

The structured data should reinforce the site's real information architecture and entity model rather than create an alternative version of the content for crawlers.

Schema markup and entity SEO

Schema is particularly useful for entity-based SEO because it lets a website express relationships explicitly. An article can reference an author, an author can be associated with an organization, and an organization can reference its official website and other identifying information.

This can help search systems connect information about the same entity across different pages and sources. A strong SEO taxonomy, consistent naming, internal links, and structured data can work together to reduce ambiguity.

How do you add schema markup in Webflow?

Schema markup can be added to Webflow using custom code, typically as JSON-LD placed in the page head or before the closing body tag. Static pages can use page-level custom code, while CMS-driven websites often need dynamic structured data populated from CMS fields.

For example, a CMS article template can use fields for the title, publication date, author, image, and canonical URL to generate Article structured data for every article.

For scalable implementations, the schema architecture should be planned together with the CMS model. This reduces duplicated manual code and helps ensure structured data remains synchronized with the visible content.

Overflow's Webflow SEO services combine technical SEO, CMS architecture, metadata, structured data, internal linking, and indexation. The Webflow agency offering covers the broader design and development implementation.

Schema markup vs. meta tags

Meta tags and schema markup both provide information about a page, but they serve different purposes. A meta description provides a concise page summary that can be used in a search-result snippet. Schema markup describes entities, properties, and relationships in a structured vocabulary.

A canonical tag serves another technical purpose: it signals which URL should be treated as the preferred version when duplicate or very similar URLs exist.

These elements complement one another, but they are not interchangeable.

What are common schema markup mistakes?

• Marking up information that is not visible or true: structured data should accurately reflect the page.
• Using the wrong schema type: choose the entity that genuinely matches the content.
• Adding invalid JSON-LD: syntax errors can prevent structured data from being parsed.
• Using outdated properties: schema and search-engine requirements change over time.
• Expecting guaranteed rich results: valid markup creates eligibility, not certainty.
• Treating schema as an AI ranking hack: current research does not show a meaningful causal uplift in AI citations simply from adding JSON-LD.
• Adding schema without a coherent entity strategy: inconsistent names, URLs, or entity relationships can reduce clarity.
• Forgetting dynamic CMS pages: scalable sites should generate appropriate schema for relevant collection items.

How do you test schema markup?

Structured data should be validated after implementation. Google's Rich Results Test can check markup related to Google-supported rich result types, while the Schema.org validator can help inspect broader Schema.org vocabulary and syntax.

Validation is only one step. You should also confirm that the properties match the visible page content, canonical URL, current entity information, and intended page type.

Can one page have multiple schema types?

Yes. A page can describe multiple related entities when that accurately reflects its content. For example, an Article entity can reference a Person as its author and an Organization as its publisher.

What matters is that the relationships are clear and valid. Adding as many schema types as possible does not make a page stronger; relevant and accurate structured data is more useful than excessive markup.

Key takeaway

Schema markup is structured data that helps search engines and other machines interpret the entities and information on a webpage. It is commonly implemented with Schema.org vocabulary in JSON-LD format.

The strongest evidence supports schema for clearer machine-readable information and eligible rich search features. Current research does not show that adding schema alone reliably improves organic rankings or AI citations. Schema should therefore be used as part of a broader technical SEO, entity, and AI Search strategy rather than treated as a direct ranking factor.