A helpful share button starts with a clear choice

Sharing a page is a product decision

A share button feels simple. Someone finishes a draft, copies a link, and sends it to a colleague. Behind that moment sits a useful question: who else should be able to find or open the page?

On October 26, Google updated its guidance for services that let people create shared pages, generated content, or interactive tools. It now explicitly asks builders to distinguish pages intended for public search from pages created for direct sharing or collaboration.

For pages meant only for sharing, Google recommends keeping them out of search by default. This is updated guidance for builders, rather than a new privacy setting that Google automatically adds to every app.

Read the announcement: Google Search Central: documentation update, October 26, 2026.

Finding a page and opening it are different things

A page can stay out of search results while still opening for someone who has its link. If its contents should be private, it needs proper access controls, such as a sign-in restricted to the right people.

One setting your builder may mention is noindex. It tells supporting search engines to leave a page out of their results. Google needs to be able to read that instruction. Blocking its visit with a separate robots.txt file can stop it seeing the instruction, and the address may still appear in search.

You do not need to edit those settings yourself to make a useful decision. Start by describing the experience you want: an invited colleague can open a draft, while an approved public guide can be found by anyone.

Sketch the sharing choices before building them

Take one example page from your planned app and draw a simple sharing panel. Use made-up content while you explore the idea.

1. Write who should be able to open the page.
2. Decide whether the page should appear in search results.
3. Show the current choice clearly beside the Share button.
4. Ask your builder to demonstrate both an allowed visitor and someone without access.

Make the choice easy to understand

This is a good exercise for a lesson or a project review because you can explain the intended result in ordinary words. Ask how access can be removed later and what happens to an old link.

A clear sharing flow helps people use a tool with confidence. Your knowledge of the work tells you which pages are ready for a wider audience and which belong with a particular team. Bring that distinction into the build from the start.