Autonomous AI SEO.
Your rules.

No. Each client connects with a single DNS record (a CNAME). The optimization happens at the edge, in front of the site, so it works on WordPress, Webflow, Framer, Kinsta, Next.js or a fully custom stack — no plugin, no CMS access.

Your brand in the panel on your own domain, reports and alerts from your own address, and a vendor-neutral help centre. The DNS target ssl.preferium.com is publicly visible and includes the Preferium name; legal documents identify Preferium where required. The launch offering includes sign-in and authentication invitation emails under your brand, plus vendor-free delivered HTML.

Clients buy your packages and credit top-ups inside your branded panel, paid through your Stripe. Preferium bills your agency separately for the platform plan, connected domain seats and extra credit packs. You set client prices and keep the margin.

Yes. Your clients can order the packages you have defined right inside your branded panel, paid on your Stripe. Checkout always happens inside the panel, never on a page that charges without your setup behind it.

Once the client’s DNS record is in place, the platform verifies it, issues the certificate, confirms the origin answers, detects the site and runs the first audit on its own. From there the engine works at the control level you set.

There is no date yet. Agencies on the waitlist are invited first, as founding partners, before registration opens to everyone.

The engine finds supported issues, prepares fixes, publishes allowed changes and checks the result. Your control level and site rules determine what runs automatically and what needs approval. Published edge changes remain reversible.

On Full autopilot, enabled changes within your rules deploy without a queue. You control visible rewrites per site. Invisible-only holds that text for review, and Review everything needs approval for every change. Menus, footers and sidebars are never touched.

Changes are delivered at the edge, leaving the CMS untouched. A real browser checks title, meta description, H1 and structured data after deployment; regressions trigger rollback and an alert. Drift checks run every 30 minutes. Published changes can also be undone with one click.

Pipeline failures fall back to the original page; Cloudflare outages and client DNS errors are outside that safeguard.

On server-rendered sites, people and crawlers receive the same optimized HTML. The cloaking guard compares a browser request with a GPTBot request and flags serious differences. For JavaScript-only sites, a real browser renders the page so crawlers can read the content people see. That is dynamic rendering.

Four assistants with prompt tracking, six answer surfaces in total: ChatGPT, Claude, Perplexity and Gemini use scheduled prompts with web search; Google AI Overviews and AI Mode are tracked separately by keyword.

Coverage follows your plan; prompts run up to weekly or on demand. Grok and Copilot are reading surfaces, not separate measurement sources yet.

No. Preferium improves existing pages: titles, structured data, canonicals, supported technical fixes and on-page answer blocks. Your agency keeps responsibility for content strategy and new articles.

No — and it says so next to each of them. The numbers here show what the panel looks like, for the fictional Northwind Cycles, and carry a visible sample-data label. Real numbers live in each client’s own panel, from GA4, Search Console and the scheduled citation measurement.

Each client has an isolated workspace. Client workspace data is stored in the EU (Stockholm). Edge delivery runs on Cloudflare's global network, and AI measurement providers are listed in the subprocessor register. A DPA is offered. Preferium holds no security certifications.

Three cases. A client who cancels keeps being served for 14 days — an undo window — and billing stops at once.

A client who has earned it can move to frozen delivery: the published pages stay live, unchanged and unbilled, with no active optimization.

A client who disconnects stops being served, the certificate is released and the site data is deleted; the client restores the original DNS record from the snapshot taken at connect.

In every case the deployed changes can be exported as CSV, and everything written for the client is the client’s. The agency white-label terms govern.

Yes. The engine detects each page’s language and optimizes in that language — a Norwegian page gets Norwegian titles and answer blocks, a German page gets German — and eight hreflang checks find broken links between language versions. Citation tracking runs in the client’s market and language too.

Preferium’s current DNS connection model does not support Wix or Squarespace. Other tools may offer integrations for those platforms; we do not claim that a JavaScript snippet is their only option.

Shopify and similar stores also need a supported connector. On other platforms, onboarding checks the routing and origin before accepting the site; DNS access alone is not a compatibility guarantee.