What stops AI reading the site.
A crawl of your client’s site for what blocks AI discovery and citation. An AI site health audit with the evidence on every issue, and a way to fix each one.
- 72of 100
- 1The answer is not in the HTML
- 2An AI crawler is blocked
- 3No sitemap
What stops AI reading a website?
AI assistants can only cite what they can reach and read. Typical blockers are a robots rule that shuts out an AI crawler, an answer that only appears after JavaScript runs, a missing sitemap and missing structured data. Site Health crawls a client’s site for these and shows the evidence it saw on each page.
It is the technical half of the work, and every finding comes with a way to fix it.
Every finding comes with a fix.
Fix with agent, on every finding.
It opens the Agent with the question drafted and the finding attached. The Agent checks the affected pages live and answers with a fix brief for your coding agent.
- Up to three affected pages checked live
- The brief is markdown, ready to hand over
- The Agent is on Pro and Agency
Allow the answer crawlers. Check the three pages live.
Improve a page without touching what ranks.
One existing page, audited the way an AI crawler reads it, then an additive, reversible fix.
- An answer-first block, an FAQ and structured data
- Made to suit the site’s stack
- Applied by your own team or your own AI coding tool
- An answer-first block
- An FAQ
- Structured data
- The page as it is
See the pages. Scan. Read. Fix.
- 01
See the pages
The page list appears before any crawl runs.
- 02
Scan
Within the plan’s page limit. The scan updates itself while it runs.
- 03
Read the issues
A score, then issues by severity, each with the evidence seen on the page.
- 04
Fix
“Fix with agent” on every finding, or “Improve a page” for an additive, reversible change.
The technical half, ready to hand over.
- At onboarding
- A first scan shows what is blocking a new client before any content work starts.
- For developers
- A Markdown fix brief from the Agent, written for the client’s coding agent.
- Sized by plan
- 100 pages a scan on Solo, 200 on Pro and Agency.
PlanThe scan is on every plan. Fix with agent needs the Agent, on Pro and Agency.See pricing
Questions about Site Health, answered plainly.
What stops AI assistants reading a site?
Typical blockers are a robots rule that shuts out an AI crawler, an answer that is not in the HTML before JavaScript runs, a missing sitemap, and missing structured data. Site Health checks for these and shows the evidence.
How is it different from a technical SEO audit?
A technical SEO audit looks at how a search engine crawls and ranks a site. Site Health looks at what blocks AI discovery and citation, and reads a page the way an AI crawler does.
What is “Improve a page”?
It audits one existing page the way an AI crawler reads it, then proposes an additive, reversible fix: an answer-first block, an FAQ and structured data. What already ranks is left alone.
What is “Fix with agent”?
A button on every finding. It opens the Agent with the question drafted and the finding attached. The Agent checks up to three affected pages live and answers with a Markdown fix brief for your coding agent.
How many pages does a scan cover?
Up to 100 pages a scan on Solo, and 200 on Pro and Agency.
Can fixes be applied automatically?
Not by Inciteful. The fix is made by your own team, or by your own AI coding tool working from the list. Inciteful never changes a client’s site.
Does the crawl feed anything else?
Yes. A crawl from the last 30 days becomes the technical health part of the AEO Boost. Without one, that part of the audit says unmeasured.



