Skip to main content
A campaign starts with a reason for a publisher to cite your work. Your agent evaluates that reason, gathers the missing context and keeps the decisions in your repository. AgentLinkOps has hosted pilot tools and a separately validated local research toolkit. The multi-page contact walk, mention and citation modules, qualification and action briefs are local research capabilities. They are not all callable through the hosted MCP endpoint. Check capability status before choosing a workflow.

​
Build a shortlist

Start with a target page, an audience and any backlink exports you already hold. Your agent can add publisher pages found through its own search and browser tools.
  1. Import the supplied inventory while preserving its source and dates.
  2. Inspect selected candidates and their surrounding page context.
  3. Record why your page helps that publisher’s readers.
  4. Keep unresolved questions beside the next action.
Hosted imports and selected candidate checks are available in the pilot. Supplier-backed discovery and live competitor-gap workflows remain in validation. An inventory gap means the source did not return a row; it does not prove a link is absent.

​
Find a public contact route

The hosted get_public_contacts tool extracts explicitly published emails and contact-page candidates from the latest saved public HTML for a watch. It needs a completed page check and available saved evidence. Read the contacts reference for inputs and refusal codes. The local research module can walk a bounded set of public pages within an allowed domain. It records page and depth limits, observation dates and attempted pages, including pages it could not read. Your agent can use its own browser to investigate an observed contact-page candidate.
An observed email address is not a deliverability check. A link labeled “Contact” is a candidate route until someone inspects it.

​
Investigate a mention or replacement citation

Unlinked mention: the local mention module distinguishes a matching mention from a page that already links to the target. Your agent checks identity, context and whether a citation would help the reader. Replacement citation: the citation module preserves the source anchor, surrounding context and destination URL. Destination checks carry repeated-failure evidence. Your agent decides whether the proposed replacement answers the original citation’s purpose. A timeout, challenge or incomplete page remains inconclusive. A dead URL alone does not establish that your page is a suitable replacement. The evidence guide explains confirmation and uncertainty.

​
Prepare a brief the agent can act on

The local campaign toolkit has six templates: guest contribution, resource addition, broken-link replacement, competitor sources, reclamation and custom campaigns. Qualification keeps observed evidence separate from judgments that still need review. Action briefs carry the target page, signal date, supporting evidence, open questions, next action and completion condition. Markdown and structured records describe the same task. Local queue work supports inspecting, rejecting, deferring and preparing an authorized local draft. Your agent owns drafting and communication through your chosen tools. AgentLinkOps does not send email or connect a mailbox. A saved draft does not mean a message was sent, and an observed link does not establish who created it.

​
Follow the placement

Declare a pursued placement as wanted in the local ledger. Once you expect it to exist, set expected. Checks write observations separately from your decisions. Hosted monitoring can preserve link history and independent destination health. Events, reports and configured delivery help you review later changes. Connect your agent to use the pilot, or consult the cloud tool reference for a particular operation. Return to the AgentLinkOps overview for the complete campaign flow.