Grok's share button makes a public link, and xAI says plainly it can be indexed by a search engine. On Grok Business the same button does close to the opposite. Here's what the person on the other end receives, and the page where you revoke it.
Grok has a share button. What it produces is a public link — and xAI says so directly, in its own words, in the Consumer FAQ.
That single fact resolves most of the confusion around it, because "share" in ordinary speech means give this to a person, and here it means put this at an address anyone can reach. Those aren't the same act, and the gap between them is where people get caught.
xAI's Consumer FAQ describes two routes to the same result: on grok.com you click Share in the top right or the share icon below the conversation "to create and copy a public share link"; on the mobile apps you tap the share icon under the conversation to do the same.
Then it adds the sentence that matters:
Any share link you generate will be accessible to anyone you choose to share the link with. For example, if you share the link publicly on a social media platform, it may be subject to indexing by a search engine (e.g., Google) just like any other publicly shared content.
Read carefully, that's not a warning about a bug — it's an accurate description of what a public URL is. Publish it somewhere crawlers reach, and crawlers will reach it. The document is being straight with you.
What it means practically: the privacy of a Grok share link is a property of where you put it, not of the link itself. Sent in a DM to one person, it is effectively private because nothing points at it. Pasted into a public post, it is publishable content. The URL didn't change between those two cases; your handling did.
This is the part people are actually searching for, and it has a specific address.
Per the same FAQ: log into grok.com, go to grok.com/share-links, and click Remove next to the link you no longer want shared.
Two things worth saying about that page beyond the mechanics:
A separate point that's easy to conflate: revoking a link and de-indexing a URL are different processes on different timelines. Removing the share stops the link serving. Anything a crawler already picked up, anyone who archived it, anyone who reposted it — those live outside the button. The same distinction bites on other platforms, and what unsharing actually undoes walks through the mechanism in more depth.
Here's the part that produces the "why won't my link open?" question.
xAI's Grok Business user guide says sharing in a team workspace is deliberately restricted:
So the same word, the same-looking control, and two opposite outcomes depending on which workspace you were in when you pressed it. Neither behaviour is wrong. A team workspace should keep its conversations inside the team; a consumer product should let you post a chat publicly if that's what you want. The friction is that nothing about the act of clicking Share tells you which of the two you just did.
The two ways that lands on people:
If you take one operational habit from this: check which workspace you're in before you press Share, not after. It's the cheaper end of the problem.
Built something in Grok worth sending on its own? Export it as a self-contained file and put it on a link whose access rules you set — unguessable by default, password optional, expiry when the job has an end date.
Everything above is about controlling the link. There's a prior question that often makes the link question moot.
A share link hands someone the conversation — the whole thread as it stood when you shared, including whatever you pasted in along the way while you were working. If what you actually want to show is the thing at the end of the thread, sharing the thread is a strange way to deliver it. Your reader gets the workings; they wanted the result. And you've now published the workings.
For a finished artefact — a page Grok built, a tool, a report, a summary — the cleaner move is to lift it out and send that, on a link whose access rules you chose deliberately rather than inherited from a button. The same reasoning applies across every AI tool with a share feature, which is why links from AI tools so often fail the person you sent them to and why taking the artefact out of the chat tends to be the step that fixes it.
None of this is an argument against Grok's share button. For its actual job — you found something worth showing the internet, you want people to be able to read it — a public link is exactly the right shape, and the FAQ tells you what it is without dressing it up.
The mismatch only shows up when the same button is asked to do delivery: a named recipient, a specific window, work that shouldn't outlive the conversation. Then "public URL until I remember to remove it" is the wrong shape, and pressing it carefully doesn't make it the right one.
Know which of the two you're doing before you press it. And if you've been pressing it for a while without thinking about which, open grok.com/share-links once and read the list.
Sharing a chat creates a snapshot anyone with the link can open. Unsharing disables that link. Neither of those is the same as 'not indexable', and the difference caught a lot of careful people in July 2026. Here's the mechanism, where to check your own shares, and when you need noindex to be a property of the link itself.
Most expiry windows get set by guess — 7 days because that's the default, 'never' because that's reversible. The actual fit comes from matching the window to what the content references.
Two architectures live under the same 'password protected' label. One is a real gate; the other is a UI prompt the receiver can click past in 30 seconds with DevTools open.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.