Schema Markup SEO: Complete Structured Data Guide

Schema markup is machine-readable code added to webpages to explicitly describe their content, entities, attributes, and relationships.

For example, instead of requiring a search engine to infer that:

• “Acme” is a company

• “Jane Smith” is its CEO

• “TrailPro 35” is its product

• “$149” is that product's price

structured data can explicitly define those relationships.

Schema markup is therefore much more than a rich-snippet tactic.

It can help create a clearer machine-readable representation of:

Who an organization is

What a page represents

Which person wrote an article

Which brand owns a product

Which service a business provides

How those entities relate to one another

Google says structured data gives its systems explicit clues about the meaning of webpages and can make eligible content available for enhanced search appearances called rich results.

Key Takeaways

• Schema markup is structured data that commonly uses the Schema.org vocabulary.

• Google supports JSON-LD, Microdata, and RDFa, with JSON-LD generally recommended.

• Schema markup can help search engines understand content and entity relationships.

• Schema itself is not a direct Google ranking factor.

• Supported structured data can make pages eligible for rich results.

• Correct markup does not guarantee a rich result.

• Schema.org supports far more types and properties than Google uses for Search features.

• Google completely deprecated its FAQ rich-result feature in May 2026.

• Several other Google structured-data search features have also been retired.

• Structured data should accurately reflect information users can see on the page.

• Entity relationships can be made more consistent by using stable @id references.

• Schema may provide useful machine-readable structure for AI systems, but there is insufficient evidence to treat it as a guaranteed AI-visibility factor.

What Is Schema Markup?

Schema markup is code that labels the meaning of information on a webpage using a standardized vocabulary.

The vocabulary most commonly used for SEO comes from Schema.org.

For example, a normal webpage might display:

Acme Digital
100 Main Street
Dallas, TX

A human understands that this likely represents a company and its address.

Schema markup can explicitly describe:

Acme Digital → Organization

100 Main Street → streetAddress

Dallas → addressLocality

Texas → addressRegion

Ahrefs defines schema markup as structured data on webpages that uses the Schema.org vocabulary to communicate page information more explicitly.

What Is Structured Data?

Structured data is information organized according to a standardized format that machines can interpret more consistently.

Google describes structured data as a standardized format for providing information about a page and classifying its content.

Examples include defining:

• Product price

• Article author

• Business address

• Event date

• Recipe ingredients

• Product availability

Schema markup is therefore a type of structured data implementation.

Schema.org vs. Structured Data vs. Schema Markup

These terms are often used interchangeably in SEO, but technically they describe different things.

Structured Data

The broader concept of machine-readable organized information.

Schema.org

A shared vocabulary defining entities, properties, and relationships.

Examples include:

• Organization

• Person

• Product

• Article

• LocalBusiness

Schema Markup

The code placed on a webpage using that vocabulary.

For SEO purposes, people frequently use “schema,” “schema markup,” and “structured data” to describe the overall concept.

How Does Schema Markup Help SEO?

Schema can support SEO in several ways.

It Gives Search Engines Explicit Information

A search engine may be able to determine from page text that something is a product.

Schema can state explicitly:

"@type": "Product"

The same principle applies to:

• Authors

• Organizations

• services

• locations

• events

• recipes

Google specifically says structured data provides explicit clues that help it understand page meaning.

It Can Make Pages Eligible for Rich Results

Supported structured data can make content eligible for enhanced Google Search appearances.

Examples may include:

• Product information

• Recipes

• Events

• Job listings

• Breadcrumbs

• Article enhancements

Google maintains a Search Gallery listing structured-data features currently supported in Search.

It Can Improve Search-Result Presentation

Rich results can sometimes display information such as:

• Ratings

• Prices

• Availability

• Images

• Event dates

Google cites case studies where sites implementing structured data saw higher engagement with enhanced search appearances, though those examples do not establish schema as a direct ranking factor.

Is Schema Markup a Google Ranking Factor?

Schema markup should not be treated as a direct ranking factor.

Google's documentation describes structured data as helping its systems understand content and enabling search features.

It does not say:

Adding schema automatically improves ranking position.

Search Engine Journal's review of Google's historical statements likewise concludes that structured data itself is not a direct web-search ranking factor.

The more accurate relationship is:

Schema → Better explicit understanding

and potentially:

Schema → Rich-result eligibility → More visible search presentation

That can support SEO performance without being a direct ranking boost.

What Are Rich Results?

Rich results are Google Search results containing enhanced visual or interactive information beyond a standard title, URL, and text snippet.

Depending on the feature, they may display:

• Images

• Pricing

• Ratings

• Availability

• Event details

• Recipe information

• Breadcrumbs

Google uses supported structured data to determine eligibility for many of these experiences.

“Rich snippets” is an older phrase frequently used by SEOs for similar enhanced search results.

Does Schema Guarantee Rich Results?

No.

This is one of the most important principles of schema markup SEO.

A page can:

• Use the correct schema type

• Include all required properties

• Pass the Rich Results Test

• Follow Google guidelines

and still receive a normal search result.

Google explicitly says structured-data implementation creates eligibility but does not guarantee rich-result display.

Whether an enhanced result appears can depend on:

• Query

• Device

• location

• page quality

• search context

• Google's algorithms

Do not promise clients guaranteed rich results.

How Schema Markup Works

Structured data creates explicit relationships.

Consider this sentence:

Sarah Brown is CEO of Acme Analytics.

A machine must infer:

Sarah Brown = person

Acme Analytics = company

CEO = role connecting Sarah Brown and Acme Analytics

Structured data can instead state those concepts explicitly.

That is the fundamental value of schema:

Reduce ambiguity.

JSON-LD vs. Microdata vs. RDFa

Google supports three main structured-data formats.

JSON-LD

JSON-LD is normally placed inside a <script> block.

Example:

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

Microdata

Microdata adds properties directly to visible HTML elements.

RDFa

RDFa similarly adds semantic attributes to HTML markup.

Why JSON-LD Is Usually the Best Option

Google recommends JSON-LD in most situations.

It generally provides advantages including:

• Cleaner HTML

• Easier maintenance

• Separation from visual content

• Easier template deployment

• Easier debugging

• Easier entity graph creation

Google supports all three formats when correctly implemented, but its documentation generally recommends JSON-LD.

Schema.org vs. Google-Supported Structured Data

Schema.org contains a much larger vocabulary than Google's Search features support.

This creates two separate questions.

Is this valid Schema.org?

A type may be valid according to Schema.org.

Does Google use it for a Search feature?

That depends on Google's current documentation.

Google explicitly recommends relying on Search Central documentation as the definitive source for Google Search behavior rather than assuming every Schema.org type influences Search appearance.

This distinction became especially important as Google began retiring structured-data search features.

Most Important Schema Types for SEO

The correct schema depends on what the page actually represents.

Organization Schema

Organization identifies a company or organization.

Useful properties may include:

• Name

• URL

• Logo

• address

• contact information

• identifiers

Google currently says Organization structured data on the homepage can help it understand administrative details and disambiguate an organization in search results.

Example

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Acme Analytics",
  "url": "https://example.com/",
  "logo": "https://example.com/logo.png"
}

LocalBusiness Schema

LocalBusiness describes a physical or local business.

Potential properties include:

• Business name

• address

• telephone

• geographic coordinates

• opening hours

Use the most specific appropriate subtype when possible.

Examples may include:

• Dentist

• Restaurant

• Attorney

• Store

The structured data should match the information visible on the website and other official sources.

Article Schema

Article, NewsArticle, and BlogPosting can describe editorial content.

Important relationships include:

Article → author → Person

Article → publisher → Organization

Typical properties include:

• Headline

• author

• image

• datePublished

• dateModified

BreadcrumbList Schema

BreadcrumbList communicates a page's position within the website hierarchy.

Example:

Home → SEO Services → Technical SEO

Breadcrumb structured data can make pages eligible for breadcrumb-style search presentation.

Product Schema

Product describes a product.

Possible information includes:

• Product name

• brand

• SKU

• offers

• reviews

• ratings

For ecommerce sites, Product and Offer structured data can support merchant search experiences involving information such as price and availability.

ProductGroup Schema

ProductGroup can define a family of product variants.

Variants may differ according to:

• Color

• size

• material

• configuration

This is particularly important for ecommerce stores with multiple variants of the same underlying product.

Person and ProfilePage Schema

Person can represent a real person.

ProfilePage can describe a page primarily about that person.

Potential relationships include:

Person → worksFor → Organization

Article → author → Person

These can help establish clearer expert and author identities.

Event Schema

Event can communicate information such as:

• Event name

• date

• location

• organizer

Eligible events may receive enhanced search presentation.

JobPosting Schema

JobPosting can describe legitimate employment opportunities.

It should accurately represent a real job listing and comply with Google's employment-related guidelines.

Recipe Schema

Recipe can describe:

• Ingredients

• preparation time

• nutrition information

• instructions

Google supports several recipe-related search experiences.

QAPage Schema

QAPage applies when a page contains one question with answers contributed by users.

It is not a replacement for the old FAQ schema.

Google still documents QAPage for genuine question-and-answer communities.

What Happened to FAQ Schema?

FAQ structured data has changed significantly.

Google originally reduced FAQ rich-result visibility in 2023, limiting it primarily to certain authoritative government and health sites.

Then, on May 7, 2026, Google deprecated the FAQ rich-result feature completely.

Google subsequently removed:

• FAQ rich-result documentation

• FAQ reporting

• Rich Results Test support

for that Search feature.

This means a typical business should not implement FAQPage markup expecting Google FAQ dropdowns.

You can still publish FAQ content when it helps users.

The visible questions themselves remain useful content.

Which Other Structured Data Types Has Google Deprecated?

Google has also retired Search support for several lower-use structured data features.

These include:

• Course Info

• Claim Review

• Estimated Salary

• Learning Video

• Special Announcement

• Vehicle Listing

The underlying Schema.org vocabulary may still exist or be useful elsewhere.

The change specifically means those types no longer generate the previous Google Search features.

This demonstrates why structured data needs regular auditing.

Schema Markup and Entity SEO

One of the strongest uses of schema is making entity relationships explicit.

Consider a consulting website.

Important entities may include:

• Organization

• Founder

• services

• locations

• articles

A machine-readable graph could establish:

Jeremy Osborn → Person

Jeremy Osborn → worksFor → Acme SEO

Acme SEO → Organization

Technical SEO → Service

Article → author → Jeremy Osborn

This is more useful than treating every schema block as an isolated object.

How to Use @id to Connect Entities

@id can provide a stable identifier for an entity.

Example:

{
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Acme SEO"
}

Another schema object can reference that same organization:

{
  "@type": "Article",
  "publisher": {
    "@id": "https://example.com/#organization"
  }
}

The publisher no longer needs to be redefined inconsistently on every page.

This helps create a coherent structured-data graph.

How to Use sameAs

sameAs can connect an entity to authoritative pages representing the same entity.

Examples may include official:

• LinkedIn profile

• YouTube channel

• industry profile

• social account

Do not add every URL mentioning the company.

The destination should actually represent the same entity.

Google notes that it can make general use of sameAs and other Schema.org properties beyond the specific properties required for rich-result features.

Sitewide vs. Page-Specific Schema

Avoid blindly inserting every schema type onto every page.

Sitewide entities may include