What it is.
Across ten nodes, the first pass categorizes your sitemap, the second reads the draft and inserts links, and the third writes a report of what it did and why.
The thresholds are all published. Long content over 1,500 words gets 8-12 links, medium content 5-8, anchors run 2-6 words, and a retroactive archive run takes about 2 to 3 minutes per URL in batch mode.
TripleDart's own guide, and it names our own platform as the build surface. The rules work whether you automate them or hand them to a writer.
What you get.
- Link count bands by content length, starting at 8-12 links for long posts.
- Anchor text rules at 2-6 words, with duplicate-usage checking across the piece.
- A published Direction prompt for the model that does the inserting.
- A worked walkthrough on a 1,500-word post, from sitemap categorization to link report.
- A retroactive archive playbook, at about 2 to 3 minutes per URL in batch mode.
How to set it up.
Categorize the sitemap first, because link quality is decided by which pages count as priority destinations.
Set the link bands to match your own content lengths before you run anything.
Cap anchors at 2-6 words and turn on duplicate checking, so the same phrase does not repeat down the page.
Run one post and read the link report, which names the reason for each insertion.
Keep a human review, since a small share of insertions need adjusting by hand.
Batch the archive oldest-first, budgeting about 2 to 3 minutes per URL.
Use cases
Set a link count per length
Use the bands so a long post carries the right number of links.
Keep anchors short
Follow the anchor rules and the duplicate check on every draft.
Give writers a standard
Hand over the rules so linking stops being a matter of habit.
Best for
An archive nobody has linked
A few hundred posts with no cross-linking is a day of manual work or one batch run.
Writers who over-link
Numeric bands settle the argument about how many links belong in a post.
Pointing traffic at commercial pages
The guide argues for linking to /pricing over another blog post, and explains when.