SEO

Recover lost backlinks

Find the backlinks a site recently lost, work out why each one disappeared (the linked page was removed, the link was edited out, a redirect broke), and build a prioritised list of links worth recovering with a fix on your side or a short outreach.

The playbook

Most lost backlinks are lost for reasons that have nothing to do with the linking site changing its mind: the page they pointed at was deleted or moved on your side. Those come back with a redirect and no email. This playbook separates those from the ones that need outreach and the ones that are gone for good.

Steps

  1. Pull the backlinks with recency. ahrefs.backlinks with the site as target, mode: "subdomains", limit: 1000. Each row has the source URL, the target URL on the site, anchor text, the source domain rating and traffic, first and last seen dates, and link type.

  2. Define lost. A link whose last_seen is older than 60 days is treated as lost; within 30 days is alive; between is uncertain. State the cutoff. Ahrefs recrawls busy pages often and quiet pages rarely, so a stale date on a tiny site is weaker evidence than one on a large site.

  3. Prioritise. Sort the lost list by source domain rating, then by source traffic. The top 20 to 30 are worth diagnosing individually; the rest get a summary.

  4. Diagnose each of the top rows with your own browsing. Fetch both the source URL and the target URL.

    • Target URL returns 404 or 410, or redirects to the homepage: the loss is on your side. Restore the page or 301 it to the closest live equivalent. Highest return, no outreach.
    • Source URL returns 404: their page is gone. Usually unrecoverable; note it and move on.
    • Source URL is live and the link is gone, or now points at a competitor: outreach. Note what replaced it, since that is the pitch.
    • Source URL is live and the link is still there: Ahrefs is stale, not the link. Mark it as a false positive and do not count it.
  5. Report. A table of lost links sorted by source DR: source URL, target URL, anchor, DR, source traffic, last seen, diagnosis, action. Then two lists: your URLs to restore or redirect (with the number of links each recovers), and the outreach list with the specific page and the reason the link was worth having.

Gotchas

  • Stale is not lost. Step 4 exists because a large share of "lost" links in any index are simply not recrawled yet. Report the false-positive rate you found.
  • Redirect to the equivalent page, not the homepage. A homepage redirect keeps the link but loses the relevance, and Google treats mass homepage redirects as soft 404s.
  • The 1000-row cap is the top slice on large sites. Say so, and offer to rerun with mode: "prefix" on a section of the site.
  • Nofollow links are worth recovering too when the source has traffic; they send visitors even if they pass no authority.
  • Do not promise a ranking change from recovered links. Report what was recovered and what to watch.

Sequel CLI

Install Sequel skills into your agent

One command connects your agent to Sequel and installs the Sequel skill, so it knows this playbook exists and reads it when a question matches. The CLI signs you in, provisions a scoped API key and writes the config for you.

Already have an MCP client?

https://api.sequel.sh/mcp

Point it at this URL and sign in when prompted, or send an API key from Settings as a Bearer token. Skills come with it; nothing else to install. Manual setup per client

  1. 1

    Install the Sequel CLI

    One line installs the latest CLI with whatever package manager you have.

    curl -fsSL https://sequel.sh/install | sh
  2. 2

    Sign in

    Authenticate in your browser and pick an organization.

    sequel login
  3. 3

    Install into your agent

    Writes the MCP config and installs the Sequel skill file for agents that support skills. Pick an agent from the list, or target one directly by its slug.

    sequel install
    • Claude Code
      sequel install claude-code
    • Claude
      sequel install claude
    • Cursor
      sequel install cursor
    • VS Code
      sequel install vscode
    • Windsurf
      sequel install windsurf
    • Zed
      sequel install zed
    • Codex
      sequel install codex
    • OpenClaw
      sequel install openclaw
    • Hermes
      sequel install hermes

More like this

Other SEO skills

Analyze high-ranking landing pages

See which pages perform best in organic search: the landing pages that earn the most clicks and impressions, the queries behind each one, and how they compare with competitor estimates from Ahrefs.

Audit internal links to important pages

Audit the site's own internal linking: crawl navigation and body links between the site's pages to find valuable pages with too few inbound internal links, orphan pages, and the handful of cross-links that would lift striking-distance rankings.

Audit or draft an llms.txt

Check whether the site has an llms.txt, whether it follows the spec and points at the pages that matter, and if it is missing draft one from the pages Search Console shows people actually find, so AI assistants get a curated map of the site instead of guessing.

Audit redirect chains and loops

Follow every redirect on the URLs Search Console still sends traffic to, on the sitemap, and on backlinked pages, to find chains, loops, redirects to the homepage, and temporary redirects that should be permanent, so link equity and crawl budget stop leaking.

Audit referring domain quality

Grade the domains linking to a site by authority, traffic and link count, spot concentration risk and link-farm patterns, and separate the referring domains that carry weight from the ones that are noise.

Audit titles and meta descriptions

Compare the title and meta description of each top page against the queries it actually ranks for in Search Console, and find missing, duplicate, truncated or misaligned metadata on the pages where a rewrite would earn the most clicks.

Put this playbook to work

Connect a source, ask the question, and the agent follows these steps. Free to start.