Structured data: what it is and how it helps your site on Google

When you search for a restaurant on Google, you sometimes see rating stars, hours and prices right in the result. When you search for a recipe, times and calories. It is not magic: it is information the site has described in a language search engines understand. It is called structured data.

In this guide I explain what it is, what it is really for and how to use it without mistakes or exaggerated promises.

What it is

A web page is written for people: headings, text, images. A search engine reads it, but has to guess what it means: is that number a price? Is that name a person or a company? Is that text a question and an answer?

Structured data is a way of saying so explicitly, with a shared vocabulary called schema.org. It is written in a separate block, in the JSON-LD format, which does not change the page's appearance.

An example in words: "this page describes a local business, it is called this, has this address and these hours".

What it is for (and what it does not do)

• It helps Google understand better what the page is about and who is behind it.
• It can make results richer, for example with ratings, navigation paths or business information.
• It is not a shortcut to first position: it is not a direct ranking factor.
• It does not guarantee that rich results will appear: Google decides, and over time it has reduced the display of some types, such as FAQs for most sites. The data remains useful for understanding, but it is best not to count on a certain visual effect.

The most useful types for a site

You do not need to mark up everything. Some types almost always make sense.

• Organization / person: who you are, your site, links to official profiles.
• LocalBusiness: for businesses with a location, with address, hours and contacts (also useful for local SEO).
• BreadcrumbList: the page's navigation path (Home › Services › …).
• Article / BlogPosting: for articles, with title, author, date and image.
• Product and Offer: for online shops, with price, availability and ratings.
• FAQPage: for pages of real, visible questions and answers.
• Service: to describe a service offered.

The rules to respect

Google's guidelines are clear, and worth respecting.

1. Describe only what is visible on the page. The data cannot say things different from the text.
2. Do not mark up misleading or irrelevant content, such as invented ratings.
3. Keep the data up to date: prices, availability and hours must match reality.
4. Fill in the required fields of the chosen type, and the recommended ones where you have the information.
5. Use a single consistent format (usually JSON-LD) to avoid duplication or contradictions.

Anyone who violates these rules risks manual actions that remove rich results.

How they are implemented

There are three routes.

• With a plugin: on WordPress sites many SEO plugins add the basic data. It is convenient, but it is worth checking what they produce, because they sometimes duplicate or get it wrong.
• Custom: the data is generated by the site from the real content of each page, consistently and under control. It is the most precise solution.
• By hand on single pages: possible for a few cases, but hard to manage if content changes often.

How to check them

Before and after publication:

• Google's Rich Results Test: says whether the page can have rich results and flags errors.
• schema.org validator: checks formal correctness.
• Search Console: in the enhancements section it shows errors and warnings for each data type, across the whole site.

After a change of theme, plugin or structure, check again: it is easy to break the data without noticing.

Common mistakes

• Copying data from an example without adapting it to the page.
• Duplicating data between plugin and theme, creating contradictions.
• Marking up what is not there: questions that do not appear, prices different from those shown.
• Not updating them when prices, hours or availability change.
• Expecting a jump in rankings right after adding them.
• Ignoring Search Console warnings.

Where they fit into SEO work

Structured data is one part of technical SEO, which also includes speed, page structure, sitemaps, internal links and multilingual versions. On their own they do not work miracles; together with a fast site and useful content they help you be understood better. For speed, start with Core Web Vitals: what they are and how to improve them. If you are about to rebuild your site, read Rebuilding your site without losing rankings.

Where to start, if you are starting from zero

You do not need to mark up everything at once. A reasonable path:

1. Organization or person on the main page, to say who you are.
2. BreadcrumbList on all inner pages.
3. Article or BlogPosting on articles.
4. LocalBusiness if you have a location to be found.
5. Product if you sell online, with real price and availability.
6. Checking with verification tools and, after a few weeks, with Search Console reports.

A small, correct implementation is worth more than an enormous one full of warnings.

Why entrust it to me

I have been programming since 1999, with more than 300 projects delivered and about 30 agencies as an external developer. I work on technical SEO: structured data (schema.org) implemented custom for each page, sitemaps, speed, and measurements before and after interventions, so you know exactly what changed. I work from Rome and remotely.

If you want to know how your site's data stands, write to me: a chat of about 20 minutes, no strings attached, then a written, free proposal. The service is in Technical SEO and site speed.