09 / Make the business understandable
Build Local Pages for Real Locations and Real Decisions
This check helps a business decide when a location page deserves to exist and how to make it locally useful instead of producing duplicated city-name variants.

Local is more than a city token. A local page earns its URL by serving a distinct place, audience, operation, question, proof set or next action.
Scenario
Illustrative scenario · not a client result
A site launches forty city pages by replacing the place name in the same template. None explains whether the business actually operates there, who answers, what services differ, or what local evidence exists.
Evidence Lab
Collect the minimum evidence needed to answer this check. Keep the date, location, platform, route, role and source beside the observation.
- 01
Legitimate locations/service areas and operating responsibility.
- 02
Distinct page job for the location.
- 03
Location-specific name/address/phone/hours/service facts where applicable.
- 04
Useful local context: service availability, operational notes, proof, FAQs, directions/landmarks when genuinely helpful.
- 05
Relationship to core service pages and canonical/structured-data strategy.
A manual search, profile screenshot, rank-grid point, website event and booked job are different kinds of evidence. Keep their definitions separate.
Principle
A local page earns its URL by serving a distinct place, audience, operation, question, proof set or next action.
The job is to help customers discover, understand, choose and contact the real business, then verify what happened. This field test is workflow guidance; it is not a claim that each action is a ranking factor.
Rebuild
- Write the page job before the title tag.
- Create location pages for real operational/local distinctions, not every city token.
- Keep services connected to core service destinations; local pages answer where and local context.
- Use unique factual proof where available; do not fabricate local projects or testimonials.
- Make contact, hours, service area and next action explicit.
- Use internal links to reveal the site hierarchy.
Before editing a Business Profile, confirm the current platform requirements in the source trail. Keep the proposed change within the business’s actual operation and your account authority.
Field Test
The test
Remove the city name from the page. If the remaining content could describe every other city without meaningful changes, the page probably lacks a distinct local job.
Record the result honestly
Verified pass · Verified fail · Partial · Not tested · Blocked · Not applicable
A pass needs reproducible evidence. If access, a definition or permission is missing, name the gap and the next person who can resolve it. Missing evidence never becomes a pass by default.
Use by role
- Owner
- Confirms real operational coverage.
- Content / SEO
- Writes unique location value and avoids doorway-page patterns.
- Designer
- Keeps local facts and action easy to scan.
- Engineer
- Implements canonical, structured data, routing and internal links consistently.
Checklist
Use these as reading markers. They stay in this page session and are not submitted, saved as an audit or sent to analytics.
Ask Your AI
Give the agent your expected state, relevant business facts and safe evidence. Keep secrets and private customer data out. Start read-only; account and production changes require their own authorization.
Read the full prompt
You are conducting a bounded local-search investigation for CHECK 09: BUILD REAL LOCAL PAGES.
PAGE / BUSINESS JOB
This check helps a business decide when a location page deserves to exist and how to make it locally useful instead of producing duplicated city-name variants.
EXPECTED STATE
State what should be true for this business, location, market and platform before proposing changes.
EVIDENCE
Collect current, reproducible evidence. Tie it to date, location, query/service, platform/surface, page/profile, and source. Separate platform policy, observed behavior, inference, hypothesis and unknown.
SPECIFIC CHECK
Evaluate whether each proposed local page deserves its own URL. Define its audience, local operation, services, unique facts/proof, FAQs, relationship to service pages, contact/action, internal links, canonical and structured-data needs. Merge or reject pages that differ only by city-name substitution. Never invent local evidence.
MORTEN A. GIRAFFE WORKING RULES
- Evidence before advice.
- The map is not the market.
- A local ranking observation is not a universal rank.
- A profile field is not permission to keyword-stuff.
- A review is customer evidence, not copy the business controls.
- A location is real because the operation is real.
- A local page earns its URL by serving a distinct audience, place, question, proof set or next action.
- Visibility is diagnostic; qualified demand and business outcomes determine whether the work mattered.
- Correlation is not clean attribution.
- Do not invent proof, rankings, review counts, customer data, testimonials, revenue, eligibility or platform behavior.
SAFETY / AUTHORITY
Begin read-only unless the user explicitly authorizes changes. Do not alter Business Profiles, listings, domains, analytics, production pages, review requests, customer records or tracking without the required account authority and a rollback/verification plan.
OUTPUT
For each finding report:
ID · market/location · platform/route · severity · confidence · classification · expected vs actual · evidence · root cause or labeled hypothesis · smallest recommendation · acceptance/retest · remaining unknowns.
Finish with the three highest-value next actions, not a generic SEO task list.
Reference:
https://www.mortenagiraffe.com/journal/local-search-field-guideVerify the result
- Did the evidence come from the intended business, location and market?
- Is every current platform claim tied to an official source?
- Are the recommendation, observed facts and untested hypothesis distinguishable?
- Are profile and website facts still consistent?
- Did the correction introduce an eligibility, review-policy, accessibility, routing or measurement problem?
- What observation would disprove the recommendation?
Questions
Is this check a ranking factor?
Not every useful practice is a ranking factor. This check addresses the accuracy and usefulness of the business’s public representation. Use the cited platform documentation for platform claims and the field test for practical verification.
Does passing guarantee visibility?
No. Local search is competitive and contextual. Google describes relevance, distance and how well-known the business is; a checklist cannot guarantee a position. Google’s local-ranking guidance explains that framework.
What if part of the test is unavailable?
Record Not tested, Blocked or Partial and state the exact access, evidence or authorization needed. Continue independent checks that can be completed safely.
Source trail
Platform sources checked . Recheck policy before acting. Illustrations and scenarios teach the method; they do not show measured client outcomes.
- Google Search: LocalBusiness structured dataFirst-party platform documentation
- Morten: Technical SEO Field GuideMorten workflow and interpretation