SEO

Local business structured data: what to mark up and what to avoid

Learn how structured data describes real business information and how to keep it consistent with visible content.

By Graphic Core   /   Published
Monthly guide series: November 2021

A miniature shop beside blocks showing location, clock and telephone symbols.

What structured data does

Structured data is a standardised way to describe information in a form software can interpret. A business website might use it to identify the organisation, its address where appropriate, or other supported details. The information still needs to be correct and relevant to the visible page; adding code does not replace clear content for customers.

Search features have their own requirements and may change. Google explains that valid structured data can make a page eligible for some features, but does not guarantee that a feature will appear. Begin with the business information people need, then decide whether a supported markup type adds value and can be maintained.

Describe the real organisation

Write down the actual business name, website, appropriate contact details and any genuine physical location before adding markup. Choose a type that reflects the organisation. Where a business has departments, branches or different operating models, ask someone familiar with the real arrangements to confirm what each entity represents.

Do not invent offices, teams, telephone numbers, operating hours or customer-facing premises. A company serving several Hertfordshire towns from one base should not create fictitious local branches in code simply because it has pages about those areas. Eligibility for a particular feature must be checked against the current documentation.

Keep markup and page content aligned

The information in structured data should correspond to what the page actually communicates. If an address changes, update the visible contact information and any machine-readable data together. Establish who owns that update: a plugin, theme, developer or site editor may control different parts of the page.

Check whether the site already produces relevant markup before adding another plugin. Duplicate or contradictory entries can make maintenance difficult, especially when one source is updated and another remains stale. Inspect the final public page rather than assuming an editor setting is the only place data is generated.

AT A GLANCE

Structured-data quality check

  • RealDescribe an actual business
  • VisibleAgree with the page content
  • ValidTest supported markup
  • MaintainedUpdate when details change
Correct information and a maintainable process matter alongside valid code.

Choose an implementation that can be maintained

Google supports JSON-LD for many structured-data features, and a content system may generate it through its theme or a suitable extension. Ask what fields are included, where values come from and how changes are approved. Do not install multiple tools solely to increase the amount of markup without understanding what each outputs.

A developer should follow the documentation for the chosen type and required or recommended properties. Details vary by feature. Only include information the business can support and is entitled to publish. A code example found elsewhere may use different business types, locations or requirements, so it should not be copied unchanged.

Test the public page

Use Google’s documented testing tools where the chosen feature is supported and inspect the live page after deployment. Fix genuine errors and consider relevant warnings in context. A syntactically valid result does not establish that the business qualifies for every search feature or that the underlying facts are true.

Check that the page can be accessed by the relevant crawler and is not unintentionally blocked or marked noindex. Review search-console feedback over time, but do not expect changes to appear immediately. A feature may be unavailable or not displayed even when the technical markup is correct.

An illustrative example

Imagine an eligible shop with a real customer-facing premises and clear opening hours on its contact page. The team confirms those details, uses an appropriate local-business markup type and tests the published page. When opening times change, the person responsible updates both the visible information and the data source used by the site.

A different service business that visits customers has a different operating model and must choose information appropriate to it. It should not list several invented shopfronts to cover neighbouring towns. These examples are illustrative and do not assert facts about any real Graphic Core customer.

Separate an entity from a service area

A business can serve customers in many places without operating a branch in each one. Describe the actual organisation and any real eligible premises accurately. A town page may explain the services available to customers there, but the presence of that page does not create a new office, staff member or postal address.

Ask the developer how organisation and service information are connected across the site. Use the documentation for any feature being targeted, and do not add review ratings, opening hours or business types unless they are true, supported and appropriate. Misleading machine-readable claims can mislead customers as well as conflict with platform rules.

Build an update workflow

Record which tool generates each structured-data field and who supplies the source values. If opening hours are edited in one system but the website reads another, the public page and code can diverge. Assign an owner to check both outputs whenever the business changes its contact details or premises.

Include a sample live-page test in the website handover and note how to remove an incorrect value. Recheck after a theme change, plugin installation or migration. The aim is a single understandable maintenance process, not the largest possible collection of scripts or schema types.

Before making a change, save the approved business details and identify the page on which each fact can be checked. After publishing, compare the rendered page with the generated data and the source maintained by the business. This is especially useful when opening hours vary or a premises changes its appointment arrangements. If no one is responsible for updating a value, leave it out until the business can supply and maintain it accurately.

Review before and after launch

Ask whether the business details are true, visible where appropriate, permitted to be shared and controlled by an identified owner. Confirm that there is no contradictory markup from another tool, then validate the implementation and keep a note of how to update it. Check the data when business hours, locations or contact details change.

Treat structured data as a useful description rather than a shortcut to rankings or rich results. A clear customer experience, accessible content and honest representation remain necessary. If the correct type or treatment is uncertain, ask a qualified developer to compare the real situation with current official guidance.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION