---
name: verify-google-business-profile-is-verified
description: "Check your firm’s profile. Find out who owns it and if the public facts are right."
category: Website QA Audit
stage: —
definitive_article: /website-qa-audit
status: complete
---

# Verify Google Business Profile is verified

Your firm’s profile should show the right facts. This guide helps you check its status and who can edit it. Start with the exact page and the right account.

**The path:** Exact profile → Account status → Public facts → Specific next owner.

**Use this when:** An eligible business’s Google Business Profile needs its verification, control and public details audited.

## Inputs
- The exact Business Profile ID/link, site URL and known business identity from the project.
- Authorized manager/owner access or a current trustworthy account-status receipt; the business-controlled primary owner record.
- The actual name, contact details, operating status, category and storefront/service-area model.
- The existing scope for any profile edit or verification action and a private evidence log.

## First-run prompt

> Inspect the supplied exact Business Profile using authorized access. Record verification, owner/control and public-fact consistency separately, preserve address privacy and real operating state, and complete only the profile actions already in scope. Return the actual pending owner or Google review step without promising ranking.

## Steps
1. Confirm this is an eligible actual business and the correct profile, not a duplicate or similarly named listing. A personal online brand without an eligible local business should not get a fictional address or new listing to satisfy the check.
2. Open the exact managed profile through the authorized account and inspect its current status. Record verified, verification pending, needs verification, suspended or unavailable exactly as observed. Public Search/Maps visibility alone does not establish account verification or control.
3. Inspect the owner/manager roles available to this account. Confirm the business’s intended primary owner and flag an old agency or unknown owner for a separate ownership resolution. Do not transfer ownership or remove managers during a read-only status audit.
4. Compare the public listing with the actual site/business record: website destination, name, phone, category and operating state. Check factual consistency, not meaningless punctuation equality. A legitimate temporarily closed state should not be “fixed” to open without current business evidence.
5. Respect the actual service-area/storefront policy. Do not expose a home or hidden service-area address simply to make a footer and listing match. Record the approved public contact details and any policy/identity question for the owner.
6. If a verification action is already in scope, follow only the methods Google actually offers for this profile. Submitted evidence, pending review and a received verified confirmation are different states. The method and approval timing are not guaranteed by the guide.
7. Check the actual public profile and website link separately after any authorized changes. A verified account does not guarantee a map-pack rank, Knowledge Panel appearance or visibility for every query.
8. Save status, role and public-fact evidence with timestamps, redact private account details in public summaries, and hand off the exact pending verification/control issue. Do not call a submitted request complete before confirmation.

## Definition of done (QA checklist)

- [ ] The exact eligible business/profile and observed account status are recorded.
- [ ] Business control and primary-owner intent have evidence or a precise access gap.
- [ ] Public facts match the real business without exposing intentionally hidden addresses.
- [ ] Verification submitted, approved and publicly observed are distinct states.
- [ ] No ranking, ownership transfer or automatic verification outcome is invented.

## Example(s)

**Fictional teaching example — no Business Profile was opened.** Maple Cycle appears in Maps, but the available management record still says verification pending. The agency has manager access; the business owner retains primary ownership.

The report says “public listing visible; verification pending; business control confirmed from current roles.” It does not infer verified status from the Maps result. For a separate mobile repair business, a correctly hidden service-area address would remain hidden rather than being copied into the public footer.

## Handoff and Content Factory context

The business/profile owner receives any exact access, ownership or verification issue. [Check schema profile links](https://local-service-spotlight.github.io/task-library/?task=check-schema-connects-to-all-verified-profiles#task-check-schema-connects-to-all-verified-profiles) follows only after the correct public identity destination is established.

This is a supporting quality check for 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 at launch and after relevant identity, account-control or status changes. Continued monitoring requires a real defined job; verification is not guaranteed to remain unchanged forever.

## 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:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 2, 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:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## 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/website-qa-audit
- Exact task: [Verify Google Business Profile is verified](https://local-service-spotlight.github.io/task-library/?task=verify-google-business-profile-is-verified#task-verify-google-business-profile-is-verified)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Website QA Audit](https://blitzmetrics.com/website-qa-audit/)
- [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.
- Actual manager status, business-controlled ownership evidence and any Google verification outcome require the real profile.