For a local business, the page-side work for AI answers is making the basic facts unambiguous: one name, one address, one phone number, the hours, and the area served, stated the same way in visible text and in structured data on every page that mentions them. An answer engine asked “is the bakery on Elm Street open on Sunday?” needs those facts to be present, consistent, and extractable. Your site is one place it can find them, and it is the one you fully control.
This post is a checklist for that half. It covers consistency of name, address, and phone (NAP), LocalBusiness markup, hours, service-area pages, and reviews. It deliberately leaves out the off-page factors: listings on other sites, review volume on third-party platforms, and the Business Profile itself, which is managed outside your website. It sits under Citability and entity signals: a GEO guide.
Where does the website fit next to the Business Profile?
The website and the Business Profile are separate sources, and Google’s documentation treats them separately. A claimed Business Profile is how “your local business information” shows “in Google Maps and Google knowledge panel,” and it is managed through the listing, not through markup on your site (Google Search Central: establish your business details). Google’s guidance on AI features recommends keeping Business Profile information up to date alongside ordinary on-site practices (Google Search Central: AI features and your website).
So the website’s job is not to replace the listing. It is to state the same facts, in more depth, in a form that any crawler can read, and to never contradict the listing. Every item below follows from that.
1. Is the name, address, and phone identical everywhere on the site?
The name, address, and phone number should be written identically on every page that shows them, and identically to the Business Profile. Small differences are the common failure: “Suite 200” on the contact page and “#200” in the footer, an old phone number in a PDF menu, a trading name on one page and the legal name on another.
By hand. Open the homepage footer, the contact page, the about page, and one location page. Copy the name, address, and phone from each into a spreadsheet, one row per page, and compare. Then check view-source: for each page to confirm the details are text in the HTML, not an image or an embedded map with no text beside it.
Across a site. In a crawler with custom extraction, add rules for the visible phone number, such as the text of //a[starts-with(@href,'tel:')], and for the address block, by whatever selector your template uses. Export, and use a pivot table to count distinct values. More than one distinct phone number for one location is a finding. Add a rule for the telephone and address values inside the page’s JSON-LD and compare those columns with the visible ones.
Choose one canonical format, write it down, and use it in the template rather than retyping it on each page.
2. Does each location have its own LocalBusiness markup?
Each physical location should be described by its own LocalBusiness entity, using the most specific subtype available. Google’s documentation for local business structured data lists name and address as required, recommends aggregateRating, department, geo, menu, openingHoursSpecification, priceRange, review, servesCuisine, telephone, and url, and says to “use the most specific LocalBusiness sub-type possible,” such as Restaurant or HealthClub. It also says to define each location as its own LocalBusiness (Google Search Central: local business structured data).
A minimal example for one location of a fictional bakery:
{
"@context": "https://schema.org",
"@type": "Bakery",
"name": "Elm Street Bakery",
"url": "https://example.com/locations/elm-street/",
"telephone": "+1-555-010-0199",
"address": {
"@type": "PostalAddress",
"streetAddress": "120 Elm Street",
"addressLocality": "Springfield",
"addressRegion": "IL",
"postalCode": "62701",
"addressCountry": "US"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "07:00",
"closes": "18:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Sunday",
"opens": "00:00",
"closes": "00:00"
}
]
}
LocalBusiness is a subtype of both Organization and Place on schema.org (schema.org/LocalBusiness), so it can carry the organisation-level properties too, including sameAs links to the business’s profiles elsewhere. Organization schema and sameAs covers how those links make an entity legible, and the schema stack that matters for AEO and GEO covers where local markup sits among the other types.
Validate the markup after every template change. Validating structured data covers the difference between markup that is missing, partial, and invalid, and how to find each across a site.
3. Are the hours stated in text and in markup, and do they match?
Hours should appear as visible text on the location page and in openingHoursSpecification, and the two must agree. Google’s structured data policies require that markup be “a true representation of the page content” and say “don’t mark up content that is not visible to readers of the page” (Google Search Central: structured data policies). Hours that exist only in JSON-LD, or only in an image of a sign, fail one side of that.
Google’s local business documentation gives three conventions worth following exactly. A day closed all day sets both opens and closes to "00:00", as in the example above. Open 24 hours is "00:00" to "23:59". Seasonal hours use validFrom and validThrough.
Write the hours as a short table or list near the top of the location page, not inside an accordion that loads on click, and add a one-sentence answer for the questions people actually ask: “Elm Street Bakery is open 7am to 6pm Monday to Friday and closed on Sundays.” How to write an answer block covers the format. Update the page the same day the hours change. A stale holiday notice is the most common way a local page contradicts its own listing.
4. Do service-area pages describe a real service, not a city name?
A business that travels to customers, such as a plumber or a cleaning service, often publishes one page per town it serves. Those pages are useful only when each says something specific to that area. Google’s spam policies list, as an example of doorway abuse, “having multiple domain names or pages targeted at specific regions or cities that funnel users to one page” (Google Search Central: spam policies). A page that swaps the town name into the same paragraph is exactly that, and after boilerplate is stripped it is also thin; thin content in an extraction world covers the consolidation choice.
The alternative is one page per service that states the area it covers, in text and in markup. schema.org’s areaServed property, defined as “the geographic area where a service or offered item is provided,” is available on Organization and Service, so it applies to LocalBusiness too (schema.org/areaServed). List the towns or postal areas in the visible text as well.
Keep a separate area page only when you have something specific to say about that area: a local office, different pricing, different response times, area-specific regulations. Link those pages from the service page with anchors that name the area and the service; internal linking for retrieval covers the cluster structure.
5. Is the reviews policy honest?
Reviews on your own site are allowed, and the markup rules for them are strict. Google’s review snippet guidelines say that if the entity being reviewed “controls the reviews about itself,” its pages that use LocalBusiness or any other Organization structured data “are ineligible for star review feature.” The same guidelines require that marked-up reviews be “readily available to users from the marked-up page” and be about “a specific item, not about a category or a list of items” (Google Search Central: review snippet).
The practical policy for a local business site:
- Show testimonials as visible text if they help visitors, attributed and dated.
- Do not add
aggregateRatingorreviewmarkup to your ownLocalBusinessentity to chase stars. Under the rule above, a business publishing reviews of itself is not eligible. - Never mark up a rating that is not shown on the page, and never import a rating from another platform into your own markup.
Contact, about, and the trust surfaces nobody audits covers the other trust signals a local site should show: a real address, a working contact route, and who runs the business.
The checklist
| # | Check | How to verify |
|---|---|---|
| 1 | Name, address, phone identical on every page and in markup | Spreadsheet of extracted values, one distinct value per location |
| 2 | Same details as the Business Profile | Compare by hand against the listing |
| 3 | One LocalBusiness entity per location, most specific subtype | Read the JSON-LD, validate it |
| 4 | Required name and address present; telephone, url, hours included | Structured data validator |
| 5 | Hours visible as text and matching openingHoursSpecification | Read the page; compare to markup |
| 6 | Closed days, 24-hour days, seasonal hours use the documented conventions | Read the markup |
| 7 | Service-area pages each say something specific, or are consolidated | Read the main content with boilerplate removed |
| 8 | areaServed and a visible list of areas on service pages | Read the page and markup |
| 9 | No self-serving review markup; testimonials visible and attributed | Search the JSON-LD for aggregateRating and review |
| 10 | NAP and hours are text in the HTML, not images | view-source: |
GEOBee covers a smaller part of this list than it might seem. It detects and validates a fixed set of structured-data types, listed in its docs, and LocalBusiness is not one of them, so validate local markup with a structured data validator. Its GEO lens scores entity clarity, from Organization or Person schema with sameAs links, and trust, which includes a visible way to make contact (the three lenses). It does not compare your site with your Business Profile, and the consistency checks above remain a spreadsheet job.
What the checklist does and doesn’t cover
Passing every item means your site states the business’s facts consistently, in text and in markup, without contradicting itself or its listing. That is verifiable, and it removes one reason an answer engine might report the wrong hours or the wrong phone number.
It does not decide whether an assistant recommends the business. Proximity, listings, third-party reviews, and the engine’s own judgement all sit off the page, and none of them are measured here.
To check entity, trust, and contact signals across every page of a multi-location site, download GEOBee. The 7-day trial includes every feature.