Skip to content
PreferiumJoin the waitlist
Autonomous AI SEO · White label · Pre-launch

Autonomous SEO for agencies.
Under your brand.

Improve existing client pages for Google and AI answers. Preferium publishes supported fixes within your rules and checks the result. Your clients see your brand and pay through your Stripe.

Built for AI visibility
  • ChatGPT
  • Claude
  • Perplexity
  • Gemini
  • Grok
  • Copilot
  • Google AI Mode
  • AI Overviews

Clean, readable HTML for search engines and AI services.

THE OPTIMIZATION ENGINE

Real site work.
Every night.

Supported fixes to existing pages, checked in a real browser. Changes that worsen core page elements are rolled back.

  1. 01FindSpot issues on existing pages.
  2. 02ImprovePrepare supported fixes.
  3. 03DeliverPublish within your rules.
  4. 04VerifyCheck core page elements.
Your original siteImproved HTML, unchanged CMS
WHITE LABEL

Your service.
Your client relationship.

Sell ongoing site optimization at your own prices. Preferium runs the engine behind your brand.

YOUR AGENCYYour brand & Stripe
YOUR CLIENTYour branded service

Clients pay you. Preferium bills your agency.Set client prices to cover your wholesale and operating costs.

Explore white label

WHY PREFERIUM

Improve client sites. Sell it under your brand.

Compare the approach
How it works

Connect once. Improve every night.

Keep the client’s existing site. Choose what can publish automatically and what needs approval.

  1. 01Connect the siteAdd one DNS record. Preferium checks compatibility and issues a certificate before go-live. No plugin or server access is needed.
  2. 02Set the publishing rulesChoose a control level, exclusions and work limits. Decide separately whether visible rewrites are enabled.
  3. 03Run within those rulesThe engine revisits pages each night. Allowed changes publish and are checked; proposals that need approval wait in your queue.
Example site connectionPropagated
Type
CNAME
Name
www
Value
ssl.preferium.com

The DNS target is public and includes Preferium’s name. Required legal documents also identify Preferium.

Nightly work · sample dataRunning
  1. FindCheck 12 existing pages
  2. Fix6 supported fixes selected
  3. DeployServe allowed fixes in the HTML
  4. Verify, or roll backRe-check core page elements in a browser
White label

Your platform. Your brand, your Stripe, your prices.

Monthly platform plans. Connected domains are billed separately; extra credit packs are one-time purchases when needed. You set the packages and prices your clients see.

Partner prices could not be loaded

Plan pricing

We could not load the current plans and usage rates. Please try again later or contact us.

How partner billing works

Check it yourself

Take a closer look before you join.

Scan a public page, review our current security position and see the company behind the platform.

Control

Set the publishing rule for each client site.

Choose what publishes automatically and what needs approval. Change the level at any time.

PUBLISHING CONTROL

One engine.
Three ways to run it.

Visible rewrites change text people read on the page. You decide whether they can publish.

01Default

Full autopilot

Supported changes publish within your rules. You control visible rewrites per site.

Publishes and checks
02

Invisible-only

Titles, meta and schema can publish. Text people read on the page waits for review.

Technical changes publish
03

Review everything

Your team approves each proposal before it can publish.

Waits for approval
Every level stays reversible. Published changes are checked; a change that worsens core elements is rolled back automatically.Explore control and safety
Product

The engine works on the site. The panel shows the work.

Each client workspace brings together site improvements and AI-answer tracking. Illustrated panels use sample data, not client results.

Preferium AI Edge/ Six of 328 client-facing capabilities
⌘Nightly optimizationSample run
✓Find18 findings
✓Prepare & deliver6 changes selected
↶Verify5 passed · 1 rolled back
client-site.example

Autonomous optimization

On Full autopilot, supported fixes run within your rules. Every delivered change can be undone.

Reversible by designChanges are added as the page is served.

Edge delivery

Changes are delivered reversibly in the HTML response, not in the CMS or the source code.

↳Crawler requestsSample
OAI-SearchBotGET /bike-serviceFetched
Perplexity-UserGET /pricingFetched
GPTBotGET /aboutFetched

A fetch does not confirm a citation.

Agent traffic

See crawler visits and AI referrals. A visit is not the same as a citation.

↗AI visibility12 weeks · sample
Answers that cite a client page
31%+4 pts
Week 1Week 12

AI visibility

See which tracked AI answers link to your clients, mention them or use other sources.

Try a control level — illustration only
✓Publish within your rules.

Eligible changes can publish automatically. You control visible rewrites per site.

◇Review visible changes.

Titles, meta descriptions and schema can publish. Text on the page needs approval.

ⅡApprove before publishing.

Every proposed change waits for your team’s approval.

Control and safety

Choose what needs approval. Pause delivery or undo changes when you need to.

✓Check the live pageSample
✓Deployed at the edge
✓Re-fetched
✓Core elements compared
5 passed↶ 1 rolled back

Verification

A real browser checks title, meta description, H1 and structured data. If they worsen, the change rolls back.

Signals

See where your clients appear in AI answers.

Track citations, brand mentions and sources using scheduled prompts, not private conversations. AI referral visits and crawler fetches are counted separately.

Three separate measurements12 WEEKS · SAMPLE DATA
  • Citation share

    31%

    How often a tracked answer cites a client page as a source.

  • Share of voice

    58%

    How often the client is named alongside other brands in tracked answers.

  • Sources behind the answer

    46

    Domains used as sources in tracked answers, including the client’s own.

Illustrative trends. A rise does not prove that a site change caused a result.

Delivery

Follow one change from finding to verified.

Follow a sample title fix through deployment and verification. See what was queued and which changes rolled back after core page elements worsened.

How the run was filtered
214 signals → 5 verified changes
Sample nightly run
Signals read214 · 100%
Findings with an action18 · 8%−196 needed no action
Changes selected6 · 3%−12 queued for the next run
Deployed and verified5 · 2%−1 rolled back
One title. Two versions.Sample
Original in the CMS
Home | Client website
Delivered to the visitor
Services and pricing | Client website

An improved title. The same original site.

Preferium changes the title in the delivered HTML. Remove that change to serve the original again. The CMS stays untouched.

Read both titles
Original in the CMS
Home | Client website
Delivered to the visitor
Services and pricing | Client website
A title fix, step by step
title · /
Sample · verified
  1. Found03:12The home-page title does not describe its services.
  2. Written03:14A clearer title is proposed within your rules.
  3. Deployed03:15Served in the HTML; the CMS stays unchanged.
  4. Verified03:17A real browser checks title, meta description, H1 and structured data.
  5. Logged03:17Saved in the panel and ready to undo.
Questions

What agencies ask first.

The essentials before you join. Pricing, platform and white-label guides explain the details.

Explore the platform
What is Preferium AI Edge?

An autonomous AI SEO platform agencies sell under their own brand. It finds supported improvements on existing client sites, delivers them within your publishing rules, checks the live HTML and tracks selected AI answers. It does not write articles for clients. Clients see your agency in the panel, reports and emails.

Does it deploy without anyone reviewing first?

You choose per site. Full autopilot publishes supported changes within your rules when those changes are enabled. You can enable visible rewrites separately. Invisible-only holds visible text for review. Review everything queues every proposal for approval.

How is my agency billed, and how do my clients pay?

Your agency pays Preferium for its plan, connected client domains and usage. Clients pay your agency at the prices you set, through your Stripe or invoice. The pricing page displays only charges published by the product.

What does my client see?

Your name, logo and colours appear in the panel on your dashboard domain, and in reports and alerts. Branded sign-in and invitation emails are included at launch. The DNS target ssl.preferium.com is publicly visible; legal documents identify Preferium where required.

Which client sites qualify?

The client must be able to add a DNS record, and the site must return HTML. A compatibility check runs before go-live and explains unsupported setups. The original DNS record is saved so the site can be pointed back.

Can we try it first?

Yes. Each agency can use one 15-day trial with one client workspace. Invitations come through the waitlist; there is no public opening date yet.

Join the founding-partner waitlist

Join for an invitation when registration opens. Agencies invited before public registration are our founding partners. The launch date has not been announced.

Talk to us

We use these details only to tell you when registration opens, and delete them if you do not become a partner.

Privacy choices

Choose which optional technologies Preferium AS may use. All of them are off until you choose.

Analytics: Google Analytics 4 counts page views. Google may receive the page address, referrer, network address, browser and device details, and online identifiers. Browser storage: _ga, _ga_*: Up to 730 days. Renewed on activity. The browser may shorten the storage period.

Provider: Google Ireland Limited. Google may transfer data to the United States.

See the cookie notice, the privacy notice and theterms.

Necessary technologies Used for site functions

Preferium AS and Cloudflare deliver the site and protect forms against abuse. A local preference remembers if you pause animation. When optional tracking is available, the site can also remember your documented privacy choices.

Consent receipt
Provider: Preferium AS. HttpOnly receipt that documents and retrieves your consent choice. Name in the browser: __Host-preferium_consent. Storage period: The receipt is valid for up to 180 days without rolling renewal.
Local privacy choices and pending rejections
Provider: Preferium AS. Local storage of privacy choices and pending rejections. The entry alone can never allow optional technologies; a valid server receipt is required. Name in the browser: preferium-consent-v2. Storage period: Until the entry is overwritten or the browser site data is cleared. No automatic timed deletion is configured.
Privacy choice synchronization between tabs
Provider: Preferium AS. The latest message that synchronizes privacy choices and pending rejections between tabs. The message can only close optional technologies and trigger a new server check. Name in the browser: preferium-consent-sync-v1. Storage period: Until the entry is overwritten or the browser site data is cleared. No automatic timed deletion is configured.
Motion pause preference
Provider: Preferium AS. Session storage restores the requested accessibility preference between pages in this tab. Nothing is sent to a server. Name in the browser: preferium-motion-paused. Storage period: Until this browser tab session ends.
Cloudflare Turnstile
Provider: Cloudflare. Abuse protection that loads only on forms where Turnstile is necessary. Storage period: Short-lived control value tied to a form submission.
Analytics

Helps us understand how the site is used, when you consent.

Provider: Google Ireland Limited. The data may include the page address, referrer, network address, browser/device, online identifiers and usage events.

_ga, _ga_*
Processes site usage for aggregated analytics after specific consent. Storage period: Up to 730 days. Renewed on activity. The browser may shorten the storage period.

You can withdraw your choice via Privacy choices. That stops further optional loading but does not recall data already sent to Google. We attempt to delete known first-party values; the browser may prevent deletion of third-party values.

How Google uses and is responsible for data · How Google uses information from partner sites · Google privacy policy