Auto-Plan Internal Links with Claude (from GSC Data)

GSC export/MCP → Claude analyzes ranking queries → human approval → MCP auto-edits → revertible

Who

Site owners or SEO practitioners with MCP-connected websites

You get

Automatically identify high-ranking queries and insert natural internal links, with a changelog for rollback

You need

Claude · Search Console · WordPress · MCP

Steps

1. Get GSC Data

   Export the last 3 months of query data from Google Search Console (articles, queries, impressions, positions), or pull it directly via a GSC MCP connector.

2. Feed Data to Claude

   Provide the GSC data to Claude as an attachment or in context, ensuring it includes each article's queries and ranking positions.

3. Ensure Website MCP Is Connected

   Make sure your website has an MCP configured so Claude can read and modify site content. The author uses a custom WordPress MCP plugin; MCP connectors exist for various blogging frameworks.

4. Run Internal Linking Prompt

   Send the following prompt in Claude, replacing [site name] with your website's MCP name. Claude will analyze the data, plan internal links, and generate a table of proposed changes for your approval.

   Execution prompt · Source text。Claude chat input; replace [site name] before sending

   Copy prompt

   I've attached my Google Search Console export (or: pull it from the GSC connector) for the last 3 months. My website is connected through the [site name] MCP.
   
   1. For each article, find the queries where it ranks best (position 1–10, decent impressions). Those are its target anchors.
   2. Go through every published post. Wherever the text naturally mentions another article's top query (or a close variant), turn that phrase into a link to that article.
   3. Rules:
      - Max 3–5 new internal links per post, spread through the body (no headings, intro sentence, or existing links)
      - Never link a post to itself, and only link each target once per post
      - Anchor text must read naturally. Don't rewrite sentences just to force a keyword in
      - Prioritize sending links to pages ranking 4–15 (they gain the most)
   4. Before changing anything, show me a table: source post → anchor text → target URL → target's query and position. Wait for my OK.
   5. After I approve, make the edits through the MCP, then give me a changelog so I can revert if needed.

5. Review and Approve Changes

   Review Claude's proposed changes table (source post → anchor text → target URL → target query and position). Once confirmed, reply to approve. Claude will execute the edits via MCP and return a changelog for potential rollback.

I've attached my Google Search Console export (or: pull it from the GSC connector) for the last 3 months. My website is connected through the [site name] MCP.

1. For each article, find the queries where it ranks best (position 1–10, decent impressions). Those are its target anchors.
2. Go through every published post. Wherever the text naturally mentions another article's top query (or a close variant), turn that phrase into a link to that article.
3. Rules:
   - Max 3–5 new internal links per post, spread through the body (no headings, intro sentence, or existing links)
   - Never link a post to itself, and only link each target once per post
   - Anchor text must read naturally. Don't rewrite sentences just to force a keyword in
   - Prioritize sending links to pages ranking 4–15 (they gain the most)
4. Before changing anything, show me a table: source post → anchor text → target URL → target's query and position. Wait for my OK.
5. After I approve, make the edits through the MCP, then give me a changelog so I can revert if needed.