---
name: add-consistent-headshots-and-bios-across-profiles
description: "Help people know they have found the right you."
category: Personal Branding
stage: —
definitive_article: /personal-brand
status: needs-work
---

# Add consistent headshots and bios across profiles

Help people know they have found the right you. This guide brings your photos and key facts into line across your work profiles. Start with your best current photo and the facts on your own site.

**The path:** Approved photo + facts → Platform drafts → Checked profiles → Identity map

**Start when:** The agreed public profiles exist, but their photos or bio facts differ.

## Inputs

- [Set up the agreed public profiles](https://local-service-spotlight.github.io/task-library/?task=set-up-professional-social-profiles#task-set-up-professional-social-profiles) with exact URLs and actual edit rights.
- An approved real headshot, crop files and permission for each use; the person’s accepted public name and verified current bio facts.
- The current site About page, allowed public contact details and a list of platforms in this pass.

## Steps

1. Compare the profiles with the site before editing. List wrong-person matches, outdated roles, old photos, broken links and missing access. Distinguish a genuine fact conflict from a platform’s length limit or a valid historic credit.
2. Choose a current real headshot that is clear at avatar size. Make the required crops from that photo and retain the original. Preview each crop so the face is recognizable; do not alter the person’s identity or create a fake event photo.
3. Write one-line, short and longer bios from the same verified facts. State the person’s work, the people served and relevant proof. Keep approved professional name and role consistent; a legal-name variant in an old record is evidence to reconcile, not erase.
4. Prepare the fields for each agreed profile. Use first person on the person’s site and the platform’s appropriate voice elsewhere. Follow [Article Guidelines](https://localservicespotlight.com/article-guidelines/) for reader value, real proof and natural voice; do not copy an unsupported credential into every bio.
5. Apply the approved edits through each platform’s supported control when authorized. Keep before values for recovery. External publisher profiles receive a specific correction request under the existing send authority; record any pending owner action instead of claiming it fixed.
6. Open the saved public profiles and compare name, photo, role and website link with the approved set. A blocked automated fetch requires a supported visible check or an unknown result, not automatic proof that the profile is correct.
7. Save the final URL list, checked facts, crop references and remaining gaps in the existing identity record. Recheck when roles or photos change; a quarterly review is a proposed cadence until the actual owner and schedule are recorded.

## 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/).

- [ ] Every in-scope editable profile matches the approved current facts, or has a specific unresolved owner action.
- [ ] Published photo crops and links have been checked; historic variants and inaccessible sources stay identified.
- [ ] The next owner receives the same bio set and checked profile list.
- [ ] 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 changes her job title. Her website and two social profiles can be edited, but an event bio belongs to the host. The team updates the three owned pages and prepares a precise request for the event page. The record shows three verified changes and one pending request, not a fully fixed web.

## Handoff and Content Factory context

[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 the checked identity facts and profile URLs; the podcast and speaker tasks reuse the approved bio set.

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=add-consistent-headshots-and-bios-across-profiles#task-add-consistent-headshots-and-bios-across-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.