Prove Visibility Progress

This workflow writes your progress report from live visibility data. The agent checks whether DR, TrueDR, traffic, and referring-domain evidence moved, audits your weakest public backlink evidence, exports the numbers when a dashboard or client report needs them, and picks one realistic next action toward getting seen. You get a plain update ready to paste to a client or founder.

Paste this into Claude, Codex, Cursor, ChatGPT, or another coding agent. The website, the expected output, and the approval boundary are already written in. First run? Complete the one-time setup; your agent can handle that too.

This is the sequence the agent follows. It reads data on its own. You approve each send or change.

1. 01

   Track movement

   Run monitor_sites to check whether TrueDR moved this week.

2. 02

   Audit backlinks

   Run get_trust_map to find the weakest public backlink evidence.

3. 03

   Export evidence

   Run export_site when the numbers feed a dashboard, script, or client report.

4. 04

   Pick an exchange

   Run find_link_exchanges to choose one relevant link exchange worth proposing.

5. 05

   Explain progress

   The agent writes a client or founder-ready progress update.

The exact MCP tool calls behind the prompt. Your agent runs these against the verifieddr server; the ones that send anything still stop for your approval.

# 1. Check whether TrueDR moved this weekmonitor_sites { site: "yourwebsite.com" } # 2. Audit the weakest public backlink evidenceget_trust_map { site: "yourwebsite.com" } # 3. Export the numbers for a dashboard or client deckexport_site { site: "yourwebsite.com" } # 4. Pick one link exchange worth proposingfind_link_exchanges { site: "yourwebsite.com" } # 5. Write a client/founder-ready progress update# the agent writes this from the data above