Free tools
Free AI search tools with no signup
Generate a robots.txt for AI crawlers, an llms.txt file and FAQ schema in a minute, then check any domain for AI crawler access. No account needed.
Free to use. Check the output before you publish it.
The tools
Pick the tool for the job
Each one solves a small, real problem we meet on almost every audit.
AI visibility, citation and traffic checker
Upload your Search Console export. See where an AI answer is likely, scan your pages and run a guided citation test across eight AI engines.
Open the toolAI crawler access checker
Enter any domain and see which AI crawlers its robots.txt allows or blocks, plus whether an llms.txt file exists.
Open the toolAI crawler robots.txt generator
Choose which AI search, user and training crawlers may fetch your pages, then copy a clean robots.txt with your sitemap line.
Open the toolllms.txt generator
Build a short Markdown guide to your site for AI tools to read. A proposal, not a ranking factor, and we explain the limits.
Open the toolFAQ schema generator
Turn your questions and answers into valid JSON LD that matches the text on your page, ready to paste.
Open the toolSchema markup generator
Build Organization, LocalBusiness and other JSON LD from your business facts, with notes on what to leave out.
Learn moreAI citation readiness checker
A 16 point self check across access, entity, content and evidence. See your weakest group in two minutes.
Learn moreGEO ROI calculator
Test what AI visibility could be worth with your own numbers and see the break even for the Pilot.
Learn moreWhy we built them
Small files that cause big problems
On almost every audit we find the same three issues. A robots.txt that blocks a crawler by accident. No clear guide to the site for AI tools. Structured data that disagrees with the visible page. All three are quick to fix when you know what to write.
The tools below remove the guesswork. They are simple on purpose. Each one produces text you can read, edit and publish yourself, and each page explains the decision behind every choice.
The three generators run in your browser. Your entries are not uploaded or stored by us. The AI visibility checker reads your CSV files in your browser. The access checker and the page scan send the address you type to our server so it can read that site's public robots.txt, and keeps the result for ten minutes. That also means we cannot recover what you typed, so copy your result before you close the tab.
Tool 1
AI crawler robots.txt generator
Decide what each AI crawler may do, then copy the file.
Use this when you want to appear in ChatGPT search, Perplexity or Claude, but you do not want your pages used to train models. The tool lists the main crawlers by purpose: search, user requests and training.
It creates one group per crawler, adds your sitemap line and keeps the syntax clean. The page also explains how to test the result and the mistakes that cost sites their AI visibility.
Use it when you launch a site, after a migration, or when a new crawler appears.
- Separates search, user and training bots
- Adds your sitemap line
- Explains how to test the file
- CriticalAI crawlers blocked in robots.txt
- WarningMissing canonical on 14 pages
- WarningSchema does not match visible text
- WarningSlow LCP on mobile templates
- NoticeSitemap lists redirected URLs
Tool 2
llms.txt generator
Write a clear Markdown guide to your site in minutes.
llms.txt is a proposed file that gives AI tools a short, readable summary of your site and links to your best pages. It is a proposal, not a standard, and it is not a confirmed ranking factor.
We include the tool because a good summary helps people and agents alike, and because it forces you to decide which pages matter. Publishing it is low cost. Expecting a lift from it is not wise.
Use it when you want a tidy guide for developers, agents and customers, and you accept that engines may ignore it.
- Name, summary and key pages
- Markdown output you can edit
- Honest about what it does and does not do
- Direct answerTwo sentences with the range
- What moves the priceScope, markets, competition
- Comparison tableRetainer vs project vs tools
- Proof and limitsDated facts, honest caveats
- FAQSix real questions
Tool 3
FAQ schema generator
Create FAQPage JSON LD that matches your visible text.
Paste your questions and answers, and the tool produces FAQPage markup you can add to the page. Google has phased out FAQ rich results, so do not build this for a snippet. Build it for clarity.
The rule that matters most is that the markup must match the text readers can see on the page. The tool reminds you of this and keeps the structure valid.
Use it when you have a real FAQ section on a page and want machines to read it cleanly.
- Valid FAQPage structure
- Copy ready JSON LD
- Clear on what Google does and does not show
{ "@type": "LocalBusiness", "name": "Your brand", "areaServed": "Dubai", "sameAs": [ "linkedin.com/..." ] }
- ValidMatches visible page text
- ValidSame name on profiles
- CheckOpening hours missing
Best order
How to use the five tools together
- 1
Fix access first
Generate your robots.txt. If a crawler cannot fetch your pages, nothing else matters.
- 2
Check the pages
Make sure the pages you want cited have a direct answer and clear facts.
- 3
Add the guide
Publish llms.txt if you want a tidy guide. Treat it as optional.
- 4
Mark up the FAQs
Add FAQ schema only where a visible FAQ exists on the page.
- 5
Test and track
Run the access checker on your domain, then record whether your brand is named in AI answers over time.
- 6
Check your visibility
Upload your Search Console export to the AI visibility checker and run the guided citation test.
Compare
Which tool for which problem
Match what you see on your site to the tool that helps.
| If this is your situation | Use this tool | What you get |
|---|---|---|
| You do not know whether AI crawlers can reach your site | AI crawler access checker | A per crawler view of what your robots.txt allows or blocks, and whether llms.txt exists |
| You want to change which AI bots may fetch your pages | Robots.txt generator | A clean robots.txt that separates search, user and training crawlers |
| You want to know whether your brand is named in AI answers | AI visibility checker | A guided citation test and a read of your Search Console export |
| You want a short guide to your site for AI tools | llms.txt generator | A Markdown file you can edit and publish |
| You have a real FAQ and want it marked up | FAQ schema generator | FAQPage JSON LD that matches your visible text |
The tools help with parts of the job. They do not replace testing your own buyer prompts.
- Access checkerNot sure if AI crawlers can reach you
- Robots.txt generatorChange which bots may fetch pages
- Visibility checkerIs your brand named in AI answers
- llms.txt generatorA short Markdown guide, optional
- FAQ schema generatorMark up a real FAQ
The problem
Signs that point to a specific tool
You are not named, and you have never checked robots.txt
Start with the access checker. A blocked crawler is the cheapest problem to find and often the quickest to fix.
You blocked a bot years ago and forgot why
Use the access checker to see what is blocked now, then the generator to write a version that matches your current choice.
Your site changed platform recently
After a migration, robots rules and sitemaps are often wrong. Run again the access checker the same day.
You have a FAQ but no markup
Use the FAQ generator, and confirm the markup matches what readers see on the page.
You think a file will fix everything
No file will. Use llms.txt for tidiness and treat it as optional. See llms.txt: do you need one.
Inside the Pilot
How the tools fit into the GEO Pilot
- 1
Week 1: the access checker and visibility test
We use the same idea in the baseline: check which crawlers can reach the site and test buyer prompts. The free versions let you see a first version yourself.
- 2
Week 2: robots rules, llms.txt and schema
We write and test the robots.txt, add llms.txt if it helps, and add structured data. The generators do the same kind of job at small scale. In the Pilot we apply them across your site and test them on a staging copy where possible.
- 3
Week 3: FAQ and answer ready pages
We write FAQs from the prompt set and mark them up to match the visible text. The FAQ generator shows the form of that markup.
- 4
Week 4: the retest
We run the same prompts again. The visibility checker is a lighter version of the same habit: ask, record, compare.
Do it yourself or hire us
When the free tools are enough
If your site is small, you have access to your own files, and the only issue is a robots.txt that blocks something by mistake, the tools may be all you need. Run the access checker, fix the file, test it, and check again in a few weeks.
The tools stop where judgement starts. They cannot tell you which ten pages matter most, rewrite a page so it answers a buyer question, or decide how your facts should read across sites. They also cannot test your prompts across five engines and compare before and after. That is the work of the GEO Pilot, a fixed $999 for 30 days, done for you.
A good habit is to run the tools first, whichever route you take. You will understand the problems better, and the Pilot starts from a better place.
A wrong robots.txt can block a whole site. Read the output, and test on a staging copy when you can.
Free tools may be enough
- Your site is small
- You can edit your own files
- The only issue is a robots.txt that blocks by mistake
The GEO Pilot, $999 for 30 days
- Choosing the ten pages that matter
- Rewriting pages to answer buyers
- Testing prompts across five engines
Limits
What each tool does not do
The access checker reads the public robots.txt of a domain. It does not test your firewall, your CDN rules or whether your pages render for a bot, so a site can pass the check and still block crawlers elsewhere. The Pilot's technical audit looks at those layers.
The robots.txt generator writes rules. It cannot know your business, so you decide which crawlers to allow. Allowing search crawlers while blocking training crawlers is a common choice, but it is a choice, and our guide on AI crawlers and robots.txt explains the trade offs.
The FAQ generator and the llms.txt generator produce text. Neither one improves the page it describes. A weak answer in valid markup is still a weak answer, and a tidy llms.txt will not make engines use it.
What the tools do and do not do
- ✓Reads a domain's public robots.txt
- ✓Shows whether an llms.txt file exists
- ✓Produces text you can read, edit and publish
- Tests your firewall or CDN rules
- Tests whether pages render for a bot
- Improves the page that markup describes
- Makes engines use llms.txt
Good habits
Using the tools safely
Read before you publish
The output is plain text. Read it line by line and make sure it matches what you want.
Keep a copy of the old file
Save your current robots.txt before you replace it, so you can go back quickly.
Recheck after changes
Run the access checker again after you publish, and again after any site update or migration.
FAQ
About the free tools
Are the tools really free?
Yes. They are free to use, with no account and no limit we enforce. They run in your browser. If you want help applying the results across a whole site, we offer that as a paid service, but you never need to buy anything to use the tools.
Do you store what I type?
No. The three generators run in your browser and do not send your entries to our servers. The access checker sends the domain you type to our server to read its robots.txt and caches the result for ten minutes. That also means we cannot recover them, so copy your result before you leave the page.
Will these tools get me into ChatGPT or Google AI answers?
They remove common blockers and clarify your content, which helps. They do not guarantee a mention or a citation. No tool can. Visibility depends on your content, your reputation and the engines themselves.
Should I check the output before publishing?
Always. Read the file, test it on a staging copy where you can, and make sure it matches your intent. A wrong robots.txt can block your whole site from search, so a few minutes of checking is worth it.
Which free tool should I use first?
Use the AI crawler access checker. It takes a minute and shows whether AI crawlers can reach your site. If a crawler is blocked by mistake, fix that before anything else.
Do I need all five tools?
No. Most sites need the access checker and, if a change is needed, the robots.txt generator. The others help in specific cases, such as a real FAQ section or a wish for a tidy llms.txt.
Do the tools replace the GEO Pilot?
No. They help with small, clear tasks. The Pilot covers the baseline across five engines, technical fixes, up to ten rewritten pages and a retest, done for you for a fixed $999 in 30 days.
How often should I run the access checker?
Run it after any change to robots.txt, hosting, security rules or platform, and now and then as a habit. Crawler rules change, and a small edit can block bots without anyone noticing.
Keep reading
Guides on this topic
AI Crawlers and robots.txt: What to Allow and What to Block
OpenAI, Perplexity and Anthropic each run separate bots for search, training and user requests. Here is which to allow, which to block and how to test it.
Read morellms.txt: Do You Actually Need One?
llms.txt is a proposal for a summary file that helps AI tools read your site. Here is what it is, what the evidence says, and when it is worth the ten minutes.
Read moreSchema Markup for AI Search: What Helps and What Is Hype
Google says AI Overviews need no special schema. So is structured data worth it? Here is what schema really does for AI search, and which types to use.
Read more- AI Crawler Robots.txt GeneratorGenerate a robots.txt that allows AI search crawlers and blocks training bots.
- llms.txt GeneratorBuild an llms.txt file in your browser.
- FAQ Schema GeneratorTurn your questions and answers into valid FAQPage JSON LD.
- AI Crawler Access CheckerCheck which AI crawlers your robots.txt allows or blocks, including OAI SearchBot, GPTBot, ClaudeBot and PerplexityBot.
- AI Visibility Checker
- GEO Pilot, $999We implement the work in 30 days.
Want us to check the whole site?
Send your site and five buyer questions. We test your crawler access and run the questions through five AI engines.
- Recorded baseline in five AI engines
- Competitors named
- Three first fixes, ranked