Collection that will not get you banned.

What review gating is, and why you will not ship it

Review gating is a flow that decides whether a visitor gets the public review links based on how happy they seem. A star screen that sends 5s to Google and 1s to a private form is the usual shape. A smileys-then-route page is the same shape. You will not ship it.

Platforms have banned businesses for this. The details differ by network and they change. You do not need a case citation to stay out of the design. If the public buttons are conditional, you are in the design. Conditional is the ban risk.

Marketers ship gates because the demo looks cleaner. The owner sees a rising Google number and does not see the unhappy people who never found Yelp. That demo is also the complaint packet. A competitor, an ex-employee, or a customer who notices the fork will take screenshots. Screenshots travel.

This product’s collect page has no hide-the-public-buttons branch. That is a lock on the Autonomy Matrix, not a missing toggle. Echo can draft replies and run campaigns. It cannot grow a gate later because a client asked nicely. If you work outside the product, copy the lock. A custom page you built in a weekend can still get them banned.

Climbo and Birdeye go deeper as reputation suites. If reputation is the only job you sell, those tools may be the better pillar. The reason this guide exists is the lock, plus the rest of the loop. Depth is not a license to gate. If a tool offers a gate, you still do not turn it on.

How to put public buttons on every visitor’s screen

Put the public review buttons on the first screen of the collect page, above any private form, and do not ask for a star rating first. Google, and any other network you can actually honor, should be visible to a person who is angry, late, and on a phone.

Label the buttons with the network names. Review us on Google is clearer than share your experience, which is how gates disguise the fork. Clarity is polite. Disguise is the behavior platforms hate.

Show the same buttons to QR traffic, SMS traffic, email traffic, and walk-in traffic. If one channel gets a different page that happens to include a star filter, you have a gate with extra URLs. One page. One rule. Every visitor.

Do not pre-fill stars. Do not default to five. Do not use a URL that lands in the Google review composer with a five already selected if you are also filtering who gets that URL. Deep links that simply open the public compose window for everyone are a different object. The test is still whether anyone was denied the public path.

Test the page as a grumpy stranger. If you cannot see Google without smiling at a widget, tear the widget out. Echo’s collect page is built so that test passes. Your page should pass it in a browser you do not control.

How to run private recovery alongside, never instead

Run private recovery as a form on the same page, under the public buttons, labeled as a way to talk to the shop if they prefer. Prefer is the word. Require is a gate.

The form can ask what happened, a phone number, and consent to be contacted. Consent cannot arrive pre-checked. That is the same Forms rule this product uses for SMS. Bundled marketing opt-in is how a recovery form becomes a junk list.

Someone has to read the form. A recovery inbox nobody opens is a prop. Staff it or do not offer it. SLA clocks belong here more than they belong on your outbound sequence. A same-day call after a private complaint is the job. A weekly digest is how small problems become one-star essays.

Do not promise that private recovery will stay private if the customer also posts. They can do both. Your page told them they could. Getting angry at a person who used the public button you displayed is how owners make the second review worse.

Never build a behind-the-form Google button that appears only after a high score. That is the gate with a handshake. Alongside means simultaneous, not sequential after a filter.

How to ask for a review without steering stars

Ask for a review by reminding them of the visit and handing them the public links. If you have a minute, here is our collect page. You can use Google or talk to us on the form. That is an ask. If we earned five stars, please say so on Google is steering.

In-person scripts drift toward steering because staff want to be kind. Write the script on a card by the register and keep stars out of it. We would love a review if you have a second. The page is on the receipt. Staff who add the five-star sentence are trying to help and are also the compliance incident.

Email and SMS asks must be consented and boring. SMS only to first-party contacts who checked a box that was not already checked. Email from a domain the shop controls, with an unsubscribe. A blast to a bought list asking for Google love is a different sin stacked on the first.

Do not write the review for them and ask them to paste it. That is not collection. That is manufacturing. You can give a blank box on your page. You cannot send three sentences and a request to copy them onto Google.

Incentives are a policy maze per network. If you cannot cite the current rule for that network, do not buy reviews with gift cards. A thank-you that happens after a review and was not advertised as a trade is a conversation with a lawyer, not with this guide. When unsure, skip the incentive. The page still works.

What you can claim on Google versus Yelp and Tripadvisor

Claim only the networks you can actually request, monitor, and, if you say so, reply on. Google is the usual first public button. Facebook is often second. Yelp and Tripadvisor in this product are monitor or assisted until live credentials are exercised. Your sales deck should match that sentence.

Assisted means a human may still have to post the reply in the native inbox. If you sell a unified inbox that posts everywhere, and Yelp is assisted, you have oversold. Echo can still draft. Drafting is not posting.

Do not tell an owner that Yelp is optional so they can ignore it on the collect page. If you include the button, it stays visible. If you cannot include it honestly, leave it off for everyone rather than hiding it from some. Off for everyone is a scope choice. Hidden for the unhappy is a gate.

Ranking inside a network is not a deliverable you can promise from collection volume. Collection changes the file. It does not print a rank. BrightLocal is better if the deliverable is a rank PDF. You are selling a page and a reply habit.

When a network changes a rule, change the page. Do not rely on a blog from 2019. This guide will not invent a statute. It will repeat the design that does not depend on a clever reading of last year’s FAQ: public buttons, no star filter, no bought language.

How to write a collect page the owner can defend

Write a collect page the owner can forward to a platform investigator without blushing. Every visitor sees the same public links. The private form is optional. No star filter. No instruction to only post if happy. No incentive that looks like a trade unless counsel signed off.

Use the shop’s name, address, and the real network destinations. A button that loops back into your lead form is not a review button. Owners get banned for tricks they did not understand. If you cannot explain the click path in one sentence, the path is too clever.

Put a dated note in the client folder: URL of the collect page, screenshot of the first screen, who approved it. When a staff member later adds a star gate because they saw a YouTube hack, you have the original to restore. Steward can hold that artifact. A shared folder can too.

Language on the page stays small. Thank you for visiting. You can review us on the public sites below. If you would rather tell us first, the form is here. Delete anything that sounds like a legal threat or a guilt trip. Guilt is a cousin of steering.

If you brand the page as the marketer, keep the shop louder than you. The portal rule is useful here too: plain language, no internal notes, no other clients’ metrics. A collect page that advertises your agency above the Google button teaches the customer the wrong destination.

What to do with a one-star week

In a one-star week you reply in public where you can, you fix the operational leak if there is one, and you do not turn on a gate. A gate after a bad week is the most obvious gate, and it is the one investigators understand immediately.

Draft replies that acknowledge the visit and invite a private path for details, without asking them to delete the review. Asking for deletion is another policy maze. When you cannot cite the current rule, do not ask. Echo can draft. Supervised means the owner or you hit post.

Do not reply from a cute brand voice that argues facts in public. Argue facts in the shop. Public can be short. We are sorry the wait got away from us on Friday. Please ask for Maya next time so we can make this right. If you do not know Maya exists, do not invent her.

A bad week is often a finding for a different module. No-show, no booking, a service-gap, a missed inbound call. Collection will not repair a phone that rings out. Sell the operational DEMO if you have one. Do not sell more ask emails to a shop that is failing in the chair.

Watchtower-style re-scans tell you the rating moved. Timing is a finding. It is not a reason to panic-install a filter. If you saved the shop as a prospect because the rating dropped, your first email can offer the collect page and the reply habit. It cannot offer to hide the next unhappy person.

How to run campaigns that still look like the same page

Run campaigns as reminders to people who already had a visit and already consented to hear from the shop, pointing at the same collect URL. New creative is allowed. A new fork is not.

Segment by visit date if you have first-party data. Do not segment by a private star you collected on a previous gate. If last year’s page gated, retire that list for public asks until you know how it was built. Old lists are how new pages get stained.

Cap the nag. One ask after a visit, one reminder, then stop. Sequences that ask weekly are how customers feel farmed. Stop-on-reply applies. If they say they already posted, you are done. If they say leave me alone, you are done and you record it.

Do not run a campaign that says we noticed you had a great visit unless you have a source that is not a guess. A completed appointment in their book is a source. A smile at the door is not a source. Invented delight is steering with extra adjectives.

Muse can put a monthly reminder on a content calendar. Publish stays gated. The owner should see the ask copy before it goes out. Reputation campaigns are still outbound mail. They inherit quiet hours, unsubscribe, and the verified domain. The collect page does not excuse a spam pattern.

How to brief a client so staff do not build a gate later

Brief the client with a one-page rule: every visitor sees the public buttons, no star screens, no scripts that mention five stars, no incentives you have not approved, no extra QR codes that point at a different page. Hang it where staff can see it.

Show them a competitor’s gated flow and say we will not do that. Concrete beats a policy PDF. Owners remember the screenshot. They do not remember a paragraph about platform guidelines.

Give staff a sentence they can say when a customer is angry at the counter. You can write that on Google if you want, and you can also tell us here so we can fix it today. Both doors. If staff are only trained on the second door, you have a verbal gate.

Schedule a quarterly look at the live collect URL. People add widgets. Widgets grow forks. A marketer who sold a clean page in March and never opened it again is how November gets a star filter from an app store install.

If they demand a gate, walk away from the reputation line or walk away from the account. You cannot keep them safe from a design they insist on. This product cannot grow the branch. Neither should you. There are other detectors to sell. There is not another honest collect page.

How to write the register script so staff do not steer stars

Write the register script so staff do not mention stars, because in-person scripts drift toward steering and staff who add the five-star sentence are trying to help and are also the compliance incident. We would love a review if you have a second. The page is on the receipt. That is an ask. If we earned five stars, please say so on Google is steering. Hang the card where staff can see it.

Give staff a sentence they can say when a customer is angry at the counter. You can write that on Google if you want, and you can also tell us here so we can fix it today. Both doors. If staff are only trained on the second door, you have a verbal gate. Show them a competitor's gated flow and say we will not do that. Concrete beats a policy PDF. Owners remember the screenshot.

Email and SMS asks must be consented and boring. SMS only to first-party contacts who checked a box that was not already checked. Email from a domain the shop controls, with an unsubscribe. A blast to a bought list asking for Google love is a different sin stacked on the first. Do not write the review for them and ask them to paste it. That is manufacturing.

Incentives are a policy maze per network. If you cannot cite the current rule for that network, do not buy reviews with gift cards. When unsure, skip the incentive. The page still works. You can run this script without Nerxus One. Echo's collect page is built so the grumpy-stranger test passes. Your page should pass it in a browser you do not control.

What to do with last year's gated list

Retire last year's gated list for public asks until you know how it was built, because old lists are how new pages get stained. If last year's page gated, segment by visit date only if you have first-party data you trust. Do not segment by a private star you collected on a previous gate. A new fork is not allowed. New creative is allowed. Campaigns still point at the same collect URL.

Cap the nag. One ask after a visit, one reminder, then stop. Sequences that ask weekly are how customers feel farmed. Stop-on-reply applies. If they say they already posted, you are done. If they say leave me alone, you are done and you record it. Do not run a campaign that says we noticed you had a great visit unless you have a source that is not a guess. A completed appointment in their book is a source. A smile at the door is not a source.

Muse can put a monthly reminder on a content calendar. Publish stays gated. The owner should see the ask copy before it goes out. Reputation campaigns are still outbound mail. They inherit quiet hours, unsubscribe, and the verified domain. The collect page does not excuse a spam pattern. If you keep Climbo as the reply desk, leftovers here are still yours to sell or to ignore. Do not gate in one place and claim you do not gate in the other.

Schedule a quarterly look at the live collect URL. People add widgets. Widgets grow forks. A marketer who sold a clean page in March and never opened it again is how November gets a star filter from an app store install. Send yourself through the QR as a stranger once a month. If a widget appeared, remove it. If a star screen appeared, take the page down until it is gone. Write the date you walked the QR on the record.

How QR codes stay the same page

QR codes stay the same page when every channel opens the same first screen with public buttons, because if one channel gets a different page that happens to include a star filter, you have a gate with extra URLs. One page. One rule. Every visitor. Show the same buttons to QR traffic, SMS traffic, email traffic, and walk-in traffic.

Label the buttons with the network names. Review us on Google is clearer than share your experience, which is how gates disguise the fork. Clarity is polite. Disguise is the behavior platforms hate. Put the public review buttons on the first screen, above any private form, and do not ask for a star rating first. Google, and any other network you can actually honor, should be visible to a person who is angry, late, and on a phone.

Do not pre-fill stars. Do not default to five. Do not use a URL that lands in the Google review composer with a five already selected if you are also filtering who gets that URL. Deep links that simply open the public compose window for everyone are a different object. The test is still whether anyone was denied the public path. Test the page as a grumpy stranger. If you cannot see Google without smiling at a widget, tear the widget out.

A QR on a receipt is not gating if it opens a page with public buttons for everyone. It is gating if the first screen asks how many stars and then hides the public path. Monthly is how ten clients do not grow ten gates. You can host this page in any host. Nerxus One is the version that cannot grow the gate and that sits next to Scout, Radar, and Steward. Useful if you buy. Required as a method either way.

What to keep when an investigator asks

Keep the collect URL, dated screenshots of the first screen, the staff script, the campaign copy, and the approval, because meaning well is not a log. If an investigator asks, you send those. You do not send a vibe that you meant well. Write a collect page the owner can forward to a platform investigator without blushing. Every visitor sees the same public links. The private form is optional. No star filter. No instruction to only post if happy.

Use the shop's name, address, and the real network destinations. A button that loops back into your lead form is not a review button. Owners get banned for tricks they did not understand. If you cannot explain the click path in one sentence, the path is too clever. Put a dated note in the client folder. Steward can hold that artifact. A shared folder can too.

Do not offer to flood the listing after a one-star. Volume you manufacture is as obvious as a gate. Organic asks to real customers are slow and they are the work. If an owner wants a miracle week, they want a different vendor, and that vendor is the ban story later. Medical, legal, and other sensitive verticals need quieter asks and a reviewer on any page that talks about care. This guide is not legal advice. It is a design.

If a vertical would tempt you to hide public links because reviews discuss health facts, get counsel. Do not improvise a fork. If they demand a gate, walk away from the reputation line or walk away from the account. You cannot keep them safe from a design they insist on. This product cannot grow the branch. Neither should you. There are other detectors to sell. There is not another honest collect page.

How a one-star week becomes an operational DEMO instead of more asks

A one-star week becomes an operational DEMO when the leak is a phone that rings out or a wait that got away, because collection will not repair the chair and more ask emails will make the second review worse. In a one-star week you reply in public where you can, you fix the operational leak if there is one, and you do not turn on a gate. A gate after a bad week is the most obvious gate, and it is the one investigators understand immediately.

Draft replies that acknowledge the visit and invite a private path for details, without asking them to delete the review. Asking for deletion is another policy maze. When you cannot cite the current rule, do not ask. Echo can draft. Supervised means the owner or you hit post. Do not reply from a cute brand voice that argues facts in public. Argue facts in the shop. Public can be short. If you do not know Maya exists, do not invent her.

Watchtower-style re-scans tell you the rating moved. Timing is a finding. It is not a reason to panic-install a filter. If you saved the shop as a prospect because the rating dropped, your first email can offer the collect page and the reply habit. It cannot offer to hide the next unhappy person. No-show, no booking, a service-gap, a missed inbound call: sell the operational DEMO if you have one.

Getting angry at a person who used the public button you displayed is how owners make the second review worse. They can do both. Your page told them they could. Never build a behind-the-form Google button that appears only after a high score. That is the gate with a handshake. Alongside means simultaneous, not sequential after a filter. Someone has to read the private form. A recovery inbox nobody opens is a prop. Staff it or do not offer it.

When Climbo stays the desk and this page stays the lock

Climbo stays the desk when the statement of work is reputation and you want a product that spends its depth there, and this page stays the lock because public buttons for every visitor is a design you can copy even if you never buy us. A reputation-first product can go deeper on request cadence, staff routing, listings consoles, and review-only reporting. That depth is their win. We will not invent a scoreboard that says otherwise.

Keep the deeper review desk if that desk already holds the book, and use Nerxus One for the hunt and the sample that starts a new account. Many firms already live this way. They request and reply in a specialist tool. They find new logos in a spreadsheet. The spreadsheet is the weak joint. Scout can search the vertical and metro. Radar can tell you which shops have a collect-page gap or a dropping rating. Forge can build the DEMO you send.

If they close, you can keep running reviews where the staff already knows the inbox, as long as the collect page you deploy still has no gating branch. The lock travels with what we publish. It does not rewrite another vendor's settings. The honest cost of two tools is two logins and a discipline about which system is the source of truth for the business row. We will not invent a live sync into Climbo.

Use both when the review desk is sacred and the pipeline is empty. Use one when you are ready for collection, the site, and the retainer to share a record. Do not use both as an excuse to gate in one place and claim you do not gate in the other. If a demo of Nerxus One starts on the collect page and never opens Scout, you were shown the wrong product. The collect page is the lock and the sample. The company is the loop.

What actually gets a client banned, and what to keep on file

A client gets banned when a platform decides the shop filtered, faked, bought, or harassed reviews. Your job is to keep your artifacts on the clean side of that line: same public buttons for everyone, no authored reviews, no star steering, no purchased volume, no reply that threatens a customer.

Keep on file the collect URL, dated screenshots, the staff script, the campaign copy, and the approval. If an investigator asks, you send those. You do not send a vibe that you meant well. Meaning well is not a log.

Do not offer to flood the listing after a one-star. Volume you manufacture is as obvious as a gate. Organic asks to real customers are slow and they are the work. If an owner wants a miracle week, they want a different vendor, and that vendor is the ban story later.

Medical, legal, and other sensitive verticals need quieter asks and a reviewer on any page that talks about care. This guide is not legal advice. It is a design. If a vertical would tempt you to hide public links because reviews discuss health facts, get counsel. Do not improvise a fork.

You can build this page in any host. Nerxus One is the version that cannot grow the gate and that sits next to Scout, Radar, and Steward. Useful if you buy. Required as a method either way. Collection that will not get you banned is a first screen with public buttons, a private door beside them, and a marketer who refuses the clever widget.

If you only change one file this week, change the collect URL’s first screen. Public buttons visible without a smile, a star, or a filter. Everything else in reputation work can wait until that screen is boring. Boring is the design that survives a complaint.

Send yourself through the QR as a stranger once a month. If a widget appeared, remove it. If a star screen appeared, take the page down until it is gone. Monthly is how ten clients do not grow ten gates. Write the date you walked the QR on the record.