PreferiumOTTO by Search Atlas

Preferium vs OTTO by Search Atlas

OTTO ships its fixes through a browser pixel. Their docs also describe an edge mode over Cloudflare DNS; we ran OTTO as paying customers for years and never got it to serve anything else. That matters because a pixel runs in a browser, and the AI crawlers deciding who gets cited do not run one. Preferium rewrites the raw HTML server-side, for every visitor, with nothing on the page.

Become a partner Run the free AI scan

TL;DR

What we got, every time, was the pixel — including on the Cloudflare install their docs describe as edge-level, and their support confirmed the limitation when we raised it. GPTBot and ClaudeBot do not execute JavaScript, so a pixel-delivered fix is a fix they never see.
Preferium has one mode and no install to get wrong. Server-side, in the raw HTML, the same bytes to humans, Googlebot and AI crawlers on every server-rendered page.
When Preferium ships a title, meta description, H1 or schema block, a real browser re-opens the live page and reverts the change automatically if the page got worse. OTTO documents preview and manual rollback; we have found no published equivalent that runs without a person.
This comparison is personal: we ran client SEO on OTTO as paying customers for years before building Preferium. The full story — including where their white-label let us down — is below.

Our story

OTTO is the reason Preferium exists

This page isn’t theoretical for us. Before building Preferium, we ran client SEO on OTTO by Search Atlas — as paying customers for several years, from the day OTTO launched until well into 2026. Plenty of it we liked. Some of it we couldn’t live with.

The deal-breaker was white-label. OTTO offers it — your own domain, reports sent from a neutral address — but in our time as customers we repeatedly found Search Atlas and OTTO branding surfacing inside the supposedly white-labeled panel. It was never fully hidden. We could not put clients in front of that panel without exposing who actually ran the stack, so we ended up never using it the way it was sold — and quietly working around it, which is exactly what an agency should never have to do.

Reliability wore us down too. Support answered quickly — credit where it’s due — but in our experience even small fixes could take months to land, and along the way we hit bugs that broke real client work while we waited.

And the architecture. The AI-generated optimizations were often decent, and deploys through the JavaScript snippet generally worked. Their documentation marketed a Cloudflare install even then — but connecting through Cloudflare made no difference to what was served. Over years of real client use the changes still shipped through the same JavaScript layer, and when we put it to their support they confirmed the limitation rather than fixing it for us. That is the part worth understanding: a documented edge mode is not the same as an edge mode that delivers, and the client whose citations depend on it has no way to tell the difference from the dashboard.

So we built what we actually needed: server-side delivery in the raw HTML that AI crawlers read, white-label with per-client isolation designed in from day one rather than bolted on, and autonomy that verifies its own deploys in a real browser. If you’re an agency that has hit the same walls, Preferium was built for you — literally.

— The Preferium team. Our own experience as customers, shared as lived, as of August 2026.

Yes, fully Partly / with caveats No

How changes deployOne path: server-side, in the raw HTML at the DNS edge. No code on the site, no mode to choose wrongOTTOThe browser pixel. Their docs also describe an edge mode over Cloudflare DNS — we ran it for years as paying customers and never saw it deliver anything but the script, and their support confirmed the limitation when we raised it

Visible to AI crawlers (GPTBot, ClaudeBot, PerplexityBot)Yes — the optimized HTML is the response itself, not a layer applied afterwardsOTTONo. Their own docs state “AI crawlers and non-JS bots only see edge-rendered content, not JS-injected fixes” — and the pixel is what we ever got served, so the fixes sat behind JavaScript the crawlers never run

Humans and crawlers see the same bytesOne response for every visitor, with a parity guard that re-fetches pages as GPTBot and as a browser to catch divergenceOTTOThe crawler reads the original HTML while the browser renders the rewrite — they diverge by design, because the rewrite only exists once JavaScript has run

AutonomyFull autopilot: finds, fixes, deploys and verifies on its own — or review every change, your callOTTOAutopilot with an optional approval mode (their docs); verifying a deploy and rolling it back stay manual steps

What tier white-label starts atGated on being a partner, not on which plan you bought — and your clients pay YOUR Stripe, not ours. Branding is table stakes now; who owns the billing relationship is notOTTOFrom their Pro tier at $399/mo — branded dashboard with your own domain, client portal, white-labeled reporting (their pricing page, verified 5 August 2026)

Deploy safetyTitles, meta, H1s and schema are re-checked on the live page with a real browser and auto-rolled-back if they would harm itOTTOManual review and rollback anytime (their docs). In our years as customers, bugs still reached live client sites

AI visibilityCitations measured weekly across all four engines — ChatGPT, Claude, Perplexity & Gemini — web-grounded, with sources and sentiment, on every planOTTOTracks how LLMs and search engines crawl your site — monitoring, per their docs

Reliability — our experienceVerification + auto-rollback exist precisely so a bad change can’t linger on a client siteOTTOSupport replied fast, but fixes took months and along the way bugs broke real client work (as customers, launch → 2026)

Time to liveServed at the edge in seconds — under a minute globallyOTTOApplied when the pixel runs in each visitor’s browser — so for a crawler that runs no JavaScript, never

Pricing modelCapability subscription plus separately published wholesale usage per delivered domain and 500-credit unitOTTOSimilar shape: monthly tiers from $99 to $999/mo plus universal credits, with paid AI activations as an add-on (their pricing page, August 2026)

InstallationOne CNAME record. No plugin, no snippet, nothing added to your pagesOTTOJS snippet added to every page (plus optional implementation services)

White-label for agenciesFull white-label: your brand, your Stripe, your prices, your packages — isolation designed inOTTOOffered — but in our years as customers, Search Atlas/OTTO branding repeatedly surfaced inside the white-label panel. We never dared put clients in front of it

If the subscription endsExport every deployed title, meta description and H1 as CSV, anytime — a portable record you can re-implement anywhereOTTOPixel changes stop rendering; their docs market a “Deep Freeze” option to preserve optimizations

Comparison accurate as of August 2026, based on public documentation and, where stated, our own experience as customers. Spotted something that changed?Tell us and we’ll fix it.

Fair is fair

What OTTO does well

Credit where due: Search Atlas bundles a broad toolset — research, audits, content and reporting — behind a clean dashboard. Their docs now market CMS and Cloudflare connectors, an optional approval mode, and a post-cancellation “Deep Freeze”. Support answered us quickly, and the AI-written optimizations were often genuinely good. If you want one login for research tooling and can live with pixel-based delivery, it is a capable suite. Their help centre documents an edge mode that modifies raw HTML — but in our years as paying customers that mode never delivered anything but the pixel, and their support confirmed the limitation rather than resolving it, so we report what we were actually served. What has not changed is the rest: a pixel install leaves AI crawlers reading the unoptimized page, there is no published post-deploy verification, and a white-label that leaks the vendor’s name isn’t one an agency can build on.

FAQ

Preferium vs OTTO — common questions

OTTO documents an edge mode. Why does your table say pixel?

Because the table reports what we got, not what the documentation offers. We ran OTTO as paying customers for years, we set up the Cloudflare install their docs describe as edge-level, and what came back was the same JavaScript pixel every time — their support confirmed the limitation when we put it to them rather than resolving it. We are not calling their documentation false; we are telling you that a documented capability and a delivered one are different things, and that the client whose citations depend on it cannot tell them apart from a dashboard. Install it yourself and fetch a page as GPTBot — that settles it in one command, for us as much as for them.

Is Preferium actually autonomous, or “autonomous with approvals”?

You choose the autonomy level. On full autopilot, Preferium finds issues, generates fixes, deploys them to the edge and verifies each one on the live page — rolling back automatically if a change would cause harm. If you prefer review gates for visible changes, turn them on. Both are first-class modes.

What happens to my optimizations if I cancel?

Like any edge- or pixel-delivered product, optimizations stop being served when the service stops. OTTO’s docs market a “Deep Freeze” option to preserve changes after cancellation; Preferium’s answer is portability — export every deployed title, meta description and H1 as CSV at any time, so you keep a record you can re-implement anywhere, with any stack.

Can I migrate from OTTO to Preferium?

Yes — connecting a site is one DNS record and takes minutes. Run both side by side during a transition if you like; Preferium never touches your CMS or your existing snippet.

Founding partners

Get early access — build your agency on Preferium

Partner registration is opening soon. Join the waitlist and we’ll invite you as a founding partner, with early-access pricing locked in.

No card required. We’ll only email you about your invite.