Bulk in and out via CSV
Export the optimized content, edit in a spreadsheet, import back with job tracking.
Chapter 02 of 05
Set the automation level for every client.
Choose what can publish automatically, what needs approval and what stays off. Review every change and undo it when needed.
Automation under your control
- Set site rules
- Choose what needs approval
- Control publishing
Platform facts
- control levels
- 3
- click to withdraw a change
- 1
- kill switch to the original site
- ~1 min
- writes to the CMS
- 0
Choose what can publish.
Decide what can publish automatically and what needs your approval. The same safety boundaries apply at every level.
Level 1Default
Full autopilot
Enabled changes publish within your rules.
Level 2
Invisible-only
Automate technical work. Review visible text.
Level 3
Review everything
Your team approves each change before it goes live.
Your rules stay in place.
Choose a level per site. Enable visible rewrites separately. Menus, footers and sidebars stay untouched.
See checks and rollbackVisible text publishes automatically only on Full autopilot, when enabled and within your rules.
Risky fixes need a safety review before automatic publication and are flagged for your team.
Compare the controls at each level
| Change type | Level 1Full autopilot | Level 2Invisible-only | Level 3Review everything |
|---|---|---|---|
| Search signalsTitle, meta description and structured data | Automatic | Automatic | Your approval |
| Technical fixesMissing canonical, language attribute and social tags | Automatic | Automatic | Your approval |
| Visible textH1, subheadings, link text, captions, answer blocks | Automatic when enabled | Your approval | Your approval |
| Risky fixesClearing a stray noindex or a conflicting canonical | After safety review | After safety review | Your approval |
Visible rewrites have a separate switch below.See checks and rollback
Protect content and limit the work.
Set work limits and exclusions before enabling automation. Your own edits take priority; you can override or undo changes.
AutomationTry the switches
Autonomous run
RecommendedRun the optimization loop within your publishing rules.
Technical findings fixed automatically
Apply supported technical fixes found by the daily audit.
Visible rewrites
Enabled by default. Turn off per site to keep visible text unchanged.
Interactive example. These switches do not change a real site.
Always protectedMenus, footers and sidebars stay untouched. Risky fixes still need a safety review.
Nine publishing rules
- PaceChoose the work intensity
- Light, standard or aggressive. See how the setting changes priorities and the pace of work.
- PagesChoose which pages can change
- Include or exclude pages by URL pattern. For example, protect every page under /campaign/.
- Work capLimit automatic work
- Set a hard cap for each site. Automatic work stops when the cap is reached.
- UsageSet limits per workflow
- Control usage separately for pages, audits and tracking. Individual workflows can also be switched off.
- Bulk changesPreview before applying
- Apply templates for titles, descriptions, robots directives or canonicals to matching pages. Run a preview first.
- ExperimentsCompare content variants
- Test titles, descriptions and headings against each other. Compare the results using real Google clicks.
- SafetyReview risky fixes first
- Removing a noindex directive or changing a conflicting canonical needs a safety assessment. The fix is flagged and stays reversible.
- TemplatesReuse your rules
- Save a rule template and apply it to another client site.
- Manual actionsConfirm selected fixes yourself
- Some actions, such as enabling a sitemap, need your confirmation. “Fix all” previews the changes before you approve.
Edit or undo changes
- Show the original site
- One click stops Preferium’s changes. The client’s original pages return in about a minute.
- Choose what can change
- Turn visible rewrites on or off for a site or for a type of page element.
- Pick the version on each page
- Use the original, the AI version, or your own text. Edit an element directly in the page preview.
- Undo an automated change
- See the last 50 automated changes and undo any reversible change with one click. The engine keeps your own edits.
Tone and brand facts
- Choose a starting tone
- Start with one of six writing styles, then adjust it for the client.
- Set writing rules
- Give the AI one instruction for the client. Add specific rules for titles, links or images when needed.
- Keep the right words and facts
- List words to use or avoid, and add the client’s key brand facts.
- Review a suggested style guide
- The AI can draft it from the client’s site. Edit it, and add separate rules for AI answers if useful.
Export your work
Your work stays portable. Illustration
Export what is published
A machine-readable overview of exactly what is live right now.
Client data can be taken out
Export deployed changes, tracked keywords, findings and affected pages. Preferium’s source code and runnable engine are not included.
What gets checked. What you can undo.
Check changes
Re-check core page elements in a real browser. Worsening changes roll back.
Detect drift
Restore overwritten changes every 30 minutes. Flag visitor/crawler differences.
Protect delivery
Serve the available origin, or a usable eligible cache. Disable the engine if serving fails.
Errors, redirects, files, signed-in traffic and POST requests are not rewritten.
All five safeguards
Verified after every deploy
A real browser checks title, meta description, H1 and structured data. Worsening changes are rolled back and reported.
Drift detection every 30 minutes
Overwritten changes are restored. You are notified if a repair fails.
Cloaking guard
The page is fetched as a visitor and as GPTBot. Serious differences are flagged.
Fail-safe toward the original page
If optimization fails, the original page is served when the origin is available. Errors, redirects, files, signed-in traffic and POST requests are not rewritten.
When the origin or serving fails
An eligible cached copy can cover an origin failure while usable. If edge serving fails, the engine disables itself.