Morten A. Giraffe

08 / Make the business understandable

Run an Ethical Review System

This check helps a business build a repeatable review-request and response workflow that produces genuine customer feedback without incentives, gating, quotas or scripted sentiment.

A neutral review request process ending with the customer choosing the words and rating.
Ask everyone. Let customers speak. Reviews are customer evidence, not copy the business gets to author.

Scenario

Illustrative scenario · not a client result

A team asks only happy customers, offers a discount, and tells staff to make sure reviewers mention a target service and city. The review count rises, but the process is biased, policy-risky and less trustworthy.

Evidence Lab

Collect the minimum evidence needed to answer this check. Keep the date, location, platform, route, role and source beside the observation.

  1. 01

    Current review-request triggers and audiences.

  2. 02

    Google review link/QR workflow where used.

  3. 03

    Any incentives, gating, staff quotas, scripts or requested wording.

  4. 04

    Response ownership and response time.

  5. 05

    Distribution of recent reviews and recurring service themes—not a magic volume threshold.

A manual search, profile screenshot, rank-grid point, website event and booked job are different kinds of evidence. Keep their definitions separate.

Principle

Reviews are customer evidence, not copy the business gets to author.

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

  1. Trigger the request from a real completed customer interaction.
  2. Use a neutral request and direct path; let the customer choose whether and what to write.
  3. Do not offer incentives, selectively ask only positive customers, set review quotas, or request particular rating/content.
  4. Respond to reviews as a customer-service practice, not as keyword insertion.
  5. Use recurring review themes as qualitative feedback for operations and content.

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

Read the review-request message and workflow. A customer should be free to leave any genuine rating/content—or none—without reward, penalty, screening or pressure.

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
Defines legitimate trigger and accountability.
Customer service
Sends neutral request and responds appropriately.
SEO / marketing
Monitors trends without scripting customer speech.
Legal / compliance
Reviews regulated-industry considerations where relevant.

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 08: RUN AN ETHICAL REVIEW SYSTEM.

PAGE / BUSINESS JOB
This check helps a business build a repeatable review-request and response workflow that produces genuine customer feedback without incentives, gating, quotas or scripted sentiment.

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 the review system against current platform policy. Identify trigger, audience, request wording, review link/QR path, incentives, gating, staff quotas, requested content, response workflow and qualitative feedback loop. Propose a neutral system that asks genuine customers without controlling sentiment. Do not invent review targets.

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-guide

Download this check’s prompt · Text

Verify 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.