{"id":31,"date":"2026-07-12T23:57:32","date_gmt":"2026-07-12T18:27:32","guid":{"rendered":"https:\/\/jnkplugins.com\/blog\/automatic-internal-linking-wordpress\/"},"modified":"2026-08-03T19:12:14","modified_gmt":"2026-08-03T13:42:14","slug":"automatic-internal-linking-wordpress","status":"publish","type":"post","link":"https:\/\/jnkplugins.com\/blog\/automatic-internal-linking-wordpress\/","title":{"rendered":"How to Set Up Automatic Internal Linking in WordPress"},"content":{"rendered":"

Internal links are one of the highest-leverage, lowest-glamour parts of on-page SEO. When you link from one post to another, you spread ranking signals between your pages, you help search engines understand how your site is structured and which pages matter most, and you keep readers moving deeper into your content instead of bouncing back to Google. A well-linked site simply reads as more authoritative \u2014 to both people and crawlers.<\/p>\n

The catch is that doing it well by hand is a grind. Every time you publish, you’re supposed to remember which older posts are relevant, dig them up, and drop in natural anchor text \u2014 and then go back and link the new post from<\/em> those older ones too. Across a few hundred posts, that’s the first task that quietly gets skipped. This tutorial walks through automatic internal linking<\/a> in WordPress<\/strong> using JnK Linkweave (formerly Automatic Linker)<\/a>, a self-hosted plugin that does the tedious part for you without shipping your content off to a cloud black box.<\/p>\n

Still deciding which<\/em> tool to use? Compare your options first in our roundup of the best WordPress internal linking plugins<\/a> \u2014 this is the hands-on how-to<\/em> guide, and it assumes you’ve already picked JnK Linkweave<\/a> and just want it set up correctly.<\/p>\n

Why JnK Linkweave (and why “self-hosted” matters)<\/h2>\n

JnK Linkweave analyzes your content with a transparent TF-IDF and cosine-similarity engine that runs entirely on your own server. In plain English: it reads what your posts are actually about and scores how related they are to each other, then surfaces the strongest internal-link opportunities. There’s no per-suggestion metering and no SaaS platform holding your data hostage \u2014 the ranking math is understandable and it stays on your infrastructure.<\/p>\n

The free core \u2014 free to install from WordPress.org<\/a> \u2014 gives you an editor-sidebar panel with ranked internal-link suggestions as you write, unlimited<\/strong> auto-linking rules (map a keyword or phrase to a target URL and it links automatically), and read-only orphan-content and broken-link reports. The Pro upgrade (from $59\/yr or $239 lifetime; Freelancer $99, Agency $199) layers on bulk URL changes, one-click broken-link repair, CSV export of the reports, and optional AI re-ranking via your own LLM key. For most of this tutorial, the free version is all you need.<\/p>\n

Step 1 \u2014 Install JnK Linkweave<\/h2>\n
    \n
  1. In your WordPress dashboard, go to Plugins \u2192 Add New<\/strong>.<\/li>\n
  2. Search for JnK Linkweave<\/strong>.<\/li>\n
  3. Click Install Now<\/strong>, then Activate<\/strong>.<\/li>\n<\/ol>\n

    That’s it \u2014 no account signup, no API key, no external service to connect. Once it’s active you’ll see an JnK Linkweave section in your admin menu and a new panel available inside the block editor.<\/p>\n

    Step 2 \u2014 Let it index, then use the editor sidebar<\/h2>\n

    On first activation, JnK Linkweave indexes your existing posts and pages so it has a map of what everything is about. On a small site this takes seconds; on a large site give it a few minutes to finish in the background. Indexing is what powers the similarity scoring, so it’s worth letting it complete before you rely on suggestions.<\/p>\n

    Now open any post in the editor and look at the JnK Linkweave sidebar panel. As you write (or on an existing draft), it shows a list of ranked internal-link suggestions<\/strong> \u2014 other posts on your site that are topically related to what you’re working on, ordered by relevance. Review each one and insert the links that genuinely fit the sentence you’re writing. You stay in control: nothing gets linked without your say-so, so you can skip suggestions that would feel forced.<\/p>\n

    \"JnK<\/figure>\n

    A good habit is to run through the sidebar suggestions once when drafting and again during your final edit pass. Two or three strong, relevant internal links per post is usually plenty \u2014 the goal is helpfulness, not volume.<\/p>\n

    Step 3 \u2014 Create auto-linking rules for priority keywords<\/h2>\n

    Suggestions are great for one-off, in-context links. But for your cornerstone pages \u2014 the ones you always want linked whenever a specific phrase appears \u2014 set up auto-linking rules<\/strong> instead. A rule maps a keyword or phrase to a target URL, and JnK Linkweave will link that phrase automatically wherever it shows up across your site.<\/p>\n

      \n
    1. Open the JnK Linkweave rules screen.<\/li>\n
    2. Add a rule: enter the keyword or phrase (for example, your main service term or product name) and the URL it should point to.<\/li>\n
    3. Repeat for each priority page. The free version supports unlimited<\/strong> rules, so you can cover every cornerstone page you have.<\/li>\n<\/ol>\n

      One important setting to configure: a sensible maximum number of links<\/strong> per phrase or per post. Auto-linking rules are powerful, and without a cap the same keyword can get linked a dozen times on one page, which looks spammy and dilutes the value of each link. Setting a conservative max (often just one link per phrase per post) keeps the linking clean and natural.<\/p>\n

      \n

      Tip:<\/strong> Reserve auto-linking rules for high-value destinations \u2014 pillar posts, key product or service pages, cornerstone guides. Let the editor-sidebar suggestions handle the long tail of contextual links.<\/p>\n<\/blockquote>\n

      Step 4 \u2014 Find and fix orphan content<\/h2>\n

      An orphan<\/strong> is a post or page with no incoming internal links \u2014 nothing on your own site points to it. Orphans are a real problem: search engines discover and value pages partly through internal links, so an orphaned post is harder to crawl and tends to underperform no matter how good it is.<\/p>\n

      Open the orphan-content report<\/strong> to see every page on your site that has zero incoming internal links. Then work through the list: for each orphan, find a relevant existing post and add a link pointing to<\/em> the orphan (the editor sidebar makes finding a natural home easy). This single habit \u2014 regularly clearing your orphan list \u2014 often produces the biggest ranking improvement, because it puts previously invisible pages back into your site’s link graph.<\/p>\n

      \"JnK<\/figure>\n

      Step 5 \u2014 Check the broken-link report<\/h2>\n

      Links break over time: you change a slug, retire a page, or move domains, and suddenly internal links point nowhere. Broken internal links waste crawl budget and frustrate readers. JnK Linkweave’s broken-link report<\/strong> flags them so you’re never guessing.<\/p>\n

      In the free version the report is read-only \u2014 it tells you exactly what’s broken so you can fix each link manually. If you manage a larger site or migrate often, Pro adds one-click broken-link repair<\/strong> and bulk URL changes<\/strong>, so after a slug rename or a domain move you can update every affected internal link at once instead of editing posts one by one. Pro also lets you export any report to CSV<\/strong>, which is handy for handing an audit to a client or tracking progress over time.<\/p>\n

      Step 6 (optional, Pro) \u2014 AI re-ranking with your own key<\/h2>\n

      The core TF-IDF engine is fast, transparent, and free \u2014 and it’s genuinely all most sites need. If you want an extra layer of nuance, Pro offers optional AI re-ranking via BYOK<\/strong> (bring your own LLM key): you connect your own provider API key, the model re-scores the suggestions for relevance, and you pay the AI provider directly with no per-suggestion markup from us. It’s strictly optional \u2014 think of it as a refinement on top of a system that already works well, not a requirement to get value from the plugin.<\/p>\n

      Internal-linking best practices<\/h2>\n