Dynamic content SEO: personalize pages Google can still index
Short answer Google reads your page as a first-time visitor with no cookies, usually from a US address, who never clicks or grants permissions. Make that default version complete: services, prices, city and contact details in the page itself. Personalize on top of it. Swapping a headline is fine; showing Google different content than people see is cloaking.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callWhat Google sees on a personalized page
Google indexes the version a brand-new visitor gets: no cookies, no saved settings, no clicks, no location permission, and usually a US internet address. Whatever you show only to returning, logged-in or local visitors, Google likely never sees.
"If you're using cookies to control the test, keep in mind that Googlebot generally doesn't support cookies. This means it will only see the content version that's accessible to users with browsers that don't accept cookies." (Google Search Central: Minimize A/B testing impact)
Google's rendering service also wipes local storage, session storage and cookies between page loads, and expects Googlebot to say no to permission prompts like location or camera (Google Search Central: Fix Search-related JavaScript problems).
It also crawls as a smartphone and indexes the mobile version of your page (Google Search Central: Mobile-first indexing).
So the rule is simple: make the default page complete, then personalize on top.
| Visitor detail | What Google sees | Fix |
|---|---|---|
| Returning visitor (cookie) | First-visit version | Put every service and offer in the default page |
| Visitor's city (from IP) | Usually the US default | Give each city or region its own URL |
| Visitor's language (browser setting) | No language set | Separate language URLs with hreflang |
| Device (phone or desktop) | Phone version | Keep the same text on phone and desktop |
| Logged-in member area | Nothing behind the login | Keep public pages public |
| Content after a click (tabs, "Show more", quiz) | Only if it's already in the page code | Load text with the page; hide it with styling if you like |
Is dynamic content bad for SEO?
No. Changing a headline, banner or offer by visitor is allowed. The line is cloaking: Google's spam policies define it as showing users and search engines different content "with the intent to manipulate search rankings and mislead users" (Google Search Central: Spam policies). Their example is a travel page shown to Google and a drug page shown to people.
A personalized "Welcome back" banner isn't that. Writing extra keyword text only for Google is. The test is the same for A/B tests: don't send Googlebot one set of URLs and people another (Google Search Central: Minimize A/B testing impact).
Location-based content: one page per city, not one page that changes
If your site swaps "Plumber in Dallas" for "Plumber in Fort Worth" by the visitor's IP address, Google will mostly see one version. Its crawler's default addresses "appear to be based in the USA," and it sends no language preference (Google Search Central: Locale-adaptive pages). Google warns it "might not crawl, index, or rank all your content for different locales."
This hits Canadian businesses hardest. A Toronto firm that shows its Canadian prices and "Serving the GTA" only to Canadian visitors may be indexed with its US fallback. Google's fix is separate URLs (for example /toronto/ and /dallas/, or /en/ and /fr/) linked with hreflang tags, which tell Google which page serves which place or language.
City pages have their own rule: each needs real local content, or Google may treat them as doorway pages. See city pages for service areas.
Pages built by JavaScript: will Google index them?
Usually yes, but slower and less reliably. Google processes JavaScript pages in three steps: crawling, rendering (running the code to build the page), then indexing (Google Search Central: JavaScript SEO basics). Rendering can lag, and other bots may skip it:
"Keep in mind that server-side or pre-rendering is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript." (Google Search Central: JavaScript SEO basics)
AI assistants are the bigger gap. A December 2024 study by Vercel and MERJ, based on crawler traffic across Vercel's network, found ChatGPT's and Claude's crawlers fetched JavaScript files but did not run them (Vercel: The rise of the AI crawler). Text that appears only after a script runs may be invisible to them. Google's AI Overviews and AI Mode use Google's normal index, with "no additional technical requirements" (Google Search Central: AI features).
Server-side rendering means your server sends the finished page, text included. Client-side rendering sends a near-empty page that the browser fills in. Most risk sits in custom-built apps and in widgets that inject text.
Skip "dynamic rendering." Serving bots a pre-built copy while people get the script version was once Google's advice. Not anymore:
"Dynamic rendering was a workaround and not a long-term solution for problems with JavaScript-generated content in search engines." (Google Search Central: Dynamic rendering as a workaround)
Google now recommends server-side rendering, static rendering or hydration (a finished page that scripts then make interactive).
The checklist for any dynamic page
- Default page complete. Services, prices or price ranges, service area, phone and address are in the page as sent, not added by a widget.
- Real links. Google can generally only follow standard HTML links (an a tag with an href address); menu items that work only by script may be missed (Google Search Central: Link best practices).
- No # for content. Google generally doesn't support URL fragments (the part after #), so don't load different pages that way (Google Search Central: URL structure).
- One canonical per page. Sort, filter and tracking versions point to the main URL with rel="canonical." Duplicates aren't penalized; "it's not a violation of Google's spam policies" (Google Search Central: What is canonicalization). Canonical just picks the version that shows.
- Tests done right. Use 302 (temporary) redirects for A/B test variants, canonical back to the original, and end the test when it's decided (Google Search Central: Minimize A/B testing impact).
- Check what Google got. Run the URL through Search Console's URL Inspection tool or the Rich Results Test; both show the rendered page and script errors (Google Search Central: Fix Search-related JavaScript problems). Find your key sentence in the rendered HTML.
Crawl budget (how many pages Google fetches) rarely matters for a small site. Google's guide is for sites with 1 million+ pages, or 10,000+ that change daily (Google Crawling Infrastructure: Crawl budget).
Example
A roofer with a returning-visitor offer
A roofing company shows "$500 off your second job" to past customers, via a cookie. Google sees the first-visit page with the standard offer. Nothing to fix, as long as the standard page lists the services.
A cleaning company that swaps cities by IP
A cleaning company serving Vancouver and Seattle shows one home page whose headline, prices (CAD or USD) and phone change by visitor location. Google likely indexes the Seattle version only. Two pages, /vancouver/ and /seattle/, each with its own prices and reviews, let both be found.
A clinic with a booking widget
A clinic's treatment list loads inside a third-party booking widget. URL Inspection shows the rendered page with no treatment names. Adding a plain-text treatment list with price ranges to each page puts them in front of Google and AI crawlers.
FAQ
Does Google penalize personalized content?
No. Google acts on cloaking, meaning different content shown to search engines to mislead. Tailoring a banner, offer or greeting for people is not cloaking if Google can see the full default page.
Can I show different prices by location?
Yes, but Google will mostly index the version for a US visitor. If prices differ by country or city, give each its own URL.
Is a chat widget or review widget bad for SEO?
Not bad, just possibly invisible. If reviews or answers matter for search, put some of that text in the page itself.
Should I block filter URLs in robots.txt?
Rarely. Google's crawl budget advice targets sites with 10,000+ fast-changing pages. Most small sites need only a canonical tag on each variant.
Different for you?
- Pages crawled but not indexed: see crawled or discovered, currently not indexed.
- Site missing from Google entirely: start with website not showing on Google.
- Choosing a platform that sends finished pages: Wix, Squarespace or WordPress for SEO.
- A French or Spanish version of your site: multilingual website SEO.
- Want rendering and indexing checked for you: SEO agent.