Auto-generate summaries and FAQs on publish (Pro)

In the free plugin, generation is something you trigger: the Regenerate button, the block, the Elementor widget. Pro adds the mode where it simply happens when a post is published.

Turning it on

The auto-generation toggles sit in the same settings screens as everything else, and become usable once Pro is licensed. Summary auto-generation and FAQ auto-generation are separate switches, so you can have one without the other.

Both are off by default. Publishing behaviour is not changed until you ask for it.

Which post types it applies to

Auto-generation follows the post types you have already enabled for that feature. If FAQ generation is set to posts only, auto-generation applies to posts only. Widening it is a settings change, not a Pro-specific one.

What it requires before it will run

FAQ auto-generation is conservative on purpose and does not produce something poor:

• An AI provider must be configured and ready.
• DataForSEO credentials must be present, because auto-generated FAQs are built from real question data rather than invented ones. See what DataForSEO adds.

If either is missing, nothing is generated and nothing is broken. RankReady shows a notice saying which one is missing, then waits for you to save the post again once it is fixed. This is the single most common reason auto-generation appears to do nothing.

It runs in the background

Generation is scheduled rather than executed inside the publish request, so hitting Publish stays fast and an API slowdown never blocks an editor. The summary or FAQ appears shortly after, not in the same instant.

On a site with WP-Cron disabled or unreliable, background work runs late. That is a hosting characteristic, not a plugin one.

What it does not do

Auto-generation applies to posts as they are published. It does not walk your existing archive. For that, use bulk generation.

Cost

Every generated summary or FAQ is a call to your own AI provider, billed by them. Automating generation automates that spend, so check the API Usage report after turning it on rather than a month later.