Related topic paths
Related topic paths show how pages should connect.
A path is a simple route from one page to the next page a reader may need. It can also help CLEA plan pages in a better order.
Think in short paths
Do not try to connect every page to every other page.
Start with a short path of two or three pages. That is easier to write, easier to review, and easier to improve later.
For example:
Prompt gap page -> Product explanation page -> Setup guide
This path makes sense because the reader moves from problem, to answer, to action.
Topic path
A good link path moves the reader from the current question to the next page that helps them act.
Use dashboard context
Related paths can come from dashboard signals.
If analytics show a weak prompt group, that can point to a problem page. If sources show missing proof, that can point to a proof page. If a planned page needs repeated follow-up, that can point to a workflow.
| Signal | Possible path |
|---|---|
| Weak prompt result | Problem page -> product page |
| Missing source proof | Working page -> source page |
| New planned topic | Sitemap page -> Page Writer draft |
| Weekly page work | Calendar item -> workflow -> sitemap page |
Add the path to the page notes
Keep the path close to the page.
When CLEA opens the markdown file later, it can use those notes to write cleaner internal link sections.