AI Readiness.
From Audit to Action.

Site-specific audits with fixes you can apply.
We check technical readiness — not brand awareness.

Our recorded audit: 99 / 100 · A
After fixes · 9 October 2026
View the full evidence →

No sign-up needed · takes about 15 seconds

Illustrative agent visits · not recorded traffic

  • GPTBot /robots.txt1 min ago
  • ClaudeBot /2 min ago
  • PerplexityBot /sitemap.xml3 min ago
  • GPTBot /products/example4 min ago

REAL PRODUCT OUTPUT · 9 OCT 2026

AI-Primed · original hosted deployment

After our fixes

First audit: 59 / 100 · D

Crawl & Bot Access100/ 100
Structured Data100/ 100
Readability100/ 100
Policy & Trust100/ 100
Entity Signals95/ 100

Commerce: not applicable. Non-store weights apply.

See the recorded before and after →

Demonstration · scan sequence

  1. [done]fetching robots.txt
  2. [done]fetching sitemap
  3. [done]fetching homepage
  4. [done]reading headers
  5. [done]checking structured data
  6. [done]scoring

Demonstrated timing, not a live request. Two passes, then stops.

Cohesive Site-Audit Experience

Manage your portfolio, run in-depth audits, verify fixes, and automate at scale.

Site Hub

Your Site Portfolio

The Site Hub is your inventory: each owned site with its latest grade, recent change, open critical findings and monitoring cadence — sortable, filterable and interactive.

  • Site Inventory

    Site capacity, scores, interactions — color-coded so problems stand out.

  • Insights at a Glance

    Score band, structured data, blocked agents, failed audits and monitoring — saved in the link so views are shareable.

  • Bulk actions

    Select sites to re-audit, pause or resume monitoring together.

Site Hub

From Audit to Fix

  1. Step 1

    Test Your Site (15 seconds)

    We visit your site the exact same way ChatGPT, Claude, and Perplexity do, and check if anything is blocking them at the door.

  2. Step 2

    See What AI Actually Reads

    Get a simple A-to-F grade showing whether AI can understand your prices, services, contact details, and location.

  3. Step 3

    Fix It in Minutes

    No coding required. We give you ready-to-use files and simple instructions you or your web designer can upload immediately.

Read what the walkthrough shows
  1. A domain is entered on Run an audit and the audit starts.
  2. The Audit Report opens on Findings & Fixes, showing the highest-impact fixes and the findings checklist.
  3. On the Site Project page, an AI Agent Test question is asked.
  4. Competitors are added and compared with the site category by category.
  5. The Site Hub lists every site with its score, recent change and monitoring cadence.
  6. A Client Report is built from selected sites.
  7. A list of sites is pasted into Bulk Audit and audited in turn.
  8. A completed Audit Report shows the Audit Summary and the six category scores.

The fix loop, with a recorded result

Find the gap. Apply the file. Run the audit again.

robots.txt · excerpt from our published fix

Added: + User-agent: GPTBot
Added: + User-agent: ClaudeBot
Added: + User-agent: PerplexityBot
Added: + Allow: /
Added: +
Added: + Sitemap: https://ai-primed.com/sitemap.xml

Additions only: no original removed lines were captured. We never invent a “before” file.

Recorded re-check · 9 October 2026

Recorded whole-site re-audit, not a claimed verification of this snippet alone. No guarantee of ranking, traffic or revenue.

Read every change and remaining finding →

Six things agents check

We check six areas, with weights matched to your site type. Commerce counts only for online stores.

  1. 01

    The Front Door

    Robots.txt & Firewalls

    Many firewalls treat AI assistants like hackers and lock them out. We show you how to open the door safely.

    What we check

    Can GPTBot, ClaudeBot and PerplexityBot reach your pages, or do robots.txt and firewalls turn them away?

  2. 02

    The Menu / Catalog

    Structured Data (Schema)

    AI can't guess what you sell. Structured data is like giving the AI a clean menu with your exact services and prices.

    What we check

    Is there schema.org JSON-LD that tells agents what you are, what you sell and at what price?

  3. 03

    Commerce Readiness

    Can an agent find a product, read its price and availability, and get to checkout?

    A shopping agent can't put your product in front of a buyer — no price, no stock status, no sale.

  4. 04

    The Executive Summary

    llms.txt

    A single, lightweight cheat sheet that tells AI assistants who you are, what you do, and why they should recommend you.

    What we check

    Is your content in the HTML, with llms.txt and a sitemap that point agents at what matters?

  5. 05

    Policy & Trust

    Are shipping, returns, privacy and terms easy for an agent to find before recommending you?

    No visible returns, shipping or privacy terms means agents treat you as a risk and pass you over.

  6. 06

    Entity Signals

    Do agents recognise your brand: name, logo, contact details and official profiles?

    Agents can't tell who you are, so your brand never gets attached to the things you actually do.

Commerce readiness only counts if you sell online. If you don't, that 20 points is spread across the other five categories so your score reflects what actually matters for your site.

Read how each category is scored →

Monitoring: Websites change. So can your score.

Yesterday’s readable site can be tomorrow’s blocked request.

A one-time audit tells you what we could read at that moment. A website update or a change to your Front Door (robots.txt rules and firewalls) can undo the fix. A locked door stops that agent from receiving the page; an incomplete Menu / Catalog (structured data) leaves fewer details to read. Ongoing checks show those observed changes—not an assumed loss of traffic or sales.

Scheduled checks, not a forgotten snapshot

Daily, weekly or monthly re-audits, with last-attempt and next-due times. A first check establishes a baseline; later comparable checks reveal change.

Dated drift, with the evidence attached

Compare scores, categories, crawler rules and findings against the previous successful audit. Open the linked reports to inspect before and after; unknown causes stay unknown.

Connected alerts with delivery evidence

Choose Slack, Discord, a signed webhook or account email. Test your destination, select events and review dated acceptance, retry or failure outcomes—not assumed inbox arrival.

Your sites. Your cadence. Your pause button.

Pause one project or all monitoring without deleting reports. The dashboard summarises scheduled sites, the next due check and failing channels.

Temporary failure is not confirmed drift

Unreachable and incomplete checks are recorded as attempts, with retries where applicable. They do not generate change alerts or replace the successful comparison baseline.

Observed visits, separate from audit scores

Upload access logs or use authenticated ingestion. Recorded requests and synthetic audit scores have separate labels and axes. No supplied logs means no traffic evidence—not zero visits.

Automatic monitoring requires Pro, Team and Agency, an account within its project limit and an enabled, unpaused schedule. Connected channels require a successful test. Checks can be delayed by capacity or retries; service acceptance does not establish receipt. 

Choose ongoing monitoring →

See how AI agents view your site.

No sign-up needed · takes about 15 seconds