Structured Data and Schema Markup Explained for Business Sites

By Grocito12 October 2026

Structured data is code added to a page that describes its content in a standard, machine-readable way, usually using the schema.org vocabulary in JSON-LD format. It helps search engines understand things like your organisation, articles, products and FAQs, and can make a page eligible for rich results. It does not promise any special display, and it must always match what visitors can actually see.

Key takeaways

Structured data labels the content already on your page; it is not a way to add content that users cannot see.
JSON-LD is the format most search engines recommend and the easiest to maintain.
Common useful types for business sites are Organization, LocalBusiness, BlogPosting or Article, FAQPage, Product and BreadcrumbList.
Markup makes pages eligible for rich results, but search engines decide whether to show them.
Validate with the Rich Results Test and the Schema Markup Validator, and review your markup whenever the page changes.

What structured data is

A web page is written for people, so a search engine has to infer that a block of text is a price, a date or a phone number. Structured data removes some of the guesswork by labelling the facts directly. A product page can say it has this name, this image and this price, while a blog post can say who wrote it and when.

The shared vocabulary is called schema.org, a collection of types and properties maintained by a community that includes major search engines. Google and others read it to understand pages and, in some cases, to show enhanced listings. It also supports efforts such as answer engine optimisation.

JSON-LD, microdata and RDFa

Structured data can be written in three formats.

JSON-LD

JSON-LD is a block of data placed in a script tag with the type application/ld+json, usually in the head or body of the page. It sits apart from the visible HTML, so you can add or change it without touching the layout. Google's documentation recommends JSON-LD, and it is the easiest option to generate from templates and content fields.

Microdata and RDFa

Microdata and RDFa add attributes directly to your visible HTML tags. They work, but they are harder to maintain because the data is tangled with the layout, and a design change can break them. Unless an existing system already produces them, choose JSON-LD for new work.

Common types for business sites

You do not need every type. Add the ones that truthfully describe your pages.

Organization

Describes your company: name, logo, website address, contact details and links to official social profiles. It usually belongs on your home page or About page. Keep the logo URL working and the details identical to those in your public profiles.

LocalBusiness

For businesses serving a local area, this type adds an address, phone number, opening hours and service area. Many subtypes exist, such as more specific kinds of shops or clinics, so use the closest accurate one. Our guide to local SEO for service businesses shows where this fits.

Article and BlogPosting

For guides and blog posts. It can include the headline, author, publication and modification dates, image and publisher. Dates should reflect real publication and genuine update times.

FAQPage

For a page that contains a list of questions and their answers, where the page itself provides the answers. Eligibility and display rules for FAQ rich results have changed over time, and Google has limited when they appear, so check the current Google documentation before relying on them. Even if the rich result is not shown, a clear FAQ section remains useful to readers.

Product

For product pages: name, description, images, brand, offers and, where genuinely collected, review information. Product markup is especially valuable on an e-commerce store, where price and availability change often and the markup should be generated from live data.

BreadcrumbList

Describes the page's position in your site hierarchy, such as Home, Services, SEO. It can help search engines show a clear path in results, and it mirrors the visible breadcrumb trail on the page.

Rich results: what to expect

Rich results are search listings that show extra information, such as star ratings, product details or breadcrumbs. Structured data can make a page eligible for them, but eligibility is not entitlement. Search engines decide whether to show an enhancement based on quality, relevance, the query and their own policies, which change from time to time. Treat markup as a way to be understood properly, and rich results as a possible bonus.

The rules that matter

Match the visible content. Mark up only what users can see on the page. If your markup says there are reviews and the page shows none, you are breaking the guidelines.
Be accurate and current. Prices, availability, opening hours and dates must reflect reality.
Use the right type. Do not mark an ordinary page as a product or a company as a different kind of organisation just to chase a feature.
Do not hide content for markup's sake. Text placed in markup but absent from the page is a common route to manual actions.
Follow the specific guidelines. Each rich result type has its own requirements, documented by the search engine. Read them before implementing.

How to implement structured data

CMS plugins and settings

Many CMS platforms and SEO plugins can output basic Organization, Article and breadcrumb markup automatically. This is the quickest route for small sites, but always inspect what the plugin produces rather than assuming it is right. Defaults sometimes include outdated details or repeat markup from several sources.

Templates and a headless setup

On custom builds, generate JSON-LD from the same content fields that produce the visible page. For example, an article template can build its BlogPosting markup from the title, author, dates and image already stored in the content system. This keeps markup and page in sync. It is one reason we like structured templates in CMS work and in headless CMS projects.

Where to place it

Add JSON-LD in the head or body of each page. Make sure it is present in the server-rendered or static HTML, or confirm through testing that the search engine can see it after rendering. Each page should have markup for its own content, not a copy of the home page's markup.

Validate before and after publishing

Rich Results Test: a Google tool that checks whether a page's markup is eligible for Google's rich result features, and flags errors and warnings.
Schema Markup Validator: a general tool that checks schema.org syntax regardless of search engine features.
Search Console: the enhancement and rich result reports show errors and valid items across your site after search engines crawl it.

Fix errors first, then review warnings, which usually point to optional properties. Test a representative page from each template, not only the home page. Retest after theme, plugin or template changes.

Common mistakes

Marking up reviews or ratings that were fabricated, copied from elsewhere or not displayed on the page.
Hiding marked-up content from users, or marking up content that appears nowhere on the page.
Copying the same markup across every page.
Leaving outdated opening hours, prices or discontinued products in markup.
Using FAQ markup for promotional text rather than real questions and answers.
Relying on a plugin and never checking the output.

Maintenance

Structured data is not a one-off task. Put these checks in your routine:

Review markup when you redesign, change a theme or switch platform.
Check Search Console enhancement reports monthly for new errors.
Update markup whenever the visible facts change, such as new hours or products.
Re-read the search engine's documentation a few times a year, as requirements are updated.
Document which templates produce which markup.

Our technical SEO checklist places structured data within a broader review, and our SEO services include markup audits.

A worked example

Imagine a small clinic network with a site built on a standard CMS. The home page has Organization markup, but with an old phone number. Clinic pages lack local markup, and the blog plugin adds Article markup with no author. The team corrects the Organization details, adds LocalBusiness markup to each clinic page using the address and hours shown on the page, and edits the blog template so the author and dates come from the post. They then test one page from each template with the Rich Results Test and the Schema Markup Validator. They deliberately skip review markup because the site does not display patient reviews. The principle is to describe only what is true and visible.

FAQ

Is structured data a ranking factor?

As far as is publicly documented, structured data is used to understand content and make pages eligible for rich results, not as a direct ranking boost. It can still help indirectly if clearer, more attractive listings earn more clicks.

What is the difference between schema markup and structured data?

Structured data is the general idea of labelling content in a machine-readable form. Schema markup usually means structured data written with the schema.org vocabulary, which is what most search engines read.

Will adding FAQ schema give me rich results?

Not necessarily. Google has changed when and where FAQ rich results appear, so check the current documentation. Add FAQ markup only to genuine question-and-answer content that is visible on the page.

Can structured data cause problems?

Yes, if it is misleading or does not match the page. Fake reviews, hidden content or inaccurate details can lead to rich results being removed or a manual action. Keep it truthful and review it regularly.

Next steps

Choose one template, such as your blog post layout, and check what markup it produces today by testing a live page with the Rich Results Test and the Schema Markup Validator. Fix any errors, make sure every property matches the visible page, and then move on to your home page and key service pages. If you would like a professional review, contact us and we can audit your markup with you.