SEO & Speed Audit
Real Core Web Vitals from Google's API, plus live on-page checks against your actual HTML.
English is live now. The rest are being translated and published one at a time.
No language matches your search.
AI Search Readiness
A growing share of buyers research through ChatGPT, Perplexity and Gemini rather than a results page. This tool checks whether those systems are allowed to read your site — and whether what they find is structured enough to quote.
Fetching robots.txt, llms.txt and analysing your page…
AI visibility for
This tool fetches your robots.txt, checks for llms.txt and llms-full.txt, retrieves your homepage HTML, and inspects the actual JSON-LD structured data, heading hierarchy and metadata present in it. Every result reflects something genuinely found or genuinely absent — no score is inferred.
The guide behind this tool llms.txt: The Complete Implementation Guide for 2026 What llms.txt is, exactly how to write one, and what it does and does not do. A practical implementation guide with a working template and honest limitations. Read the guide · 7 min read →The technical prerequisites for being read and cited by ChatGPT, Perplexity, Claude and Gemini — the parts you control.
Whether GPTBot, ClaudeBot, PerplexityBot, Google-Extended and others are allowed by your robots.txt. If they are blocked, nothing else matters.
Whether the file exists, how large it is, and a preview of what it says.
Whether a connected Schema.org graph gives models unambiguous facts instead of inference.
How many words exist in the HTML before JavaScript runs. Many AI crawlers do not execute scripts.
Heading hierarchy, because models retrieve sections rather than pages.
Whether the file exists and declares a sitemap.
The order here is strict, because each item depends on the one above it.
Blocked crawlers make everything else irrelevant. If GPTBot cannot fetch your pages, no amount of structured data will get you cited. This is often an accident — a blanket rule inherited from an old template.
Content that only appears after JavaScript is the next blocker, and the one site owners never notice, because it looks perfect in a browser. Test it yourself: curl -s https://yoursite.com/ | grep "a sentence from your page". If that returns nothing, a crawler that does not run scripts sees an empty shell.
Missing structured data means a model has to infer who you are from prose. It will, and it will sometimes be wrong.
llms.txt is last for a reason. It is genuinely useful and takes an afternoon, but it summarises a site — so it is worth doing once the four items above are true, not before.
Be sceptical of any tool claiming to measure your "ranking in ChatGPT." There is no position, no stable ordering, and no public data to compute one from. What this tool measures is the set of prerequisites you actually control.
GPTBot, ClaudeBot, PerplexityBot, Google-Extended and others respect robots.txt. Many sites block them without realising, sometimes through a blanket rule inherited from an old configuration. If they cannot crawl you, you cannot be cited.
An emerging convention: a plain-text file at your root that describes your business, services and key facts in a clean, JavaScript-free format. It removes ambiguity for models that would otherwise have to infer everything from marketing copy. Adoption is still low, which makes it a cheap advantage.
A connected Schema.org graph — Organization, Service, Article, FAQ — gives models unambiguous facts about what you do, where you operate and what you offer. Isolated, disconnected blocks are far less useful than a properly linked graph.
Models retrieve passages, not pages. Content with clear headings and a direct answer near the start of each section is far more likely to be quoted than a long unbroken argument. Server-rendered HTML matters too: content that only appears after JavaScript runs is frequently missed.
Your company name, addresses and service descriptions should be identical everywhere they appear. Contradictions across your site and third-party directories degrade the model's confidence in what it knows about you.
A proposed convention — a Markdown file at your domain root that gives AI systems a clean, structured summary of your organisation, services and key pages without them having to parse marketing pages and JavaScript. It is not yet an official standard, but it is trivial to implement and costs nothing to have in place.
For most businesses selling a product or service, yes. Being cited in an AI answer is now a discovery channel. The main exception is publishers whose business model depends on people visiting to read the content itself — that is a genuine strategic trade-off worth thinking through.
No, and be sceptical of tools claiming to. It checks the technical prerequisites: whether crawlers are permitted, whether llms.txt exists, whether structured data is present and valid, and whether your content is extractable. Those are the things you control.
In order of impact: unblock AI crawlers in robots.txt, ensure your content is server-rendered, add a connected structured data graph, publish llms.txt, and restructure key pages so each section opens with a direct answer.
Real Core Web Vitals from Google's API, plus live on-page checks against your actual HTML.
See your page exactly as Google and every social platform will render it, from your live HTML.
Extract every JSON-LD block on a page, validate it, and see which rich-result types you qualify for.
One team. Three offices. Twenty-six languages. Send us the problem and you get a senior answer — not a sales script.
A written proposal within one business day, in your language.
Talk to a human
İstanbul, Düsseldorf and Dover — one of us is usually awake
Pick the channel that suits you. A person answers — no ticket queue, no bot.