Set the pace.
Choose the intensity, cap automatic work and set usage limits for each workflow.
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.
- Set site rules
- Choose what needs approval
- Control publishing
3
control levels
1
click to withdraw a change
~1 min
kill switch to the original site
0
writes to the CMS
Control levels
Three levels, set per client site.
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.
- Search signals
- Automatic
- Technical fixes
- Automatic
- Visible text
- Automatic when enabled
- Risky fixes
- After safety review
Level 2
Invisible-only
Automate technical work. Review visible text.
- Search signals
- Automatic
- Technical fixes
- Automatic
- Visible text
- Your approval
- Risky fixes
- After safety review
Level 3
Review everything
Your team approves each change before it goes live.
- Search signals
- Your approval
- Technical fixes
- Your approval
- Visible text
- Your approval
- Risky fixes
- Your approval
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.
What do these changes include?
- Search signals
- Title, meta description and structured data
- Technical fixes
- Missing canonical, language attribute and social tags
- Visible text
- H1, subheadings, link text, captions, answer blocks
- Risky fixes
- Clearing a stray noindex or a conflicting canonical
The controls
Your engine.
Your boundaries.
Choose what runs automatically. Set the rules each change must follow.
01 / 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.
The guardrails
Nine publishing rules for each client site.
Set work limits, protected content and publishing boundaries before enabling automation for a client.
Protect what matters.
Choose which pages may change. Save your rules and reuse them for another client.
Review before it ships.
Preview bulk changes, compare content variants and confirm selected fixes. Risky changes need a safety assessment.
See all 9 publishing rules
- Choose the work intensity
- Light, standard or aggressive. See how the setting changes priorities and the pace of work.
- Choose which pages can change
- Include or exclude pages by URL pattern. For example, protect every page under /campaign/.
- Limit automatic work
- Set a hard cap for each site. Automatic work stops when the cap is reached.
- Set limits per workflow
- Control usage separately for pages, audits and tracking. Individual workflows can also be switched off.
- Preview before applying
- Apply templates for titles, descriptions, robots directives or canonicals to matching pages. Run a preview first.
- Compare content variants
- Test titles, descriptions and headings against each other. Compare the results using real Google clicks.
- Review risky fixes first
- Removing a noindex directive or changing a conflicting canonical needs a safety assessment. The fix is flagged and stays reversible.
- Reuse your rules
- Save a rule template and apply it to another client site.
- Confirm selected fixes yourself
- Some actions, such as enabling a sitemap, need your confirmation. “Fix all” previews the changes before you approve.
Your control
You decide what changes.
Pause the engine, choose what it may edit, or undo a change. Your own edits always take priority.
Show the original site.
Stop Preferium’s changes with one click. The original pages return in about a minute.
Choose the text on each page.
Keep the original, use the AI version or write your own. Your edits take priority.
Give the AI clear boundaries.
Set the tone, words and facts it should use. Review and adjust the client’s style guide.
Publishing, versions and undo
- 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, wording 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.
Your work stays portable.
Export options · illustrationsBulk in and out via CSV
Export the optimized content, edit in a spreadsheet, import back with job tracking.
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.
Verify and roll back
The self-checks and the limits.
Checks built into the engine.
Each safeguard has a specific job: check changes, detect drift or protect delivery.
See verification and rollbackCheck 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.
Want to see it on a client site?
Pick one client site for a walkthrough of the engine and your branded panel.
Check the site
Review its health checks.
See the first fixes
Understand what the engine would improve.
Explore your panel
See the client experience under your brand.
Your client siteYour guardrailsClean HTMLYour brand
Preferium AI Edge
One connection. A clear way back.
- Connect a client site
- Set the control level
- Run under your brand