> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kime.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Website Health

> Check how ready your website is for AI systems to crawl, understand and cite, and get a prioritized list of fixes.

AI Website Health checks your website the way AI systems see it. It crawls your pages, tests whether AI bots can reach and understand them, and gives you an **AI Readiness Score** with a list of issues ranked by impact.

You find it in the sidebar under **Analysis > AI Website Health**.

## What you see

### AI Readiness Score

A score from 0 to 100 with a label such as **Needs Work** or **Good**, and a short summary of what is holding your score back. Below it you see:

* The number of **critical**, **high** and **passed** checks.
* The domain that was checked and how many pages were crawled.
* The date and time of the check.

### Score over time

A chart of your AI readiness score across every check you have run, so you can see whether fixes are paying off.

### Detailed results

Each area shows a score, what was checked and how many checks failed. Fix items marked in red first, they have the biggest impact.

| Area | What it asks |
| - | - |
| **Content Optimization** | Is your content structured for AI citation? |
| **Discoverability** | Can AI systems find and navigate your content? |
| **Page Identity & Metadata** | Does each page identify itself properly? |
| **Crawler Access & Permissions** | Are AI bots allowed to reach your site? |

Open an area to see the individual checks and how to fix each one.

### Pages checked

Every crawled page is checked individually. Use the tabs **All**, **Failures**, **Warnings** and **Passed**, or **Filter by check**, to find pages with a specific problem. Click a page to see exactly what passed and what needs fixing.

### Past health checks

A table of previous checks with the date, score, number of issues, number of pages and status. Click a check to see how your site scored at that time.

## How to set it up

<Steps>
  <Step title="Make sure your workspace has the right domain">
    AI Website Health checks the website connected to your workspace. Check it under [Workspace settings](/administration/workspace-settings).
  </Step>

  <Step title="Run your first check">
    Click **Run checks**. KIME crawls your site and scores it. When it finishes, the results appear on the page.
  </Step>

  <Step title="Run it again after changes">
    Click **Run checks** whenever you have shipped fixes, so the score and history stay current.
  </Step>
</Steps>

## How to use it

<Steps>
  <Step title="Start with critical issues">
    Look at the critical checks first. They are the issues most likely to stop AI systems from accessing your content.
  </Step>

  <Step title="Work area by area">
    Open the area with the lowest score in **Detailed results** and read which checks failed.
  </Step>

  <Step title="Find the affected pages">
    In **Pages checked**, filter by **Failures** or by a specific check to get the list of pages to fix.
  </Step>

  <Step title="Turn fixes into tasks">
    Hand the list to your web team, or track the work in [Actions](/features/actions), where technical tasks are suggested for you.
  </Step>

  <Step title="Re-run and compare">
    After fixes go live, run the check again and follow the trend in **Score over time** and **Past health checks**.
  </Step>
</Steps>

## Get the most value

<AccordionGroup>
  <Accordion title="Fix crawler access first" icon="robot">
    If AI bots are blocked in your robots.txt or by your firewall, nothing else matters. Make sure the crawlers behind ChatGPT, Gemini, Perplexity and other engines can reach your site.
  </Accordion>

  <Accordion title="Ignore pages that should not be cited" icon="filter">
    Login, account and test pages often fail checks. Focus on product, category, guide and blog pages that you want AI to quote.
  </Accordion>

  <Accordion title="Run a check after every release" icon="rotate">
    Site releases can accidentally block crawlers or remove metadata. A quick re-run catches it before your visibility drops.
  </Accordion>

  <Accordion title="Connect it to your visibility data" icon="chart-line-up">
    Compare your readiness score with [Visibility](/metrics/visibility) and [AI Traffic](/features/ai-traffic) over time to see whether technical fixes lead to more mentions and visits.
  </Accordion>
</AccordionGroup>

## Who it is for

* **SEO and web teams** responsible for technical site health.
* **Content teams** who want their pages to be easy for AI to quote.
* **Agencies** running technical audits for clients.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.