---
name: close-ended-relationship-endorsement-links
description: "Keep your site clear about who you work with now."
category: SEO & Content Architecture
stage: —
definitive_article: https://blitzmetrics.com/when-trust-ends-the-link-ends/
status: needs-work
---

# Close endorsement links for an ended relationship

Keep your site clear about who you work with now. This guide checks old links when a work relationship ends, while keeping true history. Start with the agreed change and the pages your team can edit.

**The path:** Confirmed relationship change → Controlled-link inventory → Narrow edits → Public closeout check

**Start when:** The relationship owner has confirmed a specific ended relationship and the public association that must change.

## Inputs

- A dated source confirming the relationship’s end, the exact entities involved, affected roles and decision owner.
- The relevant controlled sites, public profiles and draft records, with current edit rights and release authority.
- Existing account/access ownership, historical facts to preserve and the [relationship closeout method](https://blitzmetrics.com/when-trust-ends-the-link-ends/).

## Steps

1. Confirm the actual event and scope with the owning record. Distinguish an ended agency relationship from a former employee role, an expired offer or an unsupported allegation. If the owner’s decision is missing, stage the inventory and leave the public change pending.
2. Inventory affected links and association claims only on surfaces the team controls. Save the exact URL, surrounding sentence, destination, role and current source. Use explicit searches and known site maps; an incomplete search is a bounded inventory, not proof that all web references were found.
3. Classify each item as current endorsement, active role, factual historical record, primary evidence or unrelated identity reference. The closeout removes misleading current association while retaining true history. An old event appearance or dated quote does not become false simply because the working relationship ended.
4. Prepare the smallest appropriate edit for each confirmed current endorsement. Remove a hyperlink, qualify the former role or revise its surrounding sentence as warranted. Never retarget the other party’s name to your own site and leave a misleading anchor; a new destination requires a truthful label and relevant purpose.
5. Keep account and infrastructure ownership separate. Remove only an explicitly authorized obsolete role or access grant after checking the correct account and recovery dependency. Do not delete the other party’s site, transfer their domain, lock them out or change unrelated administrators as a side effect.
6. Use the supported content rail for authorized edits, preserving current source, media and unrelated fields. Check the normal anonymous page and link behavior after save. Public caches or inaccessible profiles remain specific verification gaps; a successful save response alone does not prove the public association changed.
7. Save before/after evidence, unchanged history, inaccessible surfaces and each remaining owner. Any notice to the other party needs its own send authority. Complete the scoped closeout when its actual checks pass, without claiming control over copies or accounts outside the agreed boundary.

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

- [ ] The ended relationship and exact change are supported by the owner’s current record.
- [ ] True history and third-party ownership remain intact; changed anchor text predicts its destination.
- [ ] Every controlled changed surface has a public readback, or an explicit unresolved verification dependency.
- [ ] 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 agency stops managing a contractor’s marketing. Its team page still says the contractor is a current partner, while an old case study accurately names a 2024 project. The team removes the current-partner badge and clarifies its link. It retains the dated project story and records an external directory correction as pending, not completed.

## Handoff and Content Factory context

The relationship owner receives the checked closeout and residual gaps. [Choose the right entity destination](https://local-service-spotlight.github.io/task-library/?task=follow-entity-linking-decision-tree#task-follow-entity-linking-decision-tree) receives any revised public identity rules; a separate authorized access owner handles remaining account roles.

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/when-trust-ends-the-link-ends/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=close-ended-relationship-endorsement-links#task-close-ended-relationship-endorsement-links)
- [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.