How a landscaping company builds a review request, consent, response, and measurement system tied to completed jobs, without incentives, fake reviews, or rank promises.
Most landscaping owners do not have a review problem. They have a timing and record problem. The crew finishes a patio, the client is thrilled on the walkthrough, and then nobody sends the ask until the office remembers it three weeks later, mixed in with spring cleanup reminders.
This page is an operating guide, not a pitch. It defines how a US landscaping company asks for, responds to, and measures reviews around completed jobs, with consent handled separately and every stage measured on its own. It starts after the work is finished. It does not sell reputation management, and it makes no promise about more reviews, a star rating, Map Pack placement, ranking, traffic, leads, or revenue.
theStacc's Local SEO module covers Google Business Profile posts, owner-approved review replies, citations and NAP, and Map Pack rank tracking. It is not a review-generation or reputation-management product, and nothing below asks you to treat it as one. The commercial case for the product lives on the landscaping vertical page; the broader search umbrella sits in the landscaping SEO guide.
Here is what you will set up:
- A request moment tied to a finished-job milestone, split between project work and recurring route work.
- A clean line between review consent and the separate consent for property photos and testimonials.
- A response discipline that protects private information and routes disputes off the public thread.
- Stage-separated measurement that never relabels a review as an enquiry, a booked job, or a rank move.
What landscaping reviews actually cover
A landscaping review system is the documented workflow for asking a real customer for a review, recording consent, answering what gets posted, and measuring each step on its own. It begins only after a job is finished. It is not a reputation-management service, a review-buying scheme, or a promise of more stars, faster replies, or higher local ranking.
Four jobs sit inside that workflow, and each one has its own owner and record. The request is the genuine ask sent to a genuine customer after a completed job. Consent is the separate approval decision that covers what, if anything, may be reused beyond the review itself. The response is the owner-approved reply posted under the review. Measurement is the set of rates you compute from those records, kept apart from the rest of the funnel.
What this page does not cover is just as important. It does not promise a review count, a velocity, a response time, or any movement in local results. It does not give legal, licensing, insurance, pricing, or employment advice, and it does not rank vendors or tools. The generic how-to mechanics of asking and responding already live in the review management guide, the guide to getting more Google reviews, the ask-customers walkthrough, and the response templates. This page owns only the landscaping-specific layer: when the ask fires, how consent is split, and how the numbers are kept separate.
Separate the review lifecycle from the job funnel
The job funnel tracks a stranger becoming a finished customer, from impression to completed job. The review lifecycle starts later and logs its own events: request sent, review received, response published. Keep the two as separate records. A completed job is the earliest a request can be considered; a review is never an enquiry, qualified request, or booked job.
Mixing the two is how landscaping offices talk themselves into numbers they cannot defend. A glowing review gets counted as a "lead." A request blast sent to last year's cleanup list gets reported as demand. A reply posted by the office manager gets treated as proof the phone will ring. None of that holds up, because each event comes from a different system and means something different.
Keep every stage as its own row with its own source and owner, and write down what each row must never be called. The table below is the separation this whole page depends on.
| Stage | Source system | Owner | Must not be called |
|---|---|---|---|
| Impression | Search and profile reporting | Marketing | A click or an enquiry |
| Click | Search and profile reporting | Marketing | A call or a visit |
| Call click | Call tracking or phone log | Intake | A connected enquiry |
| Form submission | Website form log | Intake | A qualified request |
| Qualified enquiry | Intake or CRM log | Intake owner | A booked job |
| Booked job | Scheduling record | Scheduling owner | A completed job |
| Completed job | Job-management record | Operations | A review or a referral |
| Review-request sent | Request log | Review owner | A review received |
| Review received | Review-platform record | Review owner | An enquiry or a booked job |
| Response published | Response log | Review owner | A lead outcome |
Read the last column as the rule. The first seven rows are the funnel you already track. The last three are the review lifecycle, and they begin only where the funnel ends. Once those rows are separate in your reports, the rest of the system has something solid to stand on.
Tie the ask to a completed-job milestone, not a calendar
Tie every review ask to a finished-job milestone the customer has seen, not a calendar date. For design-build project work the candidate moment is the reveal and closeout. For recurring route maintenance it is a defined milestone the operator approves and records. The exact trigger is yours to set per work type, documented in the job, not fixed here.
This is the section a swapped trade would get wrong. A landscaper's work is visible, seasonal, and split between two very different rhythms, so the ask moment has to match the job. Project work ends in a single reveal the customer walks through: the patio is laid, the retaining wall is set, the outdoor kitchen is lit, the spring cleanup has reset the beds. Recurring route maintenance has no single finish line, so the milestone is a defined point such as a cleanup completed or a documented stretch of issue-free service. Commercial and property-manager contracts add a third pattern, where the approver is an account contact rather than a homeowner and the ask follows a signed-off visit, not a back-yard walkthrough.
Demand for this topic is seasonal too. DataForSEO's estimate for the head term peaked in March and softened into winter across recent years, which matches how residential project work concentrates in spring. Describe that seasonality when you plan staffing and record-keeping, but do not forecast reviews, ranking, or leads from it.
| Work type | Candidate ask moment | Required pre-condition | Owner | Record destination | Stop condition |
|---|---|---|---|---|---|
| One-time design-build project (patio, wall, outdoor kitchen, lighting) | Reveal and closeout, once the customer has seen the finished scope | Scope complete; customer walked the result; no open dispute | Project lead or office | Request log tied to the job | Open punch-list item or unresolved complaint |
| Recurring route maintenance | A defined milestone such as a seasonal cleanup or an issue-free service period | Milestone met; service record current; no open dispute | Route manager | Request log tied to the account | Skipped visit, open complaint, or paused contract |
| Seasonal cleanup (spring or fall) | Completion of the cleanup the customer can see | Cleanup done; result visible; no open dispute | Crew lead or office | Request log tied to the visit | Follow-up visit still pending |
| Commercial or property-manager contract | Signed-off visit or agreed reporting checkpoint | Contact approved the work; no open ticket | Account manager | Request log tied to the contract | Open ticket or pending approval |
Two rules hold across every row. The customer must have seen the result, and there must be no open dispute. If either is missing, the request waits. The matrix does not set a day count, because a two-day hardscaping punch list and a six-week planting establishment period do not share a clock. Write the milestone into the job record so the request fires from the work, not from a marketing calendar that does not know the job is done.
Build the request into the job record, not into someone's memory. theStacc's Local SEO module handles Google Business Profile posts and owner-approved review replies; it does not buy, script, or generate reviews. If you want the request, response, and measurement workflow mapped to your GBP setup, Sign up for free →
Keep review consent separate from photo and testimonial consent
A customer who leaves a review has approved only the review. They have not approved reuse of their property photos, before-and-after images, name, or words in your marketing. Those are separate approvals, each with its own scope, expiry, and withdrawal path, recorded apart from the review. A review never grants the others.
This is the second section a swapped trade would mishandle, because the asset a landscaper wants to reuse is the customer's property. The finished patio, the lit walkway, the before-and-after of an overgrown yard: that proof is the strongest marketing a landscaping company has, and it is also the easiest to misuse. A five-star review about a retaining wall does not give you permission to photograph that wall for a social post, print the customer's name on a postcard, or quote their words on a landing page. Each reuse needs its own yes.
| Consent type | What it covers | Scope and expiry | Withdrawal path |
|---|---|---|---|
| Review consent | The act of posting a review on a platform | Governed by the platform; the customer controls the review | Customer edits or removes the review on the platform |
| Property and before-and-after photo consent | Photographing and reusing images of the customer's property | Named uses, channels, and an expiry or review date | Written request to the named owner; images pulled from listed channels |
| Testimonial and name-reuse consent | Quoting the customer's words or name in marketing | Named placements and an expiry or review date | Written request to the named owner; quote and name removed |
Record each approval against the job, with who asked, what was approved, where it may appear, and how the customer can withdraw it. Keep those records out of the review log so nobody assumes a review covered a photo. The actual publishing workflow for approved proof, including before-and-after posts, belongs to the social media owner, not to the review request. If a customer withdraws photo consent, pause the related posts even while the review itself stays up.
Ask without incentives or sentiment conditions
A genuine ask to a genuine customer after a completed job is allowed. Discounts, gifts, entries, and any condition tied to a positive or negative sentiment are not. Never script a rating. Google's review policy and the FTC Consumer Reviews and Testimonials Rule set the floor; send solicitation-rule questions to qualified review rather than guessing from a template.
Google's Business Profile review policy permits asking real customers for reviews and prohibits incentivized or fake reviews and rating manipulation. The FTC's Consumer Reviews and Testimonials Rule separately prohibits specified fake or false reviews and bars conditioning an incentive on a review expressing a particular sentiment. Read together, they leave one clean path: ask a real customer for an honest review, and attach nothing to whether they leave it or to what they say.
For a landscaping company, the tempting shortcuts are concrete. A "free mulch top-up on your next visit if you leave us a review" is a conditioned incentive. A drawing entry for a gift card tied to posted reviews is a conditioned incentive. A spring cleanup discount that only appears for customers who reviewed you is a conditioned incentive. Even a pre-written five-star script handed to a happy client at the patio reveal crosses the line, because it scripts the rating. None of these are allowed, and none of them are necessary.
If the request goes out by commercial email, the FTC's CAN-SPAM guide also applies: accurate sender information, a non-deceptive subject, the required disclosures and postal address, and a working opt-out. That rule is about the email, not about reviews, and it is a US federal floor rather than legal advice. State and local solicitation rules can add more, so route anything beyond the basics to qualified review. The reusable phrasing for the ask itself lives in the ask-customers guide; keep it plain and keep it honest.
Respond with privacy discipline
Acknowledge positive, mixed, and negative reviews without exposing personal information or arguing in public. Move disputes to an approved private path, name one owner and an escalation route, and keep a record of each exchange. Google's review policy advises protecting personal information in public replies, so the public thread stays short and the details move off it.
Landscaping replies carry a specific privacy risk: the work happened at the customer's home. A public reply that repeats the street name, quotes the invoice, or describes a dispute about a specific planting bed can expose information the customer never agreed to share. Google's review policy calls out protecting personal information in replies for exactly this reason. Keep the public response to acknowledgement and a path forward, and take the address, the invoice, and the argument to a private channel you control.
| Review type | First owner | Public-response boundary | Move to private path when | Record to keep |
|---|---|---|---|---|
| Positive | Review owner | Thank the reviewer; no private details | Customer raises a new issue inside the praise | Reply text and date |
| Mixed | Review owner | Thank and acknowledge the concern; no specifics | Any factual dispute about scope or timing | Reply text, date, and private follow-up |
| Negative | Review owner, escalate if needed | Calm acknowledgement; no argument, no personal data | Immediately for details, refunds, or rework | Reply text, date, escalation, and resolution |
| Suspected fake | Review owner | No accusation in public | Document and route to the platform appeal | Basis, appeal reference, and outcome |
One owner keeps the voice consistent, and one escalation route keeps a hard reply from sitting unanswered while the crew is on a route. The table is a boundary map, not a script library; the actual wording patterns live in the response templates. What matters here is that the public reply never carries the address, the price, or the dispute, and that every exchange is logged so the next person to touch the account knows what was said.
Handle suspected fake or inaccurate reviews through the platform process
When a review looks fake or inaccurate, document the basis, use the platform's flag and appeal route, and keep the record. Do not publish accusations or name the reviewer in public. While an appeal is open, hold that review out of your response-rate math. The full platform process lives in the fake-reviews guide; this page sets only the landscaping boundary.
Landscaping companies attract a recognizable set of bad reviews: a competitor's burner account after a bid is lost, a confused reviewer who hired a different crew with a similar name, or a neighbor upset about noise or parking who was never a customer. The instinct is to answer in public and set the record straight. Resist it. A public accusation can create its own problem and does nothing to remove the review. The platform's flag and appeal route is the only path that changes what is posted.
Write down why you believe the review is fake or inaccurate, with whatever the job record shows: no matching customer, no matching address, a date when no crew was scheduled, or a service you do not offer. Keep that note with the appeal reference and the outcome. Until the platform resolves it, exclude the review from response-rate and request-rate math so a disputed item does not distort either number. The step-by-step flagging and appeal workflow is documented in the guide to handling fake Google reviews; use it rather than restating it here.
Measure each stage separately with a formula-definition gate
Every rate you publish carries a numerator, a denominator, an evidence window, a source system, an owner, and exclusions. There is no portable benchmark. A review never substitutes for an enquiry, a booked job, or a rank change. If any field is missing, pause the metric instead of filling the gap by relabeling a review as a lead.
Google Analytics 4 documents separate lead events such as generate_lead, qualify_lead, working_lead, and close_convert_lead, and the business defines when each one fires; a review is not any of them, per Google's GA4 guidance. That separation is the point of this section. Review-request rate and review-response rate describe review operations only. They are not averaged into, and do not imply, the qualified-enquiry or booked-job rates.
| Formula | Numerator | Denominator | Evidence window | Source system | Owner | Exclusions |
|---|---|---|---|---|---|---|
| Review-request rate | Eligible completed jobs sent a genuine, unincentivized request | Eligible completed jobs in the same window | One declared window, for example a 28-day cohort | Job-management record plus request log | Operations or review owner | Jobs with open disputes, withdrawn consent, duplicates, test records, out-of-area work |
| Review-response rate | Reviews with a published, owner-approved reply | Reviews received in the same window | One declared window with enough lag for the stated response process | Review-platform record plus response log | Review owner | Reviews under platform appeal, spam removed by the platform, duplicates |
| Qualified-enquiry rate | Unique enquiries marked qualified under the written service and area rule | All unique attributable enquiries in the same window | One declared 28-day window | Intake or CRM log plus source field | Intake owner | Duplicates, spam, employment or vendor enquiries, unsupported area or service |
| Booked-job rate | Unique qualified requests with a confirmed booked job | Unique qualified requests created in the same cohort window | 28-day intake cohort plus enough lag for the booking cycle | Scheduling or operating record | Scheduling owner | Reschedules counted once; jobs canceled before service remain booked-not-completed |
Notice what is not in the table: there is no column that turns a review into an enquiry, and no benchmark you can copy from another company. A design-build firm with twelve patio jobs a month and a route-maintenance company with four hundred weekly visits will never share a sensible request-rate target, because the denominators are built from different work. Define each field once, in writing, and hold the definition steady long enough to compare a period against the same definition.
Keep the review numbers honest by keeping them separate. theStacc's Local SEO module records Google Business Profile posts and owner-approved review replies, and Content SEO can research, draft, and publish the supporting pages; neither turns a review into a lead. If you want the four rates defined around your own jobs, Sign up for free →
Review, correct, and pause
When an approval, an owner, a consent record, or a milestone is missing, pause the request or the response. Continue, change, or pause from evidence, not from a cadence target. A paused ask is cheaper than an incentivized one, and a held reply is safer than a public argument that exposes a customer's address or invoice.
This is the part that keeps the system from running on autopilot into a wall. Landscaping work is seasonal and uneven, so a flat calendar will happily fire requests into jobs that are not done, disputes that are not resolved, and properties that fall outside your service area. Build the pause conditions into the same records that trigger the ask, so the default is to wait when the pre-conditions are not met.
Failure-state checklist
Hold the request or the response and route it to the named owner when any of these are true:
- The job is not completed, or the customer has not seen the result.
- There is an open dispute, punch-list item, ticket, or unresolved complaint.
- The customer has withdrawn review, photo, or testimonial consent.
- The property is outside your service area or the work is out of scope.
- A request for the same job or account was already sent, creating a duplicate.
- The ask includes an incentive or any condition tied to sentiment, or a scripted rating.
- A draft public reply contains an address, invoice detail, name, or other personal information.
- A platform flag or appeal on the review is still pending.
Each item on the checklist maps back to a section above. A missing milestone is a Section 3 problem. A withdrawn consent is a Section 4 problem. An incentivized ask is a Section 5 problem. Personal data in a reply is a Section 6 problem. A pending appeal is a Section 7 problem. When the evidence clears, the work continues; when it does not, the pause is the correct outcome, not a missed target.
Frequently Asked Questions
These eight answers cover the questions landscaping owners and office marketers ask most about reviews, kept inside this page's scope. They do not answer vendor-cost or hourly-rate questions, which sit outside the operator discipline this guide covers, and they restate the same boundaries the sections above set out.
How should a landscaping company ask customers for reviews?
Ask a genuine customer, after a completed job, in plain language, with no gift, discount, entry, or condition tied to the review or its tone. Send the request by a channel you already use with that customer, log that it was sent, and never script the rating. The generic mechanics sit in the ask-for-reviews and review-management guides; this page covers only the landscaping timing and consent.
When is the right time to ask for a landscaping review?
After the customer has seen the finished work and there is no open dispute. For a one-time patio, retaining wall, outdoor kitchen, or lighting project that is the reveal and closeout. For recurring route maintenance it is a defined milestone, such as a seasonal cleanup or a documented stretch of issue-free service. The exact moment is operator-approved and recorded, not a fixed number of days.
Can a landscaping business offer a discount or gift for a review?
No. Google's review policy and the FTC Consumer Reviews and Testimonials Rule both prohibit conditioning an incentive on a review or on a positive or negative sentiment. You may ask a genuine customer for an honest review. You may not tie a discount, gift, entry, or any condition to whether they leave one or to what they say. Route solicitation-rule questions to qualified review.
If a customer leaves a review, can the business reuse their before-and-after photos?
No. A review is not consent to reuse property photos, before-and-after images, the customer's name, or their words in your marketing. Each of those needs its own approval, scope, expiry, and withdrawal path, recorded separately from the review. The publishing workflow for that proof belongs to the social-media owner, not to the review request.
How should a landscaper respond to a negative review?
Acknowledge it calmly, thank the reviewer, and do not expose personal information or argue in public. State that you want to make it right and move the details to an approved private path, then record the exchange. Name one owner and an escalation route so the reply is consistent. Use the platform reply, and keep any dispute facts off the public thread.
Do more reviews guarantee better local ranking for a landscaping company?
No. A higher review count is not a guarantee of better local ranking, Map Pack placement, traffic, or leads. Reviews are one trust signal among many, and this page makes no ranking, traffic, lead, or revenue promise. Treat reviews as an operations record you ask for and answer honestly, not as a switch that forces a position in the local pack.
How should landscaping reviews be measured without calling a review a lead or a booked job?
Give every rate its own numerator, denominator, evidence window, source system, owner, and exclusions, and keep review-request rate and review-response rate as review-operations numbers only. A review, a request sent, and a response published are never averaged into qualified-enquiry rate or booked-job rate. If a field is missing, pause the metric instead of relabeling a review as a lead.
What should a landscaping business do about a suspected fake review?
Document why you believe it is fake or inaccurate, then use the platform's flag and appeal route and keep the record. Do not publish accusations or name the reviewer in public. While an appeal is open, exclude that review from response-rate math. The step-by-step platform process lives in the fake-reviews guide; this page only sets the landscaping boundary.
Build the system before the next busy season
A defensible review system is four records that agree: a request tied to a finished job, a consent decision kept apart from the review, a reply that protects private information, and a set of rates that never borrow from the funnel. Write the milestone, owner, and pause conditions into the job record before the spring rush.
Start with the two splits that matter most for landscaping. Separate project work from recurring route work, because the reveal of a finished patio and a milestone on a weekly route do not share a trigger. Separate review consent from photo and testimonial consent, because the customer's yard is the asset you most want to reuse and the easiest to misuse without a recorded yes. Then keep every stage in its own row, so a review is never reported as a lead and a reply is never sold as a ranking move.
When the request, consent, response, and measurement pieces are documented, the office stops relying on memory and the crew stops guessing about timing. That is the whole outcome this guide promises: a process you can defend, tied to real completed jobs, with no incentives and no invented results.
Wire the workflow into your Google Business Profile and content operations. theStacc's Local SEO module covers GBP posts and owner-approved review replies, and Content SEO can research, draft, and publish the supporting pages; neither one buys or generates reviews. Sign up for free →
Sources & references
- [1] Google Business Profile review policy — asking genuine customers is allowed; incentivized or fake reviews and rating manipulation are prohibited; protect personal information in replies
- [2] Google Business Profile — service-area business eligibility and accurate representation of location and service area
- [3] FTC — Consumer Reviews and Testimonials Rule Q&A (fake or false reviews; no incentive conditioned on a particular sentiment)
- [4] FTC — CAN-SPAM compliance guide, relevant when a review request is sent by commercial email
- [5] Google Analytics 4 — lead event stages such as generate_lead, qualify_lead, working_lead, close_convert_lead; a review is none of these
Rank in the Map Pack, collect reviews, and keep every location active — on autopilot.