Verified against ChatGPT · 2026-08-09
Design a pillar page outline that actually unifies a scattered set of existing posts instead of duplicating them
Takes a messy list of existing blog posts on a related topic and drafts a pillar page outline that organizes and links them into one coherent hub, flagging which posts should be merged, kept separate, or retired.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Pillar page purpose: Everything a small business needs to know about 1099 contractor compliance. Existing related posts (title + brief summary each): '1099 vs W2: What's the Difference' (basic comparison); '5 Contractor Misclassification Red Flags' (compliance-focused); 'How to Send a 1099-NEC' (tax filing mechanics); '1099 vs W2: Which Should You Hire' (near-duplicate of the first post, different angle). Business goal for readers landing on this pillar: Trust us enough to start a free trial of our contractor payment and compliance tool. Before outlining anything, first sort the existing posts into three categories: posts that should become sections summarized within the pillar with a link out to the full post, posts that substantially overlap with each other and should probably be merged into one before the pillar links to it, and posts that don't actually belong under this topic even though they're tagged similarly and should stay unlinked from this pillar. Explain your reasoning for anything in the second or third category — do not just move it silently. Then draft the pillar page outline itself as H2/H3 headings that represent the complete topic at a survey level, each with one line describing what that section covers directly on the pillar page (not just a link) and which existing post(s), if any, it should link out to for depth. The pillar page's own text must add real value beyond being a table of contents — each section needs enough original framing that someone who reads only the pillar and clicks nothing still understood the topic at a useful level. Flag any part of the topic that isn't covered by any existing post — these are new subtopics we'd need to write, not just link to. End with a one-paragraph internal linking note: which existing posts should link back up to this new pillar, and any anchor text suggestions that would need updating on those pages. Output as: (1) the sort of existing posts into the three categories with reasoning, (2) the full H2/H3 outline with linking notes, (3) the coverage gaps, (4) the backlink note.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Most pillar-page requests fail because they're written as a fresh outline in isolation, which produces a page that either duplicates existing posts word-for-word or ignores them entirely — forcing the sort-first step means GPT-5.1 has to reason about the existing corpus as material to be organized rather than generating a new structure from scratch, which is the actual job a pillar page does. Requiring an explicit reason for anything moved into the merge or exclude categories counters the model's tendency to quietly reorganize content without surfacing the judgment calls involved, which matters here because merging two posts or excluding a tagged-similar post are both decisions a content owner needs visibility into before they happen, not silent recommendations buried in an outline. The instruction that each section must add real value beyond being a table of contents addresses the single most common failure mode of AI-drafted pillar pages: because the model has been asked to "link out" to existing depth, it defaults to writing thin one-line section stubs that are functionally just a linked list, which search engines and readers both recognize as low-value duplication of a sitemap rather than a genuine hub page. Explicitly asking for coverage gaps — subtopics no existing post addresses — turns the exercise into a content-planning tool as well as an architecture tool, since a pillar strategy that only reorganizes what already exists will have visible holes the moment a competitor's pillar covers the full topic.
What you get back
Sort: Merge — '1099 vs W2: What's the Difference' and '...Which Should You Hire' cover near-identical ground from different angles; recommend combining into one comparison post before linking. Keep separate — misclassification red flags and 1099-NEC filing mechanics are distinct enough to stand alone. Outline: H2 'What Counts as a 1099 Contractor' (new — no existing post covers legal definition)... Coverage gap: no existing post addresses state-level contractor law variations.
Verified against
ChatGPT GPT-5.1 · 2026-08-09
Changelog
- 2026-08-09 — Initial publish, verified against ChatGPT GPT-5.1.
Building this for real?
This is a free starting point. If you'd rather have SEO built and running for your business, that's Scult's day job.
EXPLORE SEO
