> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anymorph.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Site Audit
> Diagnose and fix site issues that affect AI access, trust, and citation
Site Audit checks whether AI engines can actually read your site. No matter how good the content is, it won't get cited if AI can't reach the page or can't extract the key facts from it.
## Running an audit
Click **Run audit** and it proceeds in three steps.
| Step | What it does |
| ----------------- | --------------------------------------------------- |
| Discovering pages | Crawls the sitemap and internal links to find pages |
| Measuring pages | Runs technical checks page by page |
| Analyzing issues | Groups the findings into actionable recommendations |
Large sites can take a few minutes. It keeps running if you close the window, and you can come back later to check results.
On large sites, a **representative sample** is measured instead of every URL. The results page shows whether sampling was used.
## GEO readiness
GEO readiness summarizes the audit into a single score, broken into five lanes.
| Lane | The question it answers |
| ---------------- | -------------------------------------------------- |
| Access | Can AI and search crawlers reach the page? |
| Discovery | Is there a path to find important pages? |
| Technical health | Does the page work without being broken? |
| Structured data | Can machines read the page's information? |
| Measurement | Is there a system to keep confirming improvements? |
Each lane shows as **Ready**, **Needs attention**, or **Blocked**.
If Access is Blocked, improving the other lanes won't help. Fix access first.
### The three-line summary
Below readiness, this run's conclusion is shown in three lines.
| Item | Content |
| --------------- | --------------------------------- |
| What's working | Lanes in good shape |
| Biggest blocker | The lowest-scoring lane |
| Do this first | The single task to start with now |
If a previous run exists, **fixed / new / regressed** counts also show. A regression is something you fixed before that came back, so trace the cause.
## Recommendations
Issues fall into two kinds.
| Kind | Nature | Trait |
| ---------------- | --------------------------------------------------- | ---------------------------------- |
| Site-wide fixes | A single change at the theme or site-settings level | Highest leverage |
| Page-level fixes | Per-page work | Sorted by number of pages affected |
Handle site-wide fixes first. A single change often improves every page at once.
Each recommendation carries three badges.
| Badge | Values | Use |
| ------ | --------------------------------------------- | --------------------- |
| Impact | High / Medium / Low | Set priority |
| Effort | High / Medium / Low | Estimate the timeline |
| Owner | Developer / SEO / Content / Analytics / Mixed | Assign the work |
**High impact, low effort first** is the default order.
### Main recommendation types
| Recommendation | Problem | Fix |
| ---------------------------------------- | ---------------------------------------------------- | --------------------------------------------------------------- |
| Make important pages reachable | Errors, noindex, or access controls block crawling | Remove the unintended block rule |
| Expose critical facts before JavaScript | Information only appears after rendering | Server-render the key facts or include them in the initial HTML |
| Add missing facts | Not enough concrete information to answer with | Add price, stock, author, date, service area, and so on |
| Make page facts machine-readable | Missing or mismatched structured data | Add JSON-LD that matches the visible content |
| Clarify page titles and summaries | Duplicate or empty titles, descriptions, or headings | Rewrite so each page's purpose is clear |
| Consolidate duplicate or competing pages | Multiple URLs competing for the same role | Pick a canonical URL and clean up canonicals |
| Help AI/search find priority pages | Missing from the sitemap or internal links | Register in the sitemap, add internal links |
| Fix broken page experience issues | Broken resources, slow rendering, security issues | Fix the underlying technical issue |
| Set up validation | No system to confirm improvements | Set a recurring audit cadence |
## Recommendation detail
Click a recommendation to open its detail page.
| Section | Content |
| -------------------- | --------------------------------------------- |
| How this was checked | How it was determined |
| Why it matters | Impact on AI citation |
| Primary action | What to actually do |
| How to validate | How to confirm the fix |
| Affected pages | The page list, switchable by issue or by page |
| Evidence | The signals checked and sample URLs |
Export the page list as **CSV** to hand off to your dev team.
## Evidence
Open **Evidence** to see the individual checks behind the readiness score, classified as passed / needs attention / unverified.
Each judgment is either rule-based or model-based, and the screen shows which.
## Improvement loop
Establish a baseline for where you stand.
Handle high-impact, low-effort items first.
Work through pages in order of how many are affected. A CSV handoff makes this easier.
Confirm real progress with the fixed / new / regressed counts.
Site Audit only confirms technical health. Confirm actual impact separately in [AI Visibility](/dashboard/visibility).
A higher Site Audit score doesn't immediately raise AI mention rate. The audit creates the conditions for citation; actual citation still needs content and sources working together.
## Troubleshooting
Click Re-run audit to retry. If it keeps failing, your site may be blocking the crawler. Check robots.txt and firewall settings.
Pages that aren't in the sitemap and aren't reachable through internal links won't be found. That itself is a discovery issue.
Large sites measure a representative sample only. A sampling notice appears at the top of the list.
It either recurred after a deploy, or the fix only applied to some pages. Check the affected-pages list for which URLs are still failing.
That may be a previous-version screen. Access Site Audit through the sidebar.
## Related
Build content once the audit has cleared the way.
Confirm the real impact of your fixes.
See whether your pages are being picked up as evidence.
Check domain connection and serving settings.