How to Rank Pages With Schema Markup

What schema markup actually is

Schema markup — also called structured data — is a standardised vocabulary you add to a page’s code to describe what the content means. The vocabulary is schema.org, maintained jointly by Google, Microsoft (Bing), Yahoo and Yandex, so the major search engines all read the same labels.

Instead of leaving a crawler to guess that “£482,910” is revenue, that a block of text is a recipe, or that five words are a product name and a price, you label it explicitly. Most sites do this with JSON-LD — a small script in the page’s head — which is the format Google recommends and the simplest to maintain. Microdata and RDFa do the same job inline, but JSON-LD keeps your markup separate from your HTML and far easier to manage.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Rank Pages With Schema Markup",
  "description": "A practical guide to using structured data to win rich results.",
  "author": { "@type": "Organization", "name": "Heavygate Marketing" },
  "datePublished": "2026-06-10"
}

Does schema actually help rankings?

Let’s be honest, because plenty of agencies aren’t: Google has repeatedly said structured data is not a direct ranking factor. Adding schema does not, by itself, push you up the results.

So why bother? Because it changes the two things that decide whether a ranking actually earns money:

• How your result looks. Valid markup makes you eligible for rich results — review stars, prices, breadcrumbs, sitelinks, FAQs. The same position with stars next to it wins far more clicks. More click-through rate from the same ranking is free traffic.
• How well you’re understood. Schema spells out the entities and relationships on your page in a language search engines parse perfectly. That clarity feeds topical relevance, eligibility for SERP features, and increasingly the AI summaries that sit above the classic results.

The schema types that earn their keep

You don’t need every type schema.org offers — you need the ones that match your pages:

• Organization / LocalBusiness — your name, address, phone, logo and opening hours. The foundation of your knowledge panel and local visibility.
• Article / BlogPosting — author, dates and headline for guides and news, and eligibility for richer article treatment.
• Product + Offer + AggregateRating — price, availability and review stars. For e-commerce, this is one of the biggest click-through wins there is.
• FAQPage and HowTo — question-and-answer and step-by-step content.
• BreadcrumbList — a tidy breadcrumb trail in the search result instead of a raw URL.
• Service, Event, Recipe, VideoObject — whatever genuinely describes the page.

One honest caveat: Google trims rich-result types over time. It has restricted FAQ rich results to a handful of authoritative health and government sites and retired HowTo rich results entirely. The markup still helps machines understand the page, so it keeps its value — just don’t add it expecting a snippet that no longer appears.

JSON-LD: how to add it

The workflow is simple, and it’s the same every time:

1. Match the type to the page. Pick the schema.org type that genuinely fits: Product for a product, Article or BlogPosting for a post, LocalBusiness for a location, FAQPage for a real Q&A.
2. Write it as JSON-LD. Add the markup as JSON-LD inside a script type="application/ld+json" tag in the page’s head. It’s the format Google recommends and the easiest to maintain.
3. Only mark up what’s visible. Every property must reflect content a user can actually see on the page. Marking up hidden or absent content breaks Google’s guidelines.
4. Connect the entities. Use about, mentions and sameAs to link your content to known entities — Wikipedia, Wikidata, your official profiles — so search engines know exactly what you mean.
5. Validate before you ship. Run it through Google’s Rich Results Test and the Schema.org validator to catch errors and see which rich results you’re eligible for.
6. Deploy and monitor. Publish, request indexing, then watch the enhancement and rich-result reports in Google Search Console to confirm it’s recognised.

Two free tools do the validating: Google’s Rich Results Test tells you which rich results you qualify for, and the Schema Markup Validator on schema.org checks the syntax against the full vocabulary.

Entities, not just keywords

This is where schema gets genuinely powerful — and where most people miss the point. Search moved from strings to things years ago. Google’s Knowledge Graph maps entities — people, places, brands, concepts — and the relationships between them.

Using about, mentions and sameAs to connect your content to known entities — linking out to Wikipedia, Wikidata or your own official profiles — tells a search engine precisely what your page is about, in its own vocabulary. That is the heart of semantic SEO and entity SEO: you build topical authority by being unambiguous, not by repeating a phrase.

{
  "@type": "BlogPosting",
  "about": [
    { "@type": "Thing", "name": "Schema.org",
      "sameAs": "https://en.wikipedia.org/wiki/Schema.org" },
    { "@type": "Thing", "name": "JSON-LD",
      "sameAs": "https://json-ld.org" }
  ],
  "mentions": [
    { "@type": "Thing", "name": "Google Knowledge Graph",
      "sameAs": "https://en.wikipedia.org/wiki/Google_Knowledge_Graph" }
  ]
}

Mistakes that get you ignored — or penalised

• Marking up invisible content. If a user can’t see it on the page, don’t put it in the schema. It is against Google’s guidelines.
• Schema that doesn’t match the page. Mismatched markup gets ignored at best and flagged at worst.
• Fake or self-serving reviews. Inventing aggregateRating or marking up your own reviews about yourself is a fast route to a manual action.
• Stuffing the keywords field. It won’t rank you, and spammy structured data can trigger a penalty.
• Invalid syntax. A single missing bracket and the whole block fails silently. Always validate.

A practical schema checklist

• One primary type per page that matches the content.
• JSON-LD in the head, every property drawn from visible content.
• Organization or LocalBusiness sitewide, with consistent name, address and phone.
• BreadcrumbList on deep pages; Product or Service where they apply.
• about, mentions and sameAs linking to real entities.
• Validated in the Rich Results Test and monitored in Search Console.

Done like this, structured data is quiet, compounding technical SEO: it makes your results more clickable and your pages easier to understand, and it keeps paying long after the work is shipped. Want a head start? Try our free schema markup generator — or, if you’d rather we did it for you, see our SEO services in Manchester and pair it with digital PR for the links that back it up.

Frequently asked questions