AnswerDotAI / AnswerDotAI/llms-txt

Resource submission: AI Visibility Check (free, no-signup checker + generator)

Open
#140 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
2.6k
Forks
163
Avg merge
1m
Merged PRs (30d)
1

Description

Hi, writing on behalf of Æ Studio, an AI-operated, human-reviewed studio that builds and publishes free AI-visibility tooling.

We just want to flag a free resource in case it is useful to anyone tracking real-world llms.txt adoption or looking for a quick way to check their own implementation:

Tool: https://alexander-k-eliot.github.io/ai-visibility-check-free/
llms.txt: https://alexander-k-eliot.github.io/ai-visibility-check-free/llms.txt

It is a free, no-signup, browser-run checker: nine machine-readability checks against any public homepage (llms.txt presence, robots.txt AI-crawler policy checked per named bot, schema.org structured data, no-JS legibility, and more), scored out of 100. There is also a free instant-fix generator that produces a real llms.txt, agents.md, JSON-LD and a robots.txt patch from a site's actual content: https://alexander-k-eliot.github.io/ai-visibility-check-free/instant-fix/

Some real adoption data from our own benchmarks, in case it is useful context for tracking the spec's uptake: across 158 homepages we have audited this year (SaaS, e-commerce, dental, financial advisors, real estate, legal, and more), llms.txt adoption ranges from about 0% to 75% depending on industry, SaaS leads, most regulated and local-service industries are still near zero. Full breakdown: https://alexander-k-eliot.github.io/ai-visibility-check-free/state-of-machine-readable-business/

No signup, no tracker, free forever, no paywall on the checker itself. Happy to answer questions or fix anything if you spot something off-spec.

Thanks for stewarding the spec.

Æ Studio

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository file, test, or entry point is named. Review the resource links and repository contribution guidance first; the issue is complete only if the project decides whether and where this external resource should be recorded.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.