Car Dealership GBP Posts: Department-Ready Examples for Sales, Service, and Parts

A dealership profile with no posts reads like a store with the lights off. The OEM incentive that expires Friday sits in a sales manager's inbox, the service lane is booked solid through tire season, and the parts counter just shelved a full accessory shipment — and none of it shows on the one Google surface most shoppers see before they ever reach your website.

Most posting advice ignores how a dealership actually works. Sales, service, and parts are separate profit centers with different triggers, different approval chains, and different ideas of a good enquiry. Telling a marketing manager to “post consistently” produces exactly that: consistent filler.

This page is a worked library of car dealership GBP posts organized by department and trigger, plus the approval-and-expiry ledger that keeps every offer accurate. Every example uses placeholders — no live prices, APR figures, or incentive percentages — because an inaccurate offer post is a compliance incident, not a marketing asset.

You will leave with the verified post mechanics from Google's own documentation, four sales patterns, four service patterns, three parts patterns, a copyable ledger, a four-week skeleton, and a measurement setup that keeps every funnel stage separate.

What a dealership GBP post has to do

Google Business Profile posts put current, department-specific information in front of people already viewing your dealership's profile — the highest-intent audience a store gets. Each post supports one next step: a test-drive request, a service appointment, or a parts enquiry. Posts are a conversion and freshness surface, not a ranking tactic.

The audience matters. People who see dealership posts are already on the profile: they searched the store's name, the brand plus a city, or tapped the pin on Maps. A service customer checking hours, a shopper comparing two franchises of the same brand, an owner holding a recall letter — all high-intent, all one tap from a next step.

Each department wants a different next step. Sales posts support test-drive and appraisal bookings. Service posts support appointment scheduling and recall routing. Parts posts support counter enquiries and fitment bookings. That is why this library is organized by profit center: a post that tries to serve all three departments serves none of them.

The three post types map cleanly onto dealership triggers: Updates carry information, Offers carry terms with a hard end date, and Events carry dated on-the-ground happenings. The selection matrix below covers the triggers a dealership actually gets.

If a trigger is not on this matrix, the test is simple: approved terms and an end date make it an Offer, real dates on the ground make it an Event, and anything else is an Update.

One honesty note before the examples. Google states that local results are based mainly on relevance, distance, and prominence, and that there is no way to request or pay for a better local ranking. Google publishes no posts-as-ranking-factor claim, so this page treats posts as a conversion and freshness surface for people already viewing your profile — and measures them that way.

The ground rules, from Google's own documentation

Google documents three post types — Update, Offer, and Event — plus scheduling, a six-month archive rule, and a review process that can reject posts. Offers must carry a title and start and end dates. Everything in this section comes from Google's Business Profile documentation, not third-party posting advice.

Everything below traces to Google's Business Profile post documentation. Where vendor blog advice conflicts with this table, the table wins.

A “not approved” status is a signal to fix the copy, not to republish the identical text and hope. Log the rejection reason in the ledger so the same wording never goes back through review.

Before any post enters that workflow, it passes this compliance checklist:

• No phone number anywhere in the post description — the profile's phone field carries the number.
• Every Offer post has an accurate end date and a named terms owner before publishing.
• No prices, discounts, APR figures, or incentive percentages in post copy — terms live on the governed destination page.
• Content stays inside Google's post content policy — no misleading or regulated content.
• No review incentives of any kind — Google permits asking genuine customers for reviews and prohibits incentivized ones.
• Every post has a logged approver, publish date, expiry date, and takedown owner before it goes live.

Three departments posting without an approval chain is how expired offers stay live. We can help map the ledger, the named owners, and the post workflow for your rooftops — your team keeps control of every term.

Book a free strategy call →

Sales department post examples

Sales posts work when they follow the dealership's real retail calendar: model-year arrivals, OEM incentive windows, event weekends, and trade-in pushes. Each pattern below pairs one trigger with the correct post type, a placeholder copy skeleton, a destination, an expiry, and a named owner. None contains live terms.

Model-year arrival announcement (Update)

Trigger: the first units of a new model year land on the lot. Copy skeleton: “The [model year] [model] has arrived at [dealership name]. See current trims in stock and book a test drive: [model page].” CTA path: the model or new-inventory page, UTM-tagged. Expiry: none fixed; ledger review when the launch window closes. Owner: sales manager approves trim claims against actual stock; marketing publishes. Model-year changeover is when loyal brand shoppers start cross-shopping next year's unit, so the post's job is to move a profile viewer to live inventory while selection is widest. Where stores slip: recycling last year's arrival post, which names trims that are no longer on the ground.

OEM incentive window (Offer)

Trigger: a factory retail program with a hard program end date opens. Copy skeleton: “[Dealership name] is participating in the current [manufacturer] retail program on eligible [model line] vehicles. Program details, eligibility, and end date: [offers page].” CTA path: the governed offers page owned by the named terms owner. Expiry: the program end date, entered as the Offer's end date. Owner: terms owner approves; marketing compliance owner takes down. An Offer requires a title and dates and carries a “View Offer” button, which matches a program that genuinely ends. The failure this pattern prevents: the program closes, the post stays live, and a shopper walks in quoting an expired program — now the desk is negotiating against the store's own profile.

Dated sales event (Event)

Trigger: a real dated event — a holiday weekend with extended hours, a model-year-end event, a ride-and-drive. Copy skeleton: “[Event name] runs [start date]–[end date] at [dealership name], with extended showroom hours and the full [franchise] line on the ground. Hours and details: [event page].” CTA path: the event info page. Expiry: event end. Owner: sales manager plus whoever staffs the event. An event post should mark a genuine operational change — extended hours, an appraisal tent, a shuttle — because shoppers learn to ignore stores whose “events” are just the normal month with a banner.

Trade-in appraisal drive (Update)

Trigger: the used-car manager needs acquisition volume ahead of a busy retail stretch. Copy skeleton: “Thinking about trading up? [Dealership name] appraises your current vehicle in store, with or without a purchase. Book an appraisal slot: [trade-in page].” CTA path: the appraisal booking or trade-in page. Expiry: ledger review at campaign end. Owner: used-car manager approves. Acquisition is the constraint on most used-car operations, and this pattern works because it asks for the vehicle, not a purchase commitment. One rule: no value promises in copy — “top dollar” claims set a number the appraiser then has to fight.

Service department post examples

Service posts feed the fixed-operations calendar: recall notices, seasonal maintenance demand, online scheduling, and service events. The patterns below keep every warranty and recall statement factual and pointed at official channels, because the service drive runs on trust and repeat visits rather than one-off urgency.

Recall-information post (Update)

Trigger: a manufacturer recall lands on models this store services. Copy skeleton: “A manufacturer recall affecting certain [make and model range] vehicles is now active. Check your vehicle through the lookup on our recall page, then schedule with our service team: [recall page].” CTA path: the store's recall-information page, which points to the official manufacturer lookup and the scheduler. Expiry: review when the recall status changes. Owner: service manager. Owners who hear about a recall search the brand and their city, and the franchise profile is where they land. Keep the post factual — no danger framing, no urgency inflation — because the store cannot confirm VIN applicability inside a post.

Seasonal maintenance reminder (Update or Offer)

Trigger: predictable seasonal demand — tire changeover season, pre-winter battery checks, pre-summer air-conditioning service. Post type: Update for the reminder; Offer only if a terms owner approves a dated special. Copy skeleton: “[Season] tire season is here. [Dealership name] handles changeovers, storage, and alignment checks — book online: [scheduler link].” CTA path: the online scheduler. Expiry: season end or offer end date. Owner: service manager. Service demand is weather-driven and it clusters; the store that posts on the first cold snap is already behind the booking wave. The reminder's job is to pull appointments into the shoulder weeks while the lane still has capacity.

Online-scheduling post (Update)

Trigger: the BDC wants more appointments landing in the scheduler instead of the phone queue. Copy skeleton: “Skip the phone queue — book service at [dealership name] online: pick a date and time, and choose a loaner or shuttle where available: [scheduler link].” CTA path: the scheduler. Expiry: none fixed; quarterly ledger review. Owner: service manager with the BDC owner. Phones jam during morning drop-off hours, and every appointment that lands in the scheduler is one the advisors do not have to take down by hand. Test the scheduler link from a logged-out phone before publishing.

Service-clinic event (Event)

Trigger: a dated clinic, such as a multi-point inspection day or an alignment-check Saturday. Copy skeleton: “[Clinic name] at [dealership name] on [date]: our technicians walk you through your vehicle's inspection results and maintenance plan. Slots and details: [event page].” CTA path: the event page with slot booking. Expiry: event end. Owner: service manager. A clinic turns the service lane from a transaction into an advisor relationship, which is where fixed-ops retention comes from. Publish only when the bays and technicians are genuinely committed — a clinic that runs out of slots by mid-morning with no fallback turns into walk-away frustration.

Service is where dealership profitability hides: fixed-ops absorption — how much of the store's overhead the service and parts departments cover — is the number general managers watch in slow sales months. Posts that keep the lane visible in the shoulder seasons matter more to that number than any sales-weekend banner.

Parts department post examples

Parts posts are the most underused of the three, because the parts counter sells to walk-ins, wholesale accounts, and service-lane attach at the same time. The patterns here cover accessory fitment, seasonal parts offers, and ordering logistics — with one hard boundary: vehicle inventory belongs in vehicle listings, not in post copy.

Accessory fitment feature (Update)

Trigger: a new accessory line or season — truck bed accessories, roof systems, all-weather mats. Copy skeleton: “Factory [accessory line] for the [model line], fitted by the technicians who work on these vehicles every day. See the range and book fitment: [accessories page].” CTA path: the accessories page or parts enquiry form. Expiry: review when stock or season changes. Owner: parts manager. Accessories are some of the best-margin work in fixed ops, and the buyer is often someone who just took delivery — already watching the store's profile. Fitment by the franchise store is the edge over online parts sellers; the post should say so.

Seasonal parts special (Offer)

Trigger: a seasonal special on a parts category, with approved terms. Copy skeleton: “[Dealership name]'s parts department is running a seasonal special on [parts category]. Terms, eligibility, and end date: [offers page].” CTA path: the governed offers page. Expiry: the offer end date. Owner: parts manager approves terms; marketing publishes; the takedown owner removes on expiry. Tires and batteries are comparison-shopped harder than almost anything else the counter sells, so the Offer format — title, dates, “View Offer” button — does the honest work: it tells the shopper exactly when the terms stop being true.

Parts hours and ordering update (Update)

Trigger: a counter-hours change, holiday schedule, or a new online parts-request route. Copy skeleton: “Our parts counter now opens at [time] on [days]. Order ahead online and pick up at the counter: [parts page].” CTA path: the parts page; the profile's phone field carries the number, never the post copy. Expiry: none fixed; review when superseded. Owner: parts manager. Wholesale accounts and walk-ins plan around counter hours, and a wrong-hours post costs a Saturday morning's goodwill with buyers who drive to you.

One boundary stays hard: posts announce and offer; they do not carry unit-by-unit inventory. Google lets eligible dealers manage vehicle listings on their Business Profile through a separate listings surface, so a “just arrived” Update points to the inventory page rather than listing stock in the post text.

The approval-and-expiry ledger

Every post goes into a ledger before it goes live: type, department, trigger, approver, compliance check, publish date, expiry date, status check, and takedown owner. The ledger is what turns posting from a creative task into an operating system, and it is what catches the expired incentive post before a shopper quotes it back to your sales desk.

An offer a shopper can screenshot is an offer the desk may be asked to honor. Dealer advertising is regulated in most states, and OEM program terms hold the store responsible for the accuracy of advertised offers — so an expired incentive post is a compliance incident with a salesperson standing in front of it, not a small marketing slip. The ledger gives accuracy an owner and a date, every time.

Copy these columns into a shared sheet or your project tool:

A filled row reads: “Q4 incentive window — Offer — Sales — [manufacturer] program [dates] — approved by sales manager — terms owner verified figures against the offers page — published [date] — expires [program end date] — live, checked [date] — takedown: marketing compliance owner.”

Two operating rules follow. Expired incentive posts come down or get updated promptly; the monthly audit in the measurement section scores exactly that. And the wider profile operations — setup, departments, category choices — belong to the dealer GBP setup guide and the GBP categories guide; this page's ledger plugs into that system rather than replacing it.

A four-week posting skeleton

There is no universal posting frequency that fits every dealership; cadence depends on staffing and on how many profiles the store runs. What follows is a capacity-based four-week skeleton — one post per department per week at most — that a single marketing manager can sustain alongside the rest of the job.

Build it from next month's real triggers: program windows from OEM communications, recall bulletins, the service seasonal calendar, parts programs. Drop each into the grid below, and leave the cell empty when nothing true is available. An empty cell is a decision, not a failure.

Groups running several rooftops replicate the grid per rooftop. Stores with separate profiles for sales and service assign each post to the profile that represents that entity, and the ledger records which profile published what. The cadence question itself — how often is right for your situation — belongs to the GBP posting frequency guide; this skeleton is a starting grid, not a prescription.

Drafting speed is not the constraint; approval is. If you draft with the GBP post generator or a tool from the GBP posting tools roundup, route the output through the same ledger. And while GBP posts are not social posts, the photography overlaps — the Social Media module publishes scheduled posts to Instagram, LinkedIn, X, and Facebook, so one model-arrival shoot can feed both surfaces, with the GBP copy still going through this approval chain.

A skeleton only works if the approvals behind it do. Bring your department owners and event calendar, and we will walk through how the workflow fits your store.

Book a free strategy call →

Measuring posts without fooling yourself

GBP performance data tells you what happened on the profile; GA4 and your CRM tell you what happened after the click. Keep every funnel stage — impression, click, call click, form, qualified enquiry, booked appointment, completed job — as a separate entry with its own source system, and never merge stages to make a number look bigger.

Tag every post link with a consistent UTM convention — source, medium, campaign, and a content identifier for the individual post — so GA4 can separate post sessions from everything else on the profile. GA4 recommends distinct lead events — generate_lead, qualify_lead, working_lead, close_convert_lead — and the business defines what each stage means. For a dealership, generate_lead might be a submitted test-drive form or a connected call; qualify_lead might be the BDC confirming the shopper is in-market on an eligible model. Write your definitions down; the labels are yours.

With stages separated, three formulas cover almost every useful question about posting. Keep every field — numerator, denominator, window, source system, owner, exclusions — and do not turn the outputs into portable benchmarks.

The most common reporting fiction in dealership marketing is counting every call click as an enquiry. A call click is a tap on the profile's call button; it includes misdials, parts price checks, and your own staff testing the listing. The connected call lives in the phone log, the qualified version lives in the CRM, and confusing the three inflates the channel that needs the least defending. The same separation applies to paid surfaces: if the store also buys leads through Google Local Services Ads or third-party marketplaces, those enquiries arrive in their own dashboards — keep them in their own source systems and out of the post-attributed numbers entirely.

Frequently asked questions

These are the questions dealership marketers ask once the library and ledger are in place — where posts actually show up, how often to publish, whether posts move rankings, phone numbers, post lifespan, which profile posts for which department, and what never belongs in a post at all.

Where can I see Google Business posts?

Google says posts appear in the Updates or Overview tabs and in the “From the owner” section of your Business Profile on Search and Maps. To see yours as a shopper does, search the dealership's name in a logged-out browser and scroll the profile panel. If a post is missing, open the Business Profile manager and check its status: live, pending, or not approved.

How often should a car dealership post on Google Business Profile?

As often as each department can supply accurate, approvable content — there is no universal number. A single-rooftop store with one marketing manager usually sustains the four-week skeleton in this guide; groups running separate sales and service profiles multiply the workload. Cadence decisions belong to the GBP posting frequency guide; this page's rule is that approval capacity and expiry ownership set the limit, and a skipped week always beats an inaccurate post.

Do GBP posts improve local rankings?

Google publishes no claim that posts are a local ranking factor. Its documentation says local results are based mainly on relevance, distance, and prominence, and that there is no way to request or pay for a better local ranking. Treat posts as a conversion and freshness surface for people already viewing your profile, and measure them on qualified enquiries rather than ranking movement.

Can I put a phone number in a GBP post?

No — Google warns that a phone number in the post description may get the post rejected. The profile already has a phone field, and call clicks from the profile are tracked in GBP performance reporting. If a department needs its own line, that is a profile-architecture question for the dealer GBP setup guide, not a reason to force a number into post copy.

How long do GBP posts last?

Google's documentation says posts older than six months are archived unless a date range is set, which is why accurate end dates on Offer and Event posts matter. Archived is not the same as gone, and it is not the same as accurate. Your ledger should still remove or update any post whose offer, dates, or facts have expired, whatever Google's archive timing does.

Should sales, service, and parts post from the same profile?

It depends on the dealership's profile architecture. Google's guidelines require each Business Profile to represent a real-world entity accurately, and dealer groups commonly run separate profiles for sales, service, or a collision center when those qualify as distinct entities under the current guidelines. That architecture decision comes first — the dealer GBP setup guide and the GBP categories guide cover it — and the ledger then records which profile published which post.

What should a dealership never post?

Three things. First, content that violates Google's post content policy — misleading or regulated content gets posts rejected. Second, incentive figures, prices, or APR terms that a named terms owner has not approved, because an inaccurate offer is a compliance incident. Third, review incentives: Google permits asking genuine customers for reviews and prohibits incentivized ones, so “leave a review, get something” posts are out. The review management guide covers the compliant way to earn reviews.

Start with one department and one trigger

Start with one department and one trigger — usually the next real event on the retail calendar: an incentive window, a tire season, a dated sales event. Run it through the ledger, tag the link, and audit at month-end. Once the first loop runs clean, add the other two departments.

The working sequence:

1. Pick the next real trigger for one department — the closest dated event on the retail calendar.
2. Fill the copy skeleton with placeholders resolved against the source record, and route it to the approver.
3. Log the ledger row, publish, tag the link, and verify the post's status after it goes live.
4. At month-end, run the offer-hygiene audit and the two measurement formulas before planning next month's grid.

If you would rather not run the workflow by hand, theStacc's Local SEO module covers GBP posts, review replies, citations, and rank tracking, and the Social Media module publishes scheduled posts to Instagram, LinkedIn, X, and Facebook. Your store keeps ownership of terms, approvals, and expiry. See how it fits stores like yours on the auto dealers page.

Start with one department, one trigger, one ledger row. We will review your current post workflow and show you where the Local SEO module fits.

Book a free strategy call →

Sources & references

Siddharth Gangal

Founder and CEO

Founder and CEO at theStacc. Previously co-founded ARKA 360 (solar SaaS) out of IIT Mandi in 2017. Builds AI systems that automate SEO at scale.

LinkedIn About theStacc