Skip to main content

Product guide

Use AutoPress step by step

This guide describes the surfaces available today. Plan, model, and checkout availability comes from active configuration; it does not assume an external integration is enabled.

In this guide

01

Getting started

From registration to a title ready for processing.

02

WordPress connection

HTTPS, plugin, token, and minimum permissions.

03

Titles and publishing

Queue, human review, and scheduling.

04

Settings and security

Editorial configuration and safe credential handling.

05

Plans and limits

Effective usage, checkout, and subscription states.

01

Getting started

You need an AutoPress account and a WordPress site reachable over HTTPS. To publish, the WordPress integration account must also retain the native capabilities required by each operation.

  1. 1Create an account or sign in.
  2. 2Connect and validate a site from WordPress Sites.
  3. 3Review tone, language, length, image, and template settings.
  4. 4Add one or more titles, assign them to a site, and select a publishing mode.
  5. 5Monitor the queue and review any error before retrying.
Create accountOpen WordPress Sites

02

WordPress connection over HTTPS

The AutoPress Connector plugin is the recommended method. The WordPress Sites screen provides its download and validates the URL and token before saving the connection.

Install and connect

  1. Download the ZIP from WordPress Sites.
  2. Upload and activate it under Plugins → Add Plugin.
  3. Under Settings → AutoPress Connector, generate the token.
  4. Copy it immediately: the raw value is shown once.
  5. In AutoPress, use the https:// URL, paste the token, validate, and save.

Connector permissions

The content and site_info scopes are enabled by default. Settings, themes, menus, custom_css, plugins, and users require explicit opt-in by a WordPress administrator.

A scope does not replace WordPress permissions: each request also checks the current capabilities of the bound integration user.

Security: treat the token like a password. Rotate it if it is lost or exposed; rotation disconnects the previous value and disables privileged scopes again. Enable only what is required.
Manage WordPress connections →

03

Titles, queue, review, and scheduling

The Titles screen accepts individual entries or TXT, CSV, and TSV batches. Before processing, confirm the WordPress site, category, and titles detected as valid.

Autopilot

Generates and continues into the configured publishing flow. Use it only after the brief and template are proven.

Review

Leaves the result in review. You can preview, edit, approve and publish, or reject it back to pending.

Schedule

Assigns a date and time to one or more titles. Every scheduled title needs a valid WordPress connection.

Operate the queue

  • Visible states include pending, queued, processing, review, scheduled, posting, completed, and error.
  • Pause prevents new work from being claimed; do not assume it interrupts a task already in progress.
  • Review the log and connection before retrying. A provider or WordPress error does not confirm publication.
  • Always verify the draft and final WordPress entry; assisted generation does not guarantee accuracy, rankings, or business outcomes.
Open Titles →

04

Settings and security boundaries

Settings controls tone, language, length, image style and dimensions, image text, the HTML template, and reusable blocks. Save and test changes with a draft before using them at volume.

Good practice

  • Use Review while tuning prompts and templates.
  • Validate HTML, links, facts, and image rights before publishing.
  • Use History to review saved context; do not treat it as a factual source without verification.
Open SettingsOpen History

Credentials and session

  • The web session uses HttpOnly cookies; do not copy session tokens from the browser.
  • Enter the WordPress token only in the connection form; do not share it in tickets, screenshots, or logs.
  • Do not enable privileged scopes to compensate for a missing native capability. Fix the integration user instead.

05

Plans, usage, and billing limitations

Billing shows the effective plan, subscription status, period post usage, and WordPress sites used. Limits and models come from the active backend; this guide does not hard-code prices or availability.

  • Starter does not require checkout. A paid plan shows a purchase action only when its Stripe price is configured and the backend declares checkout_available.
  • Do not assume annual billing exists: it should be offered only when it appears as an available option.
  • Paid limits apply to active or trialing states. Other states may reduce effective access to Starter until Stripe confirms a change.
  • The Stripe portal appears only when the account has an associated Stripe customer and the service is configured.
  • If usage or status does not match Stripe, do not repeat checkout: reload Billing and review the status before continuing.
Open Billing →