Are Claude Artifacts Indexed by Google?

Treat a publicly published Claude artifact as content that could become discoverable through Google; publishing does not guarantee indexing. A newer shared artifact can have different sign-in and audience requirements, so the word “shared” alone does not tell you whether its contents are public.

Check access before you send the link, especially for client work or internal plans. Tools like fenbs keep the team’s approved sharing rules and publication decisions available to its connected assistants, so a later session knows what a person actually authorized.

Which kind of Claude artifact did you share?

Start with the control shown on your artifact. Anthropic distinguishes newer artifacts with a Share menu from legacy artifacts made in a chat with a Publish or Share & copy link control. Its current artifact sharing guide↗ (opens in a new tab) says newer shared artifacts require a Claude account, while a legacy artifact published from chat can be opened without one.

That distinction matters more than the appearance of the page. A polished interactive demo can still be behind sign-in, while a modest published document can be available without authentication. Do not apply a statement about one kind of artifact to every link your colleagues have created.

For a concrete review, write down the artifact type, the account or organization that owns it, and the audience selected in its menu. Use a harmless sample to check what a recipient sees. Our Claude artifact examples show the variety of outputs; that variety does not establish their privacy settings.

If you are deciding which Claude feature holds the work, see Projects, skills, and artifacts. The choice of feature and the decision to make its output public deserve separate checks.

Does having a link mean Google can index the content?

No. Link access, automated access, and inclusion in search results are separate questions. A person may be able to open a URL after signing in even when a search crawler, the software that fetches pages for a search engine, cannot read the same content.

Google explains that password protection and noindex serve different purposes↗ (opens in a new tab). Authentication restricts who can read a page. A noindex instruction tells Google to leave a page out of results, while people with its address may still visit it.

The practical conclusion is to avoid treating an unlisted address as a confidentiality control. This is a risk assessment, not a claim that Google indexes every published artifact. The official sharing instructions do not establish whether your particular URL is indexed, and a failed search does not prove the link will remain undiscoverable.

How can you check a particular artifact safely?

Check the artifact itself before searching for it. A search result is evidence of discoverability, but the absence of a result is weak evidence about access. Your goal is to understand the intended audience and remove unintended access, rather than wait for a search engine to reveal a mistake.

1. Read the current sharing menu and note every audience or invitation that grants access. Check the account that owns the artifact.
2. Open a harmless test artifact in a signed-out browser session. Then test with the kind of recipient account you actually intend to use.
3. Inspect the content recipients can reach, including downloads and any visible stored information. Review more than the opening screen.
4. For a public artifact, search its exact URL and a distinctive, non-sensitive phrase. Avoid entering confidential passages into a search query.
5. Record the approved audience and who checked it. Repeat the check after changing the artifact or its sharing settings.

If your real question is taking the artifact somewhere else, the artifact export guide covers that separate workflow. Exporting and publishing need separate decisions because a safe working copy is not automatically a safe public copy.

What should you do if sensitive content was shared?

First stop the unintended access using the controls for that artifact type. Then follow your organization’s incident process. Preserve the information your reviewer needs, such as the URL, the owner, the exposure you observed, and the time you changed access, without spreading the sensitive content into more chats.

For a legacy published chat artifact, Anthropic documents an Unpublish control and warns that it has consequences for republishing and stored data. For organization settings, consult the artifacts admin guide↗ (opens in a new tab): disabling artifact creation or sharing broadly is different from revoking existing outside access. Ask the owner to check the specific link.

If Google still shows content that has been removed or substantially changed, its Refresh Outdated Content tool↗ (opens in a new tab) may apply. Google says this updates a search result; it does not delete the source page. Search cleanup also cannot recall a copy someone already saved, so assess the original disclosure separately.

What public-sharing rule should your team record?

Write a rule that names the permitted material, the approver, and the audience. “Share carefully” gives the next person little help. “Only approved demonstration data may appear in publicly published artifacts; the project owner approves the exact version before publication” gives both a colleague and an assistant a usable boundary.

Say a design studio wants to show a scheduling prototype to a prospective client. Its public version can use invented names and dates. The private working version may contain real schedules. Keeping those versions distinct prevents someone from assuming that approval for the demo also approved the underlying source material.

In fenbs, record the person’s choice in Decisions and rules and keep the approved public URL in Links and listings. The shared work workflow lets the next connected assistant read the decision before preparing another revision. The artifact’s actual access settings still need to be enforced in Claude.

How to do this with fenbs

1. Create a free account, then add the project whose artifacts you need to review. A personal account is free, with no credit card.
2. Write the human-approved sharing rule in Decisions and rules. Include what may be published, who approves it, and which project it covers.
3. Add a task to inspect the actual artifact and its recipient access. Record what was checked and any unanswered question before marking the task complete.
4. Save approved public references in Links and listings, with their status and relevant dates. Keep sensitive incident details in your organization’s approved system.
5. Connect a supported assistant through Integrations and ask it to read the project’s rules before continuing the work.

fenbs does not control Claude sharing settings or remove Google results. It is not the right fit when you need website hosting controls or an incident-response platform. Use it for the decisions and follow-up work around those systems, and use the AI governance hub to review related approval questions.