Google now recommends that platforms publishing pages for their users apply noindex by default to any page that exists to be shared rather than found. The instruction landed on 26 October in an update to a Search Central guide that used to be about comment spam, "Prevent User-Generated Spam on Your Site", and the guide now carries a section it did not have before.
It is headed "Only index content meant for Search". The advice runs: "If your service lets users create shareable pages, generated outputs, or interactive tools, consider whether that content is meant to be found through search engines or only accessed directly by people with a link." Where pages are "created for direct sharing, collaboration, or utility rather than public search discovery", Google asks the platform to "apply the noindex rule (using a robots meta tag or X-Robots-Tag HTTP response header) or block crawling in robots.txt by default."
Barry Schwartz reported the change at Search Engine Roundtable the same day. Google's changelog entry describes it as "guidance on blocking indexing of link-shared content", added to keep "user-created pages that aren't meant for Search out of the index and detect spam earlier."
The scope covers anything that publishes a page for someone else
The guide's opening paragraph no longer stops at comment forms. It now reads on "Hosting platforms and tools that let users publish shared pages, generated content, or web apps" — a description that takes in AI chat share links, app builders, document tools, and the menu pages a restaurant's software publishes for it.
Google named no products. Marie Haynes asked publicly whether the update signals manual actions aimed at AI tools and app-building platforms, and Lily Ray suggested the target may be services that generate indexable pages at volume. Both are reading a documentation change for intent, and Google has confirmed neither.
A hosted menu falls on both sides of the test
Google's test asks whether a page is meant to be found through a search engine or only reached by someone holding a link. A menu page is honestly both. It is a utility: the QR code on the table points at it, and whoever scans that code is already sitting down. It is also the page that stands the best chance of answering a search for a gluten-free lunch or a Sunday roast in a particular town, and usually the only place the food exists in a structured form a crawler or an assistant can read.
A platform that applies the new section at face value — sharing and utility, therefore noindex — loses the second of those without any outward sign. The page still loads and the QR code still works; the menu just stops being something a search engine keeps a record of.
The setting belongs to the provider
A noindex rule is served in the HTTP response or the head of the page, which puts it in the hands of whatever generates the page. It is not visible from a menu product's admin screen, and a robots.txt block sits at the root of a domain the restaurant often does not own.
Checking takes a minute. Fetch the live menu URL and read the response headers and the <head> for a robots directive; where the menu is served from the restaurant's own domain, URL inspection in Search Console gives the same answer with Google's reading attached. The useful question to put to a provider is narrower than whether they support SEO: does any page you generate carry noindex by default, and does a menu fall inside that default.
Verification follows the domain
The same update asks platforms to verify their sites in Search Console, watch the Page Indexing and Search performance reports for unexpected spikes, and set alerts for surges in newly published public pages. That advice is addressed to the platform because the platform holds the property.
Where a menu is served from the restaurant's own domain, those reports and any manual action notice reach the restaurant. Where it sits on a subdomain of the provider, they reach the provider, and the restaurant sees whatever gets passed on.
A noindex rule leaves no mark on the front of a site. What it takes away is the index entry the rest of it reads from: the rich result, the AI Overview, the assistant citing a page because Search had a copy rather than because someone handed it one.
