17 / Keep it commercial and durable
Treat Each Location as a Real Operation
This check helps a multi-location or service-area business represent each legitimate operation accurately across profiles, pages, phones, hours, staffing and service responsibility.

No pretend offices. A location deserves separate representation because the real operation is separate—not because another city keyword exists.
Scenario
Illustrative scenario · not a client result
A service business creates virtual offices across a metro area, duplicate profiles, thin city pages and forwarding numbers. The footprint looks large until platform policy, customers or support systems expose the mismatch.
Evidence Lab
Collect the minimum evidence needed to answer this check. Keep the date, location, platform, route, role and source beside the observation.
- 01
Real locations, staffing, customer-facing status and signage/eligibility where required.
- 02
Separate service areas and operational responsibility.
- 03
Location phone/URL/hours and routing.
- 04
Profile count, duplicates and ownership.
- 05
Location pages, schema and internal links.
- 06
Review and lead routing by location.
A manual search, profile screenshot, rank-grid point, website event and booked job are different kinds of evidence. Keep their definitions separate.
Principle
A location deserves separate representation because the real operation is separate—not because another city keyword exists.
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
- Create separate profiles only for locations/operations that meet current platform eligibility.
- Do not use virtual offices or unstaffed locations to manufacture coverage.
- Keep same-brand naming/category consistency where platform policy requires it.
- Give each real location an accurate useful website destination.
- Route calls/leads/reviews to the correct operation where systems allow it.
- Document shared versus location-specific business facts.
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
For every profile/location page, answer: who staffs/serves it, what customers can do there, what phone/URL/hours apply, which market it serves, and why it is distinct.
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 / operations
- Proves the location is real and staffed/served as represented.
- Listings
- Maintains eligibility and duplicates.
- Web / engineering
- Implements location routes/schema/contact routing.
- Analytics / sales
- Separates leads and outcomes by location where practical.
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 17: TREAT EACH LOCATION AS REAL.
PAGE / BUSINESS JOB
This check helps a multi-location or service-area business represent each legitimate operation accurately across profiles, pages, phones, hours, staffing and service responsibility.
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
Audit multi-location representation. For each profile/location page verify real operation, eligibility, staffing/customer-facing status, service area, phone, URL, hours, category/name consistency, duplicates, website destination, schema, lead routing and reviews. Flag virtual/pretend locations and thin duplicate pages. Do not create coverage that the business cannot operationally support.
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 customer understanding, action or durable measurement. 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: represent your business accuratelyFirst-party platform documentation
- Google: Business Profile eligibility and ownershipFirst-party platform documentation
- Google: service-area and hybrid businessesFirst-party platform documentation
- Google Search: LocalBusiness structured dataFirst-party platform documentation