An address tester that explains itself
It does not just say blocked. It names the rule that matched and the group it came from, so you can see why.
Technical SEO
Start from a preset or paste the file you have. See what each of 14 crawlers, including the AI ones, can reach, which rule decides it, and what to fix before you publish.
A robots.txt file sits at the root of your site and tells crawlers which paths they may request. It is how you keep a staging site, a cart or an admin area out of search, and how you decide which AI crawlers may read your content.
It is also easy to get wrong. One stray line can block your whole site, a rule for one bot can be ignored because another group matches first, and the file only works at the root of the domain. This product builds the file from choices, then checks it the way crawlers read it, so you see the result before it goes live.
4 steps, and you stay in control of the result.
Allow everything, block some folders, a staging site that blocks everything, or write it yourself.
Allow or block each AI crawler separately, with a plain note on what each one does.
Enter a path and see, for every crawler, whether it is allowed and which rule decided it.
Read the warnings, such as blocking your whole site or your scripts, then copy or download the file and upload it to your site's root.
It does not just say blocked. It names the rule that matched and the group it came from, so you can see why.
Separate switches for search crawlers and AI training crawlers, with a note that blocking an AI search crawler can stop it citing you.
Flags a file that blocks the whole site, blocks styles or scripts, has no sitemap line, or contradicts itself.
Signed in, fetch the file your site serves now, check it and see a line-by-line comparison with the new one.
Block-folders asks which folders to block. It does not assume your CMS or hide a login path you may need.
The file is ready to paste. A reminder says it must be at the root, for example example.com/robots.txt.
You give it: The preset "Block some folders" with /admin/ and /cart/ blocked, GPTBot blocked and a sitemap address.
User-agent: *
Disallow: /admin/
Disallow: /cart/
User-agent: GPTBot
Disallow: /
Sitemap: https://example.com/sitemap.xmlAn illustration. The file you build uses your own folders and sitemap address.
The syntax is short, which is why mistakes get through. The rules for which line wins are the part people forget.
| Task | By hand | With this product |
|---|---|---|
| Writing the file | Remember the syntax and the paths | Choose a preset and your folders |
| AI crawlers | Look up each bot's name and what it does | A switch per crawler, with a plain description |
| Knowing what is blocked | Reason through groups and wildcards in your head | A table of allowed or blocked for 14 crawlers with the matching rule |
| Catching a disaster | Find out when your pages leave search | A warning before you publish a file that blocks the whole site |
| Updating an existing file | Edit and hope | Import it, check it and compare before and after |
A file that blocks everything is correct for staging and a disaster in production. It happens at every launch.
If a crawler cannot load your CSS and scripts it cannot render the page properly, and rankings can suffer.
A broad Disallow and a narrow Allow interact by specificity, not by order. Reading it by eye is where people go wrong.
Blocking the wrong AI crawler removes you from AI search answers; allowing the wrong one lets content be used for training.
Build a file or paste yours and see what every crawler can reach.
So you know what to expect before you start.
These come from Google's published specification and each operator's crawler documentation.
The checks follow these official documents. Read them, and check your result with the ones marked Test.
With a free account
Signed in, you can fetch the robots.txt your site serves right now, check it and compare it with the new one. The site you pick is remembered for the next product.
A plain text file at the root of your site that tells crawlers which paths they may request. It controls crawling. It is not a way to hide private content.
Add a group for each AI crawler with Disallow: /. The product has a switch for each one. Note that blocking an AI search crawler, such as OAI-SearchBot, can stop that service citing your pages.
Not by itself. A blocked address can still be indexed if other pages link to it. To keep a page out of search, allow crawling and add a noindex directive.
At the root of the host, for example example.com/robots.txt. Each subdomain needs its own file.
Crawlers treat a missing file as permission to crawl everything. A server error is treated more cautiously, so keep the file available.
The most specific one, which is the longest matching path. If an Allow and a Disallow match equally, Allow wins.
Yes. Building, checking and testing use no credits and need no account. Importing your live file needs a free account.
Page checked against the product on 4 October 2026.
Skymoon SEO Suite is made and maintained by Skymoon Infotech, a digital growth agency founded in 2023 in Ahmedabad. Each product started as a task the team repeated on client work, and is used there before it is released here.
Found a problem or have a question? Tell us. How we handle what you upload is in the privacy policy, and About says more about who we are.