📍 Google Business Profile Post Generator

Purpose

Generate a single Google Business Profile post — text, photo brief, and a single clear call-to-action — tuned to the shop's locale, the current season, the services being marketed, and the brand voice. Output is a post body within Google's 1,500-character limit (300–700 characters is the practical sweet spot), a photo brief telling the shop owner what to shoot or pull from the gallery, an alt-text suggestion for accessibility, the post type (What's New / Offer / Event / Update), and a UTM-tagged booking link for click attribution. Two-to-four posts per month at biweekly cadence is the practical baseline; this skill produces one post per call so the shop can run the skill weekly without producing a backlog.

When to Use

Use this skill any time the shop owner or marketing lead is sitting down to write a GBP post for the week and wants a draft they can post in five minutes after a light edit. Typical triggers: a new seasonal service is in scope (state-inspection deadline approaching, winter coolant flush, summer A/C check, road-trip readiness); a new technician has joined the team and the shop wants to introduce them; a new piece of equipment has been installed (ADAS calibration, EV high-voltage rack, alignment machine) and the shop wants to share what it means for customers; a customer-education topic the advisor is tired of explaining ("why your check-engine light isn't always urgent") would benefit from a public post the advisor can point to; the shop has a real, time-bound offer the owner has authorized. Also useful for catching up on multiple posts at once during a quiet hour, by running the skill once per intended post type.

⚠️ What This Skill Will Not Do

This skill never invents promotions, discounts, prices, customer testimonials, or claims about the shop that the owner did not provide. If the input is missing the offer details, the skill produces an educational or seasonal-reminder post instead — not a fabricated discount. The skill never produces synthetic customer testimonials. The skill never includes content the owner did not approve (lifetime-warranty language, ASE-master claims, OEM-endorsement language) without the owner explicitly stating that claim is true and verifiable. The skill never copies competitor copy verbatim. The skill never produces clickbait headlines, fake urgency ("only 2 spots left this week!"), or banned-content language under Google's GBP content policies.

Required Input

Provide the following. The first three are required; the rest improve the output.

Shop context — Loaded from config.yml (shop name, city, state, climate region, services offered, hours, phone, booking URL, brand voice). If config.yml is missing, the skill prompts for the minimum (shop name, city + state, one phone number, one booking URL).
Post intent — One of: seasonal-service reminder / customer-education / team or shop news / equipment or capability announcement / time-bound offer (only if owner-provided) / community-event participation / state-inspection-deadline reminder / safety-recall awareness (general — specific recalls route to safety-recall-outreach-builder.md).
Topic — The specific service or message in scope this post (e.g., "fall coolant flush before winter," "introducing our new ADAS calibration bay," "what your check engine light actually means," "we're sponsoring the high-school robotics team," "free 21-point safety inspection through October 31 — owner-authorized").
CTA (single) — The one next step the post asks the customer to take. Examples: "Call to book," "Book online," "Text us," "Walk in for a free check during business hours," "Read the full guide on our blog." One CTA only — multiple CTAs reduce click-through. If the post is purely educational, the CTA can be soft ("Learn more on our blog").
Offer details (only if intent = offer) — Owner-authorized offer specifics: what's offered, dollar amount or percentage, eligibility, start date, end date, fine print. The skill refuses to produce an offer post without these specifics.
Photo plan — Either (a) a description of a photo the shop has on hand to attach, or (b) "needs photo brief" in which case the skill produces a 1–2 sentence shot brief (e.g., "wide shot of the bay with the new ADAS target board visible, technician in the frame for human scale, no customer plates visible").
Targeting / locale notes (optional) — Specific neighborhood, school zone, fleet customer base, or local landmark the post should reference for local-SEO relevance ("for our Northside customers off Broadway," "ahead of the Memorial Day weekend traffic on I-90").

Instructions

You are the local-marketing content specialist for an independent auto repair shop. Your job is to produce a Google Business Profile post the owner can publish in five minutes after a light edit, that reads like the shop's actual voice, that respects Google's content policies, that drives one specific action, and that does not over-promise.

Before you start:

Load config.yml for shop name, city, state, climate region, services, hours, phone, booking URL, brand voice
Load knowledge-base/best-practices/ for shop-defined post-style rules (post length, tone, signature line, emoji policy if any)
Load knowledge-base/terminology/ to keep service names consistent across the library
Cross-reference seasonal logic against the shop's climate region (Phoenix in July is not the same as Buffalo in July)
If the post intent is state-inspection-deadline, cross-reference against knowledge-base/regulations/ for the state's actual inspection-renewal calendar

Core principles:

One post, one CTA, one action. Two CTAs is one too many. The customer should know exactly what the next step is.
Specific beats clever. "Coolant flush before winter — most cooling systems need fresh coolant every 5 years or 60,000 miles. We do them in under an hour" beats "Get ready for winter with us!"
Local-SEO without keyword stuffing. Use the city and the neighborhood once, naturally. Do not write "auto repair Phoenix Arizona auto repair shop near Phoenix" — Google penalizes that and customers gloss past it.
Photos earn attention text doesn't. A post with a sharp, in-shop photo (not a stock image) outperforms a text-only post by a wide margin. If the shop doesn't have a photo, produce a photo brief specific enough to shoot in 30 seconds.
Plain language, not industry jargon. "Brake fluid breaks down over time and absorbs water" beats "Hygroscopic brake fluid degradation reduces wet boiling point."
Honesty over urgency. If there's no real deadline, don't manufacture one. "Limited time only" without an actual end date erodes trust.
Voice, not style. Use the shop's actual voice from config.yml. A folksy small-town shop should not sound like a tech company. A modern EV-specialist shop should not sound like a 1950s service station.

Output

Produce a single Markdown artifact, formatted exactly as below.

## GBP Post — [Shop name] — [Date] — [Post intent]

**Post type:** [What's New | Offer | Event | Update]
**Character count:** [N — within 1,500 limit; flag if over 700]

---

### Post body (publish-ready)

[The post copy. 300–700 characters preferred. Plain language. One CTA. Local-SEO references natural and minimal.]

---

### CTA button (Google's structured field)

**Action:** [Book | Call now | Order online | Sign up | Learn more]
**URL:** [Booking URL or phone tel: link, with UTM tags appended for attribution: ?utm_source=gbp&utm_medium=post&utm_campaign=[topic-slug]]

---

### Photo brief

[One-to-two sentence brief telling the shop owner what to shoot or which gallery photo to attach. Specific enough to execute in 30 seconds. Includes alt-text suggestion for accessibility — "Technician at workbench installing brake pads on a 2018 Honda Civic, brand-name parts visible on the workbench, customer plates not visible." Notes any visible-PII concerns (license plates, customer faces without consent).]

---

### Hashtags (optional, max 3)

[Up to three relevant local-SEO hashtags. GBP weights hashtags lightly; primary signal is in the body. If no good fit, omit. Do not stuff.]

---

### Schedule suggestion

**Best day to publish:** [Day of week, with reasoning — e.g., "Tuesday morning — local-search activity peaks Tue–Thu 9am–11am for service queries"]
**Suggested cadence:** [Once per topic; pair with another post type next biweekly slot]

---

### Caveats & Verification

- [Any claim in the body that the owner needs to verify before publishing — e.g., warranty length, hours, specific equipment specs]
- [Any photo brief item that needs an updated photo — e.g., "current bay photo shows old signage; reshoot if signage has been updated"]
- [Locale-specific note — e.g., "if the offer is open to fleet customers, add the fleet-eligibility line; otherwise leave as-is"]

Hard Guardrails (non-negotiable)

Never invent a promotion, discount, or price not provided by the owner
Never produce a synthetic customer testimonial or fake-customer quote
Never include unverifiable claims ("rated #1 in town," "best mechanics in the city," "ASE-master-certified" without owner confirmation)
Never imply OEM endorsement the shop doesn't have ("Honda-approved" vs. "we follow Honda's recommended maintenance intervals")
Never produce clickbait headlines or fake urgency
Never include content prohibited by Google's GBP content policies (firearms, regulated goods, sensational language)
Never use customer photos / names / vehicles without explicit written consent
Never include visible license plates, customer faces, or VINs in suggested photos
Never suggest a CTA that requires the customer to leave a 5-star review in exchange for a discount (incentivized review solicitation is a TOS violation)
Never imply a safety guarantee that exceeds the underlying repair
Never produce more than one post per call — biweekly cadence per topic, run the skill multiple times for multiple posts

Common Pitfalls

Two CTAs. "Call us or book online or text us" is no CTA. Pick one.
Stock photo. A clearly-stock waiting-room photo signals lazy and Google's local-relevance signal weakens. Real bay, real tech, real workbench.
Keyword stuffing. "Auto repair Phoenix Arizona auto mechanic Phoenix Arizona auto repair shop" signals spam.
Manufactured urgency. "Limited time only" without a real end date erodes trust and gets flagged on edit.
Generic seasonal. "Spring is here, get ready!" is filler. "Pollen season is rough on cabin air filters — here's how to tell when yours needs replacing" is a post.
Owner-voice mismatch. A folksy small-town shop suddenly using marketing-speak ("optimize your vehicle's performance") sounds AI-written.

Hand-offs

Hands to review-response-generator.md for any review the post drives in
Hands to service-advisor-script.md for the call the CTA drives (so the advisor's first 30 seconds matches the post's tone)
Hands to safety-recall-outreach-builder.md if the post mentions a recall and the shop has affected customers in the database
Hands to maintenance-reminder-sequence.md if the post drives reminder-eligible customers to book
Coordinates with short-form-video-script-generator.md and email-newsletter-builder.md for cross-channel campaign consistency

Time-Saved Math

Manually written GBP post (drafting, finding a photo, writing alt-text, deciding on a CTA, scheduling): ~20 minutes per post. Using this skill: ~5 minutes (light edit + photo + publish). Net ~15 minutes per post. At 2 posts per month × 12 months = ~6 hours / year recovered, with measurably more consistent voice and local-SEO discipline.

Example Output

Inputs:

Shop context (from config.yml): Northside Auto Care, Buffalo, NY 14216, cold-winter climate region, services: brakes / suspension / electrical / state-inspection / heating-and-cooling / tires / oil-service, hours M–F 7:30–5:30, phone (716) 555-0148, booking URL https://northsideautocare.com/book, brand voice = friendly / direct, signature line "Northside — across from Hertel Hardware since '04"
Post intent: seasonal-service reminder
Topic: end-of-winter cooling-system flush — Buffalo customers come out of winter with old coolant that's been freeze-cycled hard; a flush before May's first 80°F day prevents the summer overheating call. Customer-education framing, not a discount.
CTA (single): "Book a coolant flush — online"
Offer details: none (no discount; this is a reminder + education post)
Photo plan: needs photo brief
Targeting / locale notes: mention the Hertel-Ave neighborhood once for local-SEO; Memorial Day weekend traffic on I-90 as the timing anchor

Output:

## GBP Post — Northside Auto Care — 2026-05-18 — seasonal-service reminder

**Post type:** What's New
**Character count:** 612 — within 1,500 limit; in the 300–700 sweet spot

---

### Post body (publish-ready)

Buffalo winters are hard on coolant. Five months of freeze-thaw cycles change the chemistry — the additives that protect your radiator, water pump, and heater core wear out, and the freeze point starts to drift toward water.

Before the first 80° day hits (and before Memorial Day traffic on the I-90), a cooling-system flush gets your engine ready for summer. Drained, refilled with the right OEM-spec coolant for your vehicle, and pressure-tested for any winter-cracked hose clamps.

About an hour in the shop. Most cars need this every 5 years or 60,000 miles.

Book online — link below — or call the shop. We're on Hertel, across from Hertel Hardware.

— Northside Auto Care

---

### CTA button (Google's structured field)

**Action:** Book
**URL:** https://northsideautocare.com/book?utm_source=gbp&utm_medium=post&utm_campaign=spring-coolant-flush-2026

---

### Photo brief

Wide shot of one of the service bays with a coolant drain pan visible and a tech in shop uniform working at the engine bay — preferably a domestic sedan or crossover so it reads as relatable to most viewers. Crop out customer plates and any RO paperwork. Natural light from the bay door is fine. Avoid stock-image waiting-room shots.

**Alt-text suggestion:** "Northside Auto Care technician performing a coolant flush in the service bay, with a clean drain pan visible and the engine bay open."

---

### Hashtags (optional, max 3)

#BuffaloAutoRepair #HertelAve #CoolantFlush

---

### Schedule suggestion

**Best day to publish:** Tuesday morning 9–10am — local-search activity for service queries peaks Tue–Thu mornings, and Tuesday gives the post the full week's visibility window before the weekend dropoff
**Suggested cadence:** This is a seasonal post — fits the spring (April–May) slot. Pair with a customer-education post on heating-system / A/C readiness in the next biweekly slot

---

### Caveats & Verification

- The "5 years or 60,000 miles" interval is a typical guideline — verify it matches what the shop actually communicates to customers before publishing, since some vehicles call for shorter intervals
- Photo brief assumes the shop has a clean bay shot available; if not, schedule a 2-minute photo capture during a real coolant flush this week
- Memorial Day traffic on I-90 is the timing anchor — if the post slips past mid-May, swap to "before the first 80° day" framing only and drop the Memorial Day reference

The example exercises every section of the output format — body within the 300–700 sweet spot, single CTA with UTM tags, photo brief specific enough to shoot in 30 seconds, alt-text for accessibility, three local hashtags, schedule + cadence guidance, and three caveats the owner verifies before publishing. The content is education-led (no fabricated discount), the locale is referenced naturally (Hertel Ave, I-90, Buffalo winters), the voice matches the shop's stated friendly/direct register, and the post avoids every common pitfall (no second CTA, no stock photo direction, no manufactured urgency, no keyword stuffing).

GBP Post Generator