---
name: verify-google-business-profile
description: "Set up the right business page on Google. Check who can use it and what is still due."
category: Digital Plumbing
stage: —
definitive_article: /digital-plumbing
status: complete
---

# Verify Google Business Profile

People need to find the right business on Maps. This guide helps you set up and check its Google page. Start with the real facts and any page that is there now.

**The path:** Eligible business → Existing profile → Offered proof → Verified state.

**Use this when:** an eligible business needs verification, has uncertain profile control, or receives a reverification request.

## Inputs
- The actual business activity, public trading name, appropriate address or service-area details and phone, supported by current records.
- The exact existing Profile ID or URL and legitimate business-controlled Google access, or the authorized setup/control-recovery scope.
- The owner or operator who can supply the real proof Google requests, using the method offered to that profile. Keep identity documents and private footage out of public evidence.

## First-run prompt

> Find the correct eligible Business Profile and inspect its control and verification state. Complete the supported method Google offers within current authority. Preserve pending review, legitimate ownership and private evidence; do not create duplicates or claim Maps visibility proves verification.

## Steps
1. Check business eligibility against current Google representation rules. An online-only personal brand does not qualify just because it has a website. Use the real customer-facing or service-area business model and preserve address privacy where required.
2. Find existing profiles by the known business name, location and supplied ID. Distinguish the intended business from legitimate branches or unrelated names. Do not create a second profile to bypass a missing-access problem.
3. Inspect actual management access and verification state. If the profile exists, use the supported claim or access-request route as needed. If none exists and it is eligible, create the correct profile within authorized scope. A public Maps listing can exist without your verified control.
4. Confirm business-controlled ownership and the operator’s actual role. Review unfamiliar accounts with the owner; do not automatically remove or demote people just because their names are new to this agent. Transfers and removals use the specific existing authority and supported process.
5. Complete the verification method or combination Google offers. For required on-site video or other business proof, use real current evidence and follow the actual prompts. Do not fabricate a storefront, manipulate location proof or substitute stock footage. Keep agent playback silent.
6. Save the submission state and time without exposing verification codes or private records. Google may review the evidence and request another step. Pending is not verified; do not promise that waiting a fixed number of days will finish it.
7. Reopen the management view and verify the actual confirmation or outstanding request. If the process fails, record the provider’s stated reason and use its supported correction or appeal route. A model cannot force verification through endless retries.
8. Compare public business facts and Maps display with the approved identity record, allowing legitimate formatting and service-area differences. Record management verification, public visibility and account control as separate results and hand off exact open items.

## Definition of done (QA checklist)

- [ ] The business is eligible and the exact appropriate profile is used without a bypass duplicate.
- [ ] Business control and operator role have actual evidence.
- [ ] Google’s requested proof is genuine, private where needed and submitted through its supported process.
- [ ] Verified, pending, failed and public-visible states are recorded distinctly.
- [ ] Public business facts match reality without forced private-address exposure or invented ranking claims.

## Example(s)

**Fictional teaching example.** Oak Repair already appears on Maps, but its management view asks for verification. The owner supplies the actual requested business proof and sees “pending review.” The lesson record therefore says “public listing visible; verification pending; owner control checked.” When a later management confirmation is actually observed, that same run can be updated. The initial Maps appearance alone never counts as verification.

## Handoff and Content Factory context

Give the confirmed state and Profile ID to the business owner. Once the actual required access and verification are ready, continue with [upload real photos and set business hours](https://local-service-spotlight.github.io/task-library/?task=upload-real-photos-and-set-business-hours#task-upload-real-photos-and-set-business-hours) or [set correct business categories](https://local-service-spotlight.github.io/task-library/?task=set-correct-business-categories#task-set-correct-business-categories) according to the remaining need.

This setup supports the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. This check does not automatically execute all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

Run for first verification or an actual control/reverification issue. A pending review can have a configured follow-up under the existing job, with the same execution ID; this guide does not create an automatic retry loop.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Gate
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 3 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Record only the property IDs, access and checks required by this task in the client register. Pass the verified result to the task that needs it.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/digital-plumbing
- Exact task: [Verify Google Business Profile](https://local-service-spotlight.github.io/task-library/?task=verify-google-business-profile#task-verify-google-business-profile)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Digital Plumbing training](https://blitzmetrics.com/digital-plumbing/)
- [Google Business Profile verification](https://support.google.com/business/answer/7107242?hl=en)
- [Google business representation rules](https://support.google.com/business/answer/3038177?hl=en)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- The contributor’s complete status is preserved, but this rewritten guide has no new independent runtime certification. Actual profile control, proof and provider confirmation remain execution requirements.