---
name: set-up-professional-social-profiles
description: "Help people find the real you on the sites they use."
category: Personal Branding
stage: —
definitive_article: /personal-brand
status: needs-work
---

# Set up professional social profiles

Help people find the real you on the sites they use. This guide checks your work profiles and connects them to your own site. Start with the accounts you already control before you make new ones.

**The path:** Existing accounts → Right identity and ownership → Approved profile setup → Verified URL list

**Start when:** The person needs a checked set of agreed public profiles or corrections to existing ones.

## Inputs

- [Build the personal brand site](https://local-service-spotlight.github.io/task-library/?task=build-personal-brand-website#task-build-personal-brand-website) with the accepted home URL, public name and real identity facts.
- The agreed platform list based on actual audience needs and the person’s existing accounts.
- Actual account owner, supported delegated roles, setup authority and secure recovery/access record.

## Steps

1. Inventory current profiles, handles and account owners before creating anything. Separate wrong-person matches, abandoned accounts and potential duplicates. A duplicate-looking result needs an ownership check; it is not permission to delete an account or assume a claim right.
2. Choose the platforms relevant to the person’s work. The source’s LinkedIn, Facebook, Instagram, YouTube and X list is a planning starting point, not a universal requirement to open all five. Record the agreed scope and why a platform is excluded or pending.
3. Use a clear handle and the accepted professional name within each platform’s actual rules. Preserve a legitimate existing handle when change would break useful links without a reviewed reason. Do not imply that matching every handle guarantees one search identity.
4. Use the actual supported account/profile type for the intended person or business. Check current platform setup documentation and the live controls before creating, converting or connecting accounts. A personal profile and a company page serve different entities and should not be silently merged.
5. Keep ownership and recovery with the person or the appropriate business owner, and use supported delegated roles for helpers. Complete verification with the account owner where required; a skill or connected browser does not confer new account-creation, transfer or publication authority.
6. Add the verified home URL where the platform permits and prepare the approved bio/photo fields. Use [Align photos and bio facts](https://local-service-spotlight.github.io/task-library/?task=add-consistent-headshots-and-bios-across-profiles#task-add-consistent-headshots-and-bios-across-profiles) for consistent current facts. Do not leave misleading blank or placeholder profiles public solely to finish a count.
7. After authorized setup, open the actual public profiles, check identity and destination and save their exact URLs. Keep blocked access, pending verification and unavailable link fields explicit. Only the accepted same-person profile list passes to schema work.

## Definition of done (QA checklist)

Quality assurance (QA) means checking the actual result against its agreed requirements. Follow the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).

- [ ] Each agreed platform has a verified correct profile or a precise remaining account-owner dependency.
- [ ] Ownership and permitted roles are checked; new accounts or destructive cleanup are not assumed.
- [ ] Public identity, allowed site links and exact URLs are read back before handoff.
- [ ] The exact output, source revision, reviewer evidence and remaining owner action are saved.
- [ ] For any reader-facing output, the short grade-five opening states the reader’s useful outcome and supporting method or proof. The body delivers that promise; a useful authentic visual appears in the first screen. Retain exact text and quoted reviewer evidence.

## Example(s)

**Fictional teaching example. This is not a client result or proof of a completed run.**

A fictional consultant already uses LinkedIn and YouTube, while an old X handle belongs to another person. Her current plan needs only the first two. The team updates those owned profiles, leaves the unrelated handle alone and passes two checked URLs to schema work, rather than creating accounts to meet a five-profile quota.

## Handoff and Content Factory context

[Align photos and bio facts](https://local-service-spotlight.github.io/task-library/?task=add-consistent-headshots-and-bios-across-profiles#task-add-consistent-headshots-and-bios-across-profiles) receives the actual editable profiles; [Add verified Person markup](https://local-service-spotlight.github.io/task-library/?task=implement-person-schema-with-sameas-links#task-implement-person-schema-with-sameas-links) receives only the final verified identity URLs.

This task supports the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/). Identity, proof, access or coordination can support several stages. Use the real inputs and receiving owner above; this task does not create unrelated transcripts, clips or ads merely because the diagram has four stages.

## Start with an agent

Give the [AI worker](https://blitzmetrics.com/build-agents/) this recipe, the real inputs, desired result and actions already authorized. Ask for the saved output, sources, checks and next owner. A [skill is a written recipe](https://localservicespotlight.com/plugin/); loading one does not prove account access or perform the task. Use the [installation guide](https://localservicespotlight.com/install/) if reusable setup is needed. A ZIP is a source snapshot, not an access grant or automatic update.

Use the app’s actual supported tools and verified file/account access. Keep a missing human verification step with its real owner. Recurring work needs its own configured job, trigger, timezone and observed result; this guide creates no schedule. Before any media playback, mute the player and set its volume to zero. If silence cannot be verified first, use captions, frames, metadata or another silent check.

## Record the real execution

Open the run record when work begins. Keep one execution ID, starting recipe revision, real inputs and current state. Write the [meta article, the record of this execution](https://blitzmetrics.com/meta-article-prompt/) with actual steps, results, checks, failures and next owner. Writing is required; public release follows existing authority. Link it to this recipe and the [Task Library](https://local-service-spotlight.github.io/task-library/).

Reuse the same execution ID for internal checks, revisions, retries and meta writing. A blocked run stays open with its dependency and owner, without an invented finish time. Dated public examples and distinct verified execution counts remain separate. Propose the smallest source-backed recipe improvement when the actual evidence reveals a defect.


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

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

- **Phase:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (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

- [Maintained source guide](https://blitzmetrics.com/personal-brand/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=set-up-professional-social-profiles#task-set-up-professional-social-profiles)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records fit together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `needs-work`. It is preserved, not promoted by this rewrite. That label alone does not prove document readiness, account access, an actual execution or a client result.

The fictional example teaches the method and does not fill a real-run evidence gap. A named semantic reviewer must check the actual opening, full method, sources and handoff. Check the useful opening visual in the normal rendered guide at the current required desktop and mobile sizes, including 1280 × 800 and 390 × 844. Source readability checks do not prove public presentation or task execution.