No accidental search-exclusion meta directives on public pages

The robots directives that actually remove pages from AI answers are the ordinary search ones. A stray noindex removes the page from the indexes AI products are built on — Google requires a page to be indexed and snippet-eligible for its AI features, OpenAI's docs say noindex is what keeps even a bare link out of ChatGPT, and Anthropic's docs say the tag tells its search partners not to send the page to Claude. nosnippet and max-snippet:0 are Google's documented levers for excluding content from AI Overviews and AI Mode, and Bing honors data-nosnippet for snippets and AI summaries. Vibe-coded apps frequently ship a noindex left over from a template or staging config on real marketing pages, which silently zeroes their AI-answer presence. The community noai/noimageai tags, by contrast, have no documented consumer among these vendors.

Remove noindex, nosnippet, max-snippet:0, and data-nosnippet from public content pages — check each layout's metadata.robots export and any X-Robots-Tag header set in server config. Keep them where they're intentional (admin, auth, user-generated content, alternate-format assets like markdown twins whose HTML canonical is indexed).

// Public content page metadata — index normally
export const metadata = {
  robots: { index: true, follow: true },
}

If the exclusion is intentional, understand the documented consequence: per Google and Bing, the content is excluded from AI Overviews/AI Mode and Copilot AI summaries; per OpenAI and Anthropic, a noindexed page won't be sent to ChatGPT or Claude by their search providers.