FAQ
Questions, answered
Everything people ask before they connect their first site. Not covered? Reach us on the contact page.
No. AutoSchedulePost publishes through the native WordPress REST API. You just add your site URL and an application password — setup takes under five minutes and nothing is installed on your site.
Claude, GPT‑4, or any model available through OpenRouter. Every schedule picks its own provider and model, and automatic failover switches to your fallback when a provider goes down or hits a rate limit.
Yes. We harvest suggestions from Google, Bing, DuckDuckGo, Amazon, and five more sources without requiring any paid API keys. Harvest as much as you like — everything lands in your keyword library.
Yes. Posts can be published as Elementor-ready layouts, and Yoast focus keywords, meta descriptions, and Open Graph tags are set automatically on every post. Other SEO plugins that read standard fields work too.
Absolutely. Publish immediately, save everything as drafts for review, or add a review gate in the Workflow Builder — every post is logged and auditable from generation to publish either way.
As many as you need. Each site connects with its own application password and gets its own schedules, templates, and logs — all managed from a single dashboard.
The queue retries automatically with exponential backoff and logs the reason for the delay. Once your site responds, publishing resumes and the schedule catches up in order.
Thin, unresearched AI content can. AutoSchedulePost is built to avoid exactly that: live research before writing, structured templates, full metadata, and internal linking produce posts that meet the quality bar search engines actually measure.
Yes — Paste & Generate accepts any keyword list. Paste from a spreadsheet or another tool, and the pipeline treats them exactly like harvested keywords.
Yes. Team members can share templates and keyword libraries, workflows can include review roles, and per-site logs make client reporting straightforward.
More questions
You do, entirely. Posts are published to your WordPress site under your account; nothing is licensed back to us and nothing is used to train models. If you cancel, everything you published stays exactly where it is.
Whatever your chosen model writes well — in practice all major European and Asian languages. Set the language per schedule and the whole pipeline, metadata included, follows it.
Yes. Add your own Anthropic, OpenAI, or OpenRouter keys to pay providers directly at cost, or use built-in access and keep billing in one place.
Featured images are set on every post for clean social sharing and archive pages, and in-post images can be enabled per template.
The dashboard covers most workflows, and everything AutoSchedulePost publishes is standard WordPress content, so the WordPress REST API is effectively your API for anything downstream.
Still deciding?
The honest answer to “will this work for my site?” is a one-week trial: connect a site, run one schedule at a gentle interval, and review every post it produces. You’ll know more from seven real posts on your own domain than from any sales page — and if the quality isn’t there for your niche, you’ll have lost an afternoon, not a quarter.
Going deeper
A note on quality control. The pipeline is deliberately transparent about everything it does around faq: every run is logged, every post is editable, and nothing is hidden behind a black box. The practical consequence is that quality problems are always diagnosable — you can trace a weak post back to its keyword, its template, its provider, and its settings, change exactly one variable, and watch the next run improve. Treat the first month as calibration: the operators who get exceptional results are the ones who read their own logs.
Measuring results deserves a system of its own. Give every schedule a clear goal before it starts — impressions on a new topic cluster, clicks on commercial pages, or simple publishing consistency — and check it against your analytics on a fixed weekly rhythm. Automated publishing produces a steady stream of data as well as posts: which templates earn clicks in your niche, which cadences hold rankings, which topics your domain can win. That feedback loop, not any single post, is what compounds.
On scaling: resist the urge to run before the walk is boring. One site publishing reliably for three weeks teaches you more than five sites launched in a weekend, because problems are legible when there is only one variable set to watch. Once the first site’s rhythm is dull — posts ship, logs are green, quality holds — cloning the setup to the next site takes minutes, and the dullness scales with it. Dull is the goal.
Keep exploring
Get started
Ready to automate your content?
Set up your first WordPress site and schedule your first AI post in under five minutes.
