Search · Term

Schema markup

Schema markup is structured data written with the schema.org vocabulary that labels page content so machines can understand it — such as Article, Organization, FAQPage, or BreadcrumbList.

Adding schema does not change how a page looks to a person, but it tells search and AI engines exactly what they are reading. That can make a page eligible for rich results in search and improves the odds that a generative engine represents your content accurately.

How it works

Schema markup is usually written as a JSON-LD block in the page's head: an object with a @type such as Article or Organization and properties such as headline, author and datePublished. Types can reference each other by @id, so a whole site can describe one connected graph of its organisation, people, pages and products.

Search engines use it to understand the page and to decide eligibility for rich results; the markup must describe what a visitor can actually see on the page.

Example

Every troiana.net glossary page, including this one, carries a DefinedTerm and a BreadcrumbList. The guides carry TechArticle with the software they cover, and the organisation is described once with a stable @id that other pages point to.

In practice

To see what markup a page already has, paste its address into Google's Rich Results Test, which lists the rich-result types Google detects and any errors or warnings. Many sites built on a CMS already output some markup through the theme or an SEO plugin, sometimes duplicated by two plugins at once, which can produce conflicting information. Ask your developer to consolidate it so each page describes itself once, consistently, with one Organization or LocalBusiness description reused across the site.

When adding markup, match it to the visible page exactly: the same prices, hours, address and names a visitor can read. Keep in mind that Google supports rich results for a limited set of types and changes that list from time to time, so markup that once produced an enhancement may later stop producing one. That does not make it harmful; it still describes the page. After changes, watch the enhancement reports in Google Search Console for new errors, which often appear when someone edits a template or a plugin updates.

Why it matters for your business

Schema markup can make a listing stand out without changing your page at all: eligible pages may show rich results such as product prices and availability, event dates or a breadcrumb path, which can draw the eye in a crowded results page. For a local business, LocalBusiness markup that matches your Google Business Profile reinforces the basics of local SEO: name, address, phone and hours. It is not a ranking boost on its own, and Google decides whether to show any enhancement. The cost is low when it is built into page templates once, and higher when someone has to maintain it by hand on every page.

Common mistakes

  • Marking up content that is not visible on the page, such as hidden FAQs or reviews.
  • Adding self-serving review ratings for your own business, which Google ignores.
  • Copying markup between templates without updating the values.

Questions people ask

Does schema markup improve rankings?

Not directly. Google has said structured data is not a general ranking factor. It helps engines understand your page and can make it eligible for rich results, which may improve how many people click. Any benefit comes through clarity and visibility in results, not from a ranking boost for having markup.

How do I test my schema markup?

Use Google's Rich Results Test to see whether a page qualifies for rich results and whether the markup has errors, and the Schema Markup Validator to check it against the schema.org vocabulary generally. After launch, Google Search Console reports detected markup and problems across the whole site.

Which schema types should a small business use?

Start with Organization or a specific LocalBusiness type on the home or contact page, and BreadcrumbList across the site. Then add types matching what you actually publish: Product for items with prices, Event for dated events, Article for blog posts. Only mark up information that visitors can see on the page.

Read: How to add JSON-LD structured data to any page →

Related terms

Have something worth building right?