How to get more Google reviews
Builds guide sites for a livingPublished July 22, 2026Last updated July 26, 202612 min read
- Merchants may not require or pressure a client to review while on the premises, which rules out the phone-in-hand ask at the dock.
- Requesting that specific content be included is prohibited, so the card telling clients what to mention has to go.
- Asking staff to solicit a certain number of reviews is named as prohibited, which kills quotas and leaderboards.
- Volume therefore comes from coverage: one fixed day a week, every client from that week, the same short message.
- Track asks sent rather than reviews received, because only the first is within your control.
A Gulf headboat that files its trip report late is not warned. It is automatically prohibited from harvesting or possessing the species, regardless of any further notification, until every delinquent report has been submitted and received.
That is what a reporting habit looks like when the consequence is built into the rule rather than into somebody's memory. A weekly deadline, an automatic penalty, and no dependence on anybody feeling like doing it. Almost every guide already lives inside a system like that, and almost none of them ask for reviews the same way. The asking is done when it occurs to them, to the clients they liked, in words that change every time, which is why the count stays where it is. Related material is grouped under the getting-booked hub.
| The habit | Position |
|---|---|
| Asking while the client is still on the boat | No pressure or requirement on the premises |
| Telling them what to mention | Requesting specific content is prohibited |
| Giving the crew a review target | Named as a prohibited request |
| Asking everyone, identically, afterwards | The version that survives the policy |
Why do most guides collect so few?
Because the ask depends on remembering, and remembering fails in July.
The typical arrangement is a mental note to ask when the day went well, executed at whatever point in the following week the guide happens to think of it.
In February that produces a review. In July it produces nothing, because July is the month with sixty trips and no spare evenings.
So the reviews arrive in clusters that correspond to the operator's free time rather than to the trips, and the profile ends up with eleven reviews for four seasons of work.
The fix is not more motivation. It is removing the decision from the loop entirely, which is what every functioning reporting system does.
What follows is the published constraint on how you may ask, and then a way of asking that runs without anybody deciding anything.
The strategy that sits above the mechanics is set out in the reviews strategy piece.
What are you not allowed to do while asking?
Three things, and they are aimed precisely at the convenient version.
Google's policy states that when soliciting reviews, merchants should not require or pressure users to leave ratings or write reviews while on the premises.
It states that they should not request that specific content be included.
And it names, as an example of prohibited conduct, merchants requesting that staff solicit a certain number of reviews.
Read those three together and the whole genre of on-the-dock review coaching is ruled out, along with the crew leaderboard and the printed card telling clients what to mention.
None of that is a technicality. It is the difference between a review that reflects an experience and one that reflects a request.
The policy is published on Google's contribution policy site.
What about asking on the boat?
Mentioning is not requiring, and the line is pressure.
The prohibition is on requiring or pressuring somebody to leave a rating or write a review while on the premises.
A boat at the dock at the end of a trip is unambiguously the premises, and the client is standing in front of somebody who has just spent eight hours being helpful to them.
That is precisely the imbalance the rule addresses, and it is why the phone-in-hand version, where the client is walked through leaving it on the spot, is the wrong version.
Saying that a follow-up will arrive and that a review helps a small operation is a statement of fact rather than a demand.
Handing somebody your phone with the review form already open is not.
The honest test is whether declining would be awkward, and on a dock with a guide watching, declining is always awkward.
The debrief that should be happening at that moment instead is described in the trip debrief piece.
Can you tell them what to mention?
No, and the prohibition is stated in exactly those terms.
The policy says merchants should not request that specific content be included in a review.
That rules out the card asking clients to mention the species, the boat name or the town, which is standard advice in a great many marketing guides.
It also rules out the softer version, which is the follow-up message suggesting what a helpful review would cover.
The reason is obvious once stated: a review shaped by the business is a description of the business's preferences rather than of the day.
What you can do is ask a genuine open question, which is what happened on the trip, and let the answer be whatever it is.
A review that mentions the species without being told to is worth more than one that mentions it because a card asked.
The wording that stays inside this line is worked out in the review scripts piece.
Can you set a target for the crew?
No, and it is named specifically.
Among the prohibited practices the policy lists merchants requesting that staff solicit a certain number of reviews.
Which kills the quota, the leaderboard and the bonus attached to a count, all of which appear in operations large enough to have staff.
For a one-boat operation this looks irrelevant until you notice it applies to you as your own crew.
A personal target of ten reviews a month produces exactly the behaviour the rule exists to prevent, which is chasing the number rather than sending the ask.
The measurable thing that is safe to track is whether the ask went out to every client, which is a process measure rather than an outcome one.
That distinction is the whole design of the system below.
What the resulting profile does for visibility is examined in the map pack piece.
What system already runs on a weekly deadline?
Your trip reporting, if you hold a federal for-hire permit.
Under the reef fish rules, the owner or operator of a charter vessel holding a charter vessel or headboat permit, and selected to report, must maintain a fishing record for each trip on forms provided, submitted weekly and postmarked no later than seven days after the end of each week.
Headboats submit electronically, through the Southeast Region Headboat Survey, at weekly intervals by 11:59 in the evening local time on the Sunday following a reporting week.
If no fishing activity occurred during a reporting week, a report saying so must still be submitted for that week.
That last provision is the interesting one, because it means the habit runs in quiet weeks too, which is exactly when a review-asking habit usually dies.
Confirm the current requirements and whether they apply to your own operation before relying on any of this, since these rules are amended and vary by fishery and region.
The section is published on eCFR at 50 CFR 622.26, and the forms are listed by NOAA Fisheries.
What does the delinquency rule teach?
That a consequence beats a reminder, every time.
The regulation states that a report not received within the specified time is delinquent.
A delinquent report automatically results in the owner and operator being prohibited from harvesting or possessing the species, regardless of any additional notification from the agency.
Authority to harvest returns only once all required and delinquent reports have been submitted and received.
Nobody chases you. Nobody sends a warning. The consequence is in the rule and it applies itself.
A review-asking habit that depends on somebody remembering has no such mechanism, which is precisely why it stops working in the busy months.
Borrowing the shape solves it: attach the ask to a weekly moment that already happens and cannot be skipped, and let the whole week's clients get it together.
The rule also allows for paper backup during catastrophic conditions declared by the regional administrator, which is a reminder that a good system has a defined failure mode rather than an undefined one.
What the weekly ask produces against the occasional one. Take an operation running a hundred and twenty trips a year. Under the remembered version the ask goes out perhaps twenty times, concentrated in the quiet months, and only to clients whose day went well. Under the weekly version every client receives the same message on the same day of the week, so a hundred and twenty asks go out and none of them require a decision. Even at an identical response rate the second version produces six times the volume, and unlike the first it is compliant, because nobody has been filtered by mood. The hundred and twenty trips and the twenty remembered asks are stated assumptions used to show the shape, not measurements, and no response rate, review rate or ranking effect is asserted here for any operation in any market.
When should the ask go out?
On a fixed day, to everybody from that week, off the boat.
Pick one day and one time, and let it be the same day you already do something administrative.
Everybody who fished with you that week gets the message on that day, including the trip that went badly and the trip where the client barely spoke.
Sending it after they have gone home removes the on-the-premises problem entirely, because nobody is standing in front of you when they decide.
It also gives them time to have told somebody about the day, which is when people are most able to describe it.
Weekly rather than daily matters, because a weekly rhythm survives a season and a daily one does not.
And a fixed day means the decision is never made, which is the entire point.
Which channel carries it is a separate question, answered in the text versus email piece.
What should the ask contain?
Four things, and none of them is a suggestion about content.
A specific reference to their day, so it reads as a message rather than a broadcast, which means the date and the water at minimum.
A plain statement that reviews help a small operation, which is true and is not pressure when they are at home.
A single link that lands them where the review is written, with no intermediate page.
And an explicit line saying an honest account is what is useful, whatever it says, which is the sentence that keeps you inside the policy and also happens to be true.
What it must not contain is any suggestion of what to mention, any offer of anything, or any indication that you will follow up again.
Short beats warm here, because a long message reads as a favour being requested rather than a door being held open.
The addresses that make this possible are gathered per the email capture piece.
How do you make it one click?
By doing the work once, in the off-season.
Find your profile's review link, save it somewhere you can reach in three seconds, and never look for it again.
Write the message once, with a gap for the date and the water, and store it beside the link.
Keep a running list of the week's clients as they book rather than reconstructing it on the day, since reconstruction is the step that fails.
Then the weekly task is pasting a stored message four or five times with two words changed, which takes under ten minutes.
Ten minutes a week for a season is under nine hours, and it is nine hours spent on the only marketing asset you cannot buy.
Anything more elaborate than that will be abandoned by August.
The profile the link points at is set up in the profile setup piece.
Which habits break the ask?
A list of seven. Three sit inside named prohibitions.
Asking on the dock with a phone in hand, which is pressure on the premises by any reading.
Telling clients what to mention, which the policy prohibits in terms.
Setting a target for crew, or for yourself, which is the practice the quota provision names.
Asking only the trips that went well, which is the selective solicitation prohibition from the same document.
Sending the ask months later, when the client has forgotten the date, the water and possibly the captain.
Sending a long message that apologises for asking, which converts a simple request into an obligation.
And measuring the count rather than whether the ask went out, which is the failure that produces all the others.
Handling the difficult ones once they arrive belongs to the piece on negative reviews.
What do operators not see coming?
The compliant version turns out to be the higher-volume one.
Most people assume the rules cost them reviews, and the arithmetic runs the other way, because asking everybody produces more asks than asking selectively ever did.
The second surprise is that the on-the-premises prohibition exists at all, since walking a client through it on the dock is the single most recommended tactic in this trade.
The third is the staff quota provision, which most operators have never read and which describes something they were about to build.
The fourth is how much of the difficulty is scheduling rather than persuasion, and scheduling is a solved problem.
The fifth is that the review from a client whose day was mediocre, written honestly, often reads better than the enthusiastic ones.
None of this requires charm, and charm was never the constraint.
Running the same discipline on the rival platforms gets weighed up in the piece on TripAdvisor and Yelp.
What if almost nobody responds?
Then you keep sending it, because the alternative is worse.
No published response rate exists for review requests in this trade, in any market, and none is asserted anywhere on this page.
What is knowable is your own: log how many asks went out and how many reviews arrived, for one full season, and you have a figure that is actually about you.
A low rate is not a reason to start filtering, since filtering is the prohibited move, and it is not a reason to start offering anything, for the same reason.
It is a reason to check the message is short, the link is direct, and the timing is within a week of the trip.
Beyond that, volume comes from the number of asks, and the number of asks is entirely within your control.
Which is a better position than most marketing problems leave you in.
Where the responses can legitimately be reused is covered in the testimonials piece.
How would you test your own ask?
Send it to yourself, then count for four weeks.
Send the message to your own phone or inbox and read it as a client would, which surfaces the apologetic sentence and the broken link immediately.
Click the link from a device not signed into your own account, since that is what a client is doing.
Then run four weeks and record two numbers: asks sent, and asks that should have been sent.
The gap between those two is the entire problem, and it is usually larger than anybody expects.
Close the gap before touching the wording, because a perfect message sent to a third of your clients loses to a plain one sent to all of them.
Only then look at the responses, and only across a full season.
The wider search context these sit inside is described in the local search piece.
The ask, in order
Same day, same words, everybody, nothing offered.
Pick one day a week and attach the ask to something you already do on that day.
Keep the week's client list as you go, so the list is never reconstructed from memory.
Send every one of them the same short message, referencing their date and their water.
Never ask on the boat, never suggest what to write, never offer anything, and never set a count as the target.
Use one direct link, saved somewhere you can reach without searching.
Include the line saying an honest account is what helps, and mean it.
Track asks sent rather than reviews received, because the first is yours to control and the second is not.
And let the quiet weeks be quiet, the same way the reporting rules require a report even when nothing happened.
No response or review-rate figures appear here. This page gives no request response rate, no review conversion rate, no star-average target and no visibility effect for a guiding operation anywhere. Research located nothing published along those lines, and inventing a plausible substitute was not an option taken. How any platform or agency enforces anything is likewise left uncharacterised. The contribution policy quoted here was read on 26 July 2026 and Google alters such documents silently; the reporting rules are federal regulations, subject to amendment and varying by fishery and region, so check what actually binds your own vessel. Nothing here is legal advice.
How this was checked. The solicitation rules are quoted from the Maps user generated content policy, prohibited and restricted content, at support.google.com/contributionpolicy/answer/7400114, read in full on 26 July 2026. Quoted from it: that when soliciting reviews, merchants should not require or pressure users to leave ratings or write reviews while on the premises, nor request that specific content be included; the enumerated example of merchants requesting that staff solicit a certain number of reviews; and the merchant prohibitions on offering incentives such as payment, discounts, free goods or services in exchange for posting any review or the revision or removal of a negative review, and on discouraging or prohibiting negative reviews or selectively soliciting positive reviews from customers. The fake engagement, rating manipulation, conflict of interest, impersonation, misinformation, misrepresentation, harassment, hate speech, personal information, off-topic, unclear, repetitive and defacement provisions of the same document were read but are not the subject of this page. The reporting requirements are quoted from 50 CFR 622.26, recordkeeping and reporting, retrieved from the eCFR enhanced renderer on 26 July 2026, paragraph (b) and its subparagraphs: that the owner or operator of a charter vessel for which a charter vessel or headboat permit for Gulf reef fish has been issued, or whose vessel fishes for or lands such reef fish in or from state waters adjoining the Gulf EEZ, and who is selected to report by the Science and Research Director, must maintain a fishing record for each trip on forms provided and submit it weekly, postmarked no later than seven days after the end of each week; that headboats must submit an electronic fishing record for each trip of all fish harvested via the Southeast Region Headboat Survey at weekly intervals by 11:59 p.m. local time on the Sunday following a reporting week; that a report must still be submitted for a week in which no fishing activity occurred; that during catastrophic conditions determined by the regional administrator, paper forms are provided as a backup with notice given through the Federal Register, NOAA weather radio and fishery bulletins; and that a report not received within the specified time is delinquent, that a delinquent report automatically results in the owner and operator being prohibited from harvesting or possessing the species regardless of any additional notification, and that authority resumes only once all required and delinquent reports have been submitted and received. The commercial vessel provisions, the advance notice of landing requirements, the approved landing location rules and the dealer provisions of that section were read but are not relied on here. The permits and forms page cited is published by NOAA Fisheries for the southeast region and was confirmed reachable on 26 July 2026; no figure is drawn from it. The arithmetic panel uses stated illustrative assumptions and contains no measurement. Nothing here is legal advice.
If your booking calendar has more open weeks than you’d like, I’ll build you a free preview of your booking site before you pay a cent.
Get a free website previewAsking for reviews, what is prohibited and what actually works
Can I ask for a review while the client is still at the dock?
Not in the way most guides do. Google's policy states that when soliciting reviews, merchants should not require or pressure users to leave ratings or write reviews while on the premises. A boat at the dock at the end of a trip is unambiguously the premises, and the client is standing in front of somebody who has just spent eight hours being helpful to them, which is exactly the imbalance the rule addresses. Saying a follow-up will arrive, and that reviews help a small operation, is a statement of fact. Handing over your phone with the form already open is not. The honest test is whether declining would be awkward, and on a dock it always is.
Can I ask clients to mention the species or the boat?
No. The policy says merchants should not request that specific content be included in a review. That rules out the card asking clients to mention the species, the boat name or the town, which is standard advice in a great many marketing guides, and it also rules out the softer version, meaning the follow-up message suggesting what a helpful review would cover. The reasoning is straightforward once stated: a review shaped by the business describes the business's preferences rather than the day. A review that mentions the species without being prompted is worth more than one that mentions it because a card asked.
Can I set a review target for my crew?
No, and it is named specifically. Among the prohibited practices the policy lists merchants requesting that staff solicit a certain number of reviews, which kills the quota, the leaderboard and any bonus attached to a count. For a one-boat operation this looks irrelevant until you notice it applies to you as your own crew: a personal target of ten reviews a month produces precisely the behaviour the rule exists to prevent, which is chasing the number instead of sending the ask. The measure that is safe to track is whether the ask went out to every client, which is a process measure rather than an outcome one.
When should the request go out?
On a fixed day each week, to everybody who fished that week, after they have gone home. Sending it off the premises removes the pressure problem entirely, because nobody is standing in front of you when they decide. Weekly rather than daily matters, because a weekly rhythm survives a season and a daily one does not, and a fixed day means the decision is never made. It also gives clients time to have told somebody about the day, which is when people are best able to describe it. Attach it to something administrative you already do on that day so it never depends on remembering.
What should the message contain?
Four things, and none is a suggestion about content. A specific reference to their day, meaning at minimum the date and the water, so it reads as a message rather than a broadcast. A plain statement that reviews help a small operation, which is true and is not pressure once they are at home. A single link that lands them where the review is written, with no intermediate page. And an explicit line saying an honest account is what is useful, whatever it says, which keeps you inside the policy and happens to be true. It must not suggest what to mention, offer anything, or promise a follow-up.
What system should the ask be attached to?
One that already runs on a deadline. Under 50 CFR 622.26, a charter vessel holding a Gulf reef fish charter or headboat permit and selected to report must keep a fishing record for each trip and submit it weekly, postmarked no later than seven days after the end of each week; headboats submit electronically through the Southeast Region Headboat Survey by 11:59 p.m. local time on the Sunday following a reporting week, and must file even for a week with no fishing activity. Borrow the shape rather than inventing one. Confirm what applies to your own operation, since these rules are amended and vary by fishery and region.
What if hardly anybody responds?
You keep sending it, because the alternatives are prohibited. No published response rate for review requests in this trade exists in any market, and none is asserted here. What is knowable is your own: log asks sent and reviews received across one full season and you have a figure that is actually about you. A low rate is not a reason to start filtering, since filtering is the prohibited move, nor to start offering anything, for the same reason. It is a reason to check the message is short, the link is direct and the timing is within a week of the trip. Volume comes from the number of asks, which is entirely within your control.
Sources & methods
- Prohibited & restricted content, Maps user generated content policy
- 50 CFR 622.26, recordkeeping and reporting for charter vessels and headboats (eCFR)
- Permits, applications and forms, southeast region (NOAA Fisheries)
Every figure here is traced to a named public source and checked against it. Licensing, tax, and fee rules change. Verify your state’s current rules with the agency directly before you count on any number here.
Evan Knox
I build booking websites and run the ads and search for owner-run fishing guides, one operation per stretch of water. My first guide client, Bowman Fly Fishing, grew its revenue 4x in a year from that work. Field Notes is where I put the straight numbers on the business of guiding.
More field notes
Reviews win the booking. A booking site takes it.
I'm Evan, and the guide who steadily earns reviews and whose site makes booking easy is the one who fills a calendar. I build booking sites and set up the review-asking and follow-up for owner-run guide operations, one operation per stretch of water, so reviews turn into bookings. Text me at (470) 777-9686 and I'll build you a free preview of your site before you pay a thing.