Will Google treat personalization on my site as cloaking?
Short answer
Not when search engines get the page a visitor with no campaign tag or referrer gets, and every version keeps the same product, offer, links and URL.
Google defines cloaking as presenting different content to users and search engines "with the intent to manipulate search rankings and mislead users". It turns into cloaking when a crawler sees something people never see, or when people see something the search result did not promise.
Last checked 25 October 2026 · Agshin Rajabov, founder of Rawuser
- Googlebot
- Your page as builtWhat a visitor with no campaign tag and no referrer gets.
- A visitor from ChatGPT
- The same page, a few lines rewordedFraming for why they came, never facts.
- The same for both
- URL, title, meta, links, product, offer, price
Last checked 25 October 2026
5 sources, each with its date
What does Google count as cloaking?
Google's spam policies define cloaking as presenting different content to users and search engines "with the intent to manipulate search rankings and mislead users".
That wording is from the policy page as updated on 28 August 2026. Its two examples are a page about travel for search engines and one about discount drugs for people, and text or keywords added only when a search engine is asking.
The same page now also counts attempts to manipulate generative AI answers in Google Search as spam. Text written to steer AI answers is covered by that line.
Does Google allow different words for different visitors?
We found no Google page about per-visitor copy; its nearest rules allow it as long as the content stays similar and crawlers are not singled out.
On dynamic rendering, where a server sends crawlers a different build of the same page, Google says it is not cloaking while it produces similar content. Its example of crossing the line is a page about cats for users and a page about dogs for crawlers (updated 10 December 2025).
On testing, Google says not to show one set of URLs to Googlebot and another to people, by server logic, robots.txt or any other method. It also notes that Googlebot generally does not keep cookies, so it sees the version a browser that refuses cookies would see.
Where does personalization turn into cloaking?
When a search engine sees something people never see, or when people see something the search result did not promise.
In practice that means any of these: keywords or text that only crawlers get; a different offer, price or topic for one group of visitors; a different URL or a redirect chosen by user agent or by where the visit came from; hidden lines aimed at AI assistants. Google's own example of hacked content is a redirect that fires when someone clicks a Google result and not when they type the address.
Ask whether a searcher who clicked your result would feel misled by the version they got, next to the title and snippet they read. If yes, you are on the wrong side of the line, whatever tool made the change.
Which version does Googlebot see when a script changes the words?
Googlebot runs JavaScript, so it sees what your script shows a visitor with no cookies, no campaign tag and no referrer, unless the script skips crawlers.
That is usually your page as built, which is what you want indexed. The risk is a script that treats crawlers as a group of their own and gives them a version people never get.
Do ChatGPT, Claude and Perplexity see the personalized page?
Mostly not. In a June 2026 test, ChatGPT, Claude, Gemini, Perplexity and Meta AI answered from a page's raw HTML without running its scripts.
Search Engine World gave 12 assistants a page whose HTML held one number and whose script replaced it with another (published 9 June 2026, updated 2 July). Copilot downloaded the script and did not run it. Grok ran it, but its answer still quoted the HTML. DeepSeek, ERNIE, Qwen, Kimi and Mistral ran it and quoted the number the script wrote. It was one pass with one prompt per assistant.
So a script's words can reach some assistants. Keep every version to the same product and the same facts, so whatever an assistant reads is still true. A person who clicks through from an AI answer is a real visitor, like any other.
How can I check what Google sees?
Two checks take about a minute each: fetch the page as Googlebot with curl, and run a live test in Search Console's URL Inspection.
The `curl` check shows what your server sends. Build ids and nonces will differ; headings and paragraphs should not. A 403 for the Googlebot request usually means your firewall blocks fake Googlebots, which is fine. curl does not run JavaScript, so a script that changes words after load does not show up here.
The URL Inspection check covers scripts. In Search Console, inspect the URL, choose Test live URL, then View tested page. You get the HTML and a screenshot of the page as Google rendered it. Compare it with your page opened in a private window with no campaign tag.
curl -s -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" https://example.com/ > as-googlebot.html
curl -s -A "Mozilla/5.0 (Macintosh; Intel Mac OS X 14_0)" https://example.com/ > as-person.html
diff as-googlebot.html as-person.htmlWhat you can do today, with no tool
Keep one URL for every version.
No redirects chosen by source, device or user agent. A visitor from any source and Googlebot open the same address.
Leave the parts search engines read alone.
The
<title>, meta description, structured data, canonical and internal links stay the same for everyone.Give crawlers the default.
Crawlers should get exactly what a visitor with no campaign tag and no referrer gets: your page as built.
Change framing, never facts.
Reword a few visible lines for why someone came. Never add keywords, a different offer or a different price for one group.
Run both checks after every change.
The
curldiff for what your server sends, URL Inspection for what scripts do.
Sources
- Google Search Central, spam policies for Google web search (updated 28 August 2026) read 25 October 2026
- Google Search Central, dynamic rendering as a workaround (updated 10 December 2025) read 25 October 2026
- Google Search Central, A/B testing best practices for Search (updated 10 December 2025) read 25 October 2026
- Search Console Help, URL Inspection tool read 25 October 2026
- Search Engine World, do AI assistants render your JavaScript when grounding? (9 June 2026, updated 2 July 2026) read 25 October 2026
Related questions