The platform
Bellhop turns a single page into the right page for each paid-search visitor — grounded in your own content, decided at the edge, and proven by the traffic. Here’s everything under the hood.
Bellhop reads the Google Ads signals behind each paid visit — the keyword, campaign and ad group — and rewrites your headline, sub-head and calls to action to match what that visitor actually searched for. When the signal isn’t there, it falls back to a geographic default, then to your original copy.
This is the part that lets you sleep at night. Bellhop writes from a knowledge base built out of your own pages, and every generated claim carries a citation back to the source it came from. Fabricated citations are rejected automatically, ungrounded output is dropped, and a person on your team approves copy before a visitor ever sees it.
“Trusted by teams in 40+ countries.”
cited from /customers grounded
“Rated #1 by every analyst.”
no source — dropped before review
Point Bellhop at your site and it crawls your existing pages to learn your product, your proof and your voice — all on Cloudflare’s infrastructure. That knowledge base is what every rewrite draws from, so the copy stays true to what you’ve already published.
Indexed from your site
A Thompson-sampling multi-armed bandit quietly routes more traffic toward the variations that convert, with sticky 30-day visitor assignment so each person’s experience stays consistent. You author the variations; Bellhop handles the ongoing optimization in the background.
Traffic follows what converts
Bellhop can recognize the company behind a paid visit and surface that context to your team — useful for prioritizing follow-up and, with HubSpot, for tying personalization back to real pipeline and revenue. It’s account-level intelligence for your team, not a name plastered across the visitor’s screen.
Surfaced to your team and tied to pipeline — never shown on the page to the visitor.
Built to be invisible
Personalization is only worth it if it never costs you the page. Bellhop runs entirely at Cloudflare’s edge, as your own first-party code.
The runtime is built to decide and render in well under a fifth of a second — no visible flicker, no layout shift.
Nothing on the render path phones a third party. Personalization is first-party, served from the edge nearest your visitor.
If anything is uncertain, Bellhop serves your original page untouched. The worst case is the page you already have.
IP addresses are hashed, there’s no fingerprinting, and company enrichment runs on a GDPR legitimate-interest basis.
Tell us your platform and your paid-search terms. We’ll show you exactly what Bellhop would rewrite — grounded in your content, before anything goes live.