Your help articles can still answer the next question.
A help centre grows one ticket at a time, so the same feature ends up explained in nine articles that do not link to each other. Silotree finds the article that should own each question and suggests links from the ones you already wrote. Approve them from a weekly email, about ten minutes a week. Code samples are never touched.
articles explain exporting in some form. The one that covers it fully has two links in, and an older version still answers the search.
- Main pageExporting your data: the complete guideHelp article · 2 links inSearch position #5
- CompetesHow to export invoices to CSVHelp article · same search · 6 links inSearch position #9
- CompetesExporting (legacy dashboard)Older version · still answers the searchSearch position #14
- No links inScheduled exportsNew feature · 0 links in, not even from its launch postSearch position #28
Point the narrower articles at the complete guide, and link the launch post to the feature it announced. Both are sentences you already wrote.
Three things a general linking tool misses here
One question, nine answers
When several articles answer the same search, they split it. Search Console shows which ones actually come up together, which is a better test than titles in a help centre where every article starts with “How to”.
What Silotree doesFind the articles answering the same searches, say which one is winning today, and propose links from the narrower ones into it, rather than suggesting you delete or merge anything.
Old versions still answering searches
Documentation for a retired screen keeps ranking long after the screen is gone. Where the old page carries a canonical tag naming the current one, Google treats them as one, and asks that your own links point at the canonical address1.
What Silotree doesNever suggest a link to a page whose canonical names another page, and report links in your writing that point at a redirect, with a one-click fix to point them at where the page now lives.
Code samples, headings and accordions
A link inserted into a code block breaks the example, and one inserted into a heading changes the table of contents. Help articles are full of both, plus collapsible sections and plugin blocks.
What Silotree doesWrite links only into ordinary paragraphs, lists and quotes, never inside code, headings, buttons, accordion summaries, shortcodes or any block another plugin owns. If there is no safe place for a link, it is skipped, with the reason shown.
The detail, when you want it
How it works on a help centre
Ten minutes a week, on posts you already wrote
- 1
Get a free audit
Paste your address. Silotree reads every post and lists the ones nothing links to, the posts readers and Google rarely reach.
- 2
Clear the backlog this afternoon
Every suggestion at once, best first: a sentence you already wrote, a phrase in it, and the post it should lead to. Approve the strong matches in one click, skip what doesn’t read well.
- 3
We write them in
Press Write and the plugin adds exactly those links, in one batch. A revision is saved first, and any batch comes out again in one click. After that, a weekly email brings up to five new ones.
Articles from a knowledge-base plugin are read and linked to like posts, because Silotree reads every public post type. Writing into them needs WordPress revisions for that post type2; where the plugin registers its articles without them, Silotree reads them and says why it will not write.
Your articles are written to close tickets, not to fit together
What is different about help centres
A help centre is written in answer to whatever support was asked this week, so its shape comes from the inbox rather than a plan. The blog is written by marketing, the docs by support, and nobody links one to the other. Google asks that every page you care about has a link from at least one other page on your site3, and in a help centre the pages that fail that test are usually the newest features.
If your help centre is not on WordPress, or is behind a login
Where Silotree is weaker for you
Many help centres live on a hosted help-desk tool rather than WordPress. Silotree crawls any public site, so the audit works there, but writing links back is WordPress-only. And it reads only what a search engine can: articles behind a customer login are invisible to it, as they are to Google.
Questions people ask
Will it link our blog to our docs? · Does it handle docs in several languages? · Can we keep some pages out entirely?
Will it link our blog to our docs?
Yes, when they are on the same site. A launch post that names the feature is the obvious source for a link to its help article, and when you publish a new article it asks straight away which older posts should point to it.
Does it handle docs in several languages?
Link wording is tuned for English, German, French, Spanish, Italian, Dutch and Portuguese, and a link never crosses from one language to another where a multilingual plugin says which is which. Other languages get the full audit.
Can we keep some pages out entirely?
Yes. The never-link list in the plugin keeps chosen posts, post types, categories and words out, in both directions: a listed page is never given a link and never linked to. Release notes and legal pages are the usual candidates.
Sources
3 sources, each opened on 15 October 2026
Sources
Each one opened and read on 15 October 2026.
You already wrote the articles.
Give them a way to be found.
Free audit with no account. Your first 3 links are written free, and paid plans come with a 7-day money-back guarantee.
Free audit · No account needed · No changes to your site