Open the AI Content Generation area of AutoSchedulePost for the first time and you’ll see three tabs rather than one big text box: Generate, Paste-Generate, and Search-Scrape. That’s not a design flourish — it reflects three genuinely different starting points for content, and understanding what happens behind each one makes the whole tool far less mysterious.
The Three Entry Points, Briefly
Generate takes a keyword or topic and builds an article from scratch around it — the mode to use when you have a target keyword and nothing else. Paste-Generate takes whatever raw material you already have — notes, a transcript, a rough outline — and shapes it into a finished article without inventing new facts to replace the ones you gave it. Search-Scrape pulls live search results for a keyword and uses the structure of what’s currently ranking — headings, subtopics, common angles — to inform an original draft. Each is covered in its own dedicated article elsewhere in this series; this one is about the shared mechanics underneath all three.
Step One: Pick a Mode and a Tone
Before you generate anything, your account already carries a default tone — Informative, Persuasive, Conversational, or whichever option you’ve set in your settings. Every generation call uses that default unless you override it for a specific piece, so you’re not choosing a tone from scratch every single time. This is a small detail with a large effect at scale: a hundred articles generated over a month all sound like they came from the same brand, not a hundred different writers.
Step Two: Generation Runs, and the Draft Lands Somewhere Permanent
Here’s the part that separates AutoSchedulePost from a plain AI chat window: the moment generation succeeds, the resulting article is saved against your account, not just held in the page you happen to be looking at. Each of the three modes keeps its own separate saved draft — the system tracks context (whether you’re in Generate, Paste-Generate, or Search-Scrape) so that a draft in one mode never overwrites or gets confused with a draft in another.
Practically, this means the article you generated doesn’t live only in your browser tab. Close the tab, navigate to a completely different part of the dashboard, log out for the day — when you return to that same generation screen, your draft is restored exactly as you left it. It’s a small thing until the first time it saves you from re-generating (and re-paying the generation cost, in time if nothing else) an article you’d already finished.
Step Three: You Decide What Happens Next
From here you have a few paths. You can edit the draft directly in the generation screen, regenerate it if the first pass missed the mark, send it onward into AutoSchedulePost’s scheduling and publishing tools, or clear it out. Clearing comes in two flavors that behave differently — a plain “Clear” resets what’s on your screen, while “Start Fresh” also deletes the saved draft itself so it doesn’t reappear next time you open the screen. That distinction gets its own detailed treatment elsewhere in this series, because it trips people up exactly once before they learn it.
Why It's Built This Way
The underlying design choice is simple: generation should feel like writing in a document, not filling out a form that resets if you look away. Content creation rarely happens in one uninterrupted sitting — you get pulled into a call, a Slack message, another task — and a tool that punishes you for stepping away by silently discarding your work fights against how people actually use it. Persisting the draft server-side, tied to your account rather than a session cookie or local browser storage, means the interruption costs you nothing.
The same logic extends into AutoSchedulePost’s bulk content tools — pillar pages and topic clusters generated in batches carry the same tone default and the same underlying generation engine as a single article you generate by hand. Whether you’re producing one post or planning a week of content in a single session, the mechanics you’re using are the same three modes described here, just orchestrated at a larger scale.
What to Read Next
If you’re deciding which of the three modes fits your current task, the comparison guide in this series walks through when to reach for each one. If you want the deep dive on why drafts survive logout, or how tone defaults get set and overridden, those get dedicated articles too. This page is meant as the mechanical overview — the rest of the pillar builds outward from here into strategy, prompting technique, and editorial workflow.
