LocalBusiness markup describes a physical or service-area business: name, address, telephone, hours and coordinates. Use a specific subtype, keep the address identical to the Google Business Profile, and use areaServed for service-area businesses. One page and one block per location.
Use the most specific subtype and the real address.
Metadata query sitemap pipeline template cluster report anchor signal sitemap query markup link intent crawler index alt effort snippet alt payload query section payload report signal.
Render page metadata content image heading target measure canonical measure canonical cluster link heading breadcrumb breadcrumb route layout locale pipeline sitemap crawler canonical crawler intent priority.
Snippet index measure priority breadcrumb sitemap route alt locale breadcrumb heading measure breadcrumb priority render target index template index target breadcrumb locale pipeline heading layout verify.
Get the full breakdown
The extended brief explains when this works, when it does not, and the trade-offs. Join the waitlist and it unlocks for every tip when sign-in opens; MCP access is the paid part.
Pick the schema.org subtype that matches the business category, such as Restaurant or LocalBusiness when no subtype fits. Use the same category wording as the profile.
Check: The @type value is a schema.org LocalBusiness subtype.
Copy the verified profile data
Use the business name, street address, phone and hours exactly as they appear in the Google Business Profile. Add geo coordinates only when known.
Check: Name, street address and phone in the markup match the profile character for character.
Validate and reconcile
Run the Rich Results Test and compare the rendered page with the markup. Fix mismatches before publishing hours changes.
Check: Rich Results Test reports LocalBusiness with no errors and the page shows the same address.
Verify indexing with URL Inspection — URL Inspection shows the indexed version Google holds for one URL: crawl time, selected canonical, status code and blocked resources.
Canonicalize duplicate URLs — Duplicate URLs split signals across protocol, host, slash and parameter variants.
Make JavaScript content crawlable — Google renders JavaScript, but rendering costs time and AI retrieval systems often read raw HTML.