Platform components
AEO/GEO & AI Crawler Integration
We make your site readable and citable by AI search and chatbots — structured schema, llms.txt, sitemap and robots.txt tuned for AI crawlers, and reporting that shows which AI bots are actually reading your content.
1. What's included
FAQ/JSON-LD schema so answer engines can parse your content directly; a generated llms.txt describing your site to AI crawlers; an XML sitemap and robots.txt tuned to allow — or deliberately restrict — specific AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others); and an RSS feed where it helps freshness signals. This is the same approach narubox™ uses on its own blog: FAQ schema and direct-answer sections built into every post.
2. Crawler observability
Most sites have no idea whether AI crawlers are actually visiting, or what they read when they do. We add logging and reporting that separates real AI bot traffic — Claude, ChatGPT, Perplexity, and others — from human visits and background noise, so you can see whether the AEO/GEO work is actually being picked up. USAnaru™ runs this today.
3. Pricing
On its own, the AEO/GEO package starts at $1,200: schema, llms.txt, sitemap/robots.txt, and crawler reporting. It's included in every platform package.
Frequently asked questions
What is llms.txt, and do I actually need one?+
llms.txt is an emerging standard — a plain-text file describing your site's structure and key content for AI systems to read, similar in spirit to robots.txt for search crawlers. It isn't required, but it's low-cost and helps AI tools understand your site correctly instead of guessing.
Can you block specific AI crawlers instead of inviting them?+
Yes — robots.txt and server-level rules can allow or block individual AI crawlers by name. We'll help you decide which ones you actually want indexing your content.
How do I know whether any of this is actually working?+
Crawler observability reporting shows real AI bot visits over time, separate from human traffic, so you can see activity change after the work ships instead of guessing.
Have data your business isn't using yet?
Tell us what your business does and what data you have — we'll tell you plainly whether a platform makes sense and what it would take.
Contact us