Schema Markup: Which Types Actually Help

Schema markup is structured data code — almost always JSON-LD — that you add to a page to label what its content means, so search engines can read a price, a rating, an author, or an event date without guessing. It does not raise your rankings on its own, and most schema types produce nothing visible in search. The payoff comes from a short list of types that unlock rich results: enhanced listings with stars, prices, images, or breadcrumbs that lift click-through.

The catch is that Google has quietly retired several once-popular rich results, so half the schema advice online is now wrong. This guide covers which schema markup actually earns a visible result in 2026, which types are effectively dead, and the one rule that will get your site penalized if you ignore it.

What Schema Markup Actually Does

Structured data does three specific jobs, and only one of them is visible to searchers. First, it can make a page eligible for a rich result — the enhanced listing with stars, a price, or an image thumbnail. Second, it helps Google connect your page to the right entities in its knowledge graph, clarifying that a brand name is the company and not the common noun, or that a string of digits is a phone number. Third — and this is where most people go wrong — it does not directly raise your position in the rankings.

Google has stated repeatedly that structured data is not a ranking factor the way a backlink or page speed is. What it buys you is eligibility plus a possible click-through boost when your listing looks richer than the plain results around it. Marking up a page correctly does not force Google to show a rich result; the algorithm decides per query whether to display one, so treat schema as a way to qualify, not a guarantee.

The Types That Reliably Earn Rich Results

These types can still produce a visible enhancement in Google Search today, and they are where your effort belongs:

• Product — price, availability, and review stars in the result; the backbone of e-commerce visibility and Google's free merchant listings.
• Review and AggregateRating — star ratings for products, recipes, books, movies, and software. Self-serving reviews about your own business on your own site are not eligible.
• Breadcrumb — replaces the raw URL with a clean navigational trail; low effort, near-universal support.
• Recipe — cook time, calories, ratings, and eligibility for the recipe carousel.
• Event — dates, venue, and ticket info, often shown in a dedicated events pane.
• Video — key moments, thumbnails, and eligibility for the video results.
• JobPosting — inclusion in the Google Jobs experience.
• Organization and LocalBusiness — feeds the knowledge panel, logo, address, and contact details.

Organization markup is also where you formally declare your brand — its name, logo, and social profiles — so Google treats it as a single entity. That entity is only as memorable as the name behind it. If you are still choosing one, curated marketplaces such as Atom.com specialize in premium, brandable names and ship each listing with a free AI appraisal, a USPTO trademark check, a designed logo, and secure escrow — the kind of distinct brand that structured data can then reinforce.

What Happened to FAQ and HowTo Schema

This is where outdated advice does real damage. In August 2023, Google sharply restricted FAQ rich results. They now appear only for a narrow set of well-known, authoritative government and health websites. If you run a normal business, blog, or store, valid FAQPage markup will pass every validator and still show nothing in search. It is not broken — the feature was simply taken away from most sites.

HowTo rich results were retired in the same window and then removed entirely. Google deprecated the visual HowTo result, so step-by-step markup no longer earns the illustrated, expandable listing it once did. You can leave the markup in place for semantic clarity, but expect zero visual payoff from it.

The practical takeaway: do not spend hours templating FAQ and HowTo schema across your site expecting rich results. Write genuine question-and-answer content for users where it helps them, but treat the schema itself as optional plumbing, not a growth lever.

Article Schema: Eligibility, Not a Snippet

Article schema is widely misunderstood. For the average website it does not generate a special snippet at all. What it does is supply eligibility signals — headline, author, publish and modified dates, publisher, and images — that support features like Top Stories and Google News for qualifying publishers.

For a typical blog, adding Article markup will not visibly change your listing. It is still worth including because it cleanly communicates authorship and freshness, both of which feed Google's understanding of expertise and recency. Just do not expect a stars-and-thumbnails transformation from it, and do not let anyone sell you Article schema as a click-through hack.

The Hard Rule: Never Mark Up Invisible Content

Here is the one rule you can never break: only mark up content that is actually visible to users on the page. Google's structured data guidelines are explicit that markup must describe content the visitor can see. Declaring a five-star rating, a low price, or an FAQ answer in your JSON-LD that does not appear on the rendered page is a violation.

The consequences are real. Marking up hidden, invisible, or misleading content is classed as spammy structured data and can trigger a manual action, which strips every rich result from your site and is slow to reverse. Common ways sites break this rule without meaning to:

• Injecting FAQ markup for questions that are not written anywhere on the page.
• Marking up aggregate ratings pulled from another source that visitors cannot see.
• Declaring a promotional price in schema while the page displays a different price.
• Adding review stars to a page that has no reviews on it.

If the searcher would feel misled after clicking through, the markup is wrong — no matter how valid the syntax is.

How to Add Schema Markup and Validate It

Use JSON-LD. Google recommends it over Microdata and RDFa because it lives in a single script block, separate from your HTML, which makes it easy to generate and maintain. Build the object from the Schema.org vocabulary, include every property Google marks as required for that type, and add the recommended properties wherever you genuinely have the data on the page.

Then validate before and after you ship:

1. Run the page through Google's Rich Results Test to confirm it is eligible for a specific feature — not merely syntactically valid.
2. Use the Schema Markup Validator on schema.org for general vocabulary checks that are not tied to a Google feature.
3. After deployment, watch the Enhancements reports in Google Search Console, which flag errors and warnings on live, indexed pages over time.

Add schema markup only where a supported rich result exists and the data is real and on-page. That single discipline separates structured data that quietly compounds your click-through rate from markup that wastes effort or, worse, invites a penalty.

Frequently asked questions

Does schema markup improve my Google rankings?

Not directly. Google treats structured data as an eligibility signal, not a ranking factor. Its value is qualifying your page for rich results and helping Google understand your content, which can lift click-through rate rather than raise your position.

Which schema format does Google prefer?

JSON-LD. It keeps structured data in a single script block separate from your HTML, so it is easier to add and maintain than Microdata or RDFa. Google recommends it for all supported types.

Why did my FAQ rich results disappear?

Google restricted FAQ rich results in August 2023 to well-known, authoritative government and health sites. Your markup is probably still valid; the feature was simply withdrawn for most websites.

Is HowTo schema still worth adding?

The HowTo rich result was deprecated and removed, so it no longer produces a visual enhancement. You can keep the markup for semantic clarity, but do not expect any search feature from it.

How do I test schema markup?

Run the page through Google's Rich Results Test to confirm feature eligibility, use the schema.org validator for general vocabulary checks, and monitor the Enhancements reports in Google Search Console after publishing.