Schema markup is a small block of code that states your business facts, such as name, address, phone number and hours, in a format search engines can read without guessing. For a local business, the place to start is LocalBusiness markup on your main business page, tested with Google’s Rich Results Test.
What is schema markup?
Schema markup is also called structured data. Google’s introduction to structured data describes it as a standardized format for providing information about a page and classifying its content.
The vocabulary comes from schema.org, a shared catalog of types such as LocalBusiness, Organization and Article. Each type has properties, such as name, address and telephone.
Google supports three formats and recommends JSON-LD in most cases. JSON-LD is a single block of code in the page, separate from the text your visitors read, which makes it the easiest to add and maintain.
Two points to keep in mind:
- Structured data can make a page eligible for richer search listings. Google describes this as something markup can enable, so plan on eligibility and not a certainty.
- For how Google Search behaves, Google says to treat its own documentation as the final word, not schema.org.
Which type should a local business use?
Schema.org defines LocalBusiness as a particular physical business or branch of an organization. It is a more specific kind of Organization, so it carries the same basic properties and adds local ones such as opening hours.
Google’s LocalBusiness documentation says, “Use the most specific LocalBusiness sub-type possible.” Schema.org offers many. Under its home and construction category alone it lists Electrician, GeneralContractor, HVACBusiness, HousePainter, Locksmith, MovingCompany, Plumber and RoofingContractor. Dentist is another listed subtype.
If your company does not serve customers at a physical location, Organization markup is the general choice. Google suggests placing it on your home page or a single page that describes your organization, such as an About page. You do not need it on every page.
Which properties does Google require and recommend?
| Type | Required by Google | Recommended by Google (selected) |
|---|---|---|
| LocalBusiness | name, address | telephone, url, openingHoursSpecification, geo, priceRange, department, menu and servesCuisine for food businesses |
| Organization | None | name, url, logo, description, address, telephone, email, sameAs, contactPoint, legalName |
| Article or BlogPosting | None | headline, image, datePublished, dateModified, author with name and url |
A few details from Google’s documentation that are easy to miss:
- Address. Include as many address fields as you can.
- Telephone. Include the country code and area code.
- Map coordinates. Latitude and longitude need at least five decimal places.
- Price range. The value must be shorter than 100 characters.
- Hours. A business open 24 hours uses 00:00 to 23:59.
- Logo. For Organization markup, the image should be at least 112 by 112 pixels and reachable by Google’s crawler.
- Reviews. Google lists the review and aggregateRating properties for LocalBusiness as only for sites that capture reviews about other local businesses.
What does LocalBusiness markup look like?
Here is a short JSON-LD example for a fictional plumbing company. Every detail is invented for illustration.
{
"@context": "https://schema.org",
"@type": "Plumber",
"name": "Example Plumbing Co.",
"url": "https://www.example.com/",
"telephone": "+1-555-555-0100",
"priceRange": "$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Example Street",
"addressLocality": "Springfield",
"addressRegion": "IL",
"postalCode": "62701",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 39.80172,
"longitude": -89.64371
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "08:00",
"closes": "17:00"
}
]
}
Reading it from top to bottom:
- @context and @type say the vocabulary is schema.org and the business is a Plumber, a specific LocalBusiness subtype.
- name and address are the two required properties. The address is its own object with separate fields.
- url and telephone point to the page for this location and its main customer phone number, with country code.
- geo gives the map coordinates to five decimal places.
- openingHoursSpecification lists the days and the opening and closing times in 24-hour format.
On a real page, this block sits inside a script tag with the type application/ld+json. Most website platforms and SEO plugins add that wrapper for you. Do not leave comments inside the JSON. Google’s help page says to remove them before publishing.
The most important rule is accuracy. The name, address, phone number and hours in your markup should match what a visitor sees on the page and what appears on your Google Business Profile.
What about FAQ and article markup?
FAQ markup
This is the area that has changed most. Google’s documentation changelog records that the FAQ rich result feature stopped appearing in Google Search on May 7, 2026. Google then removed the FAQ rich result documentation on June 15, 2026.
So there is no longer any eligibility rule to meet. FAQ markup does not produce an expanded listing on Google for any site. Many older guides still describe FAQ rich results as available, so check the date on anything you read.
A visible questions and answers section is still worth having for your readers. Microsoft also suggests question and answer formats as one way to help AI systems reference content accurately, which we cover in how to get your business cited in AI search results.
Article markup
If you publish a blog, Google’s Article documentation covers the Article, NewsArticle and BlogPosting types. It lists no required properties. It recommends the headline, images, publish and modified dates, and the author. For authors, list each one separately, and put only the name in the name field.
How do you test your markup?
Google’s own steps for LocalBusiness markup are a good routine for any type:
- Add the required properties, then the recommended ones that apply to you.
- Run the code through the Rich Results Test. You can enter a page address or paste a code snippet. Fix any errors it reports. Warnings are optional to fix, though fixing them can improve quality.
- Publish the page, then use the URL Inspection tool in Search Console to see how Google views it. Make sure the page is not blocked by robots.txt, a noindex tag or a login.
- Allow several days for Google to recrawl. A sitemap helps Google pick up later changes.
One limit to know: the Rich Results Test only checks the rich result types Google supports. It will not tell you whether every schema.org property on your page is valid.
Markup is easy to lose during a site rebuild, so add it to your website redesign checklist.
Does schema markup help with AI search?
Google’s answer is measured. Its guide to generative AI features says structured data is not required for generative AI search and that there is no special markup to add. It also says to keep using structured data as part of your overall search work.
In practical terms, add markup because it states your business facts clearly and supports richer search listings, not because it unlocks AI citations.
The short version
Start with LocalBusiness markup in JSON-LD, using the most specific business type that fits. Google requires only your name and address, and recommends phone, website, hours and coordinates. FAQ rich results ended on Google in May 2026, so do not count on them. Test with the Rich Results Test, and keep every detail matched to your visible page.



