Changes need the browser script.
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
Compare
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.
A crawler that does not run the script misses those changes.
The crawler receives the supported changes.
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.
<title>Home | Acme</title>
<meta name="description" content="">
<h1>Welcome</h1>
<!-- no structured data -->
<!-- no answer block --><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.
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.
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.
A simplified illustration of three delivery methods, not of any named product. The sourced comparisons show which mode OTTO and Alli AI document.
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.
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.
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.
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.
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.
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.
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
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.