Google Business Profile Optimization Checklist — Rebuilding Seminars

Generated: 2026-05-07 Source guidance: Google's 2026 GBP best-practices (relevance / proximity / prominence triad), AI Overview citation patterns, Local Pack ranking factors, decay-rate research (30-day inactivity penalty).

Why GBP matters most for this business: Rebuilding Seminars competes for "divorce support groups near me" (vol 2,300, KD 1, the highest-leverage in-niche keyword). That query triggers a Local Pack 100% of the time. GBP optimization is the single biggest lever on the highest-volume target keyword. It also strongly influences AI Overview citation, which Google now pulls directly from GBP services / Q&A / description fields for "near me" intent.

Owner key:

Bob = the facilitator (account holder; identity-verified actions only)
Charlie = the AI assistant (does the work, drafts, optimizes, monitors)
Annette = strategic review / approves spends / decides ambiguous calls
Auto = scheduled / automated by Charlie or a tool

Time estimates are total effort, not calendar time.

1. Setup & Claim (5-7 items)

1.1 Claim or transfer the profile to Bob's verified Google account

Action: Log in to https://business.google.com with the email Bob will own long-term. Search for "Rebuilding Seminars" + Niwot. If profile exists, claim it; if Google says someone else manages it, request ownership transfer.
Why: Without verified ownership, none of the rest works. Profile must belong to Bob's permanent Google account, not a partner / staffer / spouse / agency.
Who: Bob (must be his identity on the verification step) + Charlie (drafts the verification submission)
Time: 30 min

1.2 Complete identity verification (video selfie + address postcard fallback)

Action: Google's 2026 default is a 30-second video selfie verification with the business address visible. If video fails, request the postcard as fallback (5-7 days).
Why: Unverified profiles do not appear in Local Pack, do not appear in Google Maps, and are excluded from AI Overview citations. This is a hard gate.
Who: Bob (only — identity-bound)
Time: 15 min active, 5-7 days waiting if postcard

1.3 Confirm NAP exactly matches the schema LocalBusiness JSON

Action: Compare GBP business name / address / phone against strategy/schema/local-business.json. Both must be byte-for-byte identical.
Why: Google cross-references GBP NAP against on-site schema and citation directories. Mismatches trigger data-quality flags that suppress Local Pack rankings.
Who: Charlie (compare) + Bob (correct on GBP if mismatch found)
Time: 20 min

1.4 Set primary category: "Counselor" or "Marriage or Relationship Counselor"

Action: In GBP → Edit Profile → Business Category, set primary to the most specific match for divorce-recovery facilitation. Top candidates: "Marriage or Relationship Counselor", "Counselor", "Mental Health Service", "Coaching Center". Decision needed from Bob/Annette.
Why: Primary category is the single highest-weight ranking factor in Local Pack. It dictates which "type of business" queries the profile competes for. Get it wrong and no other optimization compensates.
Who: Annette (decision) + Bob (sets it) + Charlie (presents the 3-4 candidates with pros/cons)
Time: 30 min

1.5 Add 5-9 secondary categories

Action: Add: "Counselor", "Life Coach", "Educational Institution", "Mental Health Service", "Non-profit organization" (if applicable), "Workshop". Cap at 9 — past 9 the marginal weight drops sharply.
Why: Secondary categories expand the query universe the profile competes for without diluting the primary. Each additional relevant category adds a long-tail opening.
Who: Charlie (drafts) + Bob (approves + adds)
Time: 15 min

1.6 Set service-area mode (NOT storefront mode)

Action: GBP → Profile Type → "I serve customers at their location" (or hybrid if Bob occasionally hosts at a fixed venue). Define service-area cities from strategy/data/cities-within-100mi-niwot.json once that file is generated.
Why: Storefront vs. service-area changes which Local Pack queries you appear in. A service-area business shows up in Boulder, Longmont, Denver pack queries; a storefront shows up only in Niwot.
Who: Bob (sets it) + Charlie (drafts city list)
Time: 20 min

1.7 Hide the physical street address (service-area best practice)

Action: When service-area mode is on, GBP gives the option to hide the street address from public display. Turn it on. Address still verifies the listing internally.
Why: Bob runs cohorts at confidential venues, not a retail storefront. Public street display invites unwanted in-person visits and dilutes the service-area signal.
Who: Bob
Time: 5 min

2. Profile Completion (8-10 items)

2.1 Write a 700-character business description optimized for "near me" intent

Action: Draft a 700-character (max allowed) description that answers "what is this business / who is it for / where does it serve / what makes it different." Front-load the keywords "divorce support group", "Bruce Fisher Rebuilding Blocks", "Boulder / Front Range / online".
Why: Google pulls this field heavily for AI Overview citations on "divorce support group near me" queries. Front-loading keywords boosts both AI Overview and Local Pack relevance.
Who: Charlie (drafts) + Bob (voice review) + Annette (final approval)
Time: 45 min

2.2 Add detailed service entries for every offer

Action: Under Services, add: "10-Week Rebuilding Workshop (in-person)", "10-Week Rebuilding Workshop (online)", "1:1 Divorce Recovery Coaching", "Facilitator Training". For each: name, description (250-300 char), price (or "starting at"), duration.
Why: GBP's Services section is one of the highest-cited fields by AI Overviews in 2026. Detailed services = more "near me" query matches.
Who: Charlie (drafts all entries) + Bob (price + approval)
Time: 60 min

2.3 Set business hours that match real availability

Action: Enter the hours Bob actually responds to inquiries (not session hours, which are evening). Most likely Monday-Friday, 9am-5pm. Mark holidays.
Why: Hours-mismatch is a top reason GBP profiles get demoted in Local Pack. Google measures user clicks on "directions" / "call" against listed hours.
Who: Bob
Time: 10 min

2.4 Add the business phone number (consistent with on-site + schema)

Action: Use one phone number across GBP / website footer / schema JSON / every directory citation. If Bob wants to keep his personal number private, set up a Google Voice number dedicated to the business.
Why: NAP consistency. Different phone numbers across surfaces is the single most common reason Google de-ranks a local business.
Who: Annette (decide: personal vs. Google Voice) + Bob (publishes) + Charlie (verifies all surfaces match)
Time: 30 min

2.5 Add the website URL (root domain)

Action: Point to https://___DOMAIN___/ (root, not a subpage). Google interprets the linked URL as the canonical home for the business entity.
Why: Root-domain GBP link transfers stronger authority signal than a deep-page link. Deep-page links should be added later as Booking-link / Menu-link / Appointment-link sub-fields.
Who: Bob
Time: 5 min

2.6 Add the Booking / Appointment URL

Action: Set the Booking URL to the cohort registration page (e.g., /workshops/). When a workshop is open for enrollment, this gives users a one-click path from Local Pack to the signup form.
Why: GBP "Book" buttons drive 3-5x higher Local Pack click-through than profiles without one. AI Overviews preferentially cite businesses with bookable links.
Who: Bob
Time: 10 min

2.7 Add attributes (LGBTQ+ friendly, online appointments, identifies-as-women-owned, etc.)

Action: Walk through GBP's full attributes list. Likely toggles: "Online appointments", "Onsite services", "LGBTQ+ friendly" (if accurate), "Wheelchair accessible parking" (if venue supports it). Skip any that aren't truthful.
Why: Attributes appear as filters in Google Maps Search and as inclusion signals in AI Overview answers. Toggling truthful attributes expands the queries the profile matches.
Who: Bob (truth check) + Charlie (presents the list)
Time: 20 min

2.8 Connect the social profiles (sameAs alignment with schema)

Action: Link Facebook, Instagram, LinkedIn (if active). Make the URLs identical to the sameAs array in strategy/schema/local-business.json.
Why: Cross-surface entity reconciliation. Google reads matching sameAs URLs across schema + GBP as evidence the entity is consistent and legitimate.
Who: Bob (provides URLs) + Charlie (verifies match)
Time: 15 min

2.9 Add languages spoken

Action: Add "English" minimum. If Bob facilitates in Spanish or another language, add those — they unlock Spanish-language Local Pack queries (high-leverage given the Front Range Spanish-speaking population).
Why: Language attribute is one of the underused Local Pack ranking signals for bilingual markets.
Who: Bob
Time: 5 min

2.10 Set up the From-the-Business / About / "Why us" sections fully

Action: Fill every optional field GBP offers — opening date, "from the business" short narrative, identity attributes. Empty fields = lost ranking weight.
Why: Profile-completeness is a documented ranking factor. Google rewards businesses that use every field over those that leave blanks.
Who: Charlie (drafts) + Bob (review)
Time: 45 min

3. Reviews Strategy (5-7 items)

3.1 Establish a consent-first review collection workflow

Action: At week 8 of every cohort (after participants have measurable progress on the Fisher Scale but before the cohort ends), Bob sends a one-paragraph email asking participants who feel comfortable to leave a Google review. Include a direct review link. Never offer incentives (Google policy violation).
Why: Reviews are the single highest-correlation Local Pack ranking factor in 2026 — quantity, recency, response rate, star rating, and review content all matter. Recency outranks total count: 5 reviews in the last 30 days beats 50 reviews from 2 years ago.
Who: Bob (sends; only he has the participant relationship)
Time: 15 min per cohort, recurring

3.2 Generate the unique review-link shortcut once

Action: From GBP → Get more reviews → copy the short URL. Paste it into the cohort week-8 email template, on the workshop confirmation page, and on a printable card Bob can hand out at the final session.
Why: Friction-reduction. Most people who would happily leave a review never get past Google's "Search for the business" step. A direct link 3-5x's review submission rate.
Who: Charlie (extracts URL + builds templates)
Time: 30 min

3.3 Respond to every review within 48 hours, in Bob's voice

Action: Charlie monitors GBP daily; drafts response in Bob's voice (warm, brief, specific to the review's content); Bob reviews and posts. Never templated — Google detects copy-paste responses.
Why: Response rate is a documented ranking factor. AI Overviews cite reviews from businesses with high response rates more often than from non-responsive businesses.
Who: Charlie (drafts) + Bob (approves + posts)
Time: 5 min per review

3.4 Build the response playbook for negative reviews

Action: Draft a 1-page playbook covering: 5-star → thank, name something specific; 4-star → thank, address what kept it from 5; 3-star and below → acknowledge, take it offline (offer phone or email), never argue publicly. Pre-draft 3-4 negative-review response templates Bob can adapt.
Why: Negative reviews handled poorly tank Local Pack rankings AND scare off prospects. Handled well, they BUILD trust — research shows businesses with a few thoughtful negative-review responses convert better than 100% 5-star profiles (which read as fake).
Who: Charlie (drafts playbook) + Annette (approval) + Bob (uses it)
Time: 90 min upfront, 10 min per negative review thereafter

3.5 Target 5-10 reviews in the first 90 days post-claim, then 2-3 per cohort ongoing

Action: First-90-day push: ask Bob to reach out to past cohort alumni from the last 12 months and request reviews. Set a target of 5-10 reviews live within 90 days of claiming the profile. Then sustain at 2-3 per cohort cycle.
Why: Cold profiles with zero reviews stay invisible. Crossing the ~5-review threshold flips the profile from "new and unproven" to "active and trusted" in Google's local algorithm.
Who: Bob (sends asks) + Charlie (tracks count)
Time: 2 hr first push, 30 min per cohort thereafter

3.6 Monitor for fake or competitor-malicious reviews monthly

Action: Charlie scans GBP reviews monthly for: reviews from people who never attended a cohort, suspiciously similar review content, 1-star reviews with no detail. Flags candidates for Bob to dispute via GBP's review-flagging tool.
Why: Unrebutted fake negative reviews damage the profile. Google removes verified fakes when reported; the report queue is monthly-paced, so set a recurring sweep.
Who: Auto (Charlie monthly scan) + Bob (final flag submission)
Time: 15 min per month

3.7 Cross-list reviews on other platforms (Yelp, Facebook, Psychology Today)

Action: Once GBP review velocity is established, replicate the consent-first workflow on Yelp, Facebook page reviews, and Psychology Today professional listings.
Why: Multi-platform review presence reinforces the entity's prominence signal. Google reads reviews across platforms to validate GBP review legitimacy.
Who: Bob (sends asks) + Charlie (sets up the cross-platform links)
Time: 60 min setup, 15 min per cohort thereafter

3.8 Ask 5-star reviewers for a photo we can show next to their review

Action: Have Sparrow (Bob's remote assistant) reach out to the people who've left 5-star Google reviews and ask each one for permission to use a photo of them next to their review whenever we quote it online (the homepage testimonial cards, social posts, the reviews page, and so on). A simple headshot is plenty. The process: pull the list of 5-star reviewers from the Google Business Profile, then have Sparrow send each one a short, warm message or email asking for a photo plus written permission to display it with their quoted review. Track who says yes, collect the photos they send, and then we add those photos to the testimonial cards we use.
Why: A real face beside a real testimonial builds more trust and converts better than a text-only or anonymous review. Right now our homepage and reviews page quote real named reviews, but with no faces. Putting a friendly photo next to each quote makes the social proof land harder for someone deciding whether to book a call with Bob.
Privacy: Only ever use a photo with the person's explicit permission. If someone says no, or doesn't reply, we just keep their review as text. Keep a simple record of who gave permission, in case we ever need to show it.
Who: Sparrow (does the outreach + collects the photos and permissions) + Bob (any reviewers he'd rather reach out to personally) + Charlie (pulls the 5-star reviewer list, then adds the approved photos to the testimonial cards)
Time: about 15 min to pull the list and draft the outreach message, then ongoing as replies come in

4. Posts & Updates (3-5 items)

4.1 Post 2x per week minimum (the 30-day decay rule)

Action: Charlie drafts and Bob approves 2 GBP posts per week. Mix: cohort start-date announcements, single-block insights ("Block 7 — Grief: what the work looks like"), participant outcomes (with consent), Q&A excerpts, blog post teasers.
Why: 2026 update: profiles inactive for 30+ days see dramatic Local Pack impression drops. Posting cadence is now a top-tier ranking signal. Two posts/week is the minimum to avoid decay.
Who: Charlie (drafts) + Bob (approves + posts) — automate via the GBP API once volume is steady
Time: 30 min per week

4.2 Use all four post types in rotation: Update / Offer / Event / Product

Action: Cycle through GBP's four post formats. Each format displays differently and feeds different surfaces. Don't only use Update.
Why: Google rewards format diversity. Event posts tie into the Events Schema on the website; Offer posts feed shopping/promotional surfaces; Product posts feed the workshop catalog surface; Update posts feed news.
Who: Charlie (rotates) + Bob (approves)
Time: Built into the per-week 30-min above

4.3 Embed cohort start-date Event posts that match the Event schema JSON

Action: When a new cohort opens registration, post a GBP Event with start/end dates, location, and link — matching the event-workshop.json schema on the cohort landing page.
Why: Event-schema-on-page + matching GBP Event Post creates a strong relevance signal AND can land the cohort in Google's Events carousel for "divorce workshop" queries.
Who: Charlie (drafts) + Bob (publishes both)
Time: 20 min per cohort launch

4.4 Add Offer posts when scholarship slots are available

Action: When Bob holds reduced-tuition slots open for a cohort, run a GBP Offer post: "X scholarship seats available — first-served, no income paperwork."
Why: Offer posts get a distinct call-out in the Local Pack. They also expand the audience to people who would otherwise self-select out on price.
Who: Charlie (drafts) + Bob (approves)
Time: 15 min per offer

4.5 Build a 30-post content bank up front

Action: Charlie drafts 30 GBP-post variants in advance — one for each of the 19 Rebuilding Blocks plus 11 cohort-recurring topics (registration open, halfway-point reflections, alumni follow-up, FAQ-of-the-week, etc.). Stored in communications/gbp-post-bank.md. Bob picks 2 per week from the bank.
Why: Eliminates the per-week drafting bottleneck. Bob picks and approves in 5 minutes instead of 30.
Who: Charlie (builds bank) + Bob (picks + approves weekly)
Time: 4 hr upfront, then 5 min per week thereafter

5. Q&A Section (3-5 items)

5.1 Pre-seed the Q&A with the 12 FAQ schema questions

Action: Bob (or Annette) posts each of the 12 questions from faq-page.json to the GBP Q&A section as if asked by the public, then Bob answers them in his voice (using the schema answers as a starting point).
Why: GBP Q&A is one of the highest-cited fields by AI Overviews in 2026. Pre-seeding with the highest-volume target keywords ensures Google has the right answers indexed BEFORE random users start asking.
Who: Annette (asks from her account, anonymized) + Bob (answers) + Charlie (drafts)
Time: 90 min
Policy note: Google ToS allows business owners to pre-seed Q&A with their own question-asks; this is documented good practice, not a black-hat tactic. Use a personal Google account that ISN'T an employee account.

5.2 Subscribe to Q&A notifications

Action: GBP → Notifications → enable Q&A push to Bob's email. Charlie also monitors the profile daily as backup.
Why: Anyone can post a question to a GBP profile, and anyone can answer — including competitors. Unattended Q&A is a vulnerability.
Who: Bob (enables) + Charlie (daily check)
Time: 5 min setup, 5 min per day monitoring

5.3 Answer real Q&A within 24 hours, in Bob's voice

Action: When real users post questions, Charlie drafts the answer (drawing on FAQ schema + the 19-blocks HowTo) and Bob posts it.
Why: Response time on Q&A is a Local Pack ranking signal AND the answer becomes searchable forever. A well-crafted answer to one user's question helps thousands of future searchers.
Who: Charlie (drafts) + Bob (approves + posts)
Time: 10 min per Q&A

5.4 Upvote helpful answers from real users

Action: When a participant or alumnus posts an answer to a Q&A, Bob upvotes it (his account vote carries the most weight). Don't sock-puppet other accounts to upvote.
Why: Upvoted answers rise to the top of the Q&A display. The single visible answer is the one Google AI Overview is most likely to cite.
Who: Bob
Time: 2 min each

5.5 Flag spam / off-topic Q&A

Action: Charlie monitors monthly for spam questions (link-baiting, off-topic services, competitor poisoning). Flag via GBP's report tool.
Why: Spam Q&A makes the profile look unmaintained AND associates the business with off-topic terms. Cleanup is monthly maintenance.
Who: Auto (Charlie monthly scan) + Bob (final flag submission)
Time: 10 min per month

6. Photos & Media (5-7 items)

6.1 Upload a minimum 10 photos in launch week, target 25+ within 90 days

Action: Cover photo (1080x608), profile/logo photo (square), 3+ "interior" or "venue" shots of the cohort meeting space (with no participants identifiable), 3+ headshot variations of Bob, 3+ "team / behind the scenes" (e.g., the 19-blocks pyramid printed on a wall, the workbook on a table). All licensed by Bob.
Why: Photo count + recency is a documented Local Pack ranking factor. Profiles with under 10 photos rarely rank in the top 3 of the Local Pack.
Who: Bob (takes/provides photos) + Charlie (uploads + writes captions)
Time: 2 hr photoshoot, 30 min upload

6.2 Upload one new photo per week (the freshness signal)

Action: Set a weekly cadence — one new photo each week, even if it's a small variation (different angle of the cohort space, a workbook page, a quote card). Stored in assets/gbp-photo-queue/.
Why: Same 30-day decay rule as posts. Photo upload date is a fresher signal than upload count alone.
Who: Bob (provides) + Charlie (uploads + captions)
Time: 10 min per week

6.3 Add a 30-60 second business video

Action: Bob records a short, plainspoken "what is Rebuilding Seminars" video — phone camera is fine, no production polish required. 30-60 seconds, eye-level, well-lit. Upload to GBP under Videos.
Why: Video on GBP is rare among small businesses and disproportionately rewarded. AI Overviews increasingly cite video content. Listings with video pull 2-3x more interactions.
Who: Bob (records) + Charlie (writes the script + captions + uploads)
Time: 60 min

6.4 Geotag photos before upload

Action: Photos taken on a phone with location services on are auto-geotagged. For desktop-uploaded photos, run them through a geotagging tool (or simply re-upload from Bob's phone after AirDropping the file). Geotag should match Niwot, CO.
Why: Geotagged photos reinforce the location signal. A photo geotagged 50 miles from the listed address signals data inconsistency.
Who: Bob (uploads from phone) or Charlie (geotag tool, on desktop uploads)
Time: Built into upload

6.5 Write descriptive captions on every photo (not "IMG_4823")

Action: Every photo gets a 5-15 word caption with relevant keywords: "Rebuilding Workshop cohort space — Niwot, Colorado", "Bruce Fisher 19 Rebuilding Blocks framework reference card", "Bob FOUNDER_NAME — lead facilitator at Rebuilding Seminars", etc.
Why: Photo captions are indexed by Google. They're also read aloud by screen readers, which Google now factors into accessibility-as-quality scoring.
Who: Charlie (drafts) + Bob (approves)
Time: Built into upload

6.6 Add a logo photo that matches the on-site logo and schema ImageObject

Action: Same logo file across GBP / website header / schema JSON logo field / social profile photos. Square, minimum 250x250, ideally 600x600 PNG.
Why: Visual entity reconciliation. Same logo across surfaces tells Google's image-recognition that the entity is consistent.
Who: Bob
Time: 10 min

6.7 Photograph and upload the 19-blocks pyramid as a labeled image

Action: Create a clean visual of Dr. Bruce Fisher's 19 Rebuilding Blocks pyramid (already referenced in howto-rebuilding-blocks.json). Upload to GBP photos with caption "Bruce Fisher 19 Rebuilding Blocks — the framework Rebuilding Seminars uses."
Why: This is the proprietary visual asset that distinguishes Rebuilding Seminars from DivorceCare and from drop-in groups. AI Overviews cite labeled framework visuals more often than stock imagery.
Who: Charlie (designs) + Annette (approves) + Bob (uploads)
Time: 90 min

7. Insights & Monitoring (3-5 items)

7.1 Build a weekly GBP Insights dashboard

Action: Charlie pulls the following weekly into report/gbp-insights-weekly.md: profile views (search vs. maps), search queries that surfaced the profile, direction requests, calls, website clicks, photo views, post views, Q&A views. Compare week-over-week.
Why: Insights data is the only feedback loop on what's working. "Search queries that surfaced the profile" especially shows which keywords are landing — that data informs which Q&A and Posts to prioritize next.
Who: Auto (Charlie weekly pull) + Annette (skim)
Time: 20 min per week

7.2 Track ranking position weekly for the top 12 target keywords

Action: Charlie runs a weekly geo-grid ranking check (free tools: Local Falcon free tier, BrightLocal trial; paid: Local Falcon at ~$25/mo) for each of the top 12 keywords from audit/ahrefs/TARGET-KEYWORDS.md from a Niwot-centered grid. Output: heatmap per keyword.
Why: Local Pack rank shifts daily. Weekly geo-grid shows whether optimization is actually moving the needle, AND identifies sub-areas where Local Pack rank is weak (informing where to push more localized content).
Who: Auto (Charlie weekly) + Annette (review monthly)
Time: 30 min per week + ~$25/mo tool cost (Annette to approve)

7.3 Set up GBP API alerts for verification status, suspension risk, edits-by-others

Action: Either via GBP API or Google Maps Platform notifications, alert Bob's email immediately on: profile suspension, ownership change request, "suggested edit" by a third party (Google sometimes auto-applies these without owner consent), category change.
Why: GBP suspensions happen with no warning and are hard to reverse. Auto-edits by third parties can quietly degrade NAP consistency. Real-time alerts let Bob respond within hours instead of weeks.
Who: Charlie (sets up) + Bob (receives alerts)
Time: 60 min setup, alerts thereafter

7.4 Compare to top-3 competitors quarterly

Action: Every 90 days, Charlie pulls public GBP data on DivorceCare regional listings, Colorado Divorce Mediation, Second Saturday Denver, Rebuilders Anonymous (the top-ranked competitors per the keyword audit). Compare: review count, review rating, photo count, post frequency. Identify gaps.
Why: Local Pack ranking is relative, not absolute. Knowing the competitor benchmarks tells Bob whether he needs to push harder on reviews (DivorceCare typically dominates), photos, or posts.
Who: Auto (Charlie quarterly) + Annette (review)
Time: 90 min per quarter

7.5 Audit NAP consistency across the top 30 citation directories quarterly

Action: Quarterly check that NAP is identical on: Yelp, BBB, Yellow Pages, Foursquare, Apple Maps Connect, Bing Places, Psychology Today, Therapist Directory, Niwot Chamber of Commerce, Boulder Chamber, etc. (full list to be built in strategy/citations/directory-list.md).
Why: Citation drift is the silent killer of Local Pack rankings. A directory that auto-imported the wrong phone number 18 months ago can be quietly suppressing the profile today.
Who: Auto (Charlie quarterly) + Bob (corrections that require account access)
Time: 2 hr per quarter

Top 3 priorities (start here, in order)

1.1-1.4: Claim, verify, and set the primary category correctly. Without this nothing else ranks. The single decision that needs Annette+Bob input first: which primary category. Recommend "Marriage or Relationship Counselor" pending review of the alternatives.
3.1-3.2: Stand up the consent-first review collection workflow before the next cohort closes. Reviews are the highest-correlation Local Pack ranking factor in 2026, and Rebuilding Seminars is sitting at zero or near-zero today (verify after claim). The 5-10-reviews-in-first-90-days target is what flips the profile from "invisible" to "competing."
2.1-2.2 + 5.1: Write the 700-character description, fully populate the Services section, and pre-seed the 12 FAQ Q&As into GBP. Together these three fields are what Google's 2026 AI Overview pulls from most often for "divorce support groups near me" queries — the highest-volume, lowest-difficulty target keyword in the audit.