Grok
By SpaceXSI. No UTM value documented yet.
What works today
Grok Bot hands CAPTCHAs and human confirmation steps back to the person instead of bypassing them, according to its documentation.
As of 2026-10-31.
AI assistant: link status
Rows are tests, columns are surfaces. Select a cell to see each link location, the date, the method and the evidence. Reported means a third-party report we have not yet verified first-hand. See how we test.
Missing (2026-11-06)
- Inline citation in an answer: Missing · 2026-11-06 · Verified (manual) · Grok Bot 1.24.1 (iOS app) → Safari 27.3 / iPhone. Referer:
(none)document.referrer:(none)Landing URL:https://attribution.now/t/ref-01/spacexsi-grok/web/inline-citationClicked the "REF-01 test page" chip inside the answer sentence. Opened in Safari with Sec-Fetch-Site none. Data - Link or URL written in answer text: Missing · 2026-11-06 · Verified (manual) · Grok Bot 1.24.1 (iOS app) → Safari 27.3 / iPhone. Referer:
(none)document.referrer:(none)Landing URL:https://attribution.now/t/ref-01/spacexsi-grok/web/bare-urlAsked for the plain URL, but the answer showed it as a chip labelled "Bare URL test". Opened in Safari with Sec-Fetch-Site none. Data
n/a (2026-11-06)
- Inline citation in an answer: n/a · 2026-11-06 · Verified (manual) · Grok Bot 1.24.1 (iOS app) → Safari 27.3 / iPhone. No referrer is sent, so nothing can leak. Data
- Link or URL written in answer text: n/a · 2026-11-06 · Verified (manual) · Grok Bot 1.24.1 (iOS app) → Safari 27.3 / iPhone. No referrer is sent. Data
Missing (2026-11-06)
- Inline citation in an answer: Missing · 2026-11-06 · Verified (manual) · Grok Bot 1.24.1 (iOS app) → Safari 27.3 / iPhone. Landing URL:
https://attribution.now/t/ref-01/spacexsi-grok/web/inline-citationNo utm_* parameter. Data - Link or URL written in answer text: Missing · 2026-11-06 · Verified (manual) · Grok Bot 1.24.1 (iOS app) → Safari 27.3 / iPhone. Landing URL:
https://attribution.now/t/ref-01/spacexsi-grok/web/bare-urlNo utm_* parameter. Data
Works (2026-11-06)
- Inline citation in an answer: Works · 2026-11-06 · Verified (manual) · Grok Bot 1.24.1 (iOS app) → Safari 27.3 / iPhone. Landing URL:
https://attribution.now/t/mrg-01/spacexsi-grok/web/inline-citation?a=1&b=2?a=1&b=2 arrived intact (no tag is added). Data - Link or URL written in answer text: Untested.
Untested
- Inline citation in an answer, Link or URL written in answer text: Untested.
Works (2026-11-06)
- Inline citation in an answer: Works · 2026-11-06 · Verified (manual) · Grok Bot 1.24.1 (iOS app) → Safari 27.3 / iPhone. Landing URL:
https://attribution.now/t/mrg-03/spacexsi-grok/web/inline-citation?utm_source=newsletter&utm_medium=emailutm_source=newsletter kept (no tag is added). Data - Link or URL written in answer text: Untested.
Untested
- Inline citation in an answer, Link or URL written in answer text: Untested.
Lab-wide
Next improvements
No open improvements. Thank you.
Personal agent: Grok Bot
Each Bot works on a persistent cloud computer with a browser, a filesystem and a terminal. Launched August 2026, beta (source).
It browses your site in a browser of its own, so its visits run your pages and your analytics tag like a person's. See Detect personal agent traffic for how to label and report them.
Names itself
A name in the user agent. Easy to read, but anyone can copy it.
Missing (2026-11-06)
- Grok Bot: Missing · 2026-11-06 · Verified (manual). User agent:
Mozilla/5.0 (X11; Linux x86_64) … Chrome/156.0.0.0 Safari/537.36with Google ChromeSec-CH-UAbrands, from Cloudflare (AS13335). No agent token. Second run 2026-11-06: same result, and its terminal sentcurl/8.14.1. Data
Signs its requests
A Web Bot Auth signature a site can verify.
Missing (2026-11-06)
- Grok Bot: Missing · 2026-11-06 · Verified (manual). No
Signature-AgentorSignatureheader on the browser's or terminal's requests in either run. The agent card it read came through Exa (ExaUser/1.0), signed with Web Bot Auth ashttps://exauser.crawler.exa.ai. Data
Tags its visits
A utm_source on the first page, so the visit has a source.
How to recognize it today
Not documented, and in our run there was nothing to go on: the browser sent a plain Chrome on Linux user agent with normal client hints, from Cloudflare's network. It ran the page's JavaScript, so analytics tags count it as a desktop visitor. It read a JSON link through Exa's fetcher instead of its browser; those requests name and sign themselves as ExaUser. When a site blocks cloud computers, the person can route the Bot's traffic through their own computer, and those visits look like the person. Its terminal sends a plain curl user agent from the same network. The browser renders with SwiftShader, a software GPU, which suggests a server but is common to other cloud browsers and doesn't identify Grok. The iOS app fetched URLs in the person's message with a Grok%20Bot/… CFNetwork/… user agent, apparently from the person's phone, and showed them as chips with the page title. That's a link preview and not a Bot visit.
Last verified: 2026-11-06. Last checked: 2026-11-06.
Work on Grok and see something out of date? Request a review and we will update the entry.