Not every keyword in a topic cluster belongs on the blog. Some are better served as an actual site page — a service page, a location page, a comparison page — something meant to live in the site’s permanent navigation rather than its chronological post feed. AutoSchedulePost’s “Send to Pages builder” flow exists specifically for that handoff: moving a pillar’s keywords out of the blog-post pipeline and into a dedicated page-building flow, without losing the structure you already built around them.
What the Button Actually Does
Every cluster in the Pillar Pages builder has a “Send to Pages builder” action. Trigger it, and the pillar plus whichever of its keywords haven’t been published yet get handed to the separate Pillar & Cluster page builder. That second builder then publishes each keyword as its own page, using the exact keyword as the page’s URL slug, and preserving the nested pillar/cluster path structure rather than starting a flat structure from scratch.
The distinction — “not-yet-published” — matters. The flow specifically filters out anything from the cluster that’s already gone live, so you can send a batch, come back weeks later after adding new cluster keywords, and send again without duplicating anything or re-processing keywords that already have a live page.
Why Route Some Keywords to Pages Instead of Posts
Blog posts and site pages serve different purposes even when they’re targeting similar keywords. A blog post is dated, chronological content — useful for search intent around “how to” or “why” questions, and for building topical depth over time. A page is meant to be permanent, navigable, and often transactional — the kind of content you’d link from a main menu, not a chronological archive. A cluster keyword like “commercial espresso machine repair near me” behaves more like a page than a post: it’s not really “content” in the editorial sense, it’s a landing point someone should be able to reach directly and repeatedly.
Sending the right subset of cluster keywords through this flow, rather than running every single one through the ordinary “Write all” blog pipeline, keeps your site’s structure matched to what each piece of content is actually for.
How the Picker Works
Once keywords land in the Pages builder, its editable keyword list doubles as your selection tool. You’re not forced to send everything through in bulk — you can review the list and decide which keywords to actually build as pages right now, leaving the rest queued for a later batch. This means the “picker” isn’t a separate feature bolted on; it’s simply the same editable list you’d use to review or adjust keywords, repurposed as the mechanism for choosing a subset.
Bulk vs Selective Sending
Two patterns work depending on the size and maturity of your cluster:
- Send everything through at once — appropriate when you’ve already reviewed the full keyword list for quality and you want every not-yet-published keyword to become a page in one pass, particularly for smaller clusters where there’s little risk of sending something half-baked.
- Hand-pick a subset — appropriate for larger clusters where some keywords are clearly page-shaped (service, location, comparison intent) and others are clearly post-shaped (how-to, explainer, opinion intent). Sending only the page-shaped subset keeps the two content types cleanly separated.
Our companion article Bulk-Sending a Cluster vs Hand-Picking a Subset goes deeper into deciding which pattern fits a given batch.
What Happens to the "Write All" Path
Sending keywords to the Pages builder doesn’t replace the ordinary blog-post workflow — it runs alongside it. “Write all” remains the straight-to-processing path for keywords you want as blog posts, scheduled with the usual now/interval/one-per-day controls. The two flows are meant to be used together on the same pillar: some keywords go through “Write all” as posts, others get sent to Pages as standalone pages, and both inherit the same underlying pillar structure and nested slugs.
A Practical Workflow
- Build your pillar and review the generated cluster keyword list.
- Sort keywords mentally into “post-shaped” (how-to, explainer, listicle, opinion) and “page-shaped” (service, location, comparison, pricing).
- Run “Write all” on the post-shaped keywords with your preferred scheduling.
- Use “Send to Pages builder” for the page-shaped subset, hand-picking rather than bulk-sending if you want tighter control over what goes live and when.
- Return periodically as you add new cluster keywords, sending only the not-yet-published ones each time.
Why This Matters More Than It Looks Like It Should
It’s tempting to treat this as a minor convenience feature — “it just moves some keywords to another screen.” In practice, it’s the mechanism that keeps a pillar’s structure from splintering into two disconnected systems as it grows. Without it, you’d be manually copying keywords from one builder to another, re-typing exact slugs by hand, and hoping you remembered the nesting depth correctly each time. With it, the handoff preserves everything — exact keyword, nested path, publish status — automatically, which is the difference between a pillar structure that stays coherent as it scales past its first dozen articles and one that quietly falls apart.
