Does a 'noai' meta tag stop AI from using my content?

A noai meta tag does not stop AI from using your content, because no major engine says it reads one. OpenAI's crawler page, Google's common crawlers page, Anthropic's crawler help article, Perplexity's crawler docs and Meta's crawler docs each list the controls they honor. As of October 2026, none of them lists noai or noimageai.

That matters because an undocumented tag is a request nobody has agreed to receive. A crawler may ignore it with no notice, and you have no way to verify compliance from outside.

The controls that are documented fall into three groups:

• robots.txt rules per bot, which govern whether a specific crawler may fetch your pages.
• Google-Extended, a robots.txt token that governs Gemini training and grounding.
• Robots meta directives: noindex, nosnippet, max-snippet and data-nosnippet, which govern whether content appears in Google and Bing answers.

If your goal is to keep content out of AI entirely, read whether you can completely stop AI from using your content before you start. The honest answer has limits.

robots.txt is the main documented control, and it works bot by bot. OpenAI states that "each setting is independent of the others." Blocking one bot does nothing to another.

A training-only block looks like this:

User-agent: GPTBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: OAI-SearchBot
Allow: /

The most common mistake is a blanket AI block that also removes search eligibility. Decide per bot whether you want to stop training, stop search, or both. Meta runs several crawlers with different jobs, covered in Meta's crawler user agents.

Google and Bing document four on-page controls that keep content out of AI answers on their surfaces. They live in the robots meta tag or as an HTML attribute.

• noindex removes the page from the index. Google requires a page to be indexed and snippet-eligible to appear as a supporting link in AI Overviews or AI Mode. See noindex.
• nosnippet blocks snippets for the whole page, which also removes it from AI feature display. See nosnippet.
• max-snippet:0 has the same effect as nosnippet.
• data-nosnippet works on a section. Bing says such content "is still indexed normally, but it will be excluded from snippets and AI summaries" (October 2025).

<meta name="robots" content="nosnippet">

These suppress display. They do not add anything, and they cost you the matching visibility in classic search snippets too. The details for Google are in whether noindex or nosnippet stops AI Overviews. One practical trap: directives injected by JavaScript may never be seen by crawlers that don't render, so check whether AI crawlers see robots meta tags added by JavaScript.

Documented controls are stronger than noai, but none is airtight.

• User-triggered fetchers. When a person asks an assistant to open your page, a different agent fetches it. OpenAI says robots.txt rules "may not apply" to ChatGPT-User. Perplexity says Perplexity-User "generally ignores robots.txt rules." Meta documents that Meta-ExternalFetcher may bypass it.
• No AI Overviews token. There is no robots.txt token that blocks Google AI Overviews or AI Mode alone. Googlebot rules and the snippet directives are the control, and Google's Search Console opt-out is still reaching only some site owners as of October 2026.
• Past training. Blocking GPTBot today does not remove content from models already trained. Nothing a publisher does reaches those answers.
• Your CDN may decide for you. From 15 September 2026, Cloudflare blocks Training and Agent crawlers by default on ad-displaying pages for new domains and existing free-tier customers. Your access can change without you editing a file.

Compliance with robots.txt is also self-reported by each operator. Nobody outside can audit it at scale.

Start from what you actually want, then use the matching documented control.

1. Remove any noai or noimageai tag from your plan as a protection. Nothing documented relies on it.
2. Write per-bot robots.txt rules. Block training bots (GPTBot, ClaudeBot, Google-Extended) if you object to training. Keep search bots (OAI-SearchBot, Claude-SearchBot, PerplexityBot) allowed if you want to appear in AI answers.
3. Use snippet directives for specific content. Apply data-nosnippet to sections you never want quoted, and nosnippet or noindex to whole pages.
4. Put directives in the server HTML, not in client-side JavaScript.
5. Verify the result. Fetch your robots.txt and parse it per agent. The robots.txt Checker for AI Crawlers shows which bots each rule allows or blocks.

Accept the residual: user-triggered fetchers and already-trained models sit outside your control.

Does a noimageai tag protect my images from AI training? Not reliably. Like noai, noimageai does not appear in the crawler documentation from OpenAI, Google, Anthropic, Perplexity or Meta. If you want to keep images out of training, use robots.txt rules for the training bots, such as GPTBot, ClaudeBot and Google-Extended. That covers future crawling by those bots only. It does not reach user-triggered fetchers or models already trained.

If I block GPTBot, will I disappear from ChatGPT search? No. GPTBot governs training only. ChatGPT search uses OAI-SearchBot, and OpenAI states each setting is independent. You can disallow GPTBot to opt out of training while allowing OAI-SearchBot to stay eligible for ChatGPT search answers. Blocking OAI-SearchBot is what removes you from search answers, though navigational links can still appear.

Does blocking Google-Extended hurt my Google rankings? Google says Google-Extended does not impact a site's inclusion in Google Search and is not used as a ranking signal. It controls whether content is used for Gemini Apps and Vertex AI training and grounding. It does not keep you out of AI Overviews or AI Mode. For those surfaces, the controls are Googlebot rules and the snippet directives.

Is there any harm in leaving a noai tag on my pages? The operator documentation says nothing about noai at all, so there is no documented effect in either direction. The real risk is false confidence. If you believe the tag protects you, you may skip the robots.txt rules and snippet directives that engines do document. Treat the tag as inert and set up the documented controls instead.

Can I stop AI from quoting one part of a page but not the rest? Yes, on Google and Bing. Mark the section with the data-nosnippet attribute. Bing says that content is still indexed and available for ranking, but excluded from snippets and AI summaries. It is the only documented sub-page control. Apply it in the server-rendered HTML, and check it hasn't been inherited by template sections you want shown.