{"@context":"https://schema.org","@type":"BlogPosting","headline":"Your Business Profile UTMs Are Filing ChatGPT Traffic as Organic Search (2026)","description":"ChatGPT's map and place widget links to a business using the website URL stored in its Google Business Profile, query string included. Across 230,863 captured map entities, 112,572 of those URLs carry a query string and 80,412 carry a UTM. ChatGPT overwrites utm_source with chatgpt.com and leaves utm_medium untouched - demonstrated on same-domain pairs where only the source differs (fourseasons.com carries utm_medium=organicsearch under both google and chatgpt.com; all.accor.com carries utm_medium=seo+maps under both google+maps and chatgpt.com). Because GA4's Organic Search rule is satisfied by the medium alone - 'Source matches a list of search sites ... OR Medium exactly matches organic', with AND reserved for Direct and the paid channels - a business tagged utm_medium=organic receives its ChatGPT map-widget clicks as chatgpt.com/organic and sees them reported as Organic Search. They cannot reach the AI Assistant channel, whose rule requires the medium to match ai-assistant exactly, so channel evaluation order is irrelevant. 29,867 entities across 716 domains carry utm_medium=organic; 2,883 across 289 domains have already been captured rewritten, including Oetker Collection, Hyatt and Kempinski. The traffic is misfiled rather than invisible: session source still reads chatgpt.com, but the AI Assistant channel count breaks and Organic Search is inflated. Google's published source-category file, used to classify traffic sources, has a Last-Modified date of 9 February 2023 and contains none of chatgpt, openai, perplexity, claude, gemini, copilot, deepseek, grok or bard. The fix is to remove utm_medium=organic from the Business Profile website field; a source-only tag such as utm_source=gbp separates listing traffic without hijacking channel assignment.","datePublished":"2026-09-04","dateModified":"2026-09-04","url":"https://nicolassitter.com/research/business-profile-utm-chatgpt-organic-2026","category":"research","keywords":["Google Business Profile UTM","ChatGPT map widget","GA4 AI Assistant channel","utm_medium organic","AI traffic misattribution","GA4 default channel group"],"articleSection":"Research","wordCount":2200,"readTime":"9 min","articleBody":"September 2026Attribution · GA4\n\n# ChatGPT keeps your tracking tag.Then Google takes the credit.\n\n**TL;DR:** ChatGPT’s map widget links to a hotel using the website URL stored in its **Google Business Profile**, query string and all. It rewrites `utm_source` to `chatgpt.com` and leaves `utm_medium` exactly as the hotel set it. GA4 assigns the Organic Search channel on the medium alone, so a listing tagged `utm_medium=organic` sends its ChatGPT clicks into **Organic Search** and never into AI Assistant. **716 hotel domains** are tagged that way, Hyatt and Kempinski among them. Google gets credited for demand ChatGPT created, and the hotel did it to itself.\n\nNS\n\nNicolas Sitter\n\nPublished 4 September 2026\n\n### Summarize with AI\n\n## Executive summary\n\n80,412\n\nmap-widget URLs carrying a UTM\n\nof 230,863 entities\n\n716\n\ndomains tagged utm\\_medium=organic\n\n29,867 entities\n\n2,883\n\nalready caught rewritten\n\nacross 289 domains\n\n2023\n\nGoogle's source list vintage\n\n819 sources, 0 AI\n\nI found this while trying to disprove something else. I had a hotel where GA4 reported far more Google organic sessions than Search Console reported Google clicks, and I wanted to know whether AI traffic was hiding in the difference. It was not. But one row in that report (a single session labelled `chatgpt.com / organic`) turned out not to be the rounding error I took it for.\n\nIt is a mechanism, it runs across hundreds of hotel brands, and it points the opposite way to every other AI-attribution problem I have written about. Those are all about AI traffic being _invisible_. This one is about AI traffic being **visibly filed under the wrong name**, with a paper trail, because of a tracking tag the hotel added itself for perfectly sensible reasons.\n\n## 1\\. Google classifies your traffic with a list written before ChatGPT\n\nStart with the thing underneath everything else. GA4 decides whether a visit counts as Organic Search partly by checking the source against a published list of known search sites. That list is a downloadable file linked from Google’s default channel group documentation. It holds **819 sources**, and its `Last-Modified` header reads **9 February 2023**.\n\nGoogle's published source-category file, 819 rows total, as served in September 2026.\n\nCategory\n\nSources listed\n\nSOURCE\\_CATEGORY\\_SOCIAL\n\n592\n\nSOURCE\\_CATEGORY\\_SEARCH\n\n129\n\nSOURCE\\_CATEGORY\\_SHOPPING\n\n52\n\nSOURCE\\_CATEGORY\\_VIDEO\n\n46\n\nSearching all 819 rows for _chatgpt_, _openai_, _perplexity_, _claude_, _gemini_, _copilot_, _deepseek_, _grok_ and _bard_ returns **0 matches**. The file Google publishes for classifying where your traffic comes from was last touched in 9 February 2023, before ChatGPT had a browsing mode, before any of this existed.\n\nTo be fair to Google, this is the _published_ artifact and not necessarily the list running in production, and there is now a separate AI Assistant channel that works off a different list. That other list is not published at all. Either way, the public documentation of how your traffic gets classified is three and a half years behind the thing it needs to classify.\n\n## 2\\. ChatGPT rewrites the source and keeps the rest\n\nWhen ChatGPT shows a place card or a map, the link on it is not something ChatGPT invented. It is the website URL stored in that business’s Google Business Profile, carried through with whatever query string the owner put there. Across **230,863** captured map entities, 112,572 of those URLs carry a query string and **80,412** carry a UTM.\n\nWhat ChatGPT does to them is specific and, once you see it, obvious: it **overwrites `utm_source` with `chatgpt.com` and touches nothing else**. The proof is domains that appear under two different sources with an identical medium, and the mediums are plainly the hotel’s own vocabulary rather than ChatGPT’s.\n\nSame domain, same utm\\_medium, two different utm\\_source values. Counts are captured map entities.\n\nDomain\n\nutm\\_medium\n\nas the hotel tagged it\n\nas ChatGPT serves it\n\nfourseasons.com\n\n`organicsearch`\n\ngoogle (4,149)\n\nchatgpt.com (480)\n\nhyatt.com\n\n`organic`\n\ngoogle (3,465)\n\nchatgpt.com (244)\n\nsofitel.accor.com\n\n`seo+maps`\n\ngoogle+maps (1,570)\n\nchatgpt.com (94)\n\nanantara.com\n\n`organic_search`\n\ngoogle\\_gmb (742)\n\nchatgpt.com (103)\n\noneandonlyresorts.com\n\n`organic-search`\n\ngbp (527)\n\nchatgpt.com (105)\n\nall.accor.com\n\n`seo+maps`\n\ngoogle+maps (330)\n\nchatgpt.com (198)\n\nNobody at Accor chose `seo+maps` to describe ChatGPT. They chose it to label their Google Maps listing, years ago, and ChatGPT is now handing that label out with its own name stapled over the source field. If your Business Profile URL is untagged, you simply get `?utm_source=chatgpt.com` appended and everything works properly. The damage is done only to hotels that were already trying to measure carefully.\n\n## 3\\. Where that click lands in GA4\n\nGA4’s default channel group documentation states the Organic Search rule as three separate lines:\n\nSource matches a list of search sites listed under “SOURCE\\_CATEGORY\\_SEARCH”\n\nOR\n\nMedium exactly matches organic\n\nThat middle line is an **OR**. The deliberateness shows in the rest of the table, which joins Direct and every paid channel with AND and reserves OR for Organic Search, Organic Social, Organic Video, Email and SMS. **The medium alone is enough.** So `chatgpt.com / organic` satisfies Organic Search without the source mattering at all, which is just as well for Google, since `chatgpt.com` is not on the list it would have checked.\n\nAnd it cannot land in the AI Assistant channel instead, because that rule requires the medium to match `ai-assistant` exactly. With `organic` sitting in the medium field, the AI Assistant rule fails no matter what order the rules are evaluated in. That matters, because Google documents that ordering for custom channel groups and never for the default one. The outcome here does not depend on it.\n\nOne honest note on evidence. Google documents that a manual UTM outranks the referrer (the referrer _“may set dimensions when no other campaign or traffic source fields have been set”_) and separately that the `ai-assistant` medium is assigned _“if the referrer matches a list of AI Assistants”_. It never says in one sentence that a manual medium suppresses that automatic assignment. That step is composed from two documented facts rather than quoted from one, and I would rather flag it than let it pass as Google’s own wording.\n\nAnd here it is in the wild, in a live GA4 property:\n\n![GA4 session source/medium report listing chatgpt.com / ai-assistant at row 3 and chatgpt.com / organic separately at row 8](/_next/image?url=%2Fimages%2Fga4-chatgpt-organic-row.png&w=3840&q=75&dpl=dpl_GqBhbg1M5gyMJpPZjbrvghGB9fJy)\n\nTwo ChatGPT rows in one report. `chatgpt.com / ai-assistant` at row 3 is the channel working as intended. `chatgpt.com / organic` at row 8 is the same assistant arriving with a medium it inherited, and it will be counted as Organic Search. Source: Nicolas Sitter, Business Profile UTMs in ChatGPT map widgets, 2026.\n\n## 4\\. Who is exposed\n\n`organic` is not some exotic choice. It is far and away the most common medium on a Business Profile link, and it is the one GA4 treats as a reserved word.\n\nutm\\_medium values on ChatGPT map-widget website URLs. \"Caught rewritten\" counts entities already captured with utm\\_source=chatgpt.com and that medium intact. 63,665 entities across 1082 domains carry some medium.\n\nutm\\_medium on the listing\n\nEntities\n\nDomains\n\nCaught rewritten\n\n`organic`\n\n29,867\n\n716\n\n2,883\n\n`seo maps`\n\n4,949\n\n12\n\n0\n\n`organicsearch`\n\n4,798\n\n3\n\n487\n\n`seo+maps`\n\n4,105\n\n15\n\n681\n\n`local`\n\n3,817\n\n44\n\n368\n\n`gmb`\n\n2,072\n\n63\n\n163\n\n**716 domains carry `utm_medium=organic`** on their Business Profile link: 29,867 entities, 46.9% of every tagged listing in the corpus. That is the exposed population. 2,883 entities across 289 of those domains have already been captured with the source rewritten and the medium surviving.\n\nThese are not neglected listings. The domains already caught are largely brands with real marketing teams behind them, which is the point: the tag is a sign of somebody trying to measure their listing traffic separately, and that is precisely the effort that backfires here.\n\nDomains most frequently captured with utm\\_source rewritten to chatgpt.com while utm\\_medium=organic survived.\n\nDomain\n\nEntities caught as chatgpt.com + organic\n\noetkerhotels.com\n\n313\n\nhyatt.com\n\n244\n\nkempinski.com\n\n99\n\ndylanamsterdam.com\n\n81\n\n1hotels.com\n\n55\n\n## 5\\. What is actually lost, precisely\n\nIt would be easy to write that this makes ChatGPT traffic invisible. It does not, and the distinction is worth getting right.\n\nThe **Session source** dimension still says `chatgpt.com`. The traffic is **misfiled, not missing**. What breaks is everything that reads the channel rather than the source: the AI Assistant channel count, every channel-grouped report and comparison, and any attribution model built on the default channel group. Meanwhile the Organic Search number is inflated by clicks Google did not send.\n\nSo the hotel that did the most work to measure its listing carefully ends up with two wrong numbers instead of one missing number, and no indication that anything is off. You would only find it by opening the source/medium report and noticing that ChatGPT appears twice, on two different rows, for no obvious reason.\n\nThere may be a partial rescue. Google introduced a **Source Group** dimension in June 2026 with, in its words, _“built-in grouping for emerging traffic sources like ChatGPT (OpenAI) and Perplexity”_, populated retroactively. Being derived from the source, it ought to bucket these clicks correctly even with the medium hijacked. Google documents neither how it is derived nor how it interacts with manual UTMs, so I am flagging it as a thing to test rather than a thing to rely on.\n\n## 6\\. The fix takes one minute\n\nOpen your Google Business Profile, look at the website field, and read the query string. If it contains `utm_medium=organic`, that is the whole problem.\n\nThe instinct behind the tag was right: you wanted listing traffic separated from ordinary search traffic. The error is which field it went in. **Medium is the field GA4 uses to assign channels, and `organic` is a reserved word inside it.** A source-only tag gives you the same separation without touching the channel logic:\n\nHijacks the channel\n\n`?utm_source=google&utm_medium=organic`\n\nSeparates without hijacking\n\n`?utm_source=gbp`\n\nTwo warnings before you go and edit it. Any change to the Business Profile URL takes time to propagate into ChatGPT, since the widget reflects what Google holds rather than what you just typed. And I have seen community reports of UTMs being stripped from that field, and one of a listing suspension after adding them. Those are user-generated forum posts rather than anything Google has stated, so treat them as an unverified risk rather than guidance.\n\n## Methodology\n\n**The corpus.** ChatGPT responses to hotel prompts captured at scale and flattened to one row per map or place entity, retaining the `website_url` field verbatim so the query string survives. 230,863 entities. `utm_source` and `utm_medium` are extracted by regular expression; values are compared lower-cased, and URL-encoded variants such as `seo%20maps` and `seo+maps` are left distinct rather than merged, since they are separate strings as far as GA4 is concerned.\n\n**How the overwrite is established.** Not by watching ChatGPT rewrite a URL, which we cannot observe directly, but by finding domains that appear with an identical `utm_medium` under two different `utm_source` values, one of which is `chatgpt.com` and the other of which is the business’s own convention. A medium like `seo+maps` or `organic_search` is not plausibly ChatGPT’s invention, and it appears on the same domain under both sources.\n\n**The GA4 rules** are quoted from Google’s default channel group documentation as rendered in September 2026. The source-category file is the artifact linked from that page; its 819 rows were extracted and searched, and the 9 February 2023 date is the HTTP `Last-Modified` header on the file itself rather than a claim on the page.\n\n**Limits.** One vertical: these are hotel prompts, so the domain counts describe hotels rather than businesses in general. The corpus records what ChatGPT served rather than what visitors clicked, so this measures exposure and never traffic volume. Whether other assistants with place widgets rewrite `utm_source` the same way is untested. And the final step of the argument, that a manual medium suppresses Google’s automatic `ai-assistant` assignment, is composed from two documented facts rather than quoted from one.\n\n## Frequently asked questions\n\nPartly. In its map and place widget it links to a business using the website URL stored in that business’s Google Business Profile, including whatever query string is already there. It overwrites `utm_source` with `chatgpt.com` and leaves the rest, `utm_medium` included, untouched. Four Seasons appears with `utm_medium=organicsearch` under both `google` and `chatgpt.com`; Accor with `utm_medium=seo+maps` under both `google+maps` and `chatgpt.com`.\n\n## Related research\n\n[\n\nAI traffic is undercounted\n\nThe study this came out of: four instruments on one hotel, and the single `chatgpt.com / organic` row that started it.\n\n](/research/ai-traffic-undercounted-hotel-2026)[\n\nAI Mode stopped linking publishers\n\nThe other end of the same problem: Google’s own AI surface wrapping every citation so no publisher can be named at all.\n\n](/research/google-ai-mode-searchviewer-svid-2026)","author":{"@type":"Person","name":"Nicolas Sitter","url":"https://nicolassitter.com/about","sameAs":["https://www.linkedin.com/in/nicolassitternolleau/","https://github.com/Nicositter88","https://hotelrank.ai"]},"publisher":{"@type":"Person","name":"Nicolas Sitter","url":"https://nicolassitter.com"},"image":"https://nicolassitter.com/api/og/business-profile-utm-chatgpt-organic-2026","mainEntityOfPage":{"@type":"WebPage","@id":"https://nicolassitter.com/research/business-profile-utm-chatgpt-organic-2026"},"tags":["AI Search","Attribution","GA4","Google Business Profile","ChatGPT"],"sameAs":["https://hotelrank.ai/research/business-profile-utm-chatgpt-organic-2026"],"alternateFormat":{"html":"https://nicolassitter.com/research/business-profile-utm-chatgpt-organic-2026","json":"https://nicolassitter.com/api/post/business-profile-utm-chatgpt-organic-2026","rss":"https://nicolassitter.com/rss.xml"},"datasets":[{"name":"summary","contentUrl":"https://nicolassitter.com/data/business-profile-utm-chatgpt-organic-2026/summary.csv","encodingFormat":"text/csv"}]}