> For the complete documentation index, see [llms.txt](https://tmniche-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmniche-docs.keywordrush.com/core-concepts/interlinking.md). # Interlinking Internal links tie your site together — they pass authority between articles, guide readers, and build topical authority. TMN plans these links for the whole site during planning, then weaves them into each article as it's generated. You don't wire them up by hand. ## The link plan While building your Topic Map, TMN designs a recommended internal-link graph across the **whole** plan: * supporting (info) articles link **up** to the money articles and pillars they support, * related articles within a hub link to **each other**, * articles can link **across hubs** (depending on your silo settings), and * every **pillar** links to all the articles in its hub. Each suggested link comes with anchor text. {% hint style="info" %} **The graph is a recommendation, not a quota.** When an article is generated, TMN adds the suggested links *where they fit naturally* — it won't force every link in. How many actually appear depends on the article's topic and length. {% endhint %} ## How links appear in an article Links show up in two ways: 1. **Contextual links (preferred)** — placed inside the prose (and some blocks) right where the topic comes up. These use a `[nodelink]` shortcode (below). 2. **"Related Posts" block** — when there's no natural spot in the text, TMN adds the link in a Related Posts block instead, each with a short generated snippet and an adapted title. Contextual links are the priority; the Related Posts block is the fallback, so an important link is never lost. ## The `[nodelink]` shortcode A contextual link is stored as a shortcode. In the editor it looks like this: ``` …on a tighter budget, see our [nodelink id="7f3a9c12-4e8b-4d21-9a6f-2c5e1b8d0a44"]best wireless earbuds under $100[/nodelink] roundup before you decide. ``` It links by the target article's **ID**, not a fixed URL — so it keeps working even if the target's URL changes, and it can point to an article you haven't generated yet. That leads to one behavior worth knowing: * If the target isn't published yet, **visitors** just see plain text — never a broken link. * As an **admin**, you get a working link as soon as the target resolves — even for drafts or scheduled posts — so you can preview and click through. **Related Posts** blocks only list targets that are published or scheduled; drafts are skipped until they go live. (If they're all still drafts, the block shows a short placeholder in the editor.) You don't write or edit these by hand; TMN inserts them for you. ## What you control **Plan-wide — the wizard's Silo step.** A few settings shape how widely and how strongly TMN links: **silo architecture** (Classic / Hybrid / Topic Graph), **cross-hub linking**, **link strength**, **anchor diversity**, **cannibalization strictness**, and **always link upward to hub**. The defaults produce a clean silo — most people leave them alone. **Per article — the node drawer's Interlinking panel.** Open an article and the **Interlinking** panel shows what it *will link to*. There you can rename a link's **anchor text** or **remove** a link. Changes take effect the next time the article is generated. ![The Interlinking panel in the node drawer (outgoing links + anchor text)](/files/ai8KIPAaPoTKqa7wN1g8) ## Next * [**The Topic Map**](/core-concepts/topic-map.md) — how hubs, pillars, and articles fit together. * [**Edit your Topic Map**](/building-a-site/edit-topic-map.md) — shaping the plan, including per-article links. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://tmniche-docs.keywordrush.com/core-concepts/interlinking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.