Google Business Profile posts can share updates, offers, and event details on Search and Maps. Each type carries different fields: offers require a title and dates, while events need a title and start and end information. Google reviews posts after publication, and a post can be live, pending, or not approved. The lesson is therefore both editorial and operational.

VISUAL LESSON

What you will learn

  1. 01Choose the correct Update, Offer, or Event post type.
  2. 02Create, schedule, and quality-check the post.
  3. 03Verify review status, destination behavior, and expiry ownership.
Google Business Profile update, offer, and event cards pass through content, date, destination, review, and expiry checks
A local post succeeds operationally when the promise, post type, dates, destination, policy status, and end-of-life action agree.

ILLUSTRATIVE WORKED EXAMPLE

Plan an illustrative four-week post mix

Useful updatesService or news
4
Verified offersTerms and dates
2
Real eventsStart and end
1
Reserved capacityCorrection or gap
1 slot
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Create and verify a Business Profile post

Brief01Choose one customer action

Record verified Profile, audience, Update/Offer/Event type, promise, source facts, photo or video, CTA, destination, dates, timezone, terms, reviewer, and expiry owner.

Create02Open Posts and Add post

Select the current post type, complete required and optional fields, add accessible media and trusted link, schedule or repeat only when accurate, preview, and publish.

Verify03Read status and live experience

Check Live, Pending, or Not approved; inspect Search and Maps on mobile and desktop, test CTA and terms, correct issues, and record removal or refresh date.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Customer promise → matching post type → reviewed publication → expiry control

ChooseUpdate, Offer, or Event
PublishComplete accurate fields
MaintainStatus and expiry

THE LEAD ATLAS METHOD

Lead Atlas Data can research contacts for the campaign’s chosen business categories, locations, and market, while Google Business Profile posts educate people already discovering the business through local search.See how custom list research works ↗
01

Write the post truth sheet

Record the verified Business Profile, owner, audience, one useful customer action, source facts, post type, title, description, media, CTA, destination, dates, timezone, offer terms, event details, accessibility, regulated-industry review, support path, approval, and expiry action.

Do not use a local post to invent urgency, availability, reviews, prices, awards, event speakers, or conditions. Confirm the landing page and staff can honor the same promise before publication.

02

Choose Update, Offer, or Event

Use an Update for current business information, news, or a customer action supported by description, media, and a link button. Use an Offer for a real promotion with title, dates and times, and optional coupon, terms, link, and media. Use an Event for a real event with title and start and end details.

If start or end times are omitted, Google says an Event can show as lasting 24 hours on the event dates. Add complete times and timezone when attendance depends on them, and do not publish an Offer when the destination cannot show its material terms.

03

Create, schedule, and preview

Open the managed Business Profile, choose Posts and Add post, select the type, complete the available fields, add owned or licensed media, use a trusted destination, and schedule or repeat only when the information will remain accurate. Preview copy, crop, dates, CTA, terms, and mobile readability.

Google notes that phone numbers in a post description might cause rejection; use the supported Profile fields and action paths appropriately. Keep spelling professional, avoid distracting or auto-generated filler, and review special rules for regulated goods or services.

04

Verify review status and live placement

After publishing, inspect whether the status is Live, Pending, or Not approved. If not approved, read the indicated policy reason and correct the underlying content rather than repeatedly reposting variants. Pending content is not visible to customers.

Check Search and Maps on representative mobile and desktop views, recognizing placement can vary. Test the action button, landing page, dates, code, booking or order flow, accessibility, analytics, and customer-support answer.

05

Maintain and retire the message

Monitor status, clicks where available, destination actions, questions, bookings, redemptions, attendance, support burden, and operational changes. Edit or delete inaccurate posts promptly. Google notes posts older than six months are archived unless a date range is set.

Deliverable: post truth sheet, type decision, source evidence, media rights and alt-text plan, scheduled post capture, live-status proof, Search and Maps QA, CTA test, offer or event terms, correction log, expiry action, performance review, and owner.

THE TAKEAWAY

Choose the post type from the customer promise, keep dates and destination terms complete, verify the live status rather than assuming publication, and maintain an expiry owner for every time-sensitive message.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.