How it works
Fourteen checks, one graph, and it never writes to your database.
The whole product is one tree. Everything else is a question asked of it.
01
It reads your site the way a crawler does
Sitemap first, then every internal link. It honours robots.txt and Crawl-delay, backs off when your server asks it to, and never fetches the same page twice.
02
It learns what your template looks like, and removes it
Navigation, footers, sidebars and related-post widgets repeat across pages, stay textually identical, and are dense with links. All three signals together separate furniture from writing — and on a typical WordPress site that furniture is 85–95% of every internal link on the page.
16,477 links a crawler sees 2,233 links inside the writing 03
It builds one graph, and asks five questions of it
Topics, Orphans, Depth, Waste and Anchors are five ways of looking at the same tree, ranked into one queue. The ranking across them is the part worth paying for: it decides what to do first.
04
You review, four keys and three seconds each
Every card shows the sentence the link would sit in, with the anchor underlined in your own words. Accept, reject, edit the anchor, skip the group. Undo is unconditional, at any time, including after you cancel.
05
The plugin renders them. Your posts are untouched.
Accepted links live in a manifest. The plugin applies them while the page is being built, so post_content is never written to. Deactivate it and your content is exactly as you typed it.
The constraint everything else is built around
Why “never writes to your posts” is a build rule, not a slogan
Tools in this category commonly rewrite your content in place. That is convenient right up until you want to leave, or the tool guesses wrong, or your editor and the plugin disagree about what a paragraph contains.
Silotree stores an anchor, a target, and enough surrounding text to find that anchor again if you edit around it. If the sentence is deleted, the link is abandoned rather than moved somewhere it was never meant to be. That relocation logic is written twice — once in TypeScript, once in PHP — and both run against the same shared vectors on every build, because two implementations that agree are worth more than one you have to trust.
What we will not tell you
That this will transform your traffic
Internal linking produces single-digit uplifts and they take months to separate from noise. The monthly report is five counts of what changed on your site — links added, orphans closed, waste removed — because those are true and checkable. When the effect on your site can be measured properly, that number will appear with its confidence interval, including if the interval crosses zero.