agentlinkopsPrepare a link outreach handoff for your agent
Prepare a link outreach handoff with page evidence, destination fit, contact provenance and approval state so an agent can draft accurately and avoid duplicate contact.
A link outreach handoff should let the sender understand the page, the proposed contribution and the permission to act without repeating the research. Include the source URL, destination, reader benefit, contact provenance, prior contact and message approval state.
Keep research, drafting and sending as separate recorded steps. The agent link-building workflow gives an agent context for the task, while the link-building overview explains how a qualified page reaches that point. A prepared draft is not a sent message.
State the exact request
Name the source page and section. Explain whether the task is a correction, an added reference, an unlinked-mention suggestion or a proposed replacement for an unavailable resource.
Those requests need different evidence. A reclamation task should carry a prior positive observation. A new resource suggestion needs an explained audience fit. Do not hand the sender a generic instruction to “get a backlink” and expect accurate context to emerge later.
Provide the proposed destination and inspect it before handoff. If it redirects, requires an account or offers a paid product, state that plainly. The sender should not discover those facts after the recipient replies.
Attach enough evidence to support the message
Save the latest source-page check date and a concise description of the relevant passage. Include the observed hyperlink or its absence only when the inspection supports that statement.
Use a short source excerpt when needed, keeping attribution and the original URL. Do not copy an entire article into the message packet. Preserve larger internal evidence separately and restrict access to people who need it.
Google's spam policy addresses manipulative link creation. In this handoff, keep the proposed reader benefit explicit and avoid promises about ranking credit or disguised paid arrangements.
Verify the contact route and history
Record where the recipient address or form came from and what the page says it is for. A public editorial route is useful evidence; a guessed address is a different and weaker record.
Check previous correspondence, pending drafts, recent sends and suppression preferences. If someone declined the same suggestion, retain that outcome. Another agent should not restart the conversation because it imported the prospect from a second source.
Keep the contact details in your private working records. Public blog examples and exported reports should not include real personal addresses merely to make a template look complete.
Worked example: a resource correction packet
The following is a synthetic handoff for an unsent correction request:
| Field | Recorded value |
|---|---|
| Source | A volunteer handbook's supplies section |
| Issue | Its linked checklist now lands on a retired-resource notice |
| Proposed resource | A public replacement checklist with the same task scope |
| Reader benefit | Volunteers can prepare the supplies list before arriving |
| Contact route | Publisher's stated corrections form |
| Prior contact | No matching conversation found in the checked records |
| Message state | Draft awaiting owner approval |
| Send state | Not sent |
The packet should also hold the actual URLs and dates in the private record. The example labels are intentionally descriptive rather than a fabricated live prospect.
If the publisher's form accepts factual corrections only, review whether offering your own replacement fits that route. A broken reference does not automatically authorize a promotional message.
Make approval precise
Approval should identify the recipient, message and action. A general instruction to research publishers may authorize investigation and drafting without authorizing messages. Keep the current state visible to the tool or person that can send.
If the sender changes the factual claim or destination after approval, return that changed draft for the appropriate review. Avoid treating an old approval as a blanket permission for a new request.
For agent work, keep the send receipt separate from the prepared draft. A tool error or queued operation may leave the actual delivery uncertain. Record what the tool confirmed instead of assuming that an attempted send reached the recipient.
Close the loop after contact
Record the response and any resulting page change. If the editor agrees to add a link, verify the published page using the backlink monitoring checklist. A positive reply is correspondence evidence, while a page observation establishes the placement at a particular time.
If the answer is no, preserve the refusal and any contact preference. If there is no reply, follow only the already approved cadence. A complete handoff protects the research from being lost and lets the next agent continue accurately without inventing a new conversation.
Sources
- Spam policies for Google web search · Google Search Central · 2026-08-28
