Content workflow automation, from brief to publication
Content workflows are the part of the Process automation service in which Best Boost Partners automates the path of a text from brief to publication. Tasks are created from the content plan, every text moves through statuses, passes checks for uniqueness, length and keywords, and is published through the CMS API. The same mechanism updates many pages at once. You receive the code, the documentation and a workflow that your editors run without a programmer.
What exactly do we automate in content workflows?
Task creation
A row in the content plan becomes a task for the author with the brief attached: topic, keywords, structure, length, due date. Nobody copies the brief into a task tracker by hand.
Statuses and responsibility
Every text has a status: in writing, in review, in revision, approved, published. The status changes when the work is actually done, and the editor sees the whole queue and the tasks that are stuck.
Automatic checks
Before a text reaches the editor, the system checks uniqueness, length, the presence of keywords, the heading structure and whether the title and description are filled in. The author sees the result at once and corrects formal errors without a round through the editor.
Publishing through the CMS API
An approved text is sent to the CMS together with its meta tags, headings, images and internal links. Publication can be immediate or scheduled, and the address of the published page is written back into the content plan.
Bulk updates
When a fact, a block or a meta tag pattern has to change on many pages, the update is prepared in a table and applied through the API. The previous version of every page is saved before the change.
Translations and language versions
For sites in several languages the workflow links the original with its translations and shows which language versions are missing and which are out of date.
What do you get from content workflow automation?
- A working chain from the content plan to the published page, connected to your CMS.
- A set of automatic checks with thresholds that the editor can change.
- A bulk update tool with a log and saved previous versions of pages.
- The code in your repository and documentation for the editor and for the developer.
- A handover session in which your team takes a text along the whole path.
When is content workflow automation needed?
- Several authors and editors work at the same time, and tasks get lost between chats, documents and the CMS.
- The editor spends time on formal checks that a script can run before the text arrives.
- Texts are published by hand, and meta tags or internal links are sometimes forgotten.
- The same edit has to be made on many pages of one site or of several sites.
Frequently asked questions
Will automation replace the editor?
No. Automatic checks catch formal errors: length, missing keywords, low uniqueness, an empty description. Meaning, facts and tone are still judged by a person. The workflow takes the moving of texts and the questions about status off the editor and leaves the reading.
Which CMS can texts be published to?
To WordPress, MODX, OpenCart and sites built on Laravel we publish through the system’s API or a small module on the site side. For other and custom systems we first check what the system allows. If a CMS cannot accept content from outside, we say so before the work starts.
Is it safe to update many pages at once?
A bulk update carries the risk of repeating one mistake on every page, and the process is built with that risk in mind. The update first runs on a small sample, the previous version of every page is saved, and every change is written to a log. If the result is wrong, the pages are returned to the saved versions.
Tell us about the project
Fill in what you already know. Blank fields are fine: we will clarify the rest in conversation.
Brief sent
Thank you. We will reply within one working day.
Preview mode: the form handler is not connected yet, so nothing was sent.