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

# Crawlability

> Audit the technical health of your site — robots.txt, rendering, structured data — that decides whether AI crawlers can read and extract your pages.

If a model can't cleanly read your page, it can't cite it. **Crawlability** analyzes your website for technical health and readability — the factors that determine whether AI models can access and extract your content. It works at two levels.

## Page level

A per-page breakdown showing:

* **On-page score** — the page's overall technical health
* **Readability score** — how cleanly the content can be extracted
* **Estimated traffic** — so you fix high-value pages first
* **Citations** — whether AI currently cites the page
* **Specific issues** — what's holding the page back

Click any page for a detailed score breakdown with recommendations.

<Tip>
  Fix-first candidates are the pages where value and problems overlap: high estimated traffic, multiple issues, and few or no citations. A perfect page nobody visits and a broken page nobody cites are both lower priority than a busy page AI *almost* cites.
</Tip>

## Domain wide

Aggregated health across your entire domain. 3RD tracks a catalog of domain-wide signals, grouped by what they affect:

| Category                     | What's tracked                                                                                                                                                                             |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Crawlability & AI access** | Robots.txt configuration, XML sitemap, AI crawler allowlisting (are GPTBot, ClaudeBot & co. allowed in?), crawl budget efficiency, HTTPS & security headers, hreflang/internationalization |
| **Schema & structured data** | Organization schema, `sameAs` entity links, sitewide schema coverage, structured data validation                                                                                           |
| **Machine readability**      | HTML structure & landmarks, global meta tags, image alt-text coverage                                                                                                                      |
| **Site speed**               | Server response time (TTFB)                                                                                                                                                                |
| **Mobile & rendering**       | Mobile-friendliness and page size                                                                                                                                                          |

Each signal is scored, comes with an explanation of why it matters, and failing checks can be turned directly into [tasks](/actions/task-management). These are fix-once, benefit-everywhere issues: a template-level fix propagates to every page built on it.

## Technical audits

3RD runs automated **technical audits** across your tracked domains to keep these signals current — findings flow into the domain-wide view and can become tasks.

<Note>
  Crawlability analyzes the **domains and pages you've selected for tracking** — keep that selection accurate under [Monitoring settings](/workspace/monitoring-settings) so the analysis covers your real content footprint.
</Note>

## Related

* [Content](/drivers/content) — what to say once AI can read you
* [Task Management](/actions/task-management) — where crawlability findings become work