---
name: claim-and-brand-facebook-page
description: "Set up the right Facebook Page for your business. Check its name, photos, links and access."
category: Digital Plumbing
stage: —
definitive_article: /digital-plumbing
status: needs-work
---

# Claim and Brand Facebook Page

People may find an old or wrong Page when they search for your business. This guide helps you fix the right Facebook Page. Start by finding the Page your business should own and checking who can edit it.

**The path:** Find Page → Check control → Update facts → Public check.

**Use this when:** a business needs a Page, has an unclaimed listing, or needs its existing Page brought into line with current facts.

## Inputs
- The business identity record, canonical website and any existing Page IDs or URLs.
- A legitimate account with the needed Page permissions, or the actual owner who can provide them. Record access without sharing passwords.
- Rights-cleared logo, cover photo, business description, public contact details and the requested scope of changes.

## First-run prompt

> Find the existing business Page before creating one. Verify access and the real business facts, then complete authorized branding edits. Report pending access separately from public branding. Do not merge Pages, transfer control, send invitations or run ads unless those actions are included in the job.

## Steps
1. Search the known Page URL, business name and location. Record likely matches and why each is the same business or a distinct valid location, brand or person. Multiple results do not prove that they should be merged.
2. Open the actual Page management view and confirm the Page ID and current role. Meta distinguishes Facebook access from task access, and full control can manage permissions. An invitation or request is pending until accepted and usable.
3. If no Page exists, use Meta’s supported create-Page flow for the real business. If one exists but access is missing, use the supported request or owner-grant route within current authority. Keep a named dependency for missing control; do not create a competing Page as a shortcut.
4. Update the public business name, category, website and contact details from the identity record. Select an available clear handle. Preserve service-area address privacy and supported platform formatting rather than forcing identical characters everywhere.
5. Add the approved logo and cover image, checking crop and legibility on phone and desktop. Use real owned or licensed material; a fictional staff photo or implied customer endorsement does not belong on a real Page.
6. Write a short About section that says what the business does, whom it serves and how to reach it. Company voice may use “we”; do not force a company to speak as one individual or invent claims.
7. Choose an appropriate contact action supported by this Page and test its destination without sending an unrequested message. Link a business portfolio or Instagram account only when that connection serves the agreed workflow; do not create an ad account just for branding.
8. Save and read back the public Page and management view. Record edited fields, image crops, website destination and current control. Route duplicate merges, ownership transfers or access removals as separately scoped changes when needed.

## Definition of done (QA checklist)

- [ ] The exact Page represents the intended business; existing valid Pages were not treated as duplicates without evidence.
- [ ] The needed role works and business control is identified, or access remains a named pending item.
- [ ] Approved name, contact, website and images are saved and readable on both widths.
- [ ] Page actions lead to their intended destination; no unauthorized messages or ads were sent.
- [ ] Public branding and private account-control evidence are recorded separately.

## Example(s)

**Fictional teaching example.** Oak Repair finds two results: its main Page and a valid Page for its second branch. The main Page still links to an old website. The guide changes that one link, replaces a cropped logo and sets the call action to the confirmed branch line. Three planned edits receive three public read-backs. The second branch stays intact. A colleague’s pending invitation is recorded as pending access, not “team access complete.”

## Handoff and Content Factory context

Give the Page ID and verified public link to the profile owner. Continue with [ensure nap consistency across platforms](https://local-service-spotlight.github.io/task-library/?task=ensure-nap-consistency-across-platforms#task-ensure-nap-consistency-across-platforms) for the cross-platform fact check. Use [convert instagram to professional account](https://local-service-spotlight.github.io/task-library/?task=convert-instagram-to-professional-account#task-convert-instagram-to-professional-account) only if an Instagram workflow is part of the plan.

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 initial setup and material business or branding changes. Optional periodic checks need a configured owner and trigger; no automatic invitations, posting schedule or ad spend follows.

## 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:** 5/5 `●●●●●` — frequency 3, revenue 5, gating 5 (ads/revenue path; unblocks a chain (access/plumbing))
- **Suggested previous station:** `set-up-meta-business-manager-and-public-figure-pages`
- **Suggested next station:** `create-xml-sitemap-and-reference-in-robots-txt`
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: [Claim and Brand Facebook Page](https://local-service-spotlight.github.io/task-library/?task=claim-and-brand-facebook-page#task-claim-and-brand-facebook-page)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Digital Plumbing training](https://blitzmetrics.com/digital-plumbing/)
- [Entity linking](https://blitzmetrics.com/entity-linking/)
- [Meta Facebook Page access](https://www.facebook.com/help/187316341316631)

## 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.
- Current account-specific menus and Page eligibility require inspection in the actual account; the direct general-access help page returned a login wall during authoring.