Short answer
Schema, or structured data, is code that tells Google in a standard format what a page is about; the format Google recommends is JSON-LD. Correct markup does not guarantee a rich result. Mark up only what is visible on the page and check it in the Rich Results Test before publishing.
Picture this: the owner of a small furniture workshop installs a plugin and has question-and-answer markup added to every page of the site. They hope expandable question boxes will appear in search results. Months pass and nothing changes. The reason is simple: Google announced that the FAQ rich result would stop appearing in Search from 7 May 2026. So the practical side of “what is schema (structured data) and how do you add it” starts with knowing which type still does something. This article covers the definition, the right format, the types a small business site actually needs, the steps to add and test markup, and the usual mistakes, in that order.
What is schema (structured data)?
By Google’s definition, structured data is a standard format for providing information about a page and classifying the page content. Google uses it as explicit clues about what a page means; it also uses it to gather information about things such as people, books or companies that appear in the markup. For some types, the data makes a more detailed appearance in search possible, called a “rich result”. Most markup uses the schema.org vocabulary; even so, Google points to its own Search Central documentation as the definitive source for how Search behaves. For a short definition, see the structured data glossary entry.
The first limit you should know is in Google’s general guidelines: even if the markup is correct according to the Rich Results Test, Google does not guarantee that the data will show up in search results. Structured data makes a feature possible to show; it does not guarantee that it will show. Depending on many variables, such as search history, location and device, Google may decide that a different feature, or even a plain text result, is more appropriate. The guidelines also list markup that does not represent the main content of the page, that is misleading, or that refers to content hidden from the user among the reasons for not being shown. A manual action for a structured data issue only removes the page’s eligibility to appear as a rich result; according to Google it does not affect how the page ranks in web search.
So do not think of schema as a promise about rankings; think of it as the job of describing correctly to a machine what the page is. For its place in a technical audit, see the structured data item in our technical SEO checklist.
JSON-LD: the format Google recommends
Google Search supports three formats: JSON-LD, Microdata and RDFa. According to Google all three are equally fine as long as the markup is valid and implemented as the documentation says. Even so, it recommends JSON-LD if your setup allows it, because it is the easiest to implement and maintain at scale. JSON-LD is written in a <script> tag in the <head> or <body> of the page. The markup is not mixed into the visible text, and Google can read JSON-LD even when JavaScript or a CMS adds it to the page afterwards.
Which types does a small business site need?
Google lists the markup features it supports in a single gallery. The table below shows five types that a small business site often meets; the page match in the second column is our suggestion, and the third column summarises Google’s description in the gallery.
| Type | Which page (our suggestion) | Google’s description in the gallery |
|---|---|---|
| Organization | Home page | Organisation details such as logo, legal name, address, contact information and company identifiers; they can show up in knowledge panels and other visual elements |
| LocalBusiness | Business or branch page | Business details shown in the Google knowledge panel, such as opening hours, ratings, directions and actions to book appointments or order items |
| Article | Blog posts | A news, sports or blog article shown with features such as the title and images larger than a thumbnail |
| Product | Product page | Product information such as price, availability and review ratings |
| BreadcrumbList | Inner pages | Navigation that shows the page’s position in the site hierarchy |
You do not need every type on every page. We cover LocalBusiness in detail in our local SEO guide and Product markup in our product page article, so we do not repeat them here. On our service page, product schema is also listed among the e-commerce SEO items.
The features Google no longer shows today
Many older guides still recommend FAQ and HowTo markup. Google’s Search Central changelog shows the following today:
| Feature | Changelog entry |
|---|---|
| FAQ | September 2023: the feature is shown only for well-known, authoritative government and health websites. 8 May 2026: announced that it would stop appearing in Search from 7 May 2026. June 2026: the documentation was removed because the feature is no longer shown |
| HowTo | September 2023: the documentation was removed because the result is no longer shown on desktop or mobile |
| Course info, estimated salary, learning video, special announcement, vehicle listing (as named in the English documentation) | September 2025: the documentation was removed because these types are no longer shown |
FAQ and HowTo are also missing from Google’s gallery of supported features. Our conclusion from this (our interpretation, not the documentation’s): there is no reason today to add this markup only to get a rich result. A question-and-answer section on the page can stay, because it is written for readers. We cover how to write that section in our FAQ page guide. We did not see a statement on the pages we read that says you must delete existing markup.
How to add schema: 5 steps
The figure summarises the order; the details are below.
1. Pick the type that fits the page
Start from Google’s gallery and pick the type that matches what the page really is. Google’s guideline asks you to use the most specific applicable schema.org type and property names. As examples of irrelevant markup it gives a woodworking site labelling instructions as recipes and a live-streaming site labelling broadcasts as local events. You need to fill in all the required properties of a given type; if they are missing, the item is not eligible for rich results. Google also says it is more important to supply fewer but complete and accurate recommended properties than to fill in every one badly.
2. Prepare the visible content
The information you mark up should first be visible to readers on the page. Google’s guideline is clear: do not mark up information that is not visible to the visitor, even if it is accurate. If the markup describes a performer, the page text should describe the same performer. Do not create blank pages just to hold markup either. Put the markup on the page it describes, and do not mark up fake reviews or content unrelated to the focus of the page. The image URLs in the markup must be crawlable and indexable.
3. Add the JSON-LD
Below is the simplest Organization example that could go on the home page of an invented workshop. The fields should match what is visible on that page; do not add an email address that the site does not show. As for sameAs, Google says it can make general use of that property and other schema.org data.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Örnek Atölye",
"url": "https://www.example.com",
"logo": "https://www.example.com/images/logo.png",
"email": "iletisim@example.com",
"sameAs": ["https://social.example.com/ornek-atolye"]
}
</script>
There are three ways to add the code. The table below gathers what Google’s documentation says about each.
| Method | What Google’s documentation says |
|---|---|
| By hand (in the template or the page) | JSON-LD is described as the easiest format to implement and maintain. If you use server-side rendering, you can include the JSON-LD in the rendered output. |
| CMS or plugin | In systems such as Wix, WordPress and Shopify you may not be able to edit the HTML directly; the CMS may have a search engine settings page or a structured data plugin. Searching for something like “wordpress structured data plugin” is suggested. |
| Google Tag Manager | A Custom HTML tag is added to the container, the JSON-LD is pasted into it and the container is published. You are advised to read the information from the page with variables instead of copying it into GTM; copying increases the risk of a mismatch between the page and the markup. |
The same document also says that dynamically generated Product markup can make Shopping crawls less frequent and less reliable, which can be an issue for fast-changing information such as price and availability. For that reason, on product pages we prefer to generate the JSON-LD on the server (this is our interpretation). For more on the options, see our articles on choosing a CMS and setting up Google Tag Manager.
4. Try it in the Rich Results Test
Google describes the Rich Results Test as an easy and useful tool for validating structured data; in some cases it also previews the feature in Search. Use it during development and fix the errors. Remember its limit too: Google writes that structured data can be incorrect in a way the Rich Results Test is not able to catch. Even if the test passes, check yourself that the markup agrees with the text on the page.
5. Publish and monitor
After publishing, use the URL Inspection tool to confirm that Google has found the structured data. Do not hide the page from Googlebot with robots.txt, noindex or any other access control; the guidelines say so explicitly. Google recommends checking the rich result reports in Search Console after deployment, because pages can break after deployment because of templating or serving issues. You can see whether there is a manual action in the Manual Actions report. If you want to measure the effect, Google recommends a before-and-after test: add markup to a few pages that have none and compare their performance in the Performance report in Search Console. It also reminds you that page views can change for other reasons.
Common schema mistakes
- Marking up information that is not visible. A price, review rating or event that is not on the page goes against the guidelines.
- Marking up fake or irrelevant reviews. Google writes that reviews and ratings that are not by actual users may result in a manual action.
- Adding FAQ and HowTo hoping for a rich result. The table above shows there is nothing to gain from it today.
- Skipping required properties. An item missing a required property is not eligible for rich results.
- Hiding the page from Googlebot. Google asks you not to block pages with structured data using robots.txt, noindex or other access control methods.
- Copying information by hand in Tag Manager. For example, the price changes on the page and the old one stays in GTM.
- Staying with an old vocabulary. Google says data-vocabulary.org markup is no longer eligible for rich result features.
- Treating a passed test as a guarantee. Valid markup does not guarantee a result.
Common questions
Does adding schema improve rankings?
We did not see such a statement on the Google pages we read. The documentation says structured data helps Google understand the page and makes a rich result possible; it does not guarantee the result. A manual action only affects rich result eligibility, not rankings.
My site has FAQ markup. Should I delete it?
Google no longer shows the FAQ feature and has removed its documentation. We did not see a statement on the pages we read that says you must delete it. Our advice is not to add it to new pages for a rich result; you can simplify the existing markup during later maintenance.
Is it a problem to add schema with Tag Manager?
Google’s documentation describes it as one way to do it. The point to watch is to read the information from the page with variables and not copy it into GTM; for Product markup, the documentation notes that dynamic generation can affect Shopping crawls.
A check you can do on your own today
Paste your home page address into the Rich Results Test and see which types it finds. Compare every field it finds with what you can see on the page: are the name, logo, phone and email the same? If nothing is found, adapt the Organization example above with your own details and try it in the same test. If you would like to plan the markup together, see our SEO service.
Sources
- Google Search Central: 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
- Google Search Central: Generate structured data with JavaScript
- Google Search Central: Documentation updates (changelog)
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 14 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.