--- title: JBF Concrete — GBP Access Recovery type: article created: '2026-02-23' updated: '2026-02-23' source_docs: - raw/2026-02-23-jbf-concrete-landscaping-124664574.md tags: - local-seo - google-business-profile - access-recovery - g-suite - godaddy - jbf-concrete layer: 2 client_source: null industry_context: null transferable: true --- # JBF Concrete — GBP Access Recovery ## Overview During the February 23, 2026 website review meeting, a critical blocker was surfaced: Joe (owner, JBF Concrete) cannot access the `joe@jbfconcrete.com` G Suite account. This prevents management of the Google Business Profile (GBP) and means Joe is not receiving project-related emails sent to that address. Resolving this is the top priority before the website can go live with automated review pulling. **Participants:** Melissa Cusumano (Asymmetric), Lisa Frommelt (JBF Concrete) **Follow-up meeting:** Friday, February 27, 2026 at 8:00 AM --- ## The Problem ### Account Access Chain | Account | Status | Notes | |---|---|---| | `joe@jbfconcrete.com` (G Suite) | **Inaccessible** | Admin account exists but Joe cannot log in | | `lisa@jbfconcrete.com` (G Suite) | **Non-functional** | Created by Mark Hope; bouncing | | `jbfconcretelandscape@gmail.com` | Accessible | Personal Gmail; not tied to GBP admin | Joe currently only receives email at his personal Gmail (`jbfconcretelandscape@gmail.com`). All business-domain email is effectively dead. ### Root Cause The access issue stems from a past website/business transition. The G Suite admin account was set up under `joe@jbfconcrete.com` but control of the underlying domain and account credentials was never cleanly handed off. The domain is registered through **GoDaddy**. ### Impact - **GBP is unmanaged** — JBF Concrete cannot be found or updated in Google Search/Maps - **No automated review pulling** — the planned website feature that surfaces Google reviews requires verified GBP access - **Email dead zone** — any correspondence sent to `joe@jbfconcrete.com` is not received - **Business visibility** — as Lisa noted: *"if someone's trying to just search him as a business, he's not found right now"* --- ## Recovery Strategy ### Step 1 — Engage Mark Hope Mark Hope (`mark.hope@asymmetric.pro`) previously set up the G Suite accounts and was last in contact on **September 8, 2025**, when he requested a GoDaddy verification code from Lisa. That exchange was never followed through. **Action:** Melissa to contact Mark immediately after the Feb 23 meeting and escalate as top priority at their Wednesday standing meeting if not resolved sooner. ### Step 2 — GoDaddy Domain Verification The September 2025 GoDaddy code exchange suggests the recovery path likely runs through domain ownership verification via GoDaddy. Lisa has access to the GoDaddy account and can receive verification codes. **Action:** Lisa to forward any recovery emails or verification codes from Google or GoDaddy to Melissa immediately upon receipt. ### Step 3 — Restore or Recreate GBP Access Once G Suite admin access is restored, options include: - **Recover existing GBP** — preferred if the existing profile has reviews or history - **Create fresh GBP** — viable if the existing profile has no meaningful data, since Joe has no established review history on the locked account Melissa noted the existing GBP may have little to no content, making a fresh start a reasonable fallback. --- ## Key Decisions - **Mark Hope is the recovery path** — he holds the institutional knowledge of how the G Suite was originally configured - **GoDaddy is the likely verification lever** — Lisa can receive codes; the Sep 8 exchange is the last known touchpoint - **Fresh GBP is on the table** — if recovery proves too complex, starting a new profile is acceptable given the current lack of visibility - **Calendar invite to Lisa's LaMarie email** — `lisa@lamariebeauty.co` is her reliable inbox; JBF domain email is non-functional --- ## Action Items | Owner | Action | Due | |---|---|---| | **Melissa** | Contact Mark Hope to resolve `joe@jbfconcrete.com` G Suite access | Immediately (Feb 23) | | **Melissa** | Escalate to Mark at Wednesday meeting if not resolved | Feb 25 | | **Melissa** | Send calendar invite for Feb 27 8 AM follow-up to Lisa's LaMarie email | Feb 23 | | **Lisa** | Forward any Google/GoDaddy recovery emails or codes to Melissa | As received | | **Lisa** | Review all website copy in shared document (green-marked pages) | Before Feb 27 | | **Lisa** | Source high-resolution, landscape-oriented images for Miro board | Before Feb 27 | --- ## Related Context — Website Progress While the GBP blocker is the critical path item, website work is otherwise progressing: - **SEO copy** is complete and ready for Lisa's review (pages marked green in the shared doc); includes FAQs, meta titles, and meta descriptions - **Miro board** contains the current design with placeholder images - **Images needed:** landscape orientation preferred; high resolution required; JBF Concrete's Instagram is the only social media source available (no YouTube or LinkedIn) --- ## Broader Pattern This case illustrates a common risk in small business web transitions: **G Suite accounts tied to a domain can become orphaned** when the vendor or contractor who configured them disengages without completing a credential handoff. The GoDaddy domain ownership is the practical recovery lever in these situations, as it allows re-verification of domain control independent of the locked Google account. See also: [[clients/jbf-concrete/_index]] | [[knowledge/local-seo/google-business-profile-setup]]