Content brief for Google reviews , How to collect entity rich reviews

Content brief for Google reviews — How to collect entity-rich reviews (no keyword stuffing)

Many businesses still tell customers to “write keyword-rich reviews.” That approach tries to game search signals and produces robotic, low-value text — and it’s easy to cross the line into manipulative behavior. Google and real customers reward useful, contextual, authentic reviews: the things people actually experienced (dish names, staff who helped, wait time, price, parking).

This guide is a ready-to-use content brief you can drop into WhatsApp, Email, receipts, staff scripts or your checkout flow. It quietly nudges customers to add entity-level detail without scripting exact keywords — the safest, most effective way to make reviews both search-relevant and genuinely helpful.

Table of Contents

Add a header to begin generating the table of contents

What is this content brief?

A content brief for reviews is three things at once:

A tiny set of prompts you give customers to help them remember and describe what actually happened.
Microcopy (one-line nudges) staff or receipts can use to increase review quality.
A delivery plan — when and how to send the prompt so it’s convenient and natural.

Goal (semantic triple): business — provides — tiny prompts → customer — writes — contextual review → profile — benefits — relevance & trust.

Why this matters

Search engines and users prefer specifics, not repeated buzzwords.
Entity mentions (dish, staff, product, room type) improve relevance for local queries without “keyword stuffing.”
Short, guided prompts increase response rates and lift review usefulness — which can translate to more clicks, calls, and bookings.

Principles: what to ask and what not to ask

Ask for:

Experience (what they ate/bought/used).
Entities (dish name, staff name, room number, product model).
Attributes (wait time, portion size, cleanliness, parking).
Outcome (fixed problem, enjoyed date night, product works as described).

Don’t:

Provide a scripted sentence to copy word-for-word.
Ask exclusively for 5★ reviews.
Offer discounts or rewards in exchange for positive reviews.
Tell customers which keywords to include.

Micro-prompt structure -use this every time

Warm opener — 1 line (personal & thankful).
Two short nudges — 1 line total (what to mention).
One-tap CTA — review link or QR (single action).

Example:
“Thanks for dining with us, Priya! If you enjoyed your meal, could you say which dish stood out and whether the service or ambience worked for you? Tap here to share: [review link]”

Transformations — turn “Awesome food” into an entity-rich review

Customer wrote: “Awesome food.”
Gentle follow-up prompt to send:
“Great to hear — could you tell us which dish you loved and whether the server or the ambience stood out?”

Upgraded reviews customers will naturally write:

Short (2–3 lines): “Loved the butter chicken — big portion and rich flavor. Our server, Priya, was friendly.”
Medium: “Butter chicken and garlic naan were top-notch. Priya recommended the saffron rice. Cozy seating and easy street parking.”
Long: “Visited Friday — butter chicken (perfectly spiced) and paneer tikka (generous portions). Priya was very helpful and our mains arrived in about 15 minutes. Fair prices and a relaxed date-night vibe.”

Why it works: the prompts encourage naming the dish, staff, wait time, price, and ambience — all entities and attributes useful to both users and search engines.

Ready-to-use WhatsApp messages (copy & paste)

Use personalization tokens: [Name], [Date], [Item], [Staff]. Always include the one-tap review link.

Quick nudge (high response):
“Hi [Name] — thanks for visiting [Business]! If you enjoyed it, could you say which dish/item you’d recommend and how the service was? [review link]”
Guided (with starters):
“Hi [Name]! Hope you enjoyed your visit on [Date]. Quick favor — could you say: 1) which dish/product you’d recommend, 2) who helped you (name if you remember), and 3) anything about wait/parking/price? Example starters: ‘I loved…’, ‘Our server…’. [review link]”
Receipt/QR microcopy:
“Loved it? Tell others — which dish and team member made your visit great? Scan to leave a quick review.”

Staff script — one line to say at checkout

“Thanks so much — if you liked anything special tonight, we’d really appreciate a quick review. I can send a link if that’s okay?”
(Then send the WhatsApp micro-prompt.)

Why this works: verbal ask + instant follow-up message greatly improves completion rates.

Sector templates (one-line nudges to copy)

Restaurant: “Which dish would you recommend and how was the service?”
Hotel: “Which room/feature stood out and how was check-in/parking?”
Salon/Spa: “Who was your stylist and are you happy with the result?”
Clinic: “Which treatment did you get and did the doctor explain things clearly?”
Auto Repair: “What service was done, and did the estimate/time meet expectations?”
E-commerce: “Which product arrived, and how was packaging/delivery?”

Delivery timing & UX tips

Restaurants: 12–48 hours after dining (customers have time to digest).
E-commerce: 24–72 hours after delivery.
Hotels: 24–48 hours after checkout.
Salons: same day or next day.
Clinics/Services: 48–72 hours after service.
Use the GBP “share review” link or a QR code on receipts to reduce friction.
Personalize messages (name, date, item) — lifts response rates.
Provide star rating UI only within the review form; don’t ask for a specific star count in your prompt.

Microcopy bank (short starters — give these, not full scripts)

“I loved the ___ because ___.”
“Our server, ___, did ___.”
“It took about ___ minutes for ___.”
“Parking was ___ (easy/limited/valet).”
“Price/value felt ___ (fair/expensive/great).”

These starters lower friction while preserving authenticity.

Measuring success (quality metrics)

Track the following to measure quality, not just volume:

% of reviews that mention at least one entity (dish, staff, product).
Average review length (words).
% of reviews that mention service/price/parking (attributes).
Star distribution (healthy spread, watch for unnatural concentration of 5★ only).
Conversion lift (page views → calls/reservations after adding entity-rich reviews).

Set a baseline and A/B test different prompts (e.g., “Quick nudge” vs “Guided”) for open rates and completion.

Compliance & risk checklist (must-include)

Do not offer discounts, freebies, or financial incentives for positive reviews.
Do not ask for only 5★ reviews. Ask for honest feedback.
If you plan to republish a review in marketing, get explicit consent.
Monitor suspicious patterns (burst of similar reviews, same IPs) and correct course.
Train staff to avoid suggesting exact wording; encourage natural details instead.

Implementation playbook — 7-step rollout

Pick your channels: WhatsApp + receipt QR to start.
Create the one-tap review link and a short QR receipt card.
Load 3 personalized WhatsApp templates into your messaging tool.
Train staff on the one-line checkout script and how to send the message.
A/B test two micro-prompts for 4 weeks.
Measure entity mentions, avg length, star spread.
Iterate: tweak timing, wording, and channel mix based on results.

Quick examples (restaurant)

Bad: “Please leave a 5★ review with keywords ‘best restaurant’.”
Good micro-prompt: “Hi Ravi — glad you joined us! Which dish would you recommend and how was the service? [link]”
Resulting review: “The butter chicken was outstanding — rich sauce and big portions. Our server, Anita, recommended the house naan; it was perfect. Street parking nearby, prices fair.”

Closing — one paragraph to use on staff training sheets

“Ask for the experience, not the rating. Use a warm one-line ask, send a one-tap link, and include two short nudges (dish/people + wait/price/ambience). Short starters are fine — they make reviews more helpful for other customers and more relevant to search without ever asking people to ‘stuff’ keywords.”

12 message WhatsApp copy bank

here’s a ready-to-drop 12-message WhatsApp copy bank for collecting entity-rich Google reviews. Each message includes personalization tokens you can replace in your system: [Name] [Business] [Date] [Item] [Staff] [ReviewLink]. Below each message I’ve added a one-line when to send suggestion so your ops team knows timing.

Use these as-is or swap the sector tokens (dish → product → room → service). Don’t give full scripted sentences to copy—these are nudges (starters + CTA) that encourage customers to mention real entities and attributes.

Quick nudge — ultra short
“Hi [Name] — thanks for visiting [Business]! If you enjoyed it, could you say which dish/item you’d recommend and how the service was? [ReviewLink]”
When: 12–24h after visit/delivery.
Guided with example starters
“Hi [Name]! Hope you loved your visit on [Date]. Quick favor — could you tell us: 1) what you ordered/used, 2) who helped you (name if you remember), and 3) anything about wait/price/parking? Example: ‘I loved…’, ‘Our server…’. [ReviewLink]”
When: 24–48h after service.
Receipt/QR microcopy (short for printed receipts or SMS)
“Loved it? Tell others — which dish/team member made your visit great? Scan to leave a quick review. [QR or short link]”
When: handed at checkout or printed on bill.
Staff-sent at checkout (verbal + message)
“Thanks for coming, [Name]! If you’d like, I can send a quick link — a couple lines about what you enjoyed (dish, server, wait time) helps others. Want the link? [Yes/No button]”
When: immediate at checkout; staff offers to send.
Friendly reminder (no pressure)
“Hi [Name], hope you’re well — just checking if you had 30s to share which [dish/item] stood out and how the service was. Helps other guests a lot: [ReviewLink]”
When: 48–72h after first message if no response.
Post-delivery (e-commerce)
“Hi [Name]! Hope [Item] arrived safely. Could you tell us if packaging/condition/delivery time met expectations? A short note helps others decide: [ReviewLink]”
When: 24–72h after delivery.
Hotel follow-up (post-checkout)
“Hi [Name], thanks for staying at [Business]! Could you mention your room type, anything the staff did that stood out, and how check-in/parking was? [ReviewLink]”
When: 24–48h after checkout.
Salon / Spa next-day nudge
“Hi [Name] — glad you visited yesterday! Who was your stylist and are you happy with the result? A quick review (1–2 lines) really helps them: [ReviewLink]”
When: same day or next day.
Clinic / service follow-up
“Hi [Name], thanks for trusting [Business]. If you can spare a moment, please say which treatment you had, how Dr. [Staff] explained it, and whether booking/wait time was smooth: [ReviewLink]”
When: 48–72h after appointment.
Private help first (diversion for unhappy customers)
“We’re sorry to hear that. Could you message us directly so we can resolve this quickly? If you prefer, share details here and we’ll respond within 24h — otherwise, if you’d still like to review publicly after we help, here’s the link: [ReviewLink]”
When: immediately after seeing a negative signal (reply, low rating, complaint).
Consent to republish (for marketing reuse)
“Thanks for your review — we’d love to share it on our website/socials. Can we have permission to repost your review (we’ll credit you by first name)? Reply ‘yes’ if that’s ok.”
When: after a positive review is posted or when replying to the review publicly.
VIP / detailed ask (for loyal customers)
“Hi [Name], we really value your feedback. If you have time for a slightly longer review, could you mention the specific dish/product, who helped you, and any detail about timing/price/ambience that stood out? It really helps fellow customers: [ReviewLink]”
When: send to repeat customers or loyalty members.

Quick usage rules (one-liners)

Personalize token fields (name, date, item, staff) — personalization increases response rates.
Always include the one-tap [ReviewLink] or QR in the same message — single action = higher completion.
Avoid scripting full sentences customers should copy; give starters and examples instead.
Don’t offer incentives or request only 5★ reviews — ask for honest feedback and follow Google policy.

Checkout Staff Checklist — Collecting Entity‑Rich Google Reviews

Purpose: Quick, 1‑page script & workflow staff can follow at checkout to increase the quality of Google Business Profile reviews (entities, attributes — not keywords).

1. One‑line staff script (what to SAY)

Smile, make eye contact. Say: “Thanks so much — if you loved something tonight, I can send a quick link to leave a short review. Would that be OK?”
If customer says Yes ➜ send message immediately from the messaging tool (see message bank below).
If customer says No ➜ say: “No worries — thanks for visiting!” and do not push.

2. What to SEND (1‑tap WhatsApp message — copy/paste)

Personalize tokens: [Name] [Business] [Date] [Item] [Staff] [ReviewLink]

Quick nudge (default):

Hi [Name] — thanks for visiting [Business]! If you enjoyed it, could you say which dish/item you’d recommend and how the service was? [ReviewLink]

If they remembered a staff name (use Staff token):

Hi [Name] — thanks again! Could you tell us which dish you loved and whether [Staff] helped you well? A quick line helps others: [ReviewLink]

Receipt/QR option (if customer prefers paper):

Loved it? Tell others — which dish/team member made your visit great? Scan to leave a quick review. [QR]

3. Timing rules (when to send)

At checkout (preferred): offer verbally and send link immediately if OK. This has the highest conversion.
If customer opts out at checkout but gave consent later: send within 12–48 hours for restaurants, 24–72 hours for deliveries and hotels.
Do not send more than one follow-up if no response.

4. Quick copy starters to suggest (give these — don’t write full text)

“I loved the ___ because ___.”
“Our server, ___, did ___.”
“It took about ___ minutes for ___.”
“Parking was ___ (easy/limited/valet).”

Use these only if customer asks for help starting their review.

5. Compliance & tone rules (must follow)

Do not ask for a specific star rating (e.g., “Please give 5★”).
Do not offer discounts, freebies or incentives in exchange for reviews.
Ask for honest feedback only.
If you want to reuse the review in marketing, ask for permission after the review is posted.

6. Handling unhappy customers (diversion script)

If customer signals dissatisfaction at checkout or in replies:

Say: “I’m sorry to hear that — can I get a manager to help right now?”
Offer private resolution: “Could you message us here with a few details or I’ll have someone call within 24 hours?”
Only after issue is resolved, you may politely ask if they’d consider updating their review.

7. Quick QA checklist before sending the message

✅ Is the message personalized (Name, Date or Item)?
✅ Did you include the one‑tap [ReviewLink] or QR?
✅ Did you avoid scripted full-sentences for the customer to copy?
✅ Did you avoid offering incentives or asking for a 5★ rating?
✅ If using staff name, confirm correct spelling.

Content brief for Google reviews — How to collect entity-rich reviews (no keyword stuffing)