Using Automate
Create recurring content schedules, queue qualified Research topics, control delivery, and review monitored knowledge-source changes in Automate.
Use Automate to run supported recurring workflows for one client. The current workspace includes two distinct automations:
Create content on a schedule works through an ordered topic queue and saves each generated project to the selected destination.
Keep knowledge base current checks approved website sources for changes and waits for human review before replacing saved knowledge.
Automations remain scoped to the selected client. Confirm the client, topics, sources, destination, and cadence before turning one on.
Create a content schedule
Select the client and open Automate.
Turn on Create content on a schedule or choose Settings.
Choose Daily, Weekly, or Monthly. The cadence creates one new Copywriter draft each day, week, or month from the next pending topic. It does not refresh keyword data or work through the whole queue at once, so a long queue takes as many runs as it has topics.
Add one manual topic per line. These topics are the fallback after the Research queue is empty.
Choose where finished drafts should be saved: Projects, Projects + WordPress, Projects + Webflow, or Projects + GitHub pull request.
Complete any required destination connection, review the settings, and select Turn on automation.
The Automate header shows how many content schedules are active against the subscription allowance. Turning a schedule off stops future scheduled runs without deleting its settings, queue, or created projects.
For WordPress or Webflow, verify the correct client connection before enabling delivery. GitHub delivery requires a connected repository and an approved existing Markdown or MDX article folder. It creates a reviewable pull request and does not merge it automatically.
Queue saved Research topics
Create the content schedule before sending topics to it. Then:
Open Research → Saved research for the same client.
Open the saved list and select up to 100 qualified keywords.
Choose Add to Automate.
Select the intended content schedule.
Add optional article direction for each selected topic.
Confirm the queue action.
Adding a topic only creates a queue item. It does not generate content or record a completed usage event. Normal scheduled-work rules apply when Rankability later starts the draft.
The same saved Research keyword cannot be added to the same schedule twice. A similar phrase or a keyword from another list can still be a separate item, so remove semantic duplicates before queueing them.
Manage the Research queue
Open the content schedule's Settings to review its queue. Pending Research topics run before manual fallback topics.
For a pending item, you can:
move it up or down in the queue;
edit and save its optional content guidance; or
remove it before generation starts.
To clear several at once, select the pending items you want — Select all pending selects them all — then choose Remove selected. Remove all pending clears the whole pending list in one action. Removal applies to pending items only; a topic that is already running or completed keeps its record.
A queue item can be Pending, Running, Completed, or Failed. Open the created draft or content project when a project link is available. If an item failed before creating a project, use Retry topic after correcting the underlying problem. Do not add the same topic again merely because a scheduled run is still active.
When the Research queue becomes empty, the schedule uses the manual fallback topics in its settings. Add more qualified Research topics when you want deliberate queue order and topic-specific guidance.
Keep the knowledge base current
The knowledge-monitoring automation is separate from scheduled content:
Open Automate and choose Settings for Keep knowledge base current.
Select the saved website pages that should be monitored.
Choose the available monitoring cadence and save the automation.
Use Check now when you need an immediate comparison.
When a monitored page changes, Review changes compares the saved knowledge with the live page. Apply the update only when the new content is correct, or dismiss it to keep the approved saved version. Detection alone never replaces the source Serena uses.
Permanent URL moves require a separate redirect decision. Review the original and destination URLs before updating the source. A content difference at the destination can still require its own review after the URL is changed.
See Serena sources and data connections for source eligibility, processing states, and knowledge-review boundaries.
Usage and safeguards
Adding or reordering queue items does not generate content. Scheduled tracking and monitoring are recorded separately from ordinary on-demand work and are not blocked by the pooled on-demand windows. Provider quotas, connection failures, request-rate controls, schedule allowances, quality checks, and other operational safeguards can still delay or stop a scheduled run.
Review every generated draft before publishing it. A completed automation proves that the configured Rankability workflow reached its saved result; it does not prove that an external website changed unless the project records a successful delivery or publishing result.
Troubleshooting
Add to Automate is unavailable — Confirm that you are in a saved Research list, selected at least one row, and already created a content schedule for the same client.
A schedule is missing from the picker — Return to the intended client and create or verify the schedule in Automate. Schedules cannot receive topics from another client.
A topic says it is already queued — Open that schedule's Research queue. Existing membership is reused instead of creating a duplicate item.
A schedule is on but no run is planned — Confirm that it contains a pending Research topic or a valid manual fallback topic and that the schedule is within the active allowance.
A destination is unavailable — Reconnect the selected WordPress, Webflow, or GitHub destination and verify that it belongs to the current client.
A topic failed — Read the saved error, correct the source, destination, or setup problem, then use Retry topic when the item offers it.
A monitored page changed but Serena still uses the old text — Open the pending review. Rankability preserves the approved version until you apply the change.
Related articles
Last updated
Was this helpful?