The other way round

Keep AI out of your site.
Keep Google in.

We check which of the 14 AI crawlers that matter can read your site today, which ones are only asked to stay out, and whether Google and Bing still get in. Then you get a plan to close the door without touching your search traffic.

No sign-up, no card · Results in seconds · Google and Bing checked too

  • GooglebotGoogle Searchstays
  • BingbotBingstays
  • GPTBotOpenAIout
  • ClaudeBotAnthropicout
  • Google-ExtendedGeminiout
  • PerplexityBotPerplexityout
  • CCBotCommon Crawlout
  • BytespiderByteDanceout
Fig. 1 The same door, two kinds of visitors. Search engines keep coming in; AI crawlers are turned away. That is the whole plan.

What we check

  1. robots.txt, crawler by crawler

    The 14 AI crawlers that matter, from OpenAI's to Common Crawl's, read against your robots.txt the way they read it themselves.

  2. Whether your server really turns them away

    We knock as each crawler. A line in robots.txt is a request; a 403 from your server is a lock.

  3. Your rights reservation

    EU law lets you reserve your content from text and data mining in a machine-readable way, and AI companies have to respect it. We check whether you do.

  4. That Google and Bing still get in

    Most ways of blocking AI, done wrong, take you out of search too. We check that you haven't.

The plan, gentle on purpose

19 €$19, once: every step to close the door, ready to copy and in the order that matters. Nothing that costs you search traffic, and nothing that needs a developer unless you want the server lock too.

  • Your robots.txt block with the 14 AI crawlers, ready to paste
  • The EU rights reservation, with the tag and the file ready
  • A clause for your terms
  • How to lock the door on your server or CDN, Google untouched
  • What not to touch so you don't lose search traffic
  • A prompt so your AI applies it in your code
Check who gets in

What we won't ask you to do

  • Block Googlebot or Bingbot, or shut every bot out with a single line.
  • Add noindex, or hide your pages from search in any other way.
  • Remove your text from Google's results to keep it out of AI Overviews.
  • Hide your content behind JavaScript or a login to protect it.

What no one can promise you

What a model already learned stays
Blocking works from now on. Text collected before is already in models that exist today.
Some crawlers don't ask
The big companies respect robots.txt. Not every bot does, and OpenAI and Perplexity say the fetchers that act for a person may not. That is what the server lock is for.
Google's AI answers use Google's crawler
AI Overviews reads your site with the same Googlebot as search. There is no way to leave one without limiting the other, and we won't tell you there is.

Questions

  1. Will this take me out of Google?

    No. Everything in the plan names AI crawlers only. Google Search and Bing keep reading your site as before, and the check tells you if something already blocks them.

  2. Does it take my site out of ChatGPT?

    It stops OpenAI's crawlers from reading it from now on, which takes you out of ChatGPT search and future training. What a model already learned stays, and your text can still reach it through copies elsewhere.

  3. Why not just block every bot?

    Because search engines are bots too. A single “Disallow: /” for everyone closes the door on AI and on your visitors from Google at the same time.

  4. Is the check free?

    Yes, and it shows you exactly who gets in. What you pay for, once, is the plan: the files and lines ready to copy, the rights reservation, the server rule and a prompt for your AI.

Rather be read by AI? The other check is here