Local Business Schema: Add, Test and Maintain It

What is LocalBusiness schema?

Structured data is standardised code that gives search engines explicit clues about what a page is about. LocalBusiness is the Schema.org type for a particular physical business or branch, and it sits within both the Organization and Place families. Google recommends using the most specific applicable subtype where one exists, such as Restaurant, DaySpa, HealthClub or Store. Google’s Local Business structured data documentation also says that each location should be defined as its own local business entity. Google Search documentation

In practice, most local businesses use JSON-LD: a small block of code placed in the page source rather than woven through visible text. Google recommends JSON-LD because it is usually simpler to implement and maintain, though Microdata and RDFa can also work when valid. Google’s introduction to structured data explains the distinction and why JSON-LD is normally the practical choice for site owners. Google Search documentation

What LocalBusiness schema can and cannot do

That final point matters. Google states that correct structured data does not guarantee an enhanced appearance in Search: results vary according to factors including the query, location, device and Google’s assessment of what is useful for that search. Treat schema as sound technical housekeeping, not a shortcut around local relevance, strong service pages, a complete Google Business Profile or good customer experience. General Structured Data Guidelines

Who should use local business schema?

Schema is most useful when your site represents a real business that serves customers locally: a café, dental practice, garage, estate agent, electrician, beauty salon, solicitor’s office, restaurant, gym or retailer. It is especially worthwhile where core facts can be confused, duplicated or changed, such as businesses with several branches, seasonal opening hours or similarly named competitors.

A service business may also use areaServed to describe where a service is offered. Schema.org defines that property as the geographical area where a service or offering is provided. It can be useful supporting context, but it is not a substitute for accurate location information and should not be treated as a way to rank in every town named. Schema Org guidance

Choose the right schema type and fields

Start with the most precise type that honestly describes the business. A restaurant should normally use Restaurant, a gym may use HealthClub, and an electrician can use Electrician where that reflects the core business. If no specific subtype fits, use LocalBusiness or, for many professional firms, a relevant type such as ProfessionalService.

Do not force a niche type simply because it sounds more SEO-focused. The structured data must accurately represent the page and its visible content. Google’s general guidance also requires the page to be accessible for crawling and warns against hidden, irrelevant or misleading markup. General Structured Data Guidelines

The essential LocalBusiness fields

Google’s own LocalBusiness reference lists geo, opening-hours specifications, priceRange, telephone and location URL among its recommended properties, while its Organization guidance recommends useful identity details such as logos and official profile links where relevant. Google Search documentation

How to add local business schema

Before anyone writes code, create one reliable source of truth. Compare the business name, address, phone number, primary URL and regular hours across the website, Google Business Profile, signage and major listings. Minor formatting differences, such as writing ‘Road’ rather than ‘Rd’, are less important than factual conflicts such as an old phone number, closed branch or incorrect Saturday hours.

A copy-and-adapt JSON-LD template

This example is for a fictional electrician with a public office in Brighton. Replace every example value with information that is visible on the relevant page and accurate for your business. Remove properties that do not apply rather than filling them with guesses.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Electrician",
  "@id": "https://www.example.co.uk/#business",
  "name": "Harbour Electrical Services",
  "url": "https://www.example.co.uk/",
  "telephone": "+441273555010",
  "email": "hello@example.co.uk",
  "logo": "https://www.example.co.uk/images/logo.png",
  "image": "https://www.example.co.uk/images/brighton-office.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "27 Example Road",
    "addressLocality": "Brighton",
    "addressRegion": "East Sussex",
    "postalCode": "BN1 1AA",
    "addressCountry": "GB"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 50.82253,
    "longitude": -0.13716
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:00",
      "closes": "17:30"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "Saturday",
      "opens": "09:00",
      "closes": "13:00"
    }
  ],
  "areaServed": [
    {"@type": "City", "name": "Brighton and Hove"},
    {"@type": "AdministrativeArea", "name": "East Sussex"}
  ],
  "sameAs": [
    "https://www.facebook.com/harbourelectricalservices"
  ]
}
</script>

How the template changes by business type

A restaurant can use Restaurant as its type and add servesCuisine, priceRange and a URL for the current menu. Google specifically lists menu and cuisine fields for applicable food establishments. A dental practice or physiotherapy clinic might use a more suitable healthcare type where it accurately reflects its services, but should avoid publishing clinical claims or unavailable treatments in schema.

For a multi-branch retailer, each branch needs its own name, address, phone number, coordinates, hours and page URL. Do not simply place a list of all addresses in one homepage block and call it done. Google’s documentation is clear that each location should be represented as a LocalBusiness, and a department with genuinely different contact details or opening hours can be nested as a department. Google Search documentation

Opening hours: the detail most likely to go stale

Use separate opening-hours entries whenever the pattern changes. For example, a restaurant open from 18:00 on Saturday until 03:00 on Sunday should be modelled as Saturday opening at 18:00 and closing at 03:00. Google’s guidance also covers 24-hour businesses and temporary seasonal closures using validFrom and validThrough. Google Search documentation

For bank holidays, unexpected closures and one-off late openings, prioritise updating the visible page and Google Business Profile promptly. Update the schema at the same time if those changed hours are represented there. Accuracy for customers matters more than trying to encode every exception in a complex format.

Ways to publish JSON-LD on a WordPress site

The right method depends on who maintains the site and what is already generating schema. Choose the least complicated approach that lets you edit the data safely and prevents duplicates.

For a straightforward single-location site, a carefully configured SEO plugin or a custom JSON-LD block may be enough. For several locations, a developer-maintained template is often safer because it can pull each branch’s address, phone number and hours from controlled fields. Google can process structured data generated with JavaScript when it is available in the rendered page, but simpler server-rendered or template-driven implementation is generally easier to audit over time. Google Search documentation

How to test LocalBusiness structured data

Testing has three different jobs: confirm that the code is valid, confirm that Google can access the live page, and confirm that the data still matches the business. A green tick in one tool is useful, but it is not proof that the page will gain a particular search appearance.

The Schema Markup Validator extracts JSON-LD, Microdata and RDFa and highlights syntax mistakes, but it is a Schema.org validator rather than a promise of Google rich-result eligibility. The Rich Results Test adds Google-specific feedback, while URL Inspection helps establish whether Google can access the actual published page. Schema Org guidance

Google says the Rich Results Test supports JSON-LD, Microdata and RDFa, and its code mode is useful for checking a draft before it is public. After launch, URL Inspection separates the live test from Google’s indexed view, which can be older than the latest page version. Google Business Profile guidance

How to interpret errors, warnings and no results

Google notes that a valid test result still does not guarantee that a rich result will appear. Common blockers include pages that are not indexed, pages blocked by login requirements, robots.txt or noindex, and markup that does not meet quality guidance. General Structured Data Guidelines

Common LocalBusiness schema mistakes

Maintain schema as part of normal local marketing

LocalBusiness schema is not a one-off task. It is business data, so it needs an owner and a simple update routine. The good news is that most businesses only need to revisit it when something meaningful changes.

Review the live markup at least quarterly, and before seasonal trading peaks. A monthly check is sensible for restaurants, hospitality businesses, clinics and other firms that frequently alter hours. Keep a record of the page URL, location owner, last-checked date and the approved name, address, phone number and hours.

Also monitor the broader local-search picture. Schema works best alongside accurate profiles, useful location and service pages, prominent contact routes and a credible stream of customer feedback. For the wider framework, see this practical local SEO guide for UK businesses.

How to measure whether the implementation is healthy

Measure implementation quality separately from commercial outcomes. First, confirm that the relevant pages remain indexable, the markup is valid and the facts are current. Then track broader local organic performance over time rather than attributing every change in rankings or enquiries to schema.

Use a before-and-after record around the rollout date, but allow for seasonality, advertising, reviews, competitors, site changes and normal ranking volatility. If search visibility is the wider problem, work through local relevance and conversion fundamentals rather than adding increasingly elaborate schema properties. Our guide on ranking higher locally explains those wider priorities.

A practical 30-day LocalBusiness schema plan

Frequently asked questions

Sources and further reading

The guidance in this article was checked against the following current sources. Platforms, laws and interfaces can change, so confirm important details before acting.

• Local Business (LocalBusiness) Structured Data — Google Search Central
• General Structured Data Guidelines — Google Search Central
• Review Snippet (Review, AggregateRating) Structured Data — Google Search Central
• Inspect and troubleshoot a single page — Google Search Console Help
• LocalBusiness — Schema.org
• Schema Markup Validator — Schema.org