What Is Schema SEO? Schema Markup Explained
Schema SEO is the practice of adding schema.org structured data to a web page so that search engines can read, in a shared vocabulary, what the page is about: that a number is a price, that a line of text is a business address, that the page describes an event or a product. Google describes structured data as a standardized format for providing information about a page and classifying its content, and it uses that information both to understand the page and, for the features it supports, to show a richer listing called a rich result. Schema markup is not a ranking boost on its own, and it never guarantees a rich result. What it does is remove guesswork, and on the right kind of page that clarity can change how the listing looks.

This guide explains how the three terms people mix up relate to each other, shows what a block of schema looks like, and sets out what it changes in Google today, including the FAQ results that disappeared in 2026. It then covers which types a small Canadian business needs and how to add and check the markup without creating new problems.
Schema, structured data and JSON-LD: three different things
Structured data is the general idea of putting information on a page in a machine-readable format. Schema.org is the shared vocabulary that most structured data on the web uses, founded by Google, Microsoft, Yahoo and Yandex and now developed by an open community; on November 14, 2026 it listed 826 types and 1,540 properties. JSON-LD is one of three formats for writing that vocabulary into a page, alongside Microdata and RDFa. So when someone says a page “has schema”, they usually mean the page contains a block of JSON-LD built from schema.org types.
Google supports all three formats and says they are equally fine as long as the markup is valid, but it recommends JSON-LD because in most cases it is the easiest to implement and maintain. The reason is practical. JSON-LD sits in its own script block instead of being woven through the visible HTML, so an editor can rewrite a paragraph without breaking the markup, and Google can read it even when a plugin or JavaScript injects it into the page. Microdata and RDFa add attributes to the visible HTML elements themselves, so a theme or page builder change that rewrites that HTML can break them. The wider concept is covered in the guide to structured data in SEO, while this page sticks to the schema vocabulary and how it is used.

Here is what a small block looks like for a local trade business. The business, address and phone number below are invented for illustration, and the 555 number is one reserved for examples:
{
"@context": "https://schema.org",
"@type": "Plumber",
"name": "Example Plumbing Ltd.",
"url": "https://www.example.com/",
"telephone": "+1-403-555-0123",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Example Street SW",
"addressLocality": "Calgary",
"addressRegion": "AB",
"postalCode": "T2P 0A0",
"addressCountry": "CA"
},
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "08:00",
"closes": "17:00"
}]
}
On a real site this block goes inside a script tag of type application/ld+json, which can sit in the head or the body of the page. “Plumber” is a schema.org subtype of LocalBusiness, and Google’s guidelines ask for the most specific type that applies, so a dentist, a law firm or a roofing company would use its own type where one exists. Every value in the block should also appear on the visible page, because Google’s guidelines say not to mark up content that readers cannot see.
What schema markup changes in Google, and what it does not
Google’s documentation is clear on three points that a lot of advice online gets wrong. First, structured data makes a page eligible for a rich result, such as the rich snippets that show prices or event dates, but Google does not guarantee that the result will appear, even when its own Rich Results Test says the markup is valid. Second, when Google takes manual action over structured data that breaks its guidelines, the page loses eligibility for rich results, and Google states that this “doesn’t affect how the page ranks in Google web search”. That tells you how Google separates the two: markup affects how a result can look, not where it ranks. Third, Google’s page on AI features says there is no special schema.org structured data needed to appear in AI Overviews or AI Mode, and its guide to generative AI search lists overfocusing on structured data among the things site owners can ignore, while still recommending structured data as part of normal SEO because it supports rich result eligibility.
So why bother? Because a richer listing can change how many people click. Google’s introduction to structured data quotes case studies such as Rotten Tomatoes, which measured a 25% higher click-through rate on pages enhanced with structured data, and Nestlé, which measured an 82% higher click-through rate on pages that showed as rich results. Those are the companies’ own measurements on large recipe, review and product sites, so they show what is possible rather than what a twelve-page service site should expect. For most small business sites the realistic gains are a cleaner listing, consistent business details in Google’s knowledge panel and less doubt about which business the site belongs to. The question of whether schema helps SEO in ranking terms gets its own article.

The FAQ result is gone, and other features have been retired
Rich results come and go, which is the most common reason schema advice goes stale. In 2023 Google limited FAQ rich results to well-known, authoritative government and health websites and stopped showing How-to rich results altogether. On May 8, 2026 it added a deprecation notice saying the FAQ rich result would no longer appear in Google Search from May 7, 2026, and in June 2026 it removed the FAQ documentation entirely. In September 2025 it had already removed the documentation for course info, estimated salary, learning video, special announcement and vehicle listing markup, because those results were no longer shown.
The practical consequence for many WordPress sites is that the FAQ blocks and FAQPage markup added a few years ago for the dropdowns no longer earn anything visible in Google. A genuine FAQ that answers real follow-up questions can stay on a page for readers, but adding questions in order to win dropdowns no longer makes sense. Before acting on any schema advice, including this article, check Google’s current list of supported structured data features, because that list, and not a blog post, decides what can appear.
Which schema types a small business needs
Schema.org has hundreds of types, but Google uses only a subset of them for search features, and a typical Canadian service business needs very few. The table below is a practitioner’s starting point for which page should carry which type; the “what it can do” column follows Google’s feature documentation.

| Page | Schema type | What it can do in Google | Watch for |
|---|---|---|---|
| Home page | Organization, or a LocalBusiness subtype | Helps Google identify the business and can influence the logo and details in its knowledge panel | Google lists no required properties; add the ones that apply |
| Contact or location page | LocalBusiness subtype such as Plumber or Dentist | Business details such as hours, phone and address for the knowledge panel | Hours and phone must match the visible page and the Google Business Profile |
| Pages below the home page | BreadcrumbList | Shows where the page sits in the site’s structure | Most SEO plugins add this already |
| Blog posts | Article or BlogPosting | Helps Google show better title text, images and dates for the article in search results | The author in the markup should match the visible byline |
| Product pages (shops only) | Product with an Offer | Product snippets and merchant listings with price and availability | Prices change; stale markup is a common error |
| Event pages | Event | Event listings with date and venue | Only for real events with dates |
For a Calgary or Edmonton business that depends on local searches, it helps to keep the website’s markup and the Google Business Profile in their proper roles. The map and local pack listings come from the Business Profile, which Google says ranks local results mainly on relevance, distance and popularity. LocalBusiness markup on the website describes the same business but does not replace the profile, so the most useful thing it can do is agree with it: the same name, address, phone number and hours everywhere.
The type that causes the most trouble for local businesses is review markup. Google’s review snippet rules say ratings for a LocalBusiness or an Organization are eligible only on sites that capture reviews about other businesses or organizations, which Google calls the self-serving reviews rule. A plumber that copies its five-star Google reviews into AggregateRating markup on its own site is reviewing itself, so it cannot earn stars that way, and Google’s guidelines warn that reviews or ratings not by actual users may lead to a manual action. Showing real reviews on the page for visitors is fine; the markup will not turn them into stars in Google.
How to add schema markup to a website
On WordPress, the SEO plugin usually does a good part of the work already. Plugins such as Yoast SEO and Rank Math generate a base layer of markup automatically, typically describing the site, the organization, the page and its breadcrumbs. The common problem is duplication, where a theme, a page builder and a second plugin each output their own Organization or Article block, so Google sees competing versions of the same thing. Untangling schema conflicts between Yoast and other plugins is often the first fix rather than adding anything new.

Whatever the platform, the process is the same:
- Find out what is already there. Paste the URL into Google’s Rich Results Test, or open the page source and search for “application/ld+json”. This answers the common question of how to know whether a website has schema, and it often shows the plugin and theme duplicates described above.
- Decide what the page is. Pick the most specific schema.org type for the main content of the page, and check Google’s search gallery to see whether that type supports a feature at all.
- Write or generate the JSON-LD. Google’s documentation for each feature lists its required and recommended properties. A generator tool is a fine starting draft, as long as every value is checked against the visible page.
- Add it once. Use the plugin’s settings, a header field or the theme, but only one of them for each type, so the page does not end up with two conflicting blocks.
- Test before and after publishing. The Rich Results Test checks the markup against Google’s features, and the Schema Markup Validator checks it against the schema.org vocabulary in general. Google also suggests comparing the performance of pages with and without structured data afterwards, so the effort is judged on results.
Checking schema over time
Markup breaks quietly. Google’s own documentation warns that pages can lose valid markup after deployment because of templating or serving issues, which is exactly what happens when a theme update, a plugin change or a page rebuild rewrites the code around it. Search Console shows rich result reports under Enhancements, with product snippets and merchant listings under Shopping, and each report lists valid items and errors. A report only appears when Google finds valid markup of a supported type on the property, so a missing report is not proof of a problem; it can simply mean the site has no supported markup.

The errors worth looking for are mostly about accuracy rather than syntax:
| Problem | Why it matters |
|---|---|
| Markup that disagrees with the page (old hours, old prices, a removed product) | Google asks for complete, up-to-date markup that matches visible content |
| Self-serving AggregateRating on a business’s own site | Not eligible for stars; ratings not by actual users can lead to a manual action |
| Two or more blocks of the same type from different plugins | Competing versions of the same facts |
| FAQPage or HowTo markup kept to win dropdowns | Neither result is shown in Google Search any more |
| Markup added in place of content | Google does not guarantee a rich result and does not need special markup for AI features |
A quick look after any redesign, plugin change or price update catches most of these before they matter.
When schema is worth the effort
Schema earns the most on sites whose content maps onto a feature Google still shows, such as products, events, recipes, job postings and breadcrumbs. For a typical service business the work is smaller and mostly one-off: describe the organization accurately, mark up the location details so they agree with the Google Business Profile, let the plugin handle breadcrumbs and articles, remove duplicates and retired types, and check the reports now and then. It will not lift rankings on its own or replace useful content, links and a well-kept Business Profile, but done accurately it removes doubt about who the business is and what each page offers.
If you are not sure what your site’s markup currently says about your business, a technical review is a sensible place to start. SEO Company To-The-TOP! is a Calgary-based White Hat SEO practice, founded in 2007, where one expert does the client work, and its website SEO support covers the technical side of a site for businesses in Calgary, Edmonton, Vancouver and across Alberta and British Columbia. You can reach it at (403) 308-5949.
Contact Calgary SEO Company To-The-TOP!
Questions about anything in this article, or about your own rankings? Talk to a Calgary SEO specialist directly.
Phone: (403) 308-5949
Address: 1509 14 Ave SW, Calgary, AB T3C 0W4
Hours:
Monday to Friday: 10:00 am – 7:00 pm
Saturday: 12:00 pm – 4:00 pm
Sunday: closed
