AI Readiness ·
Free · No signup · No personal data
Enter a domain. Eight public requests become a readiness score: the systems behind your
site, the AI assistants your robots.txt lets in, and the free next step that fits.
Try
No crawl, no port scan, nothing behind a login.
Reading the public footprint of
AI Readiness ·
Seven components, published rather than hidden. Change one and rerun the check to watch it move.
AI crawler policy, read from your robots.txt
Illustrative time a first AI workflow could return to your team.
Matched against the resources your home page loads, your response headers, your cookies, and your Content-Security-Policy.
Strengths, gaps, and the duty of care that comes with them.
Austin AI Hub programs, ranked by fit to what we found. All free, all open to everyone.
Tailored to the kind of work you do.
How people move through the Hub. Most organizations start at the top left.
Come to a free workshop
No coding required. No pitch, because there is nothing to sell.
The systems behind your site
Donation platforms, CRMs, learning systems, schedulers, patient portals. Named, grouped, and scored for confidence.
Whether AI can cite you
Seventeen AI crawlers, split into the ones that cite you and the ones that only train on you. Most robots.txt files confuse the two.
A free next step that fits
Austin AI Hub programs ranked against what we found, each with the evidence that put it there. Everything is free.
AI readiness measures whether an organization can put an AI tool to work on its real information. It covers where records live, who may read them, whether anyone counts results, and whether machines can parse your public pages. The score predicts how much groundwork a first AI project needs. It predicts nothing about revenue.
Eight requests, all public. No crawl, no port scan, no intrusive probe, and nothing behind a login.
Your home page, once. Your robots.txt and llms.txt, if they
exist. Five DNS records. That is the whole list: we never follow a link, so the findings
are a floor, not an inventory.
586 hand-written rules plus 3,460 imported from the open-source Wappalyzer dataset. They match the URLs your page loads, your headers, your cookies, and your Content-Security-Policy. They never match your prose: a page that names a vendor as a customer does not run that vendor.
Ten search crawlers, like OAI-SearchBot and PerplexityBot,
decide whether an assistant can cite you. Seven training crawlers, like
CCBot, only feed the next model. Blocking the first costs you citations.
Blocking the second costs you nothing.
Legibility 18, foundations 18, system of record 15, security 15, measurement 12, AI experience 12, connectedness 10, with diminishing returns. Scores clamp between 12 and 96: nothing visible from outside justifies either extreme.
Sites behind bot protection answer with a 403, and the dashboard says so rather than presenting a thin read as a confident one. A failed lookup is marked unread, never scored against you. Hour estimates are conversation starters, not forecasts.
No. We fetch your home page once. We do not crawl, we do not follow links, and we never see anything behind a login. We also read your robots.txt and llms.txt if you publish them, and we look up five public DNS records. A system that never appears on your home page will not appear in the results, so treat the findings as a floor rather than an inventory.
From your home page, your robots.txt, your llms.txt and five DNS records, it infers what kind of organization you are, names the systems visible from outside, reports which AI crawlers your robots.txt allows, grades your web and email security, scores your AI readiness out of 100, and suggests free next steps from Austin AI Hub.
Seven weighted components: machine legibility (18 points), foundations such as a shared workspace and modern hosting (18), system of record (15), security and privacy posture (15), measurement (12), prior AI experience (12), and connectedness across systems (10). The dashboard shows what you earned in each. Scores are clamped between 12 and 96 because nothing visible from the outside justifies either extreme.
It depends which crawler. Blocking a search crawler such as OAI-SearchBot, PerplexityBot or Claude-SearchBot means that assistant cannot cite you, even when you are the best answer to someone's question. Blocking a training-only crawler such as CCBot keeps your text out of the next model and costs you no citations. Most robots.txt files that block AI do not make this distinction.
No. It adapts to whatever you are: a nonprofit, a school, a clinic, a city department, a shop, a firm, or a startup. The advice, the privacy obligations, and the example workflows all change to match.
No. Austin AI Hub is a 501(c)(3) nonprofit. Workshops, events, mentorship, and community programs are free. Nothing on this page is a sales pitch, and no one will call you.
No. The Hub's AI literacy sessions are hands-on, led by PhD researchers, and assume no coding at all. They are built for engineers and educators, students and career changers, healthcare workers, small-business owners, parents, and people who have never typed a prompt.
We keep a minimal service log: the domain checked, when, and the scores we computed, so the Hub can see how the tool is used and improve it. The log holds nothing about you: no IP address, no browser details, no account, and no way to tell who ran a check. No one is contacted and there is no follow-up. The eight requests we make gather only what any visitor could see.