How Many Types of Schema Are There in SEO?

Ask four sources how many types of schema in SEO exist. Expect four numbers back.

Ten, says one guide. Thirty-five, says the next. Sixty from a third. Somewhere past eight hundred from the vocabulary itself. Nobody in that group is lying to you.

They are counting two separate lists. One list is a vocabulary. The other is a menu of search features. Until you know which list a number came from, the number tells you nothing.

Types of Schema Get Counted on Two Lists, Not One

Schema.org publishes the vocabulary. Think of it as a shared dictionary of nouns for describing things on the web. There is a type for Person. One for Recipe. Museum sculptures have their own. Another for veterinary care. The vocabulary tries to name everything, so it runs long. Hundreds of types long.

Google publishes something else entirely. A gallery of structured data features it supports inside search results. Every entry there is a visible outcome. Star ratings under a listing. A job posting card. Breadcrumbs sitting where the URL used to be.

That second list stays short by design. Google documents markup that changes how your listing looks. Also markup that changes where the listing can appear. Nothing else earns a page in the gallery.

So the real answer runs two numbers deep. Hundreds in the vocabulary. Roughly thirty in the gallery. Neither figure is the one people came looking for.

Count Them Yourself in About Four Minutes

Both counts move. Any number quoted in a blog post ages badly, this post included. Go and count instead of trusting one.

Open schema.org and find the full type hierarchy. Every type in the vocabulary sits in that one tree, nested down from Thing at the root. Scroll it once. The scale registers faster than a figure ever would.

Then open Google’s search gallery inside the Search Central documentation. Count the entries listed down the side. You will finish that one considerably faster.

Now hold the two counts next to each other. The ratio between them is the finding. Not either number sitting on its own.

The Gallery Counts Outcomes, the Vocabulary Counts Nouns

Here is why the two lists refuse to reconcile.

Take Product. It appears in Google’s gallery once. One entry. A single row.

Then read what Google asks you to put inside that entry. Price and availability arrive through Offer. Stars arrive through AggregateRating. Customer text arrives through Review. Brand carries the manufacturer name.

Four more vocabulary types, minimum. Offer never gets a gallery entry of its own. Neither does Brand. They are ingredients rather than dishes.

That single Product feature just consumed five schema types. Repeat that arithmetic across the whole gallery and the two lists stop being comparable at all. You would be counting outcomes against nouns.

Anyone asking how many types of schema in SEO matter is really asking a third question. How many will I have to write? That number lands somewhere between the other two.

Somebody Will Say Just Do the Supported Types of Schema

Reasonable objection. Skip the vocabulary. Implement the gallery. Ignore the rest. Try holding to that for ten minutes.

You hit LocalBusiness almost immediately. Google’s gallery lists local business once. Schema.org hands you a whole branch underneath it. Dentist sits down there. So does Plumber. HVACBusiness and AutoRepair as well. Dozens of descendants, each one narrower than the parent above it.

Google’s own guidance then tells you to pick the most specific subtype that fits your business. So the single gallery entry walks you straight back into the vocabulary tree. Staying inside the short list turns out to be impossible. The short list points at the long one.

That objection is the argument, put another way. Working from the feature count is exactly what proves the feature count was never a type count.

Types Are Only Half of What Gets Counted

One more wrinkle worth knowing about.

Schema.org counts properties separately from types. Properties are the fields sitting inside a type. A name. The street address. An opening hours specification. The property count runs higher than the type count.

Which matters, because implementation effort tracks properties rather than types. Adding LocalBusiness sounds like adding one thing. You then fill in a dozen fields underneath it. Several of those Google treats as required before the markup becomes eligible for anything.

So a five-type site can carry sixty properties. The type count told you almost nothing about the work involved.

A Third Count Hides Inside the Testing Tools

Two validators exist. They give two different answers about what counts.

Google’s Rich Results Test only reads types tied to a search feature. Feed it perfectly valid markup from outside the gallery and it reports nothing detected. People read that as broken. It is not broken. The tool was only ever scoped to the short list.

The Schema Markup Validator reads across the whole vocabulary instead. Same page. Identical code. A completely different verdict.

So the count changes again depending on which tab you have open. Three lists now. The vocabulary. Then the gallery. Whatever your validator agreed to look at today.

Plenty of pointless rewrites start right here. Somebody runs the wrong test. Nothing detected comes back. Out goes markup that was working perfectly well.

Both Numbers Moved Since You Last Read a Listicle

Neither list is frozen.

Schema.org ships versioned releases. Types get added. Some sit in a pending extension for a while, waiting to earn a place in the core vocabulary.

Google’s gallery shrinks about as often as it grows. HowTo rich results left it entirely. FAQ rich results got narrowed to a small set of government and health domains. That one change quietly deleted the easiest win most agencies were selling at the time.

Two sites marked up identically a few years ago would score differently today. Same markup. Different gallery.

Which is the case against memorising any number at all. Learn where the lists live. Then check them on the day it matters.

What the Unsupported Hundreds Are Doing There

Fair follow-up. Why does the vocabulary name hundreds of types Google will never draw?

Because Google is one consumer of it, not the owner. Schema.org was built as a shared vocabulary for the web rather than a Google feature spec. Other parsers read it. So do catalogue systems and internal tools that never touch a search result at all.

Mark up a type from outside the gallery and the default outcome is nothing visible. That is not a failure. It is the design. Your page carries a machine-readable description of itself either way.

Worth being blunt about the limit though. No visible change usually means no measurable change in your reporting. Nobody should bill you for invisible markup as though it were a ranking service. Structured data is one input among many in search engine optimization. A smaller input than most sales decks imply.

Types of Schema a Calgary Business Actually Needs

Practical version now. Most service businesses need neither hundreds of types of schema nor thirty of them.

Six or seven covers most small sites. Organization for the company itself. A LocalBusiness subtype for the premises. WebSite and WebPage holding the structure together. BlogPosting on editorial pages. BreadcrumbList once the navigation runs deeper than one level.

That is how many types of schema in SEO actually earn their keep on a site this size. The remaining hundreds describe businesses that are not yours.

Getting those six right beats adding a seventh. Most sites we open during a website audit have the count roughly correct and the contents wrong. Mismatched addresses. A logo URL pointing at nothing. Two Organization blocks disagreeing about the company name.

None of this touches paid search, incidentally. Structured data does not feed your ad copy. Shopping listings run off a separate product feed, handled through Google Ads management and its own set of rules. Nothing in the gallery applies to Google Ads at all. Different system. Separate vocabulary altogether.

Run the Count on Your Own Home Page

Four minutes, no tools required.

Open your home page. View source. Search the markup for @type. Write down every distinct value that comes back.

Most small business sites return three to five. Some return nothing at all. A few return the same type twice, emitted by two plugins that do not know about each other.

Then compare your list against the gallery. Anything on your page missing from Google’s list will never produce a rich result. Fine, provided you knew that going in.

That comparison beats any published count. Yours is the only one describing your actual site. Proper Calgary SEO work starts from what sits on the page today. Never from a checklist somebody published years ago. SEO Company To-The-TOP! has been doing this work in Calgary since 2007. The count is almost never the part that is wrong.

Nothing about the count tells you whether the values inside it are true. That part still nobody automates.

Common Questions About How Many Types of Schema Exist

So what is the actual number of schema types?

Schema.org’s vocabulary runs into the hundreds. Google’s supported gallery sits nearer thirty. Both figures shift between releases. Read the current count off the two source pages rather than off a blog post.

How many schema types does a small business website need?

Six or seven, typically. Organization comes first. A LocalBusiness subtype matching the trade. WebSite and WebPage. BlogPosting for articles. BreadcrumbList once the navigation goes more than one level deep. Ongoing SEO services rarely need to add much beyond that.

Does using more types of schema improve rankings?

No. Markup describes a page rather than promoting it. Extra types add description, not weight. Whatever gain structured data brings arrives through eligibility for search features. A display question, not a ranking one.

Why does Google support so few schema.org types?

Every supported type costs Google a documented feature to build and police. The gallery only carries markup that changes something visible in a result. Everything else stays valid and stays invisible.

What happens if I use a schema type Google does not support?

Nothing breaks. The Schema Markup Validator still passes it. Your listing looks exactly as it did before. Any plan that depended on that markup showing up simply will not pay off.

Are structured data and schema markup the same thing?

Close enough in daily use. The phrase structured data names the general practice. Say schema markup and you mean one specific vocabulary. Nearly everyone uses it. Counting types of schema means counting inside that one vocabulary.