Start here: Schema is code that describes page content. Check the facts and the live implementation before treating a successful test as complete.
LOOK AT THE EXAMPLE
Use URL to test a published page, or Code while preparing changes. A valid test checks supported markup; it does not prove the facts are correct or promise a search display. Check the visible page and the deployed code as well.
Open the Rich Results TestHere’s what schema is, why it matters for local SEO, and how to use it to get discovered, without getting lost in the technical web world.
What is schema markup?
When it comes to local SEO, schema markup is a type of code you add to your website to help search engines understand what your content is about.
The code gives search engines an explicit description of facts on the page, such as the business name, telephone and hours. Those facts still need to be accurate.
Schema can describe visible business facts such as your business type, location, services and opening hours. Use only properties that accurately match the page. Structured data can help search engines interpret information and, for supported eligible types, consider a page for enhanced search features. Valid markup does not guarantee a display, a ranking improvement or a change to your Google Business Profile.
FROM OUR RESEARCH
Check what your website says in its code.
We inspect the implementation before calling it a missing piece. Then we check that the business type, contact details and services in the markup agree with the information customers can see. The goal is a clear, accurate description of your real business.
US home-services prospect analysis. Checked-page snapshots from July 9 to November 13, 2026. Google structured-data guidance · Research method
How to read this example
Why schema markup matters for local SEO
Structured data describes information on the page in a machine-readable form. Use it to represent accurate, visible content, not as a ranking guarantee or a substitute for useful pages. Check Google’s current documentation for each supported search feature. Adding markup does not by itself create a Business Profile, secure a Map Pack position, or guarantee a featured answer.
- Business Profile eligibility is separate
- Map Pack rankings are not guaranteed
- Featured answers are not guaranteed
- Check each feature’s current requirements
When structured data is applicable
Use applicable markup that accurately describes visible content. A page can rank without structured data, and successful validation does not guarantee an enhanced result. Google’s structured data guidance explains eligibility and content requirements.
Common schema types for local businesses
There are hundreds of schema types, but these are the ones that matter most for local service businesses:
LocalBusiness schema
Tells Google: You’re a local company serving a specific area.
Acts as a core schema for local business websites that you can use to mark up your business name, address, phone number, hours, and services. See LocalBusiness schema options.
Service schema
Tells Google: What you do (for example, “HVAC repair,” “Dental cleaning,” “Roof inspections”).
Use this on service pages to help Google understand your offerings more clearly. See Service schema.
Review and AggregateRating schema
Review and AggregateRating describe review information that matches visible content and meets the relevant eligibility rules. Google does not show self-serving review snippets for LocalBusiness or Organization pages reviewing themselves, including reviews displayed through a third-party widget. Do not expect stars on your own business page. Read Google’s review snippet guidelines.
Event and Offer schema
Tells Google: You’re offering something now, like a discount, sale, or seasonal promotion.
Offer markup can describe an actual offer where it fits the page and the relevant schema requirements. It does not publish a campaign or guarantee a promotional display in Google. See Offer schema.
FAQPage schema
FAQPage describes a visible list of questions and answers using Schema.org vocabulary. Google stopped showing FAQ rich results in May 2026. Keep useful FAQs for your readers, and be wary of anyone selling FAQ markup as a way to get that retired feature back. Google’s documentation updates record this change.
A copyable local business schema example
This LocalBusiness example uses Local Howl’s business details. Choose the most specific current subtype that accurately describes your business, then replace the example values with verified facts visible on your page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Local Howl",
"legalName": "Local Howl Agency, LLC",
"url": "https://www.localhowl.com/",
"telephone": "+1-856-280-9614",
"email": "info@localhowl.com",
"address": {
"@type": "PostalAddress",
"streetAddress": "10465 Manchester Rd, Suite 540",
"addressLocality": "Kirkwood",
"addressRegion": "MO",
"postalCode": "63122",
"addressCountry": "US"
},
"hasMap": "https://www.google.com/maps?cid=9171390678750910385"
}
</script>- Pick the most specific type. Use the LocalBusiness subtype that matches the business, such as RoofingContractor, Dentist or HVACBusiness. Our builds for Coastal Roofworks, Miami Smile Dental and Air Control Services use exactly those.
- Match your profile and your page. The name, address and phone should read the same in the markup, on the page and on your Google Business Profile.
- Add hours only when they agree. Include openingHoursSpecification when the hours on your page and on your Google Business Profile match. Fix the mismatch first.
- Leave out what you can’t show. No rating you don’t display, no service you don’t offer, no address you hide from customers.
- Validate the live page. Test the published URL, not a draft, and test again after every template change.
Best practices for schema markup (without getting too nerdy)
Validate markup before release and after relevant content changes. Google’s Rich Results Test checks supported Google search features; the Schema.org validator checks vocabulary and syntax more broadly. A valid result in either tool does not guarantee indexing, higher rankings or an enhanced search appearance. Keep markup consistent with the visible page.
Use Google’s Markup Helper tool
You can tag content visually without writing code. Try the Structured Data Markup Helper.
Keep schema updated
If your hours or service list change, update your schema too.
Stick to what’s accurate
Don’t add fake reviews or offers. Google may penalize misleading schema.
Use JSON-LD format (Google’s favorite)
It’s easier to manage, less prone to break, and recommended by Google.
Validate your schema
After adding markup, test your page using Google’s Rich Results Test: test your schema.
Where schema fits in your website work
Structured data supports an accurate website; it does not replace useful pages or business-profile work. Prioritize clear service information, consistent business details across relevant listings, genuine customer feedback, relevant editorial references, and accurate profile details with useful customer updates. Evaluate schema eligibility alongside those separate tasks, without treating markup or repeated keywords as a shortcut to rankings.
How Local Howl uses schema strategically
Our schema markup services review existing markup against visible business facts, identify applicable types, and document recommended corrections. Implementation and ongoing maintenance depend on the agreed scope and website access. In our own builds that has meant replacing a schema block that misspelled its own telephone property and giving each of six clinic locations its own markup.
We can show you which business details the markup contains and how to check them when those details change.
And if you want to go deep? Here’s the full list of schema types: browse all schema options.
Schema doesn’t have to be complicated
A generator or suitable plugin can help you prepare the code. You still need verified business facts, website access and a live-page test. If a template or plugin conflict needs development work, give your developer the affected pages and test results.
Check your business markup from page to live test
Inspect one important page
Start with your home page or a location page. Run the URL through a structured-data testing tool and note the business types and details it detects. Our research found no LocalBusiness or recognized subtype on the checked pages for 113 of 313 domains. That is a reason to investigate those pages, not proof that every page on those websites lacks markup. A plugin may already supply the code you need.
Match every business fact
Compare the detected name, phone, address and hours with the visible page and your current business records. In this guide, the Local Howl example includes its name, telephone and Kirkwood address. If you adapt the example, replace its values with your own verified details. Choose the most specific business type that accurately fits. Leave out facts you cannot support, and investigate conflicting blocks before adding another one.
Add the code through the right place
Find out whether your theme, SEO plugin or developer controls the existing markup. Update that source so the correction survives future page edits. On a business with several locations, inspect each location page and make sure its details describe that location. Keep a copy of the previous code and the pages affected. This makes a mistaken phone number or template change easier to trace and correct.
Test the published result
Use the Rich Results Test for Google-supported search features and the Schema Markup Validator for broader vocabulary checks. Test the live URL after publishing, then read the detected values yourself. A test can accept correctly formatted but outdated hours. Save the result and check again when business details or templates change. Google’s LocalBusiness guidance explains supported properties and eligibility; validation does not guarantee a rich result.
What it actually takes to do this yourself
You’ll need verified business details, access to the code and a way to test the live output.
- Tools
- A schema generator, Google’s testing tools and Search Console.
- Access
- The ability to edit your site’s code or tag manager, and to see what plugins already add.
- Know-how
- Reading JSON-LD. Choosing the right type and properties. Knowing Google’s structured data rules.
- Upkeep
- Every change to hours, services, locations or the site itself means the markup needs checking.
Where owners get stuck
- Syntax errors that prevent the markup from being read.
- A plugin and a pasted snippet describing the same business differently.
- Valid markup that still contains outdated business details.
- Adding code without checking which pages and templates output it.
How Local Howl can help
Your program sets the scope. We’ll agree on who handles each task and how we’ll report it.
DO IT YOURSELF
You can inspect a page, verify the business facts and use a suitable plugin or generator to prepare the markup. If you have website access, make a controlled change and test the published URL. Ask your developer to help when the same template controls many pages or several plugins produce conflicting code.
- Learn the vocabulary
- Pick the right business type
- Write the JSON-LD
- Add it to the right pages
- Test and fix
- Keep it in sync with the business
We can check the existing markup and prepare the code or implementation your plan includes.
WITH LOCAL HOWL
Generating a block of code takes minutes. Checking existing markup, resolving conflicts and getting the right version onto the live site needs website access and testing. We can prepare the code for your developer or implement it through the agreed scope, then check the published pages. Business details still need updating when they change.
- We inspect existing markup and choose types that fit your business
- We prepare code for your developer or implement it through your agreed plan
- We test the live pages after installation
- We explain the fixes and the details that need checking when the business changes
Guidance checked November 18, 2026. Read the source: