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.
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
1
Make sure your workspace has the right domain
AI Website Health checks the website connected to your workspace. Check it under Workspace settings.
2
Run your first check
Click Run checks. KIME crawls your site and scores it. When it finishes, the results appear on the page.
3
Run it again after changes
Click Run checks whenever you have shipped fixes, so the score and history stay current.
How to use it
1
Start with critical issues
Look at the critical checks first. They are the issues most likely to stop AI systems from accessing your content.
2
Work area by area
Open the area with the lowest score in Detailed results and read which checks failed.
3
Find the affected pages
In Pages checked, filter by Failures or by a specific check to get the list of pages to fix.
4
Turn fixes into tasks
Hand the list to your web team, or track the work in Actions, where technical tasks are suggested for you.
5
Re-run and compare
After fixes go live, run the check again and follow the trend in Score over time and Past health checks.
Get the most value
Fix crawler access first
Fix crawler access first
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.
Ignore pages that should not be cited
Ignore pages that should not be cited
Login, account and test pages often fail checks. Focus on product, category, guide and blog pages that you want AI to quote.
Run a check after every release
Run a check after every release
Site releases can accidentally block crawlers or remove metadata. A quick re-run catches it before your visibility drops.
Connect it to your visibility data
Connect it to your visibility data
Compare your readiness score with Visibility and AI Traffic over time to see whether technical fixes lead to more mentions and visits.
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.