Industry News

Google Business Profile Posts Can Now Be Removed for Unverified Contact Information

By Paul Lovell · September 27, 2026 · 4 min read

Google's Business Profile photos, videos & posts content policy now includes a dedicated section on posts that contain contact information, and it's a removal risk many businesses won't be watching for.

What the policy says

Under "Posts including contact information," Google states:

"To avoid fraud or abuse, we may remove posts with unverified contact information. This includes phone numbers, email addresses, and social media handles."

"Alternatively, attach a Call now button to your post. This uses your verified Business Profile phone number so customers can contact you."

That second line is the actionable part: Google isn't banning contact information from posts outright, it's steering businesses toward the Call Now button, which pulls the number from the profile's own verified phone field rather than free text typed into a post.

What "unverified" means here

Google hasn't published a precise definition of what counts as verified versus unverified contact information inside post text. It isn't clear, for instance, whether typing your own verified Business Profile number directly into a post's body copy is treated as safe because it matches your listing, or flagged anyway because the enforcement is about the post text itself, not just what number appears. Until Google clarifies, the safer assumption is that any phone number, email address or social handle typed into the post body — rather than attached via the Call Now button — carries some removal risk.

Why it matters

Posts get used constantly for genuinely useful contact-driving content: "call this number for today's offer," "DM us on Instagram," "email bookings@..." Multi-location and franchise accounts, where a location manager might post a direct line that differs from the main listed number, are the most exposed — that's exactly the kind of unverified, non-matching number this policy targets.

This sits alongside a wider pattern in Google's local product this year: identity and contact-detail verification has been tightening across Business Profiles generally, not just in Posts. Treating this as an isolated Posts-only rule risks missing the direction of travel — Google is increasingly unwilling to surface any contact route it can't independently confirm belongs to the business, wherever that route appears on the profile.

A removed post costs more than the content itself. Repeated policy violations across Google Business Profile generally carry escalating consequences, and posts are one of the few profile elements a business fully controls the wording of — which also makes them one of the easier places to accidentally trip a policy that's aimed at fraud prevention rather than at ordinary business owners.

Franchise and agency exposure

Any workflow where a template or bulk-posting tool inserts a phone number pulled from a spreadsheet, CRM, or franchise-specific field — rather than pulling it live from the verified Business Profile record — is exposed here by design, not by accident. The number in that spreadsheet might be entirely correct and still get treated as "unverified" by this policy, because verification in Google's sense means matching what's on file for that specific listing, not simply being a real, working number.

Agencies managing bulk Posts across multiple locations should check whether their publishing tool supports the Call Now button natively, or whether it's still inserting raw text phone numbers into post bodies as a matter of habit.

What to do

  • Stop typing phone numbers, emails or social handles directly into post body text.
  • Use the Call Now button (pulls your verified Business Profile number) for phone contact.
  • For social handles or email, link out via the website field or a landing page rather than posting the raw contact detail.
  • Audit scheduled and templated posts now, especially any multi-location workflow that reuses a location-specific number in post copy.

The unanswered question

What Google hasn't clarified is whether this is enforced by automated detection at the point of publishing, by review after a complaint, or both. That distinction matters practically: if it's automated pattern-matching against phone-number-shaped text, businesses should expect near-immediate removal and can test cautiously; if it's complaint-driven, a policy-violating post could sit live indefinitely until someone reports it, then disappear without warning. Until Google says more, the only safe assumption is that a violation is a matter of when it's caught, not whether it counts as one.

Sources