Advertisement
Content Moved? Use Search to Locate
Business team collaborating with laptops and documents in a meeting, showcasing teamwork and cooperation.

How Do You Keep Link-Shared Pages Out of Google Search?

To keep a WordPress page accessible to anyone with its link but out of Google Search, let Googlebot crawl the page and serve a noindex directive. If the content should be available only to approved people, require authentication instead. A robots.txt block is neither a reliable way to exclude a URL from Search nor a privacy control. Google’s guidance for user-created pages describes the choice between Search discovery and direct access by link.

Want expert help applying this? Tell the Splinternet Marketing app what you need and get a plan for your business.

Choose the right control for the job

These settings address different goals. Search exclusion means asking Google not to include a crawlable page in its index; noindex is the relevant directive. Crawl control means limiting which URLs Googlebot can fetch; that is what robots.txt is for. Access control means deciding who can see the content; use authentication when access must be restricted. A link that works for anyone who has it is still a public-access link, not a password.

Google advises services with shareable pages, generated outputs, or interactive tools to decide whether each kind of page is meant for Search discovery or direct access by link. For a page that should stay link-accessible but out of Search, a crawlable page with noindex fits the goal. Google’s updated guidance also discusses applying noindex or blocking crawling by default for certain direct-sharing, collaboration, or utility pages; the right choice depends on the intended behavior. If Googlebot cannot crawl a page, it cannot see a noindex directive in that page’s HTML or response headers, as explained in Google’s noindex documentation.

Do not use robots.txt as a substitute for either control. Google’s Introduction to robots.txt explains that a blocked URL can still appear in Search, sometimes with its URL and publicly available information. Blocking a URL can also prevent Google from seeing a noindex rule on that page. Robots.txt does not enforce access control; use password protection or another access-control mechanism for private content.

Set up a link-shared WordPress page

  1. Choose a representative URL. Use a real page created by the feature, not just the template or a preview. Confirm that the page is supposed to open for people with the link and should not be discovered through Google Search.
  2. Check that Googlebot can crawl it. Review the site’s robots.txt rules and any other crawl restrictions that apply to the URL. Do not block the page in robots.txt if you expect Google to read its noindex directive.
  3. Serve noindex on that page. The directive can appear in the page’s HTML, for example <meta name="robots" content="noindex">, or in an HTTP response header such as X-Robots-Tag: noindex. Configure the page-generating feature or your site implementation so the directive applies to the intended user-created pages, not accidentally to unrelated pages. Google documents both methods in its guide to blocking Search indexing with noindex.
  4. Check the delivered page. Load the link in a browser and confirm that it still works for someone who should have access. Then inspect the page’s HTML or response headers to confirm that noindex is present. The directive needs to be in the version Googlebot can access; seeing it in an editor or in a different page template is not enough.

Hypothetical example: shareable tool results

A WordPress tool creates a unique results page that a visitor can send to a colleague. The operator wants recipients with the link to see the result, but does not want the page found through Google. The operator configures the generated page to remain accessible to anyone with the link and include noindex, without blocking Googlebot from crawling it. The link remains usable; the directive asks Google not to include the page in Search. If the result contains information that should not be visible to anyone with the link, the operator should require authentication instead.

Verify what Google can see

  1. Use URL Inspection in Search Console. Inspect the representative URL and review its crawl information and the HTML Google received or rendered. If the inspection shows that Google cannot access the page, investigate the crawl restriction first. If the accessible HTML does not contain noindex, check the page output, response headers, or feature configuration. Google’s noindex guidance describes using URL Inspection to check the HTML Googlebot received.
  2. Check the Page Indexing report after Google recrawls. Google recommends the Page Indexing report for monitoring pages from which Googlebot extracted a noindex rule. The expected evidence is that Google can crawl the URL and sees the directive; the report can reflect the extracted signal after a recrawl. Google must recrawl the page to see a newly added directive, and the timing can vary.
  3. Watch for unexpected patterns. Google’s user-generated spam guidance recommends reviewing Search Console’s Page Indexing and Search performance reports for unexpected increases in indexed pages, impressions, or queries. Compare those signals with your own page-creation and indexing metrics to investigate anomalies. These reports are useful evidence, not proof that every affected URL or abuse incident has been found.

For WordPress operators who want help configuring and checking this workflow, Splinternet Marketing’s website maintenance service can support implementation and ongoing measurement. Brian Bateman’s managed service draws on 30 years of experience and the DOYJO process, with technology supporting data-driven improvements around the clock; the app connects readers to that service rather than replacing the work. The offer is $421 per month per business, month to month, with cancellation at any time.

Google Search Central dates an update to its user-generated spam documentation to October 26, 2026. The Documentation Updates page describes its scope as keeping user-created pages not meant for Search out of the index and detecting abuse earlier. That is a documentation update, not evidence of a new indexing rule or a change in Google’s underlying behavior. The cited guidance concerns Google Search; it does not establish how every other search engine or third-party crawler will handle the same directives.

Sources

Editorial note: AI assists with research, drafting and automated checks. Sources are linked so you can verify the guidance. Platform requirements can change; confirm the details that apply to your setup.