Every page on the web is written for humans. Search engines read the same pages, but they have to infer meaning from the structure of the HTML — headings, paragraphs, links, and images. Sometimes that inference is easy. Sometimes it is wrong.
Schema markup exists to remove that guesswork. It is a small piece of code that tells search engines, in a format they understand, what a page is about and what its key details are.
This guide explains what schema markup is, why it matters, the common types worth knowing, and how to add it to a page without any coding background.
Schema Markup Generator Meta Tag Generator Google SERP Preview Open Graph Preview On-Page SEO Checker
What schema markup actually is
Schema markup — also called structured data — is a standardized vocabulary that describes the content of a web page. It is written in a format called JSON-LD, which is a small block of JavaScript that sits in the page's HTML and is not visible to human visitors.
A search engine reading the page sees both the visible content and this hidden structured data. The structured data explicitly says what the page is, who published it, what it is about, and the key facts a reader would care about.
The vocabulary itself is maintained by an open community called Schema.org. It includes hundreds of defined types — Article, Product, FAQPage, Recipe, Event, LocalBusiness, Person, Organization, and many more.
Why search engines need this
Consider two pages with identical HTML structure. One is a blog post about a product. The other is the product listing itself. To a human, they look completely different. To a search engine, the HTML may be similar enough that it has to infer which is which.
Schema markup tells the search engine exactly which one is which — no inference needed.
Why it matters for a small store
Schema markup is often described as advanced SEO. In practice, it produces two meaningful benefits even for a small site, and both matter more than most sellers expect.
1. Rich results in search
When a page has schema markup, search engines can display extra elements in the search result. These are called rich results, and they stand out visually.
| Schema type | What shows in search results |
|---|---|
| Product | Price, availability, star ratings |
| FAQPage | Expandable question and answer pairs |
| Article | Headline, thumbnail, publication date |
| Recipe | Cooking time, calories, star ratings |
| Event | Date, location, ticket availability |
| LocalBusiness | Address, hours, phone number |
A rich result takes up more space on the search page. It is more visually distinctive than a standard blue link. In competitive search results, that difference often produces more clicks — even when the ranking position is the same.
2. Clearer understanding of the page
Search engines use the structured data to build a clearer picture of what a page offers. This affects which searches the page is eligible to appear in. A product page with Product schema can show up in searches that specifically look for products. A page with FAQPage schema can surface on searches phrased as questions.
Neither of these is a ranking boost in the traditional sense. They are changes to which searches the page can be shown for — which, in practice, often amounts to the same result.
Schema markup is not a ranking hack
This is worth stating clearly, because it is where most early articles about schema markup overpromise. Schema markup is not a direct ranking factor.
Adding schema markup to a page will not move it from position 30 to position 5. It will not produce backlinks. It will not make content rank for keywords the content is not actually about.
What it does is help search engines understand the page and display it more richly. In competitive categories, that often produces more clicks. Whether that results in a ranking change is a side effect, not the point.
Misleading markup
Search engines have explicit policies against structured data that misrepresents the page. Marking up content that does not appear on the page — or claiming ratings or reviews that are not real — can result in a manual action that removes rich results across the whole site.
Schema markup should always reflect the actual content of the page. If the page does not have 5-star reviews, do not mark it up as if it does.
The common schema types
Most sites only need three or four schema types. Each one applies to a specific kind of page.
Article
Used for blog posts, news articles, and long-form guides. Marks the headline, author, publisher, publication date, and featured image.
Why it helps: search engines can display article thumbnails and dates in search results, which many searchers use as signals of freshness and relevance.
Product
Used for product pages. Marks the product name, description, price, currency, availability, brand, and optionally ratings and reviews.
Why it helps: this is the schema that produces price, availability, and star ratings in search results — one of the most visually prominent rich results.
FAQPage
Used for pages that answer a list of common questions. Marks each question and its answer.
Why it helps: search engines can display the questions as expandable dropdowns beneath the search result. This can significantly increase the amount of space a result takes on the page.
Organization
Used on the homepage and about page. Marks the site's name, logo, contact details, and social profiles.
Why it helps: contributes to brand recognition in search results and helps search engines connect the site to its identity across the web.
BreadcrumbList
Used to mark the site's navigation path. Instead of showing a URL in the search result, the search engine shows the breadcrumb trail (Home › Guides › Schema Markup).
Why it helps: cleaner, more scannable search results. Small improvement, but consistent.
LocalBusiness
Used for businesses with a physical location. Marks address, phone, opening hours, and business type.
Why it helps: feeds into local search results and map listings. Only relevant for businesses with a physical presence.
What schema markup looks like
A single schema block is small. This is an example of Article schema for a blog post:
Example — Article schema
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "What Is Schema Markup",
"datePublished": "2026-09-17",
"author": {
"@type": "Organization",
"name": "JunctionKit"
},
"publisher": {
"@type": "Organization",
"name": "JunctionKit"
}
}
That is the entire block. It sits in the page's <head> section inside a <script type="application/ld+json"> tag.
The fields are self-explanatory. Any search engine reading the page knows the title, the publication date, the author, and the publisher — without inferring any of it from the visible content.
How to add schema markup
There are three common ways to add it, depending on the site platform and the level of control available.
1. Platform plugins and apps
Most modern website platforms have built-in support for schema markup or offer it through an app. WordPress has multiple SEO plugins that add schema markup automatically. Shopify has apps that do the same. Wix and Squarespace include basic schema by default.
This is the easiest path for most sellers. The plugin handles the code; the seller fills in the details.
2. A schema generator
For pages where a plugin does not apply — a custom landing page, a static HTML site, or a single page that needs a specific schema type — a generator produces the code from a set of form fields.
The seller enters the details (title, date, author, description) and the generator outputs the JSON-LD block, which gets pasted into the page's HTML. A code generator takes a few minutes per page.
3. Manual markup
For developers and technically comfortable users, JSON-LD can be written directly. The Schema.org documentation lists every available type and property. Most users find this unnecessary once they have tried the other options.
Testing the markup
After adding schema markup to a page, it should be tested before publishing. Two things need to be checked:
- Validity. The markup is correctly formatted and all required properties are present.
- Eligibility. The markup is eligible to produce rich results for the type of content on the page.
Search engines provide free testing tools for this. The markup is checked against the current requirements, and any errors or warnings are listed. Fixing the errors before publishing avoids wasted effort.
After the page is live, search engine consoles report which pages have valid structured data and which have issues. It is worth checking this occasionally to catch problems that appear over time — particularly after site changes or platform updates.
Which schema to add first
A practical order for a small store or content site:
| Priority | Schema type | Where |
|---|---|---|
| 1 | Organization | Homepage and about page |
| 2 | Product (if selling products) | Each product page |
| 3 | Article (if publishing content) | Each blog post or guide |
| 4 | FAQPage | Pages with a Q&A section |
| 5 | BreadcrumbList | Every page (usually automatic through a plugin) |
Starting with Organization and the primary page type usually produces the most visible results. Adding the others over time extends the benefit.
Common mistakes
- Marking up content that does not exist on the page. The most serious mistake. Search engines check, and misleading markup can result in penalties.
- Adding the same schema to every page. Schema should describe what is on the specific page, not the site in general.
- Ignoring required properties. Each schema type has required and recommended fields. Missing required ones makes the markup invalid.
- Not testing before publishing. A small typo can break the whole block. Testing takes a minute.
- Assuming it will improve rankings directly. It does not. It changes how the page appears in search results, which often produces more clicks — but that is not the same as a ranking factor.
- Faking reviews or ratings. Specifically prohibited. Ratings in search results must reflect genuine reviews visible on the page.
What to do next
Start with the page that matters most. If the site sells products, mark up a product page with Product schema. If the site publishes content, mark up the most-read article with Article schema. If the site is a storefront with a clear brand, mark up the homepage with Organization schema.
Generate the code, add it to the page, and test it. Then repeat for the next most important page. The whole process takes a few minutes per page and produces a visible change in how search results for those pages appear.
Schema markup is not the highest-leverage SEO task. It is one of the easiest, and one of the few that produces a visible improvement without changing the content itself.
Schema Markup Generator Meta Tag Generator Google SERP Preview Open Graph Preview On-Page SEO Checker Readability Score