What is schema markup? A plain-English guide for business owners
The short answer
What is schema markup? It is a short block of code, usually written in a format called JSON-LD, that describes a page to search engines using the shared Schema.org vocabulary: your business name, address, hours, services or articles. It helps Google understand the page and can make it eligible for rich results, but it does not guarantee them or lift your rankings.
On this page
If you have spoken to a web designer or an SEO consultant lately, you have probably been told "you need schema." It sounds like jargon, and the advice that comes with it is often vague or out of date.
This guide explains what schema markup is, what it does for your business, which types are worth adding, and how to add and test it. It also covers what changed in 2026.
What is schema markup?
Schema markup is a short block of code on a web page that describes the page in a fixed, standard format. A visitor reading your contact page sees your name, address and opening hours. Schema markup states the same facts so a machine can read them without guessing which line is the phone number.
Google calls it structured data. Its introduction to structured data defines it as "a standardized format for providing information about a page and classifying the page content." Google also says: "You can help us by providing explicit clues about the meaning of a page to Google by including structured data on the page."
The word "schema" comes from Schema.org, the shared vocabulary that most structured data uses. Schema.org describes itself as "a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond." It reports that "As of 2024, over 45 million web domains markup their web pages with over 450 billion Schema.org objects."
The vocabulary works like a set of labeled forms. Each kind of thing has a type, such as LocalBusiness, Article or Service, and each type has properties, such as name, address and telephone. In everyday use, "schema markup", "schema" and "structured data" mean the same thing.
What schema markup does for SEO, and what it does not
Schema markup for SEO does two jobs. It removes guesswork, so Google can tell that a page belongs to a law firm in Chicago, or that an article was written by a named person on a given date. And it can make a page eligible for rich results: listings with extra detail, such as review stars, breadcrumbs or a business knowledge panel.
Google's own case studies report real gains: "Rotten Tomatoes added structured data to 100,000 unique pages and measured a 25% higher click-through rate" on those pages compared with pages without it. That is a large publisher, though, and the gain came from rich results.
Here is what schema markup does not do:
- It does not guarantee rich results. Google's general structured data guidelines say: "Google does not guarantee that your structured data will show up in search results." Valid markup only makes a feature possible, because "The Google algorithm tailors search results to create what it thinks is the best search experience for a user."
- It is not a ranking boost. Markup helps Google read a page. It does not make the page more useful or more trusted than it already is.
- It does not keep every rich result alive. In June 2025 Google said it would be "phasing out support for a few structured data features in Search," and in 2026 it removed FAQ rich results entirely.
So is it worth adding? For most business websites, yes, as a modest job done once and checked after every big change. It helps Google read your key pages and keeps you eligible for the features Google still shows, but it will not rescue a page that is failing for other reasons. It is one of the checks in my speed and technical SEO sprint, alongside indexing and Core Web Vitals.
JSON-LD: the format Google recommends
Structured data can be written in three formats: JSON-LD, Microdata and RDFa. Google says "all 3 formats are equally fine for Google, as long as the markup is valid and properly implemented." It still has a preference: "In general, Google recommends using JSON-LD for structured data if your site's setup allows it," because it is "the easiest solution for website owners to implement and maintain at scale."
The practical reason is that JSON-LD sits in its own <script> block, separate from the text people read. Microdata and RDFa are written into the attributes of the page's HTML tags, so a design change can break them without anyone noticing.
Here is a realistic example for a fictional cleaning company. It would sit on the home page or contact page, where the same details are printed for visitors.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Example Cleaning Co.",
"url": "https://www.example.com/",
"telephone": "+1-217-555-0123",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main Street",
"addressLocality": "Springfield",
"addressRegion": "IL",
"postalCode": "62701",
"addressCountry": "US"
},
"areaServed": "Springfield, IL",
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "08:00",
"closes": "18:00"
}]
}
</script>@context names the vocabulary and @type says what is being described. Everything else is a property. Google's local business guide lists name and address as required, and telephone, url, geo and openingHoursSpecification among its recommended properties. areaServed suits a business that travels to its customers.
A block like this is a few hundred characters of plain text, so it has no meaningful effect on loading time. If your site feels slow, my website speed guide covers the usual causes.
Local business schema: where most businesses should start
If customers visit you, or you travel to them within an area, local business schema is the first markup to get right. Google explains that "Search results may display a prominent Google knowledge panel with details about a business that matched the query," and markup lets you tell Google details such as your opening hours.
Use the most specific type that is true
Google's advice is to "Use the most specific LocalBusiness sub-type possible." Schema.org lists 30 more specific types directly under LocalBusiness, including Dentist, FinancialService, LegalService, ProfessionalService and RealEstateAgent.
- Law firms: LegalService, as I use in website design for law firms.
- Real estate agencies: RealEstateAgent, covered in real estate website design.
- Cleaning companies: Schema.org has no type made for house or office cleaning. The nearest-sounding one, DryCleaningOrLaundry, describes a different business, so plain LocalBusiness is the honest choice, as in the example above, and as I use for cleaning company websites. The rest of what such a site needs is in what a cleaning business website needs.
Keep it consistent with your Google Business Profile
Local business schema is not what puts you in the map results. Google says local results are "mainly based on relevance, distance, and popularity," and its tips for improving local ranking focus on your Business Profile without mentioning structured data at all.
Treat the two as partners. Your profile does the work on Maps, and your markup makes sure your website states the same name, address, phone number and hours.
Other schema types that matter for small businesses
Beyond your business details, a handful of types cover almost everything a small business site needs. Google lists the features it supports in its search gallery. Schema.org types outside that list can still be valid, but they will not produce a special Google result.
| Type | Use it for | In Google's search gallery |
|---|---|---|
| LocalBusiness or a subtype | Your business details on the home or contact page | Yes, as Local business |
| Organization | Companies customers do not visit, such as software firms | Yes |
| Service | Each service page | No |
| Product or SoftwareApplication | Goods you sell, or a software product | Yes, as Product and Software app |
| BreadcrumbList | The trail from your home page to each inner page | Yes, as Breadcrumb |
| Article | The headline, author and dates of posts and guides | Yes |
| FAQPage | Visible question and answer sections | No longer |
Organization and Service
Organization describes a company in general, so it suits businesses customers never visit, such as a SaaS company. A local business does not need it as well, because LocalBusiness already inherits Organization's properties.
Schema.org defines Service as "A service provided by an organization, e.g. delivery service, print services, etc." On a service page, it can name the service and link it to your business as the provider. Google has no rich result for it, so its value is clarity, not a special listing.
Product or SoftwareApplication
Product is for goods you sell. For software, Google's Software app markup exists "to better display your app details in Google Search results," but that result requires a name, a price in offers.price (0 for a free app) and either an aggregateRating or a review. A new product without genuine ratings can still describe itself this way; it just will not qualify for that result yet. My page on SaaS website design covers how this fits with product pages, and B2B SaaS SEO covers the pricing and comparison pages around it.
FAQPage: what changed
FAQ markup used to be a popular recommendation because it could earn an FAQ rich result. In August 2023, Google limited FAQ rich results to "well-known, authoritative government and health websites." Then, in its documentation updates for May 2026, it announced: "This feature will no longer appear in Google Search starting May 7, 2026." By June it had removed the documentation, noting that "The FAQ rich result feature is no longer shown in Google Search results."
If someone offers to add FAQ schema so your listing takes up more space in Google, that result no longer exists for anyone.
Reviews and ratings
Star ratings have the strictest rules. Google's review snippet guidelines say that if the business being reviewed controls the reviews about itself, its pages using LocalBusiness or any other Organization markup "are ineligible for star review feature." In practice, the testimonials on your own website will not earn stars for your business.
Google also says "Don't aggregate reviews or ratings from other websites," so you cannot copy your Google reviews into your markup.
How to add schema markup to your site
Whatever platform you use, Google's rule is to "Put the structured data on the page that it describes." Business details usually go on the home page or contact page, service markup on each service page, and article markup on each post.
WordPress
The simplest route on WordPress is an SEO plugin. Yoast SEO's developer documentation, for example, says "Every page should (attempt to) output" Organization, WebSite and WebPage pieces, with an Article piece on single posts. Check what your plugin already outputs and only add your own markup where it leaves a gap, because two plugins, or a plugin and a theme, can each describe the same business differently.
Webflow
Webflow lets you paste JSON-LD into a page's settings, in the custom code section "Inside <head> tag," and code there "will only apply to that page." At the time of writing (October 2026), custom code needs a paid workspace or an active site plan, and it only goes live once you publish. If you are still choosing a platform, my Webflow guide weighs it up fairly.
Plain HTML
On a hand-built or static site, paste the <script type="application/ld+json"> block into the <head> of each page it describes. Google says JSON-LD can sit in "the <head> and <body> elements of an HTML page," and that "Google can read JSON-LD data when it is dynamically injected into the page's contents," for example by JavaScript or a widget in your content management system.
On this site, a small Node script generates each page's structured data from the same content as the visible page, so the two stay in step.
How to test schema markup and keep it working
Testing takes a few minutes per page type. These four tools do different jobs, so use them together.
| Tool | What it checks | When to use it |
|---|---|---|
| Rich Results Test (Google) | Whether your markup is valid for the rich result features Google supports | During development, on each page type |
| Schema Markup Validator (Schema.org) | Whether your markup is valid Schema.org, whatever Google does with it | For types Google has no rich result for, such as Service |
| URL Inspection (Search Console) | Whether Google found the structured data on the live page | After launch, on your key pages |
| Rich result reports (Search Console) | Valid and invalid items across the whole site | Monthly, and after any redesign or template change |
Google advises: "Be sure to check your structured data using the Rich Results Test during development." The Schema Markup Validator, at validator.schema.org, took over from Google's old Structured Data Testing Tool, and Schema.org says it "does not try to check your content against the information needs of specific services, tools or products."
After launch, Google suggests you "Confirm that your markup is valid, and that Google has found your structured data using the URL Inspection tool on your page." Then watch the rich result reports, which Search Console's help says to "Locate the reports under Enhancements in the navigation bar."
One caution: Google says "The reports aren't a comprehensive list of all detected items." A clean report is reassuring, not proof that every page is right, which is why structured data is one of the 20 checks in my new website SEO checklist.
Common schema markup mistakes
Most schema problems are not about syntax. They come from markup that says something untrue, or something the page does not.
- Markup that does not match the page. Google says "Don't mark up content that is not visible to readers of the page," and markup must be "a true representation of the page content." Old opening hours and a phone number you no longer use both count.
- The wrong business type. A law firm marked up as a generic ProfessionalService, or a house cleaning company marked up as DryCleaningOrLaundry because the name sounds close. Google asks you to "use the most specific applicable type," but it has to be the correct one.
- Fake reviews. Google's guidelines say "Don't mark up irrelevant or misleading content, such as fake reviews or content unrelated to the focus of a page."
- Copied markup with someone else's details. Markup taken from a template or another company's site often keeps their name, phone number or address. The code is valid, so it passes the tests. Read each value yourself.
- Errors left after a redesign. A new theme can drop, duplicate or break markup, and nobody notices because the page looks fine. Re-test every page type after launch, along with the other checks in my guide to redesigning a website without losing rankings.
- Blocking the pages that carry it. Google says "Don't block your structured data pages to Googlebot using robots.txt, noindex, or any other access control methods." A staging noindex tag left on after launch hides your markup along with everything else.
More questions
Does schema markup improve Google rankings?
Not directly. In April 2025, Google's John Mueller wrote: "Structured data won't make your site rank better." He explained that it is "used for displaying the search features listed in" Google's search gallery. Its value is helping Google read your pages correctly and keeping you eligible for those features, not lifting your position.
Do I need a developer to add schema markup?
Not for the basics. An SEO plugin on WordPress, or a block pasted into a page's settings in Webflow, covers most small business sites. A developer helps when markup has to be generated across many pages, or when tests show errors you cannot trace. My technical SEO sprint, from $600, includes adding or fixing schema and validating it.
Can schema markup hurt my site?
Accurate markup will not. Misleading markup can cost you features: Google says a structured data manual action means a page "loses eligibility for appearance as a rich result," although "it doesn't affect how the page ranks in Google web search." Invalid markup is simply ineligible until it is fixed, so errors waste the work rather than harm the page.
Should I remove FAQ schema now that Google no longer shows FAQ results?
There is no need to. When Google first limited FAQ results in 2023, it said: "Structured data that's not being used does not cause problems for Search, but also has no visible effects in Google Search." If the questions are visible on the page, the markup is accurate, which is why this page keeps it. Just do not pay anyone to add it for Google's sake.
Sources
- Introduction to structured data markup in Google Search, Google Search Central
- General structured data guidelines, Google Search Central
- Structured data markup that Google Search supports (search gallery), Google Search Central
- Local business (LocalBusiness) structured data, Google Search Central
- Review snippet (Review, AggregateRating) structured data, Google Search Central
- Software app (SoftwareApplication) structured data, Google Search Central
- Latest documentation updates (FAQ rich result deprecation, May and June 2026), Google Search Central
- Changes to HowTo and FAQ rich results (August 2023), Google Search Central Blog
- Google reduces the visibility of HowTo and FAQ rich results in search (Barry Schwartz), Search Engine Land
- Rich result report overview, Search Console Help
- Tips to improve your local ranking on Google, Google Business Profile Help
- Welcome to Schema.org, Schema.org
- LocalBusiness, Schema.org
- Service, Schema.org
- Announcing Schema Markup Validator: validator.schema.org (May 2021), Schema.org Blog
- Google again says structured data does not make your site rank better (April 2025), Search Engine Roundtable
- Custom code in head and body tags, Webflow Help Center
- Yoast SEO: Schema output, Yoast developer portal