When should you use it?
- You have a genuinely useful page (template, tool, guide) in a niche full of older resource articles
- You found guides with outbound links that no longer work
- You want outreach that helps the editor first
Not for: Pitching a sales or pricing page as a replacement for a resource; Building a replacement page before you know the opportunity is real; Mass emailing every page that has an error in a link checker
What do you need, and what do you get?
You need
- Guides in your niche with suspected broken outbound links, from a crawl or a link checker
- Access to an archive service to see what the missing page used to offer
- Your own resources, with a line on what each helps a reader do
You get
- Each suspected link sorted into confirmed failure, redirect, or unverified access error
- For confirmed failures, what the missing resource did, from the archived copy where available
- A match or no-match against your pages, with the reason
- For real matches, a short note naming the link, where it sits on the page and why your page fits
How does it work, step by step?
- Collect candidatesCrawl a set of relevant guides or use a link checker's export to list outbound links that look broken.
- Confirm the failureHave the agent request each link and sort results. A block or rate limit is not proof of a dead page, and a redirect may still land somewhere useful.
- See what was thereOpen an archived version to see what readers got from the missing page.
- Match honestlyOffer your page only if it does that same job. If nothing fits, note the gap and stop; build something only after you confirm demand.
- Draft the noteWrite a few lines naming the heading, the dead link and your replacement. Read it against the live page before sending.
The prompt
The original prompt by @BuildingWaves, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, ChatGPT agent and Claude. Values in lime are placeholders.
Original prompt by @BuildingWaves
Check these suspected broken external links and their referring pages. Separate confirmed failures, redirects and unverified access errors. Establish what the missing resource helped readers do. Compare that with my resources. For a real match, draft a factual note naming the broken link, its location and why our page is a useful alternative. Don't create a replacement until we've confirmed the opportunity.
Exactly as published by @BuildingWaves in X Article: SEO/AEO need backlinks, babe. Get them with AI.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
Check suspected dead links on other sites and draft notes only for real matches. Do not send anything. Suspected links and the pages they sit on: {suspected_links}. My resources: {my_resources}. 1) Request each link. Sort into: confirmed failure (404 or 410), redirect (note where it lands), or unverified (blocked, timed out, other errors). 2) For confirmed failures, check an archived version where available to describe what the missing page helped readers do. 3) Check my resources against that need. If one does the same job, explain why; if not, say there is no match. Do not propose building anything yet. 4) For each real match, draft a note under {max_lines} lines: the section heading, the dead link, my replacement and what it offers. No claims about their search ranking. 5) Add a public contact page for the editor if one exists.
What can go wrong?
- Link checkers report many false failures from bot blocks and timeouts. Recheck in a normal browser before writing.
- Editors get many of these emails. A specific location and a real fit matter more than polish.
- Promising that the swap will help their search ranking is unfounded and off-putting. Leave it out.
- Some guides are no longer maintained. Check for a recent update date or an active contact before spending time.
Our take
Broken-link outreach has a bad name because most of it is lazy: a scraped list, a pricing page offered as a replacement, and a vague promise about rankings. Ghaffari's version is the respectable kind, and his prompt is worth quoting as published. It separates confirmed failures from redirects and access errors, works out what the missing page did, and forbids building a replacement before the opportunity is confirmed. We kept those rules and added a few practical checks: recheck in a normal browser, skip guides nobody maintains, and leave out any claim that the swap will help the editor's search ranking. His article's sample note is a good model of tone: the location, the problem, the alternative, and a line that the heads-up stands on its own even if they decline. Google's link spam policy, linked below, is a useful reminder that a helpful editorial link is fine while anything paid or forced is not. In our dry run with three fictional suspects, the agent confirmed one 404 for a late-payment email example, matched it to the site's own template, and drafted a four-line note naming the section. It marked a second link as unverified after a 403 and found the third had simply moved to a working new address, so it drafted nothing for either.
Where the time goes back: Separating real dead links from false alarms and checking archives is slow detective work. The agent does it, so you only write to editors with a confirmed problem and a real fix.
FAQ
Should I build a page just to replace a dead link?
What should the note say?
Does the agent send the email?
Source and credit
The original prompt on this page is by @BuildingWaves, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- X Article: SEO/AEO need backlinks, babe. Get them with AI
- Creator
- Kourosh Ghaffari (@BuildingWaves)
- Published on
- X
- Original date
- Oct 26, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 26, 2026: passed. Dry-run tested by our AI test agent on sample input. Failures, redirects and blocks separated; honest match; no ranking claims; draft only.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 26, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Also see: Spam policies for Google web search: link spam by Google Search Central. More official guidance we used; credited and linked only, nothing from it is reproduced word for word. Not legal or financial advice.
Are you the creator? Claim or correct this page.