# Guides for AI-ready documentation

import { LinkCard, CardGrid } from '@astrojs/starlight/components';

AI assistants, answer engines, and training crawlers now read documentation alongside human readers. You can track this traffic and prepare any docs site for it, whether or not you use EkLine. The methods use open standards and common practices, not EkLine features.

## Monitor AI traffic

Understand which AI bots read your documentation, how to identify them in your logs, and how to measure their activity.

<CardGrid>
  <LinkCard
    title="Understand AI traffic to your docs"
    description="What AI bots and crawlers are, the three categories that matter, and why they affect documentation teams."
    href="/guides/ai-traffic/understanding/"
  />
  <LinkCard
    title="Identify AI bots and crawlers"
    description="A reference of common user-agent tokens by operator, with verification methods."
    href="/guides/ai-traffic/identify-bots/"
  />
  <LinkCard
    title="Monitor AI traffic to your docs"
    description="Measure AI crawler and referral traffic using server logs, CDN analytics, and web analytics."
    href="/guides/ai-traffic/monitor/"
  />
</CardGrid>

## Make your docs AI-ready

Configure your documentation site so AI tools can fetch, read, and use your content, and decide which AI systems may access it.

<CardGrid>
  <LinkCard
    title="Serve a Markdown version of every page"
    description="Give each page a clean Markdown version through per-page files, content negotiation, and an HTML discovery tag."
    href="/guides/serve-markdown/"
  />
  <LinkCard
    title="What is llms.txt?"
    description="The proposed standard, its format, and how it differs from robots.txt and sitemap.xml."
    href="/guides/llms-txt/what-is-llms-txt/"
  />
  <LinkCard
    title="Add an llms.txt file to your docs"
    description="Create, place, and maintain an llms.txt file, with platform-specific options."
    href="/guides/llms-txt/add-llms-txt/"
  />
  <LinkCard
    title="Control AI crawler access"
    description="Use robots.txt to block training crawlers while allowing AI search and on-demand fetchers."
    href="/guides/control-ai-access/"
  />
  <LinkCard
    title="Stop AI assistants from recommending removed API endpoints"
    description="Retire an endpoint so AI tools find the removal and its replacement in your docs, spec, llms.txt, and API responses."
    href="/guides/retire-api-endpoints-for-ai/"
  />
</CardGrid>

## Where EkLine helps

Serving your docs to AI tools only pays off when the content behind them is accurate. EkLine keeps that side current.

<CardGrid>
  <LinkCard
    title="How EkLine Docs Reviewer works"
    description="Catch style, terminology, and broken-link problems in pull requests before AI tools read the published page."
    href="/reviewer/overview/"
  />
  <LinkCard
    title="EkLine Automations"
    description="Run recurring audits, including an SEO review of titles, descriptions, headings, and internal links, on a schedule you set."
    href="/agent/scheduled-agents/"
  />
</CardGrid>