Guide

robots.txt: what it blocks, and what it doesn't

robots.txt guides crawlers, not visitors. Here is what it blocks, what it doesn't, and why it does not protect your data.

Same URL, different link order depending on Instagram/TikTok/YouTube. Configure once. Korli applies the rest automatically.

  • Examples: TikTok visitor sees offer first, Instagram visitor sees proof first
  • Common mistakes: too many links, same order for everyone, no tracking
  • Setup: create page → set Smart Rules → measure clicks (30 seconds)

Back to the hub · Relevant docs

Proof demo: source switch → different order

Same URL, but a different rendering based on where the visitor comes from. Configure once. Korli applies the rest automatically.

Definition: an instruction file, not a wall

  • robots.txt is a text file at the root of the domain. It gives directives to crawlers visiting your site.
  • It does NOT prevent visits. A human visitor sees whatever they want.
  • Disallow means "don't crawl", not "doesn't exist". A blocked page stays reachable if someone knows the URL.

What it actually does on korli.fr

  • The file allows the whole site and blocks /dashboard, /admin, /api: areas that should not be in an index.
  • It explicitly allows GPTBot, ClaudeBot, PerplexityBot: those crawlers can read the site so it can be cited in AI answers.
  • It declares two sitemaps so Google discovers new pages faster.

What robots.txt does NOT do

  • It protects nothing. A sensitive file stays readable if you block crawlers but leave the URL public.
  • It does not deindex. To deindex a page you need noindex in its <head>, not robots.txt.
  • Blocking an already-indexed page makes it SLOWER to disappear: Google must recrawl to notice the block.

Concrete example

Example: why Korli lets AI crawlers in

  1. Your content can be cited by an AI assistant when someone asks about the topic.
  2. Blocking GPTBot prevents those citations: you become invisible in generated answers.
  3. Korli allows those crawlers explicitly while keeping /dashboard and /api blocked.
  4. Result: you are readable everywhere, but your dashboards are not indexed.

How it works (3 steps)

  1. Write the file at the root: https://korli.fr/robots.txt
  2. List directories to block (dashboard, admin, api) with Disallow.
  3. Declare sitemaps at the end of the file to speed up discovery.

Common mistakes

  • Blocking the whole site thinking you protect against copy-paste.
  • Putting noindex in robots.txt: that tag is not read by Google.
  • Blocking GPTBot out of habit and silently losing AI citations.

In the same category

Tip: read 2 pages in the same cluster, then refine your link order by source.

Read next

Tip: read 2 pages in the same cluster, then refine your link order by source.

FAQ

How do I check my robots.txt?

Open https://korli.fr/robots.txt directly in a browser to see the raw text. You can also use Google Search Console's robots testing tool to verify blocks.

Does blocking a URL in robots.txt remove it from Google?

No, and it is counter-intuitive. If the page was already indexed, blocking only prevents seeing the change. To deindex it, add noindex in the page's <head>.

Should I allow GPTBot and other AI crawlers?

If you want to be cited in ChatGPT, Perplexity or Claude answers, yes. Blocking GPTBot makes you invisible there. It is a choice: generative visibility vs full crawl control.

CTA

Configure your smart rules once. Korli applies the rest automatically.