SEO

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.

The playbook

Internal links are the one ranking signal a site controls completely, and the most under-used. Pages that earn impressions but sit at position 12 with two internal links are the cheapest ranking gains on the site. This playbook finds them and names the links to add.

Sequel supplies the traffic data. The crawl uses your own browsing.

Steps

  1. Build the target list. google_search_console.query with dimensions: ["page"], 90 days ending 3 days ago, rowLimit: 1000, and with dimensions: ["query", "page"], rowLimit: 5000. Add the sitemap URLs. This is every page the site or Google considers real.

  2. Crawl a bounded set. Start from the homepage and the top 100 pages by clicks. Fetch each, extract every same-host <a href>, and record source, target, anchor text. Cap the crawl at a few hundred pages and state the cap. Use sequel_workbench for the loop if you can execute code.

  3. Separate template links from editorial links. A link that appears on most crawled pages (navigation, footer, sidebar) is a template link. Count it, but count it separately; editorial links from within body content carry more meaning. A simple rule: a target linked from over 80% of crawled pages is template-linked.

  4. Count inlinks per target, total and editorial, and join to the Search Console data by path.

  5. Find the findings.

    • Orphans: pages in Search Console or the sitemap with zero inlinks in the crawl. If they earn clicks, they are hanging on external links alone.
    • Under-linked opportunities: pages with meaningful impressions at position 8 to 20 and fewer than three editorial inlinks. These are the ranking gains.
    • Generic anchors on important targets: "click here", "read more", "learn more" on pages that should be described by their topic.
    • Hubs: high-traffic pages with few outbound editorial links, which could carry links to the under-linked pages.
  6. Recommend specific links. Ten recommendations, each: from page A (a hub or a topically related page with traffic) to page B (an under-linked opportunity), with the anchor text drawn from B's top query. Say what makes A a sensible source.

Gotchas

  • A crawl of a few hundred pages is a sample. Inlink counts are lower bounds. Say so, and raise the cap for a large site if the user wants precision.
  • Links behind JavaScript may be invisible to a plain fetch. If the navigation seems to have no links, that is why; note it rather than reporting the whole site as orphaned.
  • Do not add links for the sake of it. A link the reader would not click is a link Google discounts. Every recommendation should make sense on the source page.
  • Redirected or canonicalised targets should be linked at their final URL. Continue with redirect-chain-audit if the crawl found links pointing at redirects.
  • Search Console lags 2 to 3 days. End the window 3 days back.

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 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.

Backlink profile health check

See who links to the site and whether the backlink profile is healthy: referring domains, authority distribution, anchor text mix, dofollow share and concentration risk from Ahrefs, optionally compared against a competitor.

Put this playbook to work

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