Local SEO for Small Businesses: Add LocalBusiness Schema the Right Way
Local SEO for small businesses is often described as a content problem, but a chunk of it is markup: search engines can only trust your location facts when the visible page and the machine-readable data say the same thin
Local SEO for small businesses is often described as a content problem, but a chunk of it is markup: search engines can only trust your location facts when the visible page and the machine-readable data say the same thing. This walkthrough shows how to add a single LocalBusiness (or a more specific subtype) JSON-LD block to a small-business website, how to test it, and how to avoid the errors that create a second, conflicting NAP.
I build and review sites for local service businesses. I also run North Fox Digital. The example below is fictional. Do not copy the names, phone numbers, or coordinates onto a live site.
You only need one canonical JSON-LD graph on the templates that represent the business as a whole, usually the homepage and the contact page. You do not need a unique LocalBusiness blob on every blog post. If you already have Open Graph tags, leave them; they do not replace schema.
A JSON-LD recipe you can adapt
Prefer JSON-LD in a <script type="application/ld+json"> tag over microdata sprinkled through the HTML. JSON-LD is easier to review in a pull request, and you are less likely to break it when a designer edits the header.
Start with the most specific type Google documents for the business. LocalBusiness is the safe parent. A dental office can use Dentist, a shop can use Store, a trades firm can use HomeAndConstructionBusiness or a narrower subtype. Do not pick a type because it βsounds stronger.β If no subtype fits, stay with LocalBusiness.
Here is a compact example for a fictional service-area plumber. The @id values let the organization, the website, and the owner node point at each other without duplicating the telephone number in three disconnected objects.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "HomeAndConstructionBusiness",
"@id": "https://example-plumbing.example/#business",
"name": "Example Plumbing",
"url": "https://example-plumbing.example/",
"telephone": "+1-407-555-0142",
"email": "[email protected]",
"image": "https://example-plumbing.example/images/van.jpg",
"priceRange": "$$",
"areaServed": [
{ "@type": "City", "name": "Orlando" },
{ "@type": "AdministrativeArea", "name": "Orange County" }
],
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "07:30",
"closes": "17:00"
}
],
"sameAs": [
"https://www.facebook.com/exampleplumbing",
"https://maps.google.com/?cid=0000000000"
]
}
]
}
A storefront business should add a PostalAddress under address, with streetAddress, addressLocality, addressRegion, postalCode, and addressCountry. If the business is service-area only and hides the street address on the public profile, do not invent a public street in JSON-LD to look more complete. Use areaServed for the cities or counties the crew actually covers, and keep that list short and true. Listing every city in a metro area will not create a branch office.
telephone should be the public customer number in international format, not a tracking number that differs from the number on the contact page. sameAs should list official profiles you control, not directories you have not claimed. If you do not have a given profile, omit it.
Common implementation mistakes:
-
Two generators, two stories. A theme plugin emits one
LocalBusinessblock, a marketing plugin emits another, and the footer still shows a retired phone number. View source and keep a single graph. - Markup that does not match the page. If the visible heading says βExample Plumbingβ and the JSON-LD says a different legal name, fix the source of truth first. Schema is not a place to try a keyword variation.
-
Coordinates for places you do not occupy. Do not drop a
GeoCoordinatespin on a city you merely hope to rank in. If you have a real premises, use the real lat/long. -
AggregateRatingyou did not earn on that page. Do not hard-code star ratings. If you later add review markup, it has to follow the current rich-result rules and represent reviews that are actually present. - Copy-pasted opening hours. A holiday exception that exists on the Google Business Profile but not in JSON-LD (or on the contact page) is a contradiction. Update the facts in one place, then regenerate the script.
When the script is in a staging build, validate it before you merge. I use three checks, in this order:
- The Schema.org Validator at validator.schema.org, to confirm the JSON is valid and the types exist.
- Googleβs Rich Results Test at search.google.com/test/rich-results, to see whether the page is eligible for any documented rich result. A valid
LocalBusinessgraph can still produce βnot eligible,β which is fine; you are aiming for accurate entity data, not a decorative badge. - A visual diff of the rendered homepage and contact page against the JSON-LD: name, phone, hours, and area served must match.
If the site is a static or server-rendered app, generate the JSON from the same configuration file that prints the footer. That is the whole trick. In a Next.js or similar project I keep a business.json module and serialize it into the layout, so a hours change cannot land in the footer and miss the graph.
Local SEO for small businesses also depends on work that schema cannot do: service pages that name the offer clearly, a contact path that works on a phone, and public listings that repeat the same facts. Markup is the consistency layer, not a substitute for those pages. If you want a non-code walkthrough of the basic parts of local search visibility, that explanation is written for owners who will approve the facts you are about to encode.
Ship the script, run the three checks, and then leave it alone until a fact changes. A quiet, accurate LocalBusiness block is more useful than a quarterly rewrite of the same JSON.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.