AutoSchedulePost actually has two related but distinct paths for turning a pillar keyword into published content: the straightforward “Write all” flow inside the Pillar Pages builder itself, and the separate Pillar & Cluster page-building flow reached through “Send to Pages builder.” Understanding when each is the right tool avoids a common confusion — using one when the other was actually the better fit for what you’re trying to publish.
The Simple Pillar Flow: "Write All"
Once you’ve built a pillar and its cluster keyword list, “Write all” is the direct, straight-to-processing path. It queues the pillar and its clusters as blog posts, applies your chosen scheduling (now, interval, or one-per-day, with a start time), and generates each article — hero image, per-H2 images, and tone settings all honored per your toggles. This is the path for content that belongs in your blog’s chronological feed: how-to articles, explainers, comparisons, troubleshooting guides.
The Pillar & Cluster Page Builder: "Send to Pages"
Triggering “Send to Pages builder” on a cluster hands the pillar and its not-yet-published keywords to a separate builder, one purpose-built for standalone site pages rather than blog posts. That builder publishes each keyword as its own page, using the exact keyword as the URL slug, preserving the nested pillar/cluster path structure. The editable keyword list there doubles as your picker for choosing which not-yet-sent keywords to actually build right now, whether that’s the full set in bulk or a hand-picked subset.
The Core Difference: Post vs Page
The distinction underneath both flows is the difference between a blog post and a site page. A post is dated, chronological, editorial content meant to answer a specific question and then live in your archive — useful for search intent around “how,” “why,” and “what” questions, and for accumulating topical depth over time. A page is meant to be permanent and navigable — the kind of content you’d link from a main menu, built around service, location, pricing, or comparison intent rather than an evolving editorial voice. “Write all” produces the former; “Send to Pages builder” produces the latter.
Using Both on the Same Pillar
These flows aren’t mutually exclusive — most mature pillars end up using both. A cluster keyword list built from one seed keyword typically contains a mix of post-shaped and page-shaped intent: some keywords are genuinely “how do I do X” questions that deserve a blog post, others are “I need someone to do X for me” or “where can I find X” queries that deserve a permanent page. Running the post-shaped subset through “Write all” and sending the page-shaped subset through “Send to Pages builder” — on the same pillar, sharing the same nested structure — is the normal, expected pattern rather than an edge case.
What "Not-Yet-Published" Protects You From
Because the send-to-Pages handoff specifically filters for keywords that haven’t been published yet, running it more than once on a growing pillar is safe — anything already live through either flow is automatically excluded, so you never risk duplicating a keyword that’s already a post by accidentally sending it through as a page too, or vice versa in terms of double-processing.
A Practical Decision Guide
- Choose “Write all” when the keyword clearly implies editorial content — a question, a guide, a comparison, an opinion — that belongs in your dated blog feed.
- Choose “Send to Pages builder” when the keyword implies a permanent destination — a service, a location, a pricing tier, a named comparison — that a visitor would expect to find through site navigation, not by scrolling an archive.
- Reconsider your cluster list if you find most of your keywords are genuinely page-shaped — it may be a sign the underlying pillar is really a site-structure project more than a content-marketing one, and worth planning accordingly from the start.
Why This Distinction Is Worth Getting Right
Sending a page-shaped keyword through “Write all” produces a dated blog post that ages out of relevance and gets buried in an archive — a poor fit for something like a service-area page meant to be permanently discoverable. Sending a post-shaped keyword through “Send to Pages builder” produces a static page trying to answer an evolving how-to question, which reads oddly without the editorial framing readers expect from that kind of content. Matching keyword intent to the right flow keeps both your blog and your site’s page structure doing the job each is actually good at.
The Takeaway
“Write all” and “Send to Pages builder” aren’t competing features — they’re complementary paths for two different content types that a single pillar’s keyword list will usually contain. Sort your cluster keywords by intent before committing to a flow, and expect most substantial pillars to use both.
