---
name: step-14b-run-linkwhisper-for-internal-links
description: "Review link ideas from Link Whisper. Add only the links that help a reader, then check them on the page."
category: Content Factory — Post
stage: Post
definitive_article: https://localservicespotlight.com/article-guidelines/
status: complete
---

# Step 14b: Run LinkWhisper for internal links

A link tool can suggest pages, but it cannot choose your story for you. This guide helps you pick links that make sense. Start with the page’s main topic, then read each suggested target before you add it.

**The path:** Topic map → Review suggestions → Scoped link edits → Saved link checks.

**Use this when:** A prepared article needs useful outgoing and incoming links, and the site uses Link Whisper.

## Inputs
- The exact article and current [SEO Tree](https://blitzmetrics.com/seo-tree/) map, plus the [entity-linking guide](https://blitzmetrics.com/entity-linking/) for choosing owned and identity destinations.
- A working Link Whisper installation, license/features where required, and current link data. Link Whisper is a WordPress add-on that suggests and adds links. Check that its installed version supports the editor and content type.
- Authority and access to change this article and any older pages chosen for incoming links.
- The page’s publication state, current revision and a place to record each source sentence, anchor, target and result.

## First-run prompt

> Review Link Whisper suggestions for the exact article and page map I provide. Read targets and choose useful links; apply only scoped edits. Check older source pages before adding incoming links. Do not enable auto-linking or paid AI by default. Report inserted links separately from suggestions and staged edits.

## Steps
1. Open the existing Link Whisper setup and confirm it is ready for this post type. Verify that its content scan includes the current article revision; run the approved scoped scan or name the setup owner when data is stale or setup is missing. Do not accept launch-wizard defaults blindly: current options may create automatic linking rules.
2. Read the article’s outgoing suggestions. These point from the article to other pages. Open each candidate and compare it with the sentence’s meaning and the main topic owner.
3. Choose a small set of helpful links. Point method mentions to their maintained owned guide; use accurate identity destinations and precise primary proof where needed. Reject irrelevant, duplicate, misleading or competing-hub suggestions.
4. Edit anchors into clear words that describe the target. Follow the maintained house guidance of roughly three to six descriptive words where it fits, without changing the sentence’s meaning to hit a word count.
5. Apply only the reviewed outgoing links through the supported editor/plugin control. Save and check that the expected sentences and URLs survived. If the editor/builder is unsupported, route a manual source-aware linking task and do not claim the plugin succeeded.
6. Review incoming suggestions, which would add a link on an older page pointing here. Confirm each older page is in scope and that the final target will be accessible to its readers. Avoid publishing a public link to a private draft.
7. Apply the specific authorized incoming edits and verify the changed source pages. Record any separate owner’s pending action. Do not turn a single-page link pass into cross-site connection, autolinking, paid AI processing, or a global search-and-replace.
8. Check every added URL and named fragment, first in the saved content and then in the served body when published. Update the inventory with actual outgoing/incoming paths and any pending work. Suggestions or map lines are not proof that links were inserted.

## Definition of done (QA checklist)

- [ ] The plugin setup, scan freshness and supported source are known; a missing/stale setup has a named owner and optional automation has not been silently enabled.
- [ ] Every accepted suggestion has a source sentence, meaningful anchor and verified target.
- [ ] The page has the required relevant upward/incoming paths, or exact unresolved edits are recorded.
- [ ] Changes to older pages stayed in scope and do not expose a private draft link.
- [ ] Saved and served links are verified as applicable, with no unsupported ranking or zero-orphan guarantee.

## Example(s)

**Fictional teaching example — no plugin was run.** A sample quote article gets three suggested destinations:

| Suggested anchor | Destination | Decision |
| --- | --- | --- |
| how our quotes work | Main repair-quotes guide | Accept; it explains the current sentence |
| our clear process | Unrelated tire-sale page | Reject; the shared word “process” is not enough |
| before your shop visit | Visit-planning guide | Accept after reading the guide |

An incoming suggestion would link an older guide to the new article, which is still a private draft. The publisher stages that sentence and adds it when the target is public under the actual job scope. “Two outgoing saved; incoming staged” is the truthful result.

## Handoff and Content Factory context

The publisher receives the changed sentences and live/draft link state. [Check SEO Tree placement](https://local-service-spotlight.github.io/task-library/?task=place-content-on-seo-tree-with-proper-links#task-place-content-on-seo-tree-with-proper-links) confirms the page’s place, then [Check the full article checklist](https://local-service-spotlight.github.io/task-library/?task=verify-all-items-on-blog-posting-checklist#task-verify-all-items-on-blog-posting-checklist) verifies the article.

This task serves **Post** in the [Content Factory](https://blitzmetrics.com/content-factory/). Produce supplies the source, Process prepares it, Post places and checks it on the agreed channels, and Promote distributes proven work under its own scope. The task’s actual handoff above defines the next step; list order alone does not create a prerequisite.

## When this runs

Run for a prepared article or defined link repair. A new article may require fresh plugin data; a tool installation is not a recurring linking schedule.

## First-run setup and continuity

Use the exact account, source, destination and authority recorded for the job. Carry out publication, messages or repairs already authorized once their required checks pass; do not ask for the same approval again. If an action is outside that scope, finish the authorized work and state the specific remaining need. A login, plugin, or task file does not itself grant new authority.

Keep the latest state, record IDs, revisions and next owner in the project tracker or files. Before a retry, check the current saved/sent/published item to avoid duplicates or overwriting another edit. A model has no guaranteed memory, scheduler or account access just because it is called persistent. A future check needs a configured timer or a named person.

Keep all agent media previews muted with volume zero before playback. If this cannot be verified, use captions, metadata or still frames and state what was not tested. No first-load autoplay is part of these page instructions.

## Write up the real run

For each actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this exact task, source revision, trigger, work, decisions, evidence, result and next owner. Failed, partial and blocked attempts still get a written record. A private draft is a valid writing outcome; public publication follows the existing scope.

Keep one stable execution ID for the actual task run. Retries, checks and changed artifacts do not add runs. A separately scoped child task may have its own ID linked to its parent; writing the parent’s meta record is part of that same run. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains the distinction. Teaching examples below or above are not execution evidence and must not enter the run count.


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

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

- **Phase:** Post
- **Importance:** 4/5 `●●●●○` — frequency 4, revenue 4, gating 2 (runs every factory cycle or weekly; creates the asset ads amplify)
- **Suggested previous station:** `step-14a-configure-rankmath-seo-plugin`
- **Suggested next station:** `place-content-on-seo-tree-with-proper-links`
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

- Canonical article: https://localservicespotlight.com/article-guidelines/
- Exact Task Library record: [Step 14b: Run LinkWhisper for internal links](https://local-service-spotlight.github.io/task-library/?task=step-14b-run-linkwhisper-for-internal-links#task-step-14b-run-linkwhisper-for-internal-links)
- Working writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Link Whisper’s feature guide](https://account.linkwhisper.com/knowledge-base/link-whisper-starter-guide/)
- [Link Whisper setup requirements](https://account.linkwhisper.com/knowledge-base/how-to-install-and-activate-link-whisper/)
- [Link Whisper launch-wizard behavior](https://account.linkwhisper.com/knowledge-base/link-whisper-launch-wizard-guide/)
- [Entity linking: choose the right person, company or guide](https://blitzmetrics.com/entity-linking/)

## Review and evidence still needed

The original contributor status in the header is preserved. It does not certify this proposed rewrite or prove that this account, publication, message, player or check has run. Every worked teaching example is explicitly invented; replace it with actual evidence when documenting a real execution.
- The actual plugin version, license, editor support, link scan and insertion results remain unverified until a real site run.