Article SEO & Marketing

What structured data is and where it helps

A vocabulary for describing a page in terms a machine can parse directly, and what it can realistically earn you.

iFastHosting Support Team Updated 26 August 2026 8 min read Intermediate

A page written for a human reader relies on that reader inferring meaning from layout, context, and plain language — a price sitting next to a product name is obviously the product's price to anyone looking at the page, but nothing in the HTML states that relationship explicitly. Structured data is the fix for that gap: a standardised way of stating facts about a page directly, in a form a machine can parse without guessing.

The vocabulary behind it

Structured data on the web overwhelmingly uses the vocabulary maintained at schema.org, a shared standard originally backed jointly by the major search engines specifically so that site owners would not need to learn a different format for each one. It defines types for the concrete things a page might describe — an Article, a Product, a LocalBusiness, a Recipe, an Event — and a set of properties appropriate to each type.

The format most commonly used to write it is JSON-LD: a small, self-contained script block placed in a page's <head>, separate from the visible HTML.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Product",
  "offers": {
    "@type": "Offer",
    "priceCurrency": "USD",
    "price": "29.99"
  }
}
</script>

What it does not do

This needs to be stated plainly because it is the most common misunderstanding around structured data: Google has said structured data is not a general ranking factor. Adding it does not make an otherwise average page rank higher purely by virtue of being marked up. It is a description layer, not a boosting mechanism.

What it can do instead is earn a richer display

Valid, accurate structured data makes a page eligible to be considered for an enhanced result — a recipe with a photo and cook time shown directly in results, a product with its price and stock status visible, an FAQ that expands inline. Whether any of that is actually shown remains entirely at the search engine's discretion, and it can change without warning. Eligibility is the honest ceiling of what markup buys you.

Where it genuinely helps

E-commerce product pages. Price, availability and review counts, marked up correctly, are some of the most consistently used structured data types in results — when a search engine chooses to display them.
Recipes. Cook time, ratings and ingredient counts are a long-established, well-supported structured data type with a strong track record of visible results.
Local businesses. Address, opening hours and contact details marked up formally reduce the chance of a search engine misreading information that is present but only stated in prose.
Articles and how-to content. Author, publish date and step structure help a search engine correctly attribute and categorise the content, even when nothing visually different results from it.
FAQ-formatted pages. Question-and-answer content marked up as such can occasionally appear as an expandable list directly in results — though Google has scaled back how widely it shows this over time, which is a useful reminder that display eligibility is not permanent even once earned.

Where it is not worth the effort

Marking up content that is not genuinely present on the page, or forcing a schema type onto a page that does not actually match it, does not create value — it risks the opposite. Google's structured data guidelines are explicit that markup has to reflect what a user can actually see, and a mismatch is treated as a spam signal rather than an ambitious use of the feature. If a page does not naturally fit a recognised schema type, it is entirely reasonable to leave it unmarked rather than stretching a type to fit.

The AI search connection

Structured data has taken on a second relevance beyond traditional search results: AI systems that summarise or answer questions by drawing on web content generally find clearly, formally described facts easier to extract accurately than the same facts stated only in loosely structured prose. This is not a guarantee of being cited or quoted, but a page that states its facts explicitly gives an automated summariser less room to misread them than a page that leaves everything to inference. See how to be cited by AI search engines for more on that separate but related goal.

Testing rather than assuming it works

A structured data block with a single misplaced comma fails silently — the page loads exactly as normal, with no visible symptom, while the markup itself is entirely ignored. This makes testing worthwhile every time, rather than trusting that code copied from an example or generated by a plugin is automatically correct for your specific page. Google's Rich Results Test accepts a live URL or pasted code directly and reports both outright syntax errors and whether the page currently qualifies for any enhanced display type it recognises.

Getting started without overcomplicating it

Most CMS platforms and SEO plugins generate common schema types automatically from fields already being filled in for other reasons — an author name, a publish date, a product's price — with no separate markup to write. Start there rather than hand-writing JSON-LD for every page type on day one. For pages that need something a plugin does not cover, how to add schema markup to your pages covers the manual process and how to test it before publishing.