Fix noindex in Initial HTML, Not Just the Rendered DOM, for Public Pages

A public page whose initial HTML contains a noindex robots tag should not rely on JavaScript to remove it later, since the earlier directive can still affect search engines. Developers are advised to correct the initial server response for pages meant to be indexed, then verify the rendered document and route states separately. Before changing anything, the public page and its intended indexing eligibility should be identified, and access protection for private routes should be kept intact. Google's documentation notes that a noindex tag may cause rendering to be skipped, so inspecting the raw response for the exact URL is the recommended first diagnostic step. The article illustrates this with a hypothetical product whose shared app shell applies noindex to public guides.