What this prompt does
This prompt designs a hub-and-spoke internal linking plan and returns a concrete linking map instead of linking theory. It frames the model as a senior SEO architect and asks for six deliverables: a pillar plus supporting articles for each cluster, an anchor-text strategy, cross-cluster bridge links, orphan-page detection and fixes, strategic links toward a money page, and a linking table with source, target, anchor, and reason for each link.
Four variables drive the map. [topic_clusters] defines the hubs the whole structure is organized around. [content_state] tells the model what already exists so it can spot orphans and gaps realistically. [money_page] is the conversion target that supporting articles should funnel toward where intent fits. [anchor_style] controls anchor diversity so the plan avoids over-optimized exact-match links that look spammy. Internal links are the cheapest ranking lever most sites own, and this turns linking-by-vibe into a deliberate hub-and-spoke architecture. Because the table gives a reason for every link, you can audit the plan later and prune anything that no longer serves the cluster.
When to use it
- Your pillars are stranded and supporting posts don't link up to them
- Your money page gets little internal link equity and you want to fix that
- You have orphan posts with no inbound links and need a remediation list
- You're building topical authority across several clusters and want them connected
- You want an anchor-text strategy that stays varied and natural
- You need a concrete source-to-target linking table you can execute row by row
Example output
You get a linking table — source URL, target URL, anchor text, and the reason for each link — plus a per-cluster summary. The plan names a pillar page and supporting articles for each cluster, lays out an anchor strategy in your chosen style, adds cross-cluster bridge links where topics genuinely overlap, lists orphan pages with fixes, and routes strategic links from supporting articles toward the money page where user intent fits.
Pro tips
- Watch the anchor strategy closely; set
[anchor_style]to descriptive, partial-match, and varied so exact-match anchors don't pile up and look spammy - Give an honest
[content_state](e.g. 40 posts, several with no inbound links) so orphan detection reflects reality instead of guesswork - Define
[topic_clusters]as genuinely distinct themes so the pillar-and-spoke grouping doesn't blur together - Only route links to
[money_page]where intent actually fits; forcing commercial links into informational posts hurts both - The model doesn't know your real URLs, so feed it your post list and titles for an accurate, executable map
- Add cross-cluster bridges only where topics truly overlap; manufactured bridges dilute the structure and confuse the topical signal you're trying to build
- Revisit the linking table after publishing new posts so fresh articles get wired into the relevant pillar instead of becoming the next orphan
