Skip to main content
Cheers

Playbooks

Should Home Services Publish Coupons for Google AI?

How multi-location service brands should publish coupons and seasonal offers so pages, profiles, call scripts, and field teams repeat the same terms.

Dylan Allen-Arnegard, CEO and Co-Founder of Cheers
Dylan Allen-Arnegård

CEO & Co-Founder, Cheers

10 min readPublished Updated

Last verified .

Google Business Profile Help states a rule that breaks most promotional calendars: "Posts older than 6 months are archived unless a date range is set." A spring tune-up coupon published without dates does not stay live and does not stay dead. It goes quiet on its own schedule while dispatch is still being asked about it.

Coupons, seasonal discounts, free inspection offers, tune-up specials, first-visit promotions, med spa packages, and membership discounts all create the same source problem. A customer sees one promise in Google Search, another on a location page, a third in a Google Business Profile offer post, and a different answer from dispatch. AI search does not make that inconsistency cleaner; it gives the inconsistency more places to appear.

Google's own documentation is specific about what an offer post is:

Offers: Provide promotional sales or deals from your business. It requires a title, dates, and time.

Dates are mandatory, which tells you what Google thinks an offer is: a fact with an expiry, not a slogan. Everything below follows from treating it that way.

For a 60-location HVAC group, that might mean a spring tune-up discount that applies only in participating markets. For a pest control brand, it might mean a seasonal inspection offer with clear exclusions. For a med spa group, it might mean a package price that depends on location, provider availability, or consultation rules. For a franchise service brand, it might mean corporate owns the offer language while franchisees confirm market participation.

Important

Publish coupons and offers as operating facts. The page, Google Business Profile post, service listing, call script, and field handoff should say the same thing before the offer is pushed into more channels.

Diagram comparing undated campaign copy against a dated offer record with a source URL and participating locations
Google's posts documentation requires a title and dates on an offer, so an undated coupon quietly archives while dispatch keeps fielding it.

Offer terms are source facts

An offer is different from a service description. It has a start date, an end date, eligibility rules, participating locations, and a customer action. That makes it easier to use, and easier to make stale.

Google's offer-post documentation is useful because it forces a basic structure. The offer needs a title and dates. It can include a coupon code, link, and terms. For multi-location brands, the missing work is governance. The post surface can show the promotion, but it cannot decide whether the Dallas branch, the Phoenix branch, and the Columbus franchisee can all honor the same terms.

When a customer asks an assistant what a tune-up costs or whether anyone is running a special, your offer terms are the answer being assembled.

That is why coupons belong in the same governed source set as service prices, financing options, accepted payment methods, emergency hours, and location-page proof. They are customer-facing promises.

What an offer needs before it goes public

A good offer starts with one sentence the local team can repeat without improvising. "AC tune-up for participating Phoenix-area branches through July 31" is better than "summer savings." "Free pest inspection with paid treatment, new residential customers only, participating markets only" is better than "free inspection" if the actual terms are narrower.

Write the offer like a customer will compare it across sources. What service qualifies? Which locations participate? Does the customer need a coupon code? Is the discount tied to a minimum invoice, new-customer status, inspection, membership, or weekday appointment? Does the offer expire by date, inventory, season, provider, or market? If the customer calls one branch and the branch says the offer does not apply, the public offer system failed.

The FTC's Guides Against Deceptive Pricing are a useful guardrail for discount language. They warn that former-price comparisons should not be fictitious and that meaningless reductions can be deceptive. The FTC's bait-advertising guides warn against insincere offers that are used to switch a buyer to something else. This article is not legal advice, but the operating standard is clear: do not use a discount as a lead hook if the team is trained to move most customers away from the advertised offer.

For local-service brands, the risk often hides in branch reality. Labor rates vary by market. A seasonal HVAC tune-up may exclude commercial systems. A garage door coupon may apply to service calls but not parts. A med spa package may depend on provider availability and consultation rules. A pest control inspection may be free only inside certain service areas.

Where the offer should live

The durable offer should live on the website, usually on the service page, location page, market page, or a short offer page that is linked from the relevant service and location pages. That page can carry the terms, expiration, participating locations, contact path, and update date in one place.

Google Business Profile offer posts can distribute the offer. Profile services can reinforce the service and price context when that field is available. Google says service businesses can organize services under categories and add details such as descriptions and prices. The profile should not become a separate coupon database with different terms from the page.

The call path needs the same source. A dispatcher should be able to answer the obvious questions: does this branch participate, when does the offer expire, which service qualifies, and where should the customer book? Field teams need the same rule before they hand over an estimate or explain why the discount does not apply.

This is especially important when the offer is tied to local pages. Location pages built for AI Search need branch-specific facts, not copied corporate claims. If one region runs a shoulder-season HVAC offer and another does not, the branch pages should not use the same promotion block.

Branch availability is the hard part

Multi-location brands often publish offers centrally because it is faster. The page looks clean, the ad looks clean, and the profile post looks clean. The mess appears later, when one franchisee opts out, one market has different labor costs, one service area lacks the licensed crew, or one location keeps an expired post live.

Treat participation as a data field, not a Slack thread. The offer should have an owner, a date range, participating locations, excluded locations, qualifying services, terms, and a source URL. If a branch is excluded, the branch page should avoid the claim. If a branch is included, the call script and estimate handoff should match.

For a pest control brand, the difference can be small but material. A "free inspection" offer may apply only to residential recurring plans. It may exclude commercial facilities, termite work, or markets outside the technician's coverage zone. Those exclusions are not fine print for AI. They are the facts that prevent the wrong answer from reaching a customer.

Branch availability also affects internal links. The offer page should link to the specific service and location pages that can honor it. The participating location pages should link back to the offer while it is active. When the offer ends, those links should be removed, redirected to an evergreen service page, or updated to the next active promotion. If you run this across dozens of markets, multi-location local SEO is where the participation record and the page inventory have to stay in sync.

Next step

Is AI recommending your business?

Find out how visible you are across ChatGPT, Gemini, Perplexity, and AI Overviews.

Keep coupons away from review incentives

Coupons and reviews should never be mixed. Google's Maps user-generated content policy is direct about it:

Content that has been posted due to an incentive offered by a business.

That sentence sits under Prohibited and Restricted Content, and the policy names payment, discounts, free goods, and services as examples. It also covers content posted after a business asks for a review to be revised or removed in exchange for something.

That rule matters for operators because frontline teams often see coupons and review requests as part of the same customer handoff. Keep them separate. A technician can explain a legitimate service offer. A front desk worker can provide a neutral review request after real service. The customer should never feel that the discount depends on writing a review, changing a review, removing a complaint, naming a staff member, or leaving a specific rating.

If the team needs a refresher, use the review compliance playbook before launching a promotion that touches the service counter, technician handoff, or post-visit message flow.

A 30-day offer governance pass

Keep the first pass small. Pick the offers that can change customer behavior and create real source confusion.

  • Choose three to five active or upcoming promotions across priority service lines.
  • Create one source URL for each offer with terms, expiration, participating markets, excluded markets, and the next customer action.
  • Update only the Business Profiles and service descriptions for locations that can honor the offer.
  • Align call scripts, estimate templates, field coaching, ads, email, social, and third-party profiles with the same source URL.
  • Remove expired posts, stale coupon pages, old PDFs, outdated landing pages, and franchise microsite claims.
  • Test Google Search, Maps, Google AI Search, ChatGPT, Gemini, Perplexity, and internal visibility reports for offer-sensitive prompts by market.

The checklist only works when each part has an owner. Marketing owns the source page and campaign links. Operations owns whether each branch can honor the offer. Legal or finance owns sensitive terms. Local managers own the customer handoff. The AI visibility owner records where the answer still repeats an old or incomplete version.

Check whether the offer stayed true

Do not measure only clicks. Measure whether the offer stayed true across sources.

Start with a source readout. Search the offer by service, market, brand, and competitor. Check whether the live page, profile post, service listing, ad landing page, and local page agree. Review the AI answer or summary for the exact offer terms, cited source, location fit, expiration, and competitor mentions.

Then audit the human path. Call or message a participating branch. Ask the same question a customer would ask. Does the staff member know the offer? Do they state the right date? Do they explain exclusions without improvising? Does the estimate handoff match the page?

The strongest offer system is boring. One current source, a clear expiration, participating branches, compliant terms, and a team that can honor the promise. That is enough to make the offer useful to customers, safer for operators, and easier for AI search systems to represent accurately.

Sources

Every link below was opened and checked on September 2, 2026.

  • Create and manage posts on your Business Profile. Google Business Profile Help. Undated help page, checked September 2, 2026. support.google.com/business/answer/7342169. Source of the quoted offer-post requirements and of the six-month archive rule for posts without a date range.
  • Prohibited and restricted content. Google Maps user-generated content policy, Google Help. Undated policy page, checked September 2, 2026. support.google.com/contributionpolicy/answer/7400114. Source of the quoted line on content posted due to an incentive.
  • Google's guide to optimizing for generative AI features on Google Search. Google Search Central. Last updated July 10, 2026, checked September 2, 2026. developers.google.com/search/docs/fundamentals/ai-optimization-guide. Supports the local-business and Search-foundation framing for AI Overviews and AI Mode.
  • How to check pricing for local businesses with AI in Google Search. Google Search Help. Undated help page, checked September 2, 2026. support.google.com/websearch/answer/16421135. Supports keeping offer terms aligned with local quote, price, and availability workflows.
  • Manage your services on your Business Profile. Google Business Profile Help. Undated help page, checked September 2, 2026. support.google.com/business/answer/9455399. Supports service organization and optional service descriptions or prices on Business Profiles.
  • Tips to improve your local ranking on Google. Google Business Profile Help. Undated help page, checked September 2, 2026. support.google.com/business/answer/7091. Supports the complete and accurate business information standard, plus profile freshness.
  • 16 CFR Part 233, Guides Against Deceptive Pricing. Electronic Code of Federal Regulations, US Federal Trade Commission. Current as of the September 2, 2026 check. ecfr.gov/current/title-16/chapter-I/subchapter-B/part-233. Supports the caution against fictitious former-price comparisons and meaningless sale claims.
  • 16 CFR Part 238, Guides Against Bait Advertising. Electronic Code of Federal Regulations, US Federal Trade Commission. Current as of the September 2, 2026 check. ecfr.gov/current/title-16/chapter-I/subchapter-B/part-238. Supports the caution against insincere offers used to switch buyers to a different sale.

Last verified: September 2, 2026.

Dylan Allen-Arnegård is the CEO & Co-Founder of Cheers, the local search platform for multi-location service businesses.

Written by

Dylan Allen-Arnegard, CEO and Co-Founder of Cheers

Dylan Allen-Arnegård

CEO & Co-Founder, Cheers

Dylan co-founded Cheers after building reputation software for frontline teams. He leads the work that makes multi-location service brands visible to AI.

Share this article

How multi-location service brands should publish coupons and seasonal offers so pages, profiles, call scripts, and field teams repeat the same terms.

Frequently Asked Questions

Publish the offer when it is real, dated, location-aware, and supported by the website, Business Profile, call path, and field handoff. Google's offer post format already requires a title and dates, so treat coupons as public business facts with an expiry rather than loose promotional copy.

The website should own the durable offer terms. Google Business Profile offer posts, service descriptions, location pages, ads, call scripts, and technician handoffs should point back to the same rule instead of becoming separate versions.

Offer posts are distribution, not governance. Google says an offer requires a title, dates, and time, and that posts older than 6 months are archived unless a date range is set. Multi-location teams still need an owned page that explains eligibility, participating markets, and expiration.

Google's Maps user-generated content policy prohibits content posted because a business offered an incentive, naming payment, discounts, free goods, and services. Keep promotional offers separate from review requests, including requests to revise or remove a review.

Track whether Google Search, Maps, AI answers, call-center responses, and field estimates repeat the same offer by market. Record stale pages, expired posts, branch exclusions, wrong coupon terms, and any prompts where competitors own the offer language.

Keep reading