How IntentGrid rewrites a page for each visitor
IntentGrid rewrites a web page's visible copy for the individual visitor reading it, using only the context that arrives with the request. It changes headlines, body copy and calls to action. It does not change design, layout, pricing or product claims. IntentGrid is in early access: the public demo rewrites any URL you paste and renders it in a sandbox on intentgrid.ai, while adaptation on your own domain is set up per site by hand.
Last updated 22 September 2026.
What IntentGrid reads when a page loads
Everything it uses comes from the request itself and from the visitor's own browser. There is no account lookup, no data broker and no profile kept afterwards.
- Traffic source and referrer, so a visitor from a forum link and a visitor from a search result are not treated identically.
- Campaign and UTM parameters, so a page can answer the promise the ad made.
- Approximate city, region and country, resolved from the IP address.
- Device type and browser.
- Language preference.
- Screen and window size, and whether they prefer dark or light.
- Timezone, platform, and local time of day for that visitor.
The rewrite never learns a visitor's name or email, and never looks up the company behind an IP address. It knows how someone arrived, not who they are.
Four things belong in the same breath, because they are easy to assume away. The visible copy of a page you paste is sent to a third-party inference API to be rewritten. Where the city is not already in the request, it is resolved from the IP through a third-party geolocation service. This marketing site keeps a random id in your browser and reports demo runs and sign-ups to Google Analytics and Reddit Ads, including a one-way hash of any email you submit, which is ordinary ad measurement rather than part of the adaptation. And a URL pasted into the demo is relayed to a private team channel with the requester's IP and the same context the rewrite used: approximate city, device, referrer or campaign, language, local time and screen size.
What it rewrites and what it never touches
It rewrites text: headlines, subheadings, body copy, feature descriptions and the labels on buttons.
Your own design, layout, colours, components, typography, images, pricing and product claims come back untouched. The demo does add four things on top of them: a welcome strip in a colour taken from your own stylesheet, a personalized overlay, a highlight on your headline, and a small IntentGrid badge. If the model has nothing better to say for a given sentence, it returns that sentence unchanged. It is instructed never to invent a price, a feature or a claim your page does not already make, because the fastest way to ruin a landing page is to put a promise on it that the product cannot keep.
This is worth being blunt about: if your site reads as AI-generated because of the gradient hero, the three rounded cards and the glass everything, IntentGrid does not fix that. That is a design problem and this is not a design tool. See why vibe coded websites look the same for the part it does and does not address.
What a search crawler gets
On-domain adaptation is built so crawlers receive your canonical default page: one URL, one canonical version, no per-segment duplicates competing with each other in the index, and nothing served to a crawler that a person cannot see. That part is not shipped yet, so today nothing is served to a crawler at all and your live page is untouched. The cloaking line is the reason it is built that way, and it is covered in detail in does website personalization hurt SEO.
What works today: the demo, step by step
One thing is live right now, and it is a demo. Here is precisely what happens when you paste a URL at intentgrid.ai:
- The server fetches that public page's HTML.
- It strips every script and inline handler, keeping the markup and CSS.
- It sends the page's visible text, up to a few hundred strings, to a third-party language model along with the context of your request.
- It puts the rewritten strings back into the markup.
- It renders the result in a sandboxed iframe on intentgrid.ai.
Links to other pages adapt too, though forms and anything script-driven will not work, because the scripts were stripped, and each click counts against the demo's per-visitor limit. What you are looking at is a preview of your page. It is not your page, and it is not running on your domain.
What the demo cannot do
It cannot change your site, so it cannot break it. It fetches your public HTML and stylesheets the way any browser would, and has no access to a backend, a database, an environment variable or any user data.
A fully client-rendered application returns a near-empty shell, because a near-empty shell is what the fetch received. There is little copy in it to rewrite, and the preview will look sparse.
Choosing a persona, as in “show me the Hacker News version”, is on the roadmap and is not in the demo. The demo writes for the kind of visitor it can actually see: your city, device, language and how you arrived. Two visitors who look alike on those signals get the same cached version for a few minutes.
It also runs on a daily inference budget. When that is exhausted, or the model call fails, the preview quietly falls back to a template that swaps your headline and adds a welcome line, without rewriting the body. The frame labels it “adapted” rather than “AI-adapted” when that happens.
It measures nothing. There is no conversion rate, no lift figure and no statistical proof anywhere in this product, and there is no published customer result, case study or testimonial, because there is not one yet.
What is early access
Running adaptation live on your own domain, for your own visitors, is not shipped. It is early access: switched on per site, by hand, with the IntentGrid team. It is not self-serve, and there is no install snippet to copy yet. The roadmap on the homepage still marks per-visitor rewriting as in progress, because that is where it is.
It is free during early access. No paid plan has been published, and no standing free tier has been promised to anyone.
Who checks the copy
A language model is writing your words, and bad copy has no error message. Nothing here removes the site owner from that loop. Because early access is set up by hand, the adapted copy gets looked at with you before it goes near real visitors. Tone controls, a banned-word list and a review queue are not built yet.
If your product has no audience, no sentence fixes that, and IntentGrid will not tell you so. Rewriting a headline is one of the most productive-feeling ways to avoid asking why nobody is buying. This is a tool for pages that already get visitors who leave, not a substitute for finding out whether anyone wants the thing.