---
name: link-all-content-back-to-personal-brand-site
description: "Help readers reach the right next page from your work."
category: Personal Branding
stage: Post
definitive_article: /personal-brand
status: needs-work
---

# Link all content back to personal brand site

Help readers reach the right next page from your work. This guide checks links in posts, profiles and guest features. Start with your live content list and the site that should be your public home.

**The path:** Asset list → Right destination → Owned edits or host request → Checked path

**Start when:** A bounded set of published assets needs its identity and topic links checked.

## Inputs

- The current content inventory with exact URLs, platform and edit owner.
- Verified person/company sites and relevant topic/offer pages; [entity linking, choosing the right home for a named person or topic](https://blitzmetrics.com/entity-linking/) and the [SEO Tree, the map from proof pages to main topics and offers](https://blitzmetrics.com/seo-tree/).
- Actual edit/send authority and the previous link audit, if one exists.

## Steps

1. Set the scope from the existing inventory and add newly discovered assets there. Record URL, publisher, article purpose, current destination and edit owner. A known list is a bounded audit scope, not proof that every asset on the web has been found.
2. Choose the useful destination for each first mention. The person’s name points to their verified home, a company to its own site, and a method to its maintained guide. A source citation or required tool action keeps its direct source rather than being replaced with an irrelevant internal page.
3. Use meaningful anchor text that identifies the person or destination naturally. The house three-to-six-word preference is a guide, not permission to pad a two-word person’s name or change the sentence’s meaning. Do not repeatedly link the same entity in one piece.
4. On the owned site, check a real path from each supporting page to its topic and relevant offer under the SEO Tree. Add a useful parent link and related proof where appropriate. Avoid forcing every article directly to the homepage when a more specific branch serves the reader.
5. On social pages, use the supported website field or relevant post link. If a channel makes links non-clickable, record the actual profile or other supported path and test it. Do not claim every post contains a clickable link when the platform does not provide one.
6. For a third-party feature, prepare a specific factual credit/link request to its actual editor under send authority. Keep pending, declined and accepted outcomes separate. The host controls its editorial links; a refused link does not erase a real mention.
7. After authorized changes, follow each repaired path from the normal public asset to the intended page. Save exact URLs, source revision, results and remaining owner actions. Review newly released or changed content through this same bounded method; recurring timing needs an actual owner.

## 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 in-scope asset has a checked useful path or a specific supported limitation and next owner.
- [ ] Identity links, topic hierarchy and primary citations retain their correct purposes.
- [ ] Repaired links are publicly read back; outside requests are not counted as accepted edits.
- [ ] 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 coach’s interview links to an old home page. Her own recap can be changed, so it receives the correct topic link and her current home. The host’s show notes need an editor request. The report shows the repaired owned path and the pending host action, rather than claiming all links are fixed.

## Handoff and Content Factory context

[Collect and classify positive mentions](https://local-service-spotlight.github.io/task-library/?task=positive-mentions-harvester#task-positive-mentions-harvester) receives verified outside references; the site/content owner receives unresolved link repairs and the updated [SEO Tree, the map from proof pages to main topics and offers](https://blitzmetrics.com/seo-tree/) map.

The source places this task in Post within the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/). Produce captures real sources, Process makes the selected useful assets, Post releases approved work, and Promote distributes proven work. The actual handoff above determines what this task must supply.

## 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:** Post
- **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:** Draft URL or WP post ID, slug, author user ID, featured-image media ID. Promote reads the live URL, not the draft.

## 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=link-all-content-back-to-personal-brand-site#task-link-all-content-back-to-personal-brand-site)
- [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.