Every automated content platform eventually gets asked the same question by a prospective user: “what actually works today, versus what’s still being built?” It’s a fair question, and one worth answering plainly rather than with a vague features page. AutoSchedulePost is built in public in the sense that its roadmap moves fast — pieces of the pipeline get hardened, expanded, and occasionally rebuilt based on how real sites actually use them. Here’s an honest snapshot of where the platform stands: what’s live and dependable right now, what’s rolling out in refined form, and what’s next on the list.
Live Today: The Core Research-to-Publish Pipeline
The backbone of AutoSchedulePost — research, generate, schedule, publish, track — is fully live and used daily across connected sites. That means every stage below is not a future promise; it’s working software.
Keyword Gap Analysis
You can add your own site and any number of competitor domains, and the tool surfaces keywords your competitors rank for that you currently don’t. One detail that took real iteration to get right: keywords you’ve already acted on stay marked with a checkmark even after a fresh scan drops them from the live gap list, so your strategy history doesn’t disappear every time the data refreshes. Your own site also sits in a visually distinct, accented panel — labeled “You” — so it’s never confused with the competitor list around it.
AI Content Generation, Three Ways
You can generate a full article from a keyword, paste in your own draft and have it expanded or polished, or start from a scraped competitor page and rework it into original content. All three paths now persist your in-progress work: if you generate a piece and then navigate away, close the tab, or log out and back in, the draft is restored exactly where you left it, rather than forcing you to regenerate from scratch. A dedicated “Start Fresh” action clears the saved draft when you genuinely want a clean slate.
Pillar Pages and Topic Clusters
Feed in a seed keyword and the system builds a pillar page plus a cluster of supporting articles around it, using your exact keyword as the URL slug rather than a rephrased version. Cluster structures can nest two, three, or even four levels deep (a pillar with a child topic, which itself has its own sub-topic), which matters if you’re building genuinely deep topical authority rather than a flat list of loosely related posts. A “Write All” control lets you queue every article in the cluster to publish right now, spaced a set number of hours apart, or one per day starting at a time you choose.
Auto Scheduler and Queue
Content can go out two ways: “Add to Queue — ASAP” publishes during the same request, so it works even if your scheduled task isn’t running yet, and “Schedule for Later” holds a post until its slot, checked every minute by a background scheduler. On shared hosting, that’s a single cron job hitting your site once a minute; on a VPS, it can run as a persistent background process instead. Either way, once it’s confirmed running, the platform shows a live “scheduler last ran” heartbeat so you’re never guessing whether queued posts will actually go out.
Rank Tracking
Every page you publish through the platform is automatically enrolled in rank tracking the moment it goes live — no separate setup step required, though it can be switched off if you’d rather track selectively. A dashboard widget surfaces your top-moving keywords, gainers and losers side by side, so a ranking win or a ranking drop is visible without digging through a full report. Check frequency defaults to weekly, with a daily option at a time you set.
Competitor Watch and Publishing Add-ons
Competitor Watch follows the RSS feeds of sites you’re tracking and flags new posts as they publish, with bulk actions to check everything at once, dismiss items you don’t care about, and rewrite a competitor’s post into your own draft or straight into your scheduling queue. On the publishing side, schema markup settings (article type, publisher name, an AI fallback for FAQ sections when a page doesn’t have one written manually) are configurable per site, and your content calendar supports drag-to-reschedule, year navigation, and clickable entries that jump straight to a live post or its queue history.
Rolling Out: Recently Rebuilt or Being Refined
A second tier of features is live but actively being sharpened based on real usage patterns:
- Send to Pages Builder. A dedicated flow for taking a cluster of generated pages and publishing them with clean, nested URLs (pillar, then pillar/child) rather than a flat structure — useful once a topic cluster has grown large enough that URL hierarchy starts to matter for both users and search engines.
- Stuck-job recovery. Long-running generation jobs — particularly large pillar pages — occasionally used to sit indefinitely in a “processing” state if they ran past a timeout. That’s now handled: a job that fails partway through gets flipped to a clear “failed” status with a readable error, instead of silently parking forever.
- Image placement in generated content. A hero image toggle and an “image under every heading” toggle are live, using the same AI image pipeline and sized to never overflow the page. A more granular version — clicking directly into any individual heading to choose or swap its image — is still being built.
On the Roadmap: Next in Line
A handful of items are explicitly next, not yet shipped:
- Workflow time-of-day pacing. The Workflow Builder already lets you chain together multiple content types (say, a batch of pillar pages and a batch of standalone posts) into one running schedule. The next step is variable posting density through the day — heavier volume during known high-engagement windows, lighter volume midday — rather than a flat, evenly spaced interval.
- Instant indexing beyond Google. Search Console integration exists today; a Bing/Microsoft Webmaster Tools submission path, so newly published pages get pinged to both major search engines automatically, is planned next.
- Manual interlinking control. Automatic internal linking between related pages already runs in the background; a manual override — for the pages auto-linking doesn’t catch — is on the list.
- A fallback data source for rank checks and backlink pulls. If the primary ranking or backlink API has an outage or hits a rate limit, a secondary provider to fall back to automatically is a planned reliability improvement.
- Trend surfacing on the dashboard. Rather than auto-queuing a post the moment a topic spikes in search interest, trending topics will surface as a suggestion on your main dashboard — kept visually distinct from general trend data — so you decide whether to act on it, instead of the platform acting for you.
Why This Distinction Matters for You
The reason this roadmap breakdown is worth publishing at all — rather than a generic “everything is amazing” features page — is that it lets you plan your own rollout realistically. If you’re deciding whether to lean on the Send to Pages flow for a big cluster launch this month, you should know it’s live and stable, not experimental. If you’re hoping for automatic Bing indexing today, you should know to submit manually in the meantime rather than wait on a feature that isn’t there yet.
This also reflects how the platform is actually built: incrementally, driven by what real connected sites hit in practice. Features like the stuck-job recovery handler and the persistent keyword checklist weren’t planned in the abstract — they came from watching what broke or frustrated people in daily use, then fixing the actual root cause rather than papering over the symptom. That’s the same posture you should expect going forward: fewer flashy unreleased promises, more steady hardening of the pipeline you’re already relying on to get content out the door.
How to Use This List Practically
If you’re new to the platform, start with the fully live pipeline — Keyword Gap Analysis into Generation into Pillar Pages into the Auto Scheduler into Rank Tracking — since that’s the complete, dependable loop today. Treat the “rolling out” tier as usable but worth double-checking on your own site (for example, confirm your scheduler heartbeat is actually ticking before you queue a week’s worth of scheduled posts). And treat the roadmap tier as exactly that: don’t build a workflow today that assumes a feature which isn’t shipped yet, like automatic Bing indexing or auto-detected trend queuing.
Roadmaps age fast in software, and this one will too. But the underlying shape won’t change: research feeds generation, generation feeds scheduling, scheduling feeds publishing, and publishing feeds tracking — which in turn tells you what to research next. Everything on this list is either strengthening one of those links or adding a new one, not reinventing the loop itself.
