Skip to content
PreferiumJoin the waitlist

Compare

Preferium vs overlay SEO tools.

Preferium delivers supported changes before the page reaches visitors and crawlers. A browser-only overlay needs its script to run first. OTTO and Alli AI also document server-side options, so compare the delivery mode you will actually use.

Choose by how the service works

← All comparisons

What reaches the crawler?

What the crawler gets

Browser-only overlayScript-dependent

Changes need the browser script.

Client siteOriginal HTMLCrawler

A crawler that does not run the script misses those changes.

Page title
Original title
Description
Empty
Main heading
Original heading
Structured data
Missing
Answer block
Missing
Preferium AI EdgeOur delivery

Changes arrive in the HTML.

Client siteEdge rewriteCrawler

The crawler receives the supported changes.

Page title
Specific service title
Description
Description added
Main heading
Specific service heading
Structured data
FAQ schema added
Answer block
Answer block added

No page script. No CMS plugin. The original CMS stays unchanged.

Server-rendered pages receive the same HTML for people and crawlers. JavaScript-built pages require browser rendering.

Inspect the sample HTML

Original HTML

<title>Home | Acme</title>
<meta name="description" content="">
<h1>Welcome</h1>
<!-- no structured data -->
<!-- no answer block -->

Preferium’s delivered HTML

<title>Acme — B2B logistics software for Nordic freight</title>
<meta name="description" content="Route planning and customs…">
<h1>Freight software built for Nordic customs rules</h1>
<script type="application/ld+json">{ "@type": "FAQPage", … }</script>
<!-- answer block: what Acme does, in one paragraph -->

Illustrative example for a fictional Acme page. Inspect a public page with the free AI scan.

Where the change lives

  1. CMS write

    Written into the client’s CMS, so the source itself changes.

    Change applied at: Client CMS.

    A crawler that runs no script gets the change.

  2. Edge delivery

    Preferium’s path: applied as the page is delivered. The CMS stays unchanged.

    Change applied at: Edge.

    A crawler that runs no script gets the change.

  3. Browser overlay

    Applied by a script after the page reaches the browser.

    Change applied at: Browser.

    A crawler that runs no script gets the original HTML.

A simplified illustration of three delivery methods, not of any named product. The sourced comparisons show which mode OTTO and Alli AI document.

What Preferium adds

Deliver page improvements

  • Inspect what crawlers receive

    Inspect the HTML in a simulated crawler request.

    Crawler View makes a simulated request with a named crawler user agent. It shows the live title, meta description, H1 and structured data; it does not prove an observed crawler visit.

  • One DNS record per client

    Connect the site without installing a CMS plugin.

    Connect with one CNAME record to ssl.preferium.com. The certificate is issued automatically and the client’s server is checked before go-live. Preferium remains visible in public DNS and required legal disclosures.

Check and undo changes

  • Live checks after each change

    Core page elements are checked after deployment. Regressions trigger rollback.

    After deployment, a real browser checks the live title, meta description, H1 and structured data. If those checks detect a regression, the change is rolled back and you are alerted. Other changes remain reversible with one click.

  • You keep the record

    Export deployed changes. The client’s CMS stays unchanged.

    Edge delivery stops with the service; the client’s CMS stays unchanged. Export every deployed change as CSV at any time. Qualifying clients can use frozen delivery to keep published pages live, unchanged and unbilled.

Run your agency’s service

  • Measured AI visibility

    Track mentions and citations across six answer surfaces.

    Four assistants with prompt tracking, six answer surfaces in total: ChatGPT, Claude, Perplexity and Gemini, plus Google AI Mode and AI Overviews. Results come from real answers with web search. Mention rates include confidence ranges.

  • You control what publishes

    Choose the approval level and control visible rewrites per site.

    Choose Full autopilot, Invisible-only or Review everything for each client site, and control visible rewrites separately. Element optimization is charged only for elements changed; crawling, audits and measurement can use credits separately.

Where snippet tools fit

Quick setup. No DNS change.

Install a snippet without changing DNS. Some tools support Wix and Squarespace; Preferium does not.

A crawler sees browser-side changes only if it runs the script or gets a rendered page.Compare the response HTML

Founding partners

Build your agency on Preferium.

Partner registration opens by invitation from the waitlist, and there is no date yet. Read the agency agreement and how partner billing works before you decide.

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