Structured Data and Schema Markup: What a Business Website Should Actually Add

Structured data is one of the few areas of search optimisation where the mechanism is completely public. You describe what a page is about in a machine-readable format, search engines read it, and in some cases they reward you with an enhanced listing. It is also an area full of folklore: plugins that add a dozen schema types to every page, guides promising rich stars for any site, and markup that describes content the visitor cannot see.

This article separates what is worth doing on a typical business website from what is noise. It explains the vocabulary, the recommended format, the types that matter, how to test, and how to keep markup accurate as the site changes. It complements the broader work described on our SEO page and the audit process in content audits.

What Structured Data Is (and Is Not)

Structured data is a standardised way of labelling information on a page. The shared vocabulary is schema.org, maintained by a community that includes the major search engines. A page about a product can state, in a format machines can read, that it is a Product with a name, an image, a price and an availability. A page about your company can state that it is an Organization with a name, logo and contact details.

What it does

• Helps search engines understand entities and relationships on your pages with less guesswork.
• Makes pages eligible for certain enhanced search appearances, called rich results, where Google supports them.
• Provides consistent information to other consumers, such as knowledge panels, voice assistants and increasingly AI-powered search features.

What it does not do

Structured data is not a ranking switch. Google’s documentation is clear that markup makes a page eligible for features; it does not promise them, and it is not a substitute for helpful content. Adding markup to a thin page produces a thin page with markup. Treat it as clarity, not as a shortcut.

Choose the Format: JSON-LD

Schema.org data can be written in three syntaxes: JSON-LD, Microdata and RDFa. Google recommends JSON-LD, and for good reasons. It lives in a single script block rather than being woven through your HTML, so designers can change templates without breaking it, and developers can generate it from the same data that renders the page.

A minimal example

A JSON-LD block for an organisation looks like this: a script element of type application/ld+json containing an object with @context set to schema.org, @type set to Organization, and properties such as name, url, logo and sameAs. That is the whole idea: an object with a type and properties, using the schema.org vocabulary.

Rules that prevent most errors

1. The markup must describe content that is visible on the page. Hidden or misleading markup violates Google’s guidelines.
2. Use absolute URLs and consistent names. If the company name appears three ways across your markup, entity understanding suffers.
3. Valid JSON is mandatory. One trailing comma turns the entire block into nothing.
4. Use the most specific type that is accurate. LocalBusiness subtypes such as Dentist or Restaurant beat a generic label when they apply.
5. Keep one source of truth. Generate markup from the same fields as the visible content so they cannot drift apart.

The Types Worth Adding to a Business Website

You do not need every type. A short list covers the vast majority of company sites.

Organization (or LocalBusiness)

Place this on the home page or the about page. Include the legal or trading name, logo, official website, contact points and links to your official profiles through sameAs. For businesses with a physical location, use LocalBusiness with address, opening hours and geographic coordinates. This is the foundation for entity understanding, and it should match the details on your Google Business Profile, which matters a great deal for local SEO.

WebSite

Declares the site name and, if you have an internal search, the search action. It is small, easy and occasionally useful for how the site name appears in results.

BreadcrumbList

Describes the navigation path of a page. Breadcrumb markup can replace the raw URL in the search listing with a readable trail. It is one of the most consistently supported types and is straightforward to generate from your menu or category hierarchy.

Article or BlogPosting

For editorial content, mark up the headline, author, publication and modification dates and the main image. Accuracy matters more than volume: use real dates, and update the modification date only when the content genuinely changes.

Product and Offer

For shops, product markup with price, currency, availability and review data can qualify pages for product rich results and merchant listings. Prices and stock must match what is on the page at the time of crawl. Stale markup that advertises an out-of-stock item as available is one of the most common causes of warnings in Search Console.

FAQPage and HowTo: know the current status

Google reduced the visibility of these enhancements. FAQ rich results are now shown only for well-known authoritative government and health websites, and HowTo rich results were withdrawn. Marking up a genuine FAQ on your page remains harmless and helps machines parse the content, but do not expect expandable listings, and do not invent questions to chase a feature that no longer exists for most sites. Check the current documentation for FAQPage before investing time.

Review and AggregateRating

Be careful here. Self-serving reviews, where a business marks up ratings about itself on its own pages, are not eligible for star rich results in most cases, and marking up reviews that were not genuinely collected is a fast route to a manual action.

Types People Add That Rarely Help

• Markup for content that does not exist on the page. If the visitor cannot see it, do not describe it.
• Dozens of overlapping types on every page. Some plugins add Article, WebPage, Person, Organization and more, often with conflicting values. More is not better.
• Fake or templated review counts. These damage trust and risk penalties.
• Deprecated properties and types. Old guides recommend fields that search engines no longer read.

How to Implement It on Common Setups

WordPress

SEO plugins generate a basic graph of Organization, WebSite, WebPage, BreadcrumbList and Article automatically. That default is often good enough. Check what it produces before adding a second plugin or hand-written markup, because duplicate, conflicting blocks are a typical problem. For custom post types, such as case studies or job listings, you may need a small amount of custom code or a dedicated field group to output the right type.

Custom-built sites and shops

Generate JSON-LD in the template layer from the same data the page displays. For a shop, that means the price and stock values in markup are read from the product record at render time. A developer writing this once is more reliable than markup pasted into content fields. It is worth specifying in the brief when you plan a website development project.

Tag Manager

You can inject JSON-LD through a tag manager, and Google can process it, but it adds a dependency and makes markup easy to break or forget. Prefer server-rendered markup where possible.

Validate Before and After Publishing

Untested markup is a liability. Use a small set of tools in a fixed order.

1. Schema Markup Validator. Checks whether the syntax and vocabulary are valid against schema.org in general, regardless of Google features.
2. Rich Results Test. Google’s Rich Results Test shows which rich result types the page is eligible for and flags errors and warnings.
3. Search Console reports. After indexing, the enhancement reports show valid items, warnings and errors at scale across the site, and the URL Inspection tool shows what Google saw.
4. Your own parser check. In a build pipeline, parse every JSON-LD block as JSON. A block that does not parse is silently ignored.

Errors versus warnings

Errors block eligibility and should be fixed. Warnings usually flag missing recommended properties; fix them when the data exists, and do not invent values just to clear a warning.

A Comparison of Schema Types for a Typical Company Site

Keeping Markup Accurate Over Time

Structured data decays. Prices change, opening hours shift, staff leave, and templates get redesigned. Build maintenance in from the beginning.

• Generate markup from the same fields as visible content.
• Add a schema check to your release routine, next to tests for forms and tracking. The same discipline applies to analytics tags; see our 30-day rollout plan for a new website for how we sequence launch tasks.
• Review Search Console enhancement reports monthly. A jump in errors after a deploy points straight at the change that caused it.
• Re-audit after any migration. Markup pointing at old URLs is a common casualty, which we cover in migrating without losing rankings.

A Step-by-Step Plan for a Small Company Site

1. List your page types: home, services, blog, contact, and product pages if you sell online.
2. Assign a schema type to each, using the table above as a guide.
3. Check what your SEO plugin or theme already outputs. Remove duplicates.
4. Complete the Organization or LocalBusiness data, including logo, contact details and official profiles.
5. Add or verify BreadcrumbList on inner pages.
6. Add Product markup on shop pages, sourced from live product data.
7. Run every template through the Rich Results Test and the Schema Markup Validator.
8. Submit key pages in Search Console and watch the enhancement reports for a month.
9. Document what you added so the next developer does not duplicate it.

For the official rules, read Google’s introduction to structured data, which lists the supported features and the general guidelines every markup block must follow.

Frequently Asked Questions

Does schema markup improve my Google rankings directly?

No. Google says structured data is not a direct ranking factor. It helps search engines understand a page and can make it eligible for rich results, which may improve click-through rate, but the content still has to earn its position.

Should I use JSON-LD, Microdata or RDFa?

Use JSON-LD. Google recommends it, it is kept separate from your HTML, and it is easier to generate and maintain than markup embedded in page elements.

Can I still get FAQ rich results?

For most websites, no. Google now shows FAQ rich results only for well-known government and health sites. You can still mark up a real FAQ, but treat it as helping machines read the page rather than as a way to gain expandable listings.

How do I know whether my markup is working?

Run the page through the Rich Results Test and the Schema Markup Validator, then watch the enhancement reports in Search Console after the pages are indexed. Also confirm that the JSON parses without errors.

Is it a problem if two plugins output schema at the same time?

Yes. Duplicate or conflicting blocks confuse parsers and often produce warnings. Inspect the page source, keep one source of markup, and disable overlapping output in the other plugin.

What happens if the markup does not match the page?

Markup that misrepresents visible content can trigger a manual action, which removes rich result eligibility. Even accidental mismatches, such as outdated prices, cause warnings and erode trust in your data.

The Bottom Line

Schema markup rewards accuracy and restraint. Describe your organisation clearly, add breadcrumbs, mark up products and articles from real data, test every template, and ignore promises of instant rich results. A small, correct, maintained set of structured data does more for a business website than a large, conflicting one produced by default settings.

If you want an audit of the markup your site currently outputs, or structured data planned into a new build, talk to our team and we will go through it page type by page type.