Turn the existing website into a controlled, scored editorial queue without generating near-duplicate articles.
Strategy fields
| Field | Allowed values | How to use it |
|---|---|---|
| Subject | Optional free text | Leave blank for website inference or enter a clear editorial area to constrain discovery |
| Clusters | 1–10; default 3 | Number of strategic groups to propose |
| Topics per cluster | 1–100; default 20 | Depth of the proposed backlog; start smaller for review |
| Language | Site/detected or an available language | Keeps evidence, topics, links and taxonomy assignment language-aware |
| Goal | Traffic, Sales or Both | Influences commercial versus informational emphasis |
| Mode | Review or Auto | Review requires editorial approval; Auto can advance eligible topics automatically |
| Minimum score | Numeric; default 70 | Prevents low-confidence suggestions from advancing |
| Prefer products | On/off; default on | Uses product evidence when commercially relevant |
| Use GSC | Optional | Adds query/page opportunity evidence when Search Console is connected |
What website inference reads
Publisher can analyse titles, content, excerpts, H2/H3 headings, public taxonomy terms, available SEO keywords, outbound links and eligible product data across the public inventory. Eligible custom post types can influence strategy even though generated output is always a native WordPress post.
Generate a strategy
- Rebuild inventory if the site was recently migrated or bulk-edited.
- Choose the language and goal.
- Leave Subject blank for broad inference or enter a narrow, defensible scope.
- Start with 3 clusters and 5–10 topics per cluster in Review mode.
- Keep the minimum score near 70 until you understand the scoring distribution.
- Generate and inspect the queue before approving anything.
Topic batches are processed in groups of up to 20 through Action Scheduler when available or WP-Cron otherwise.
Topic states
| Status | Meaning | Next action |
|---|---|---|
| Suggested | Proposed but not approved | Review score and overlap evidence |
| Approved | Editorially accepted | Queue manually or allow the configured workflow |
| Queued | Waiting for a worker | Monitor Create articles/History |
| Generating | An article job owns the topic | Follow Live Pipeline |
| Completed | Linked article finished | Inspect article and report |
| Failed | Generation ended with an error | Resolve the first error, then retry through the eligible workflow |
| Conflict | Overlap is too high | Merge, narrow or archive; do not force duplication |
| Skipped | Policy or eligibility prevented use | Inspect the recorded reason |
| Archived | Removed from the active queue | Restore only if editorially needed |
A topic may also be shown as stuck when the stored state and active job no longer agree. Use History & Logs to identify the worker or recovery condition.
Manual topics
A manually added topic receives informational intent, priority 5, score 100 and supporting type as safe defaults. It still passes overlap and generation checks. A score of 100 means it was explicitly supplied, not that search performance is guaranteed.
Scoring and overlap
Scores rank the confidence and usefulness of suggestions within the strategy. They are not traffic forecasts. Publisher flags high overlap when title similarity reaches approximately 0.72 or keyword similarity reaches approximately 0.86. Open the related content and decide whether to consolidate, change intent or narrow the topic.
Queue limitations to understand
The visible queue shows title/keyword, cluster, language, score, status/error and linked post. Stored intent, priority, topic type and internal instructions are not displayed as queue columns in 3.7.6, so do not use the queue as a complete strategy record.
Review checklist
- The topic has a distinct search and reader purpose.
- The cluster is coherent and the language is correct.
- The score clears policy without being treated as a promise.
- Overlap evidence has been opened, not dismissed from the badge alone.
- Commercial topics serve an actual product or conversion path.
- Only approved topics enter automatic generation.
Troubleshooting
- No useful suggestions: rebuild inventory, narrow Subject and verify that eligible public content exists.
- Too many conflicts: inspect whether the site already covers the cluster; change angle or intent instead of lowering safeguards.
- Queue does not move: verify licence, pause state and background jobs.
- Wrong language: correct the strategy language and underlying WPML/Polylang assignments before regenerating.