FREE TOOLS

Robots.txt generator

The file most sites need: one rule for every crawler, the folders to keep out, and where your sitemap is. Then, if you want, decide on twenty AI crawlers one at a time — and check what your current file actually permits.

Runs entirely in your browser. Nothing is uploaded, nothing is stored.

1 · Rules for every crawler

For most sites this is the whole file: a default, the paths to keep out, and your sitemap. All of it goes into one User-agent: * group that every crawler reads.

Default for all crawlers

Crawlers may read every page except the paths you list below.

One per line, starting with /. A trailing slash covers the whole folder; * matches anything and $ marks the end. A missing slash or a full URL is fixed for you.

Adds /wp-admin/ and keeps /wp-admin/admin-ajax.php open — the same two rules WordPress serves itself when there is no file.

Pages inside a blocked path that should stay open. The longer rule wins, so Allow: /wp-admin/admin-ajax.php beats Disallow: /wp-admin/.

Crawl-delay

Seconds between requests. Google ignores this line — its documentation lists crawl-delay as unsupported — while Bing reads it. Leave it off unless a crawler is straining your server.

One per line, full URL with https://. WordPress's built-in sitemap is /wp-sitemap.xml; Yoast and Rank Math use /sitemap_index.xml. A blog on a separate system needs its sitemap listed too.

2 · AI crawlers (optional)

Without a group of their own, AI crawlers follow the rules above like every other crawler. Name them here only to treat some differently. There is no answer that fits every site — only what each crawler does, and whether you want that.

Off — AI crawlers follow the rules above. Pick a preset or change any row to turn it on.

Blocks the training crawlers, keeps the ones that can cite you. · Also removes you from AI answers that would have linked back.

Everything starts allowed because that is what hitmind.ai's own robots.txt says — our choice, not a recommendation for your site. Change any row.

Answer engines that cite you

These read a page to answer a question and link back to it. Blocking one trades away the citation, which is the part that sends people to your site.

Training crawlers

These collect pages to build or fine-tune a model. No promise of a click or a citation in return. This is where most sites actually want to make a choice rather than default into one.

Neither

Ad safety checks, social card previews, R&D fetches. They neither train on your pages nor cite them, so blocking one costs little and gains little.

3 · Your file

Replace the whole of robots.txt with this, or merge the groups into what you already have.

One group for every crawler
# robots.txt — generated by https://hitmind.ai/tools/robots-txt-generator

# All crawlers
User-agent: *
Allow: /

Where it goes — The root of the domain, always: https://example.com/robots.txt. Not a subfolder, not a subdomain you also own — each hostname reads its own file.

4 · Check what you have now

Paste your current robots.txt. Every rule is applied the way a crawler applies it — Google and Bing first, then each AI crawler.

Across the top 10,000 domains, 29.8% of the files that block paths for everyone and name AI crawlers have at least one gap of this kind. Read the study →

The homepage by default. Try a folder you meant to block, such as /wp-admin/.

This reads rules, not enforcement. robots.txt is a request; a crawler that ignores it is stopped at the server or CDN, not here.

Paste a file above to see what it permits.

HOW IT WORKS

Six rules that decide everything

robots.txt looks like a list read top to bottom. It is not.

A crawler reads one group only

It finds the group matching its own name and uses that. If there isn't one, it uses User-agent: *. It never combines the two — so a path blocked only under * is open to every crawler you named elsewhere.

The longest match wins, not the first

Disallow: /a/ plus Allow: /a/b/ means /a/b/c is allowed: the longer rule wins regardless of order. When two rules are the same length, Allow wins.

An empty Disallow blocks nothing

Disallow: with nothing after it is the opposite of Disallow: / — it permits everything. Both appear in real files, usually by accident.

It is a request, not a lock

Well-behaved crawlers obey it. The rest read it and continue. Anything you genuinely need kept out belongs behind auth or a server rule, not in this file.

Blocking the crawl is not blocking the index

A disallowed URL can still show up in Google: its documentation says Google 'may still index the URL and show it in search results without a snippet.' To keep a page out of search, let it be crawled and mark it noindex.

Sitemap lines belong to no group

Sitemap: applies to every crawler wherever it sits in the file, and must be a full URL, protocol and host included. It is the one line not scoped to a User-agent.

QUESTIONS

Common questions

How do I create a robots.txt file?
Choose the default, list the paths to keep out, add your sitemap, then download the file. Upload it to the root of your domain so it opens at https://your-site.com/robots.txt — a plain text file named exactly robots.txt. Paste it into the checker on this page to see what it permits.
Where is the robots.txt file located?
At the root of the host, always: https://example.com/robots.txt. Crawlers never look for it in a subfolder, and Google's documentation says its rules apply only to the host, protocol and port it is served from — www.example.com and shop.example.com each need their own.
What is the difference between a sitemap and robots.txt?
robots.txt says what crawlers should not fetch; a sitemap lists the pages you want found. The Sitemap: line in robots.txt is where the two meet — it tells every crawler where your sitemap is. A page listed in the sitemap but blocked in robots.txt sends both signals at once; the orphan page checker flags that conflict.
Does blocking a page in robots.txt keep it out of Google?
Not reliably. Google can't read a blocked page, but its documentation says it 'may still index the URL and show it in search results without a snippet.' To keep a page out of results, allow crawling and add a noindex tag — a crawler that can't fetch the page never sees the tag.
Is robots.txt still used?
Yes. It became an internet standard in 2022 (RFC 9309), and the major search engines all read it. AI crawlers made it more relevant, not less: the vendors listed on this page publish their own robots.txt names so sites can decide about them separately. Two old lines do nothing at Google: crawl-delay was never supported, and noindex inside robots.txt stopped counting in 2019.
Does WordPress already have a robots.txt?
Yes, a virtual one. With no robots.txt file on the server, WordPress answers that URL itself: User-agent: *, Disallow: /wp-admin/ and Allow: /wp-admin/admin-ajax.php — plus, since version 5.5, a Sitemap line for its built-in sitemap when the site is public. A real robots.txt in the site root is served instead, and SEO plugins can rewrite it, so open the live URL after any change.
Will blocking AI crawlers hurt my Google ranking?
Google-Extended is separate from Googlebot. Google's documentation states Google-Extended 'does not impact a site's inclusion in Google Search nor is it used as a ranking signal.' Blocking Googlebot itself is a different matter — that removes you from Search entirely. Applebot-Extended works the same way: Apple states pages that disallow it 'can still be included in search results.'
Should I just block everything with 'bot' or 'GPT' in the name?
That is the template circulating online, and it is a regex standing in for a decision. It blocks the answer engines that link back alongside the training crawlers that don't — one of those costs you referral traffic, the other costs you nothing. The two are worth separating.
Some of these say they ignore robots.txt. Why write a rule at all?
Perplexity's documentation says Perplexity-User 'generally ignores robots.txt rules' because a person asked for the page. The line is still worth writing: it records your position, and it is what you point at if you later escalate. But it will not stop the fetch — only a server or CDN rule does that.
Does the order of the groups matter?
No. Crawlers select by name, not by position. What matters is that each group is complete on its own, because none of them inherit from another.
I have a blog on a different platform. One file or two?
One file per hostname. example.com/robots.txt covers example.com only — a blog at blog.example.com needs its own. A blog in a subfolder, example.com/blog/, is covered by the main file.
Where does the AI crawler list come from?
Each crawler links to its vendor's own documentation. One entry — Bytespider — has no reachable documentation, so it is marked as unverified rather than assumed compliant. We would rather show the gap than fill it with a guess.
NEXT

Related

THE REST OF THE FILE

robots.txt is one of four files we read

The free audit checks robots.txt, your sitemap, llms.txt and the homepage, scores five dimensions, and ranks what to fix first. No account, no card.

Run free audit

5 dimensions · no signup · ~60 seconds