Structured data is how you tell a machine what your business is

What structured data actually is, without the jargon

Strip away the vocabulary and structured data is just labels attached to facts already sitting on your page. Your phone number is already visible in the footer. Structured data is a tag, invisible to a reader, saying "this specific text is a phone number" instead of leaving a machine to guess.

It doesn't change how the page looks to a visitor. It changes how cleanly a machine — a search engine, an AI assistant summarizing results — can pull a fact out of your page instead of misreading it.

Think of it as a second, invisible copy of your page written specifically for machines to read. The visible page stays exactly the same. Nothing about the design changes. Only the code underneath gets more precise.

The vocabulary around this subject exists to make it sound harder than it is. Underneath the terminology, it's a fairly mechanical piece of work, closer to filling in a form correctly than writing anything new.

The local business markup nearly any site can carry

The single most useful piece for a small business is local business markup: your name, address, phone number, and category, labeled formally instead of left as plain text a machine has to interpret. It's the baseline, and it applies to nearly any physical or service-area business.

It isn't complicated to add. Most website platforms have a plugin or a built-in field for it. Worth checking whether yours already has it turned on before assuming it needs building from scratch.

If your platform doesn't handle it automatically, a developer can add it directly to the page code in an afternoon. It's a small, contained job, not an ongoing project.

Ask to see it working before you pay for it as a separate line item. A finished implementation is easy to verify with a free tool, so there's no reason to take a supplier's word for it on faith. A five-minute check on your part confirms whether the work was actually done, and how well, before any money changes hands over it.

Labelling services, opening hours, and location

Past the basics, you can label individual services, your opening hours, and your service area the same way. This lets a machine answer "is this plumber open right now" or "does this business serve my neighborhood" accurately, pulled straight from your page instead of guessed.

Keep it factual and specific. A vague service name labeled as structured data is just as unhelpful to a machine as it is to a person reading the page directly.

Update it when your hours change. Markup that still says you're open on a day you've since closed is worse than no markup, because it actively misleads whoever reads it. Put a reminder on your calendar to check it every time your hours shift for a season or a holiday.

Review and rating markup and the rules that come with it

You can label reviews and star ratings so they're eligible to show up directly in a result, which is a real, visible advantage. It also comes with strict rules: the reviews have to be genuine, collected the way the platform requires, and displayed honestly on the page itself.

Markup showing a rating that isn't genuine and verifiable, or one collected outside the rules, tends to get penalized rather than rewarded. This is a place where doing it properly matters more than doing it at all.

Read the actual rules before adding this specific type. These rules change more than the rest of structured data, and getting them wrong carries a real cost.

Testing what you added and reading the errors it reports

After adding structured data, run it through a free testing tool before assuming it worked. These tools show exactly what a machine will read from your page, and flag anything broken or missing.

Errors are common on a first attempt and almost always fixable — a missing required field, a mismatched value. Warnings are usually optional fields worth adding but not blocking anything. Read the actual output rather than assuming silence means success.

Do this after every significant change to the page, not just once at launch. A field that worked fine before a redesign can break silently after one, with nothing on the visible page telling you it happened.

Bookmark the testing tool and make checking it part of any future site change, the same way you'd check a page still loads correctly after an update.

Markup that contradicts what the page visibly says

The worst outcome here is markup claiming something the visible page doesn't back up — hours that don't match what's printed on the page, a rating that isn't shown anywhere a person can see it. That mismatch reads as manipulation, whether or not it was intended that way, and it can cost more trust than having no markup at all.

Check the two against each other occasionally. What the markup says and what the page says should always match exactly. If a supplier suggests markup that inflates a rating or invents a detail the page doesn't show, that's worth refusing outright, whatever the reasoning offered for it.

Structured data describes the pages your site actually needs to exist in the first place — there's nothing to label accurately if the underlying page is thin or missing.

It also sits inside the wider mechanism behind how small businesses actually get found online, and it's one of the more concrete ways a business becomes something an AI assistant can accurately quote. If you'd rather have someone else implement it correctly, whether this belonged in the original build instead of a separate line item is worth asking before you pay for it twice.

More from the blog

All posts