Run in the background (close the page safely)

What it is

AISA can keep optimising even when you are not watching. The list bulk actions (from the native WordPress post/product lists) queue work into a true background worker that runs with the page closed. 1-Click runs in the browser but continues if you switch tabs, and can hand off the remaining queue to the same background worker.

Where to find it

Background queueing is triggered from the WordPress Posts / Pages / Products lists via the AISA "Bulk actions", and from AISA → 1-Click SEO (the "keep this page open" note and the continue-in-background hand-off). Progress is visible in the AISA Dashboard.

Requirements & tier

Background mass optimisation is a Premium / Cloud function (it consumes AI unattended). The background worker uses a loopback request chain with a secret token and a per-slot lock, so it survives page closing. AISA Turbo controls how many generations run in parallel (1 = off, capped at 20).

How to use

From a WordPress list (Posts/Pages/Products), select rows and choose an AISA bulk action; the items are queued and the worker starts in the background — you can navigate away.
A notice confirms how many items were queued and links to the AISA Dashboard to follow progress.
For 1-Click, press Optimize and keep the page open; you may switch tabs (it continues, just possibly slower).
If you need to close the page during 1-Click, use the background hand-off so the remaining items finish via the worker.
Watch the live progress bar in the Dashboard; queued items are de-duplicated and the total stays consistent if you add more.

Questions people ask

What's the difference between list actions and 1-Click? List bulk actions queue straight into the background worker; 1-Click runs in the browser but can hand off to the same worker.
If I close the 1-Click page, what happens? The browser-driven part stops; items already done are saved, the rest are not — unless you handed off to background.
Does the background worker need cron? It uses non-blocking loopback requests that re-spawn themselves; there is a WP-Cron fallback.
What is AISA Turbo? Parallel generation (×2/×4/×8…) to optimise many pages quickly; it auto-tunes down if the provider rate-limits (429).
Can I add more items while a job runs? Yes — new IDs are appended (de-duplicated) and the progress total grows accordingly.
Where do I see it's finished? The Dashboard shows 100% and a brief "just finished" state.

Troubleshooting

If list actions show a Premium upsell, background mass optimisation requires Premium/Cloud. If progress doesn't advance, your host may block loopback requests; the WP-Cron fallback should still process the queue. If a provider rate-limits, the worker sleeps briefly and retries, so throughput may dip. Fix actions (ALT, slug) touch content, so a backup is recommended — the notice reminds you.

Note on speed: Processing time depends on two things: your AI provider's response speed and the server where the plugin runs (PHP workers, memory and hosting). A slow provider or a constrained host makes large batches take longer — use AISA Turbo and run in the background to mitigate it.

Bulk actions from the post/product lists
1-Click SEO: optimize the whole site
Scheduled SEO regeneration (Scheduler)
Optimization history