Google Maps Policy Update: What Merchants Can't Post in Listings

6 October 2026 · The Cresia team

What can't merchants post in Google Maps listings and posts? Google has now written the answer into the advertising and solicitation section of its prohibited and restricted content policy for Maps and Business Profiles, and that page is the list to check against. For AEO and GEO teams, the change matters less as a new rule and more as a clearer line: promotional or solicitous content in local listings has a firmer basis for removal, and the factual data that feeds local answers should get cleaner as a result.

Key takeaways

Google's advertising and solicitation section now lists what merchants and business owners can't post in listings and posts. Audit against the policy text itself, not a summary of it.
Listings and posts are source material for local search and AI-assisted answers, so promotional clutter is a compliance risk and a data-quality problem at once.
Answer engines tend to favour consistent, factual, corroborated business information. Maps content is one input among several, not the whole picture.
Audit by location. A single franchise or agency-managed profile with bad habits can cause trouble for a whole account.
Measure with a fixed prompt set and listing-level metrics, before and after cleanup. Don't read one week's movement as proof.
Don't bulk-delete on a hunch, and don't expect a policy tidy-up alone to change what AI tools cite.

What Google changed in the Maps policy

Search Engine Roundtable reported that Google updated the advertising and solicitation section of the Google Maps and Business Profiles prohibited and restricted content policy. The section now lists what merchants and business owners cannot post in their listings and in their posts.

That's the whole verified development. The details of each item sit on Google's policy page, and they're the part that matters. If you manage local presence for a brand, read that section start to finish before anyone on your team summarises it from memory. Policy language is precise, and the edge cases (what counts as solicitation, what counts as advertising inside a description field versus a post) are exactly where teams get caught.

It's also worth being clear about what this isn't. A policy clarification doesn't tell you how aggressively Google will enforce it, how fast, or against whom. Enforcement patterns for Business Profiles have shifted before, and they can again. Treat the update as a signal about direction. Don't treat it as a forecast of a crackdown.

Why listing and post content matters for AEO and GEO

Local queries are some of the most answer-shaped searches there are. Who's open late near the station? Which dentist takes walk-ins? Is there a bike shop in this neighbourhood that does e-bike repairs? Those are questions where the user wants a short, specific, trustworthy answer, and where the data comes from structured places: listings, reviews, websites, directories.

A business listing is about the most structured thing a local merchant owns. Name, address, categories, hours, services, attributes, description, posts. When those fields hold clean facts, they're easy for any system to read and reuse. When the description field is stuffed with offers, phone-number pleas and calls to act now, the facts get buried under noise, and the entry reads like an ad rather than a record.

So there are two separate risks from the same habit. The first is policy: content that breaches the rules can be removed, and repeated breaches can put a profile at risk. The second is quality: even content that survives moderation may be a poor thing for a retrieval system to lean on. A team that fixes only the first risk is leaving value on the table.

This is also where the AEO crowd and the local SEO crowd often don't talk to each other. Local SEO owns the listings. AEO owns prompt tracking and entity work. Nobody owns the overlap. This policy update is a decent excuse to put one person in charge of it.

How AI answer engines pick and cite local sources

No vendor publishes a full recipe, and anyone who tells you exactly how a given assistant ranks local sources is guessing. What you can say with reasonable confidence is a set of general tendencies, and each one is worth checking against the vendor's own documentation.

First, answer engines look for agreement. If your website, your listing, your reviews and a few third-party directories all say the same thing about your hours and services, that agreement is easy to trust. If they disagree, the system has to pick, and it may pick wrong or hedge.

Second, they favour specifics they can quote. A line such as 'Same-day screen repair for most phone models, Monday to Saturday' is quotable. 'Best repairs in town, call now for a deal' is not, because it carries no fact the answer could safely repeat.

Third, different products pull from different places. A Google surface may draw on Google's own Maps data in ways a third-party assistant can't. Another assistant may lean on the open web, review sites and licensed data. Your listing might be central in one and nearly invisible in another. Check each product's help pages for what it says about local sources, and test your own prompts rather than assuming.

Fourth, freshness and consistency matter more than volume. Posting daily doesn't make a business more citable. Having correct, current facts in the right fields does.

Put together, that argues for treating the listing as a reference record and treating posts as short, dated, factual updates. That happens to be a good match for what a tidy reading of the policy would push you towards anyway.

What to change in practice

Start with an inventory, not a rewrite. You can't prioritise what you haven't counted.

Pull the policy section and turn it into a checklist. One row per prohibited item, written in your team's words, with the policy page linked beside it.
Export every listing description, post and attribute field for every location. For a chain, that may be thousands of rows. For a single-site business, it's an afternoon.
Flag by pattern, not by hand. Look for repeated template text, shared phone numbers or links across unrelated locations, and posts that read as offers rather than updates. Then have a human review the flagged set.
Rewrite descriptions as facts. What you sell, where you are, who you serve, what's different. Keep promotional claims on your website, where they belong.
Reshape posts into updates. New service added, holiday hours changed, event on Saturday. Short, dated, specific.
Align the listing with the site. The same name, address, hours and service names everywhere. This is dull work, and it's the work that actually helps retrieval.
Set a rule for agencies and franchisees. Anyone with posting access needs the checklist, and you need a way to see what they've posted.

One worked example. Picture a regional pharmacy group with 60 locations and a central marketing team that pushes the same weekly post to every profile, with an offer headline and a phone number to call. After the audit, they split the content in two. Offers move to the website and email, where they were always better placed. Profiles get location-specific posts: a flu clinic date, a changed opening time, a new service. The second set takes more effort per post, but each one holds a fact that's true for that store alone, and that's what makes it useful to a local answer.

A working audit plan, with owners

The hard part of this isn't knowing what to do. It's that the work sits across teams. A simple ownership table keeps it from falling between them.

Task	What done looks like	Suggested owner	Cadence
Policy checklist	Plain-language list mapped to the Google policy page	Local SEO lead	Once, then on each policy change
Content inventory	Every description, post and attribute exported per location	Analytics or data team	Quarterly
Pattern flagging	Shared templates and risky posts surfaced for review	Local SEO with analytics	Quarterly
Rewrite and remove	Descriptions factual; promotional posts retired or moved	Content or brand team	Rolling
Access control	Named posters per location, templates approved	Marketing operations	Ongoing
Prompt tracking	Fixed local prompt set tested monthly	AEO or GEO lead	Monthly

If you run media and local together, the media teams solution page describes how teams in that position organise shared reporting. And if the real problem is that nobody can say which locations have which content live, that's a marketing operations gap. The marketing operations primer covers that framing.

How to measure the effect

Be careful here, because local AI visibility is noisy. Answers vary by user, location, phrasing and day. A single before-and-after screenshot proves nothing.

A more reliable setup looks like this.

Fix the prompt set. Twenty to fifty local-intent prompts per market, written the way customers talk, kept unchanged across the test.
Record presence and accuracy separately. Does your business appear? And does the answer get your hours, services and address right? Accuracy is often the more useful signal.
Track listing-level metrics in Google's own dashboard. Views, calls, direction requests and any messages from Google about removed content. Those are the facts you can rely on, and they sit in your account.
Tag the change date per location. Staggered rollouts across locations give you a rough comparison group, which is far better than a single cutover.
Wait long enough. Directory and index updates take time. Judge over weeks, not days.

Tools in the MediaPilot family are aimed at this kind of AI-search visibility tracking, so it's a reasonable place to look if you're building the prompt-set habit. Whatever you use, write the method down so the numbers mean the same thing next quarter.

The Ahrefs Blog has made a point that applies directly here: AI visibility data piles up quickly, and teams stall when they track everything and decide nothing. Pick three metrics tied to decisions. Drop the rest.

What not to do

Most of the damage from a policy update comes from overreaction, so this list matters as much as the one above.

Don't mass-delete everything. Old posts that are factual and harmless don't need to go. Delete what clearly breaches the policy text, rewrite what's borderline, and leave the rest.

Don't assume it's all about Google. Cleaning up your Maps content helps with one input. Your site, reviews, and third-party listings feed the same answers. A perfect profile on top of an inconsistent web presence still gives a muddy picture.

Don't stuff facts into fields that weren't built for them. If a policy tidy-up leads someone to cram keywords into the business name or description, you've swapped one problem for another.

Don't chase a workaround. Posting the same promotional message in a slightly different form is the kind of thing a policy list exists to catch, and it adds risk for no gain.

Don't promise leadership a lift. The honest pitch is that you're reducing risk and improving the quality of data that AI tools may read. Whether that moves citations in a given assistant is something you'll learn from testing, not something to forecast.

And one thing to ignore: the urge to rewrite your whole local strategy around a single policy page. It's a clarification of rules for one section. Do the audit, fix what it finds, and carry on.

Where this fits in your wider AEO and GEO work

The larger lesson is about data hygiene. AI answers pull from records, and records are only as good as the people who maintain them. A team that already keeps its analytics definitions tidy will find local content easy to govern in the same way. If you don't yet have a shared definition of what gets tracked and where, the idea behind a tracking specification transfers well: write down what each field means, who owns it, and what valid looks like.

What will probably change next? Expect more explicit rules about what business profiles can contain, and more automated enforcement over time. That's a guess, and it's labelled as one. The safe position is to build content processes that would pass a stricter version of the policy, because they cost little and they hold up either way.

Frequently asked questions

What did Google change in the Maps and Business Profiles policy?

According to Search Engine Roundtable, Google updated the advertising and solicitation section of its prohibited and restricted content policy to list what merchants and business owners can't post in their listings and posts. The exact items are on Google's policy page, so read that section directly. Use it as the basis for your audit.

Will following the policy improve my visibility in AI answers?

Not on its own, and nobody can promise that. Staying within the policy protects your profile from removal, and cleaner, factual listings give retrieval systems better material. Whether a particular assistant cites you more often is something to test with a fixed prompt set over several weeks.

Should I delete old Google Business Profile posts?

Only the ones that clearly breach the policy text, or that carry outdated facts like old hours. Harmless, accurate posts can stay. Rewrite borderline content rather than removing it, and keep a record of what you changed so you can explain any shifts in metrics.

Who should own local listing content on a multi-location team?

One named person should own the standard, usually in local SEO or marketing operations, with location managers and agencies working inside it. Give posting access to named people only, approve templates centrally, and review what's live on a schedule. Split ownership is how risky content ends up on one profile out of sixty.

How often should we re-check our listings against the policy?

At least quarterly, and whenever Google changes the policy page. Add a lighter check after any large campaign, since campaigns are when promotional content tends to reach profiles. A shared checklist makes each pass quicker than the last.

Sources

https://www.seroundtable.com/google-maps-policy-listings-or-posts-42228.html
https://ahrefs.com/blog/ai-visibility-workflow/
https://www.conductor.com/academy/aeo-geo-benchmarks-report/