Schema, Explained · a three part series for people who know a little code
- Part 1: Organization, WebSite, WebPage, and BreadcrumbList
- Part 2: LocalBusiness, Service, Article, and local search (you are here)
- Part 3: FAQ, Person, Event, Recipe, and reviews
LocalBusiness is Organization plus a physical presence: address, phone, hours, and service area. Use the most specific subtype that fits (such as ProfessionalService, Dentist, or Restaurant), and make every detail match your Google Business Profile and website footer exactly. Service describes one thing you offer, on that service's page, and points back to the business as its provider. Article (or BlogPosting) describes a piece of content: its headline, dates, image, author, and publisher, with the author as a real Person. For local search, schema does not replace your Google Business Profile, reviews, or links, but it confirms the same facts in a format machines read without guessing.
What is LocalBusiness schema, and when should you use it?
LocalBusiness is a more specific kind of Organization. It says everything Organization says (name, logo, website, profiles) and adds the details that matter to someone nearby: a street address, a phone number, opening hours, a map location, and the area you serve.
Use it if customers can visit you, or if you serve a defined local area. A law firm, a dental office, a restaurant, a salon, a plumber, and a local consultancy all qualify. A software company with no local customers is better described as a plain Organization.
Because LocalBusiness is an Organization, you do not need both for the same company. Describe it once, as the most specific type that fits, with one @id. Part 1 explained why that matters, and why I am fixing my own homepage, which currently describes Double Atari both ways.
Which LocalBusiness type should you choose?
Schema.org has dozens of LocalBusiness subtypes. Using a specific one tells machines what kind of business you are before they read a word of your copy. A few common ones:
| Business | Type to use |
|---|---|
| Consultancy, agency, design studio, accounting, legal | ProfessionalService, or LegalService / AccountingService where they fit |
| Dentist, doctor, clinic, therapist | Dentist, Physician, MedicalClinic, or MedicalBusiness |
| Restaurant, cafe, bar, bakery | Restaurant, CafeOrCoffeeShop, BarOrPub, Bakery |
| Shop | Store, or a specific one such as ClothingStore or BookStore |
| Trades and home services | HomeAndConstructionBusiness, Plumber, Electrician, HVACBusiness |
| Salon, spa, gym | BeautySalon, DaySpa, HealthClub |
If nothing fits, plain LocalBusiness is fine. Do not pick a wrong subtype just to be specific. A design studio is not a Store.
How do you check a LocalBusiness block?
Here is a cleaned-up version of what a local consultancy's LocalBusiness block should look like, based on the one on the Double Atari homepage.
{
"@context": "https://schema.org",
"@type": "ProfessionalService", // a specific LocalBusiness subtype
"@id": "https://www.double-atari.com/#localbusiness", // the same name tag used everywhere
"name": "Double Atari", // identical to Google Business Profile
"url": "https://www.double-atari.com/",
"logo": "https://www.double-atari.com/assets/double-atari-logo.webp",
"image": "https://www.double-atari.com/assets/social-share.png",
"telephone": "+1-612-817-4302", // same number as the footer, international format
"email": "andrew@double-atari.com",
"address": {
"@type": "PostalAddress",
"addressLocality": "Minneapolis",
"addressRegion": "MN",
"postalCode": "55407",
"addressCountry": "US"
},
"geo": { "@type": "GeoCoordinates", "latitude": 44.9778, "longitude": -93.265 },
"areaServed": ["Minneapolis", "St. Paul", "Twin Cities", "Minnesota"],
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "09:00", // 24-hour time
"closes": "17:00"
}],
"priceRange": "$$",
"sameAs": ["https://www.linkedin.com/company/double-atari-digital-marketing-experts/"],
"founder": { "@id": "https://www.double-atari.com/about#person" }
}The // notes are added for this article. Real JSON-LD does not allow comments, so never paste them into a live page.
| Check | What good looks like |
|---|---|
| name, address, phone | Character-for-character the same as your Google Business Profile and site footer. "St." versus "Street" matters less than you fear, but a different suite number or an old phone number matters a lot. |
| address | Broken into parts (street, city, region, postal code, country), not one long string |
| geo | Coordinates that actually land on the business. Paste them into a map to check. |
| openingHoursSpecification | Matches the hours on the site and on Google. Uses 24-hour times. Seasonal or holiday hours are kept current, or left out. |
| areaServed | Places you really serve, not a list of every suburb you would like to rank in |
| image and logo | Real files that open, ideally on your own domain |
| priceRange | Optional. If used, keep it honest and short, such as "$$" or "$100-$500". |
One more thing you may find in a LocalBusiness block: reviews and ratings. Google does not show review stars for reviews a business publishes about itself on its own site, which it calls self-serving reviews. So adding your testimonials to LocalBusiness schema will not earn stars in search. If you keep them, make sure the details are accurate. Part 3 covers when review markup does count.
How does schema help local search?
It helps to be clear about what schema does and does not do for local search, because it is often oversold.
What drives local rankings is mostly your Google Business Profile (categories, completeness, reviews, photos), how close you are to the searcher, how relevant your site is to the search, and your reputation around the web: links, mentions, and consistent listings in directories.
What schema adds is confirmation. It states your name, address, phone, hours, and service area on your own website in a format machines read without interpretation. When those facts match your Google Business Profile and your directory listings, every source agrees. When they do not, you have created doubt about basic facts, which is the opposite of what you want.
So treat LocalBusiness schema as part of your consistency work, not a ranking trick. The best order of operations for a local business is: get the Google Business Profile complete and accurate, make the website footer and contact page match it, then make the schema match both. That sequence is a big part of what I do for Minneapolis SEO clients.
What about multiple locations or service-area businesses?
Multiple locations. Give each location its own page and its own LocalBusiness block with its own @id, address, phone, and hours. Then connect them to the brand with parentOrganization.
{
"@context": "https://schema.org",
"@type": "Dentist",
"@id": "https://www.example.com/locations/st-paul/#location", // unique per location
"name": "Example Dental, St. Paul",
"url": "https://www.example.com/locations/st-paul/", // the location page, not the homepage
"telephone": "+1-651-555-0100", // this location's own number
"address": { "@type": "PostalAddress", "streetAddress": "123 Example Ave",
"addressLocality": "St. Paul", "addressRegion": "MN",
"postalCode": "55102", "addressCountry": "US" },
"parentOrganization": { "@id": "https://www.example.com/#organization" } // the brand
}The // notes are added for this article. Real JSON-LD does not allow comments, so never paste them into a live page.
The mistake to look for: every location page reusing the homepage block, so ten pages all claim to be the head office.
Service-area businesses, such as a plumber or a consultant who goes to clients, may not want a street address shown publicly. Google Business Profile lets you hide it. In schema, describe where you work with areaServed, and include only the address parts you are comfortable publishing, such as city and postal code. Whatever you include should match what you show publicly.
How do you check Service schema?
Service schema describes one thing you offer. It belongs on that service's own page, not all on the homepage. Google does not show a special search feature for Service, so its value is clarity: it tells machines exactly what this page sells, where, and who provides it.
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://www.double-atari.com/services/website-audits/#service",
"name": "Website Audits", // the service name used on the page
"serviceType": "Website audit", // a plain category label
"description": "Website audits covering technical SEO, content, CMS structure, analytics, and performance, delivered with a prioritized action plan.",
"url": "https://www.double-atari.com/services/website-audits/", // this page
"provider": { "@id": "https://www.double-atari.com/#localbusiness" }, // points to the business
"areaServed": [
{ "@type": "City", "name": "Minneapolis" },
{ "@type": "Country", "name": "United States" }
]
}Close to the real Service block on the Double Atari website audits page. The // notes are added for this article. Real JSON-LD does not allow comments, so never paste them into a live page.
| Check | What good looks like |
|---|---|
| One service per page | The page and its schema are about the same single service |
| name and description | Taken from the page copy, not invented for the schema |
| provider | Points to the business by @id instead of describing it again |
| url | This service page, not the homepage |
| offers (optional) | Only if the page shows a price. Never put a price in schema that is not on the page. |
A homepage with a list of every service in one big Service block is a common pattern. It is not wrong, but the stronger setup is a short Service block on each service page, each pointing to the same provider.
How do you check Article and BlogPosting schema?
Article schema describes a piece of content: a blog post, a news story, a guide. Use BlogPosting for blog posts and NewsArticle for news. This is the type where the details of who matter most, because a lot of trust is judged by authorship.
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Schema Markup Explained, Part 2", // matches the H1 closely
"description": "How to read and check LocalBusiness, Service, and Article schema.",
"url": "https://www.double-atari.com/blog/schema-markup-explained-localbusiness-service-article/",
"mainEntityOfPage": "https://www.double-atari.com/blog/schema-markup-explained-localbusiness-service-article/",
"image": "https://www.double-atari.com/assets/social-share.png", // a real, large image that represents the post
"datePublished": "2026-11-15", // the date shown on the page
"dateModified": "2026-11-15", // changes only when the content really changes
"author": {
"@type": "Person",
"@id": "https://www.double-atari.com/about#person", // a real person with a real page
"name": "Andrew Charon",
"url": "https://www.double-atari.com/about"
},
"publisher": { "@id": "https://www.double-atari.com/#localbusiness" }
}This is close to the schema on this post. The // notes are added for this article. Real JSON-LD does not allow comments, so never paste them into a live page.
| Check | What good looks like |
|---|---|
| headline | The same as, or very close to, the visible title |
| author | A Person with a name and a URL to a real bio page, not "Admin" or the company name |
| datePublished and dateModified | Match the dates shown on the page. dateModified does not update every time the site rebuilds. |
| image | A real image that represents the article |
| publisher | Points to the Organization by @id |
The red flag I see most often in content teams: dateModified set to "today" automatically on every page, every day. It is meant to tell machines when the content changed. If it always says today, it stops meaning anything.
How should these types connect?
Put parts 1 and 2 together and the whole site describes one connected picture:
| This | Points to | Using |
|---|---|---|
| WebSite | The business | publisher |
| Every WebPage | The WebSite | isPartOf |
| The business (LocalBusiness) | The founder (Person) | founder |
| Each Service | The business | provider |
| Each location | The brand | parentOrganization |
| Each article | The author and the business | author, publisher |
If you sketch those arrows for your own site and every one of them uses the same @id for the same thing, your schema is in better shape than most. If you find yourself drawing two boxes for the same company, that is the fix.
The local schema review
| Question | If the answer is no |
|---|---|
| Is the business described once, as the most specific LocalBusiness type that fits? | Merge Organization and LocalBusiness blocks into one with one @id. |
| Do name, address, phone, and hours match Google Business Profile and the footer exactly? | Fix the source of truth first, then the schema. |
| Do the geo coordinates land on the business on a map? | Replace them with the correct ones. |
| Does each location have its own page, block, and @id? | Stop reusing the head office block on location pages. |
| Does each service page have its own Service block pointing to the provider? | Add one per page, using the page copy. |
| Does every article name a real Person as author, with a bio page? | Replace generic authors and add the Person @id. |
| Do article dates match the visible dates? | Stop auto-updating dateModified. |
Part 3 covers the content-specific types: FAQ, Person, Event, Recipe, and reviews, including which ones Google still turns into search features and which ones it quietly stopped showing.
LocalBusiness, Service, and Article schema FAQ
What is LocalBusiness schema?
LocalBusiness schema is a type of Organization markup for businesses with a physical location or a defined local service area. It adds details such as street address, phone number, opening hours, map coordinates, and area served, so search engines can read those facts directly.
Should I use Organization or LocalBusiness schema?
Use one, not both, for the same business. If customers visit you or you serve a defined local area, use the most specific LocalBusiness subtype that fits, such as ProfessionalService or Dentist. Otherwise use Organization.
Does LocalBusiness schema improve local rankings?
Not on its own. Local rankings depend mostly on your Google Business Profile, proximity, relevance, and reputation. LocalBusiness schema helps by confirming your name, address, phone, and hours in a machine-readable format that matches your other listings.
Where should Service schema go?
On each service's own page, describing that single service, with a provider property that points to the business by its @id. Only include a price if the page shows that price.
What makes Article schema trustworthy?
A real Person as the author with a link to a bio page, a publisher that points to the organization, a headline that matches the page, and published and modified dates that match the dates shown on the page.
Explore related Double Atari resources: schema explained, part 1, Minneapolis SEO, local SEO for therapists, and GEO and AEO / AI search.