att.com
CrawlCheck last read att.com on 2026-11-16 and graded it C, 81 of 100, for how well AI agents and search crawlers can read it, with 7 findings.
llms.txtagents.mdMedia kitEntity graphAI access policyAgent-callable
Owner not verified. Is this your site? Prove it is yours — free, by DNS TXT or a meta tag.
Facts on record
| Fact | Value | How it is known |
|---|---|---|
| Owner | Not verified | nobody has proved they run this site |
| Grade | C, 81 of 100 | measured on the last read |
| Last read | 2026-11-16 | the date CrawlCheck fetched the site |
Get these 7 findings fixed
Every defect this row counts, corrected on the site itself and then re-measured from the outside — done is measured, not asserted. One-time, $100 for one small-business site, thirty days of monitoring included.
Get this fixed — $100Claiming is free and changes nothing but the owner mark. What a licence adds is the record behind this entry: re-measured twice a day, finding age on every defect, change receipts between any two dates. Keep it on the daily record.
What the fetch found
| Finding | Severity |
|---|---|
| robots.txt rules do not apply to named agents | 3 of 5 |
| Almost nothing a machine receives from this page is readable text | 3 of 5 |
| The HSTS header asks for browser preloading but does not qualify for it | 2 of 5 |
| An answer engine's crawler was refused while a browser was served (unconfirmed from this vantage) | 2 of 5 |
| The ARD manifest is valid but its entries will not be found by search | 1 of 5 |
| A missing agent file answers with a full page | 1 of 5 |
| A business record gives an address but no coordinates | 1 of 5 |
Section scores on this fetch
Weakest first. 9 of 24 scored sections at 90 or above.
| Section | Score |
|---|---|
| Payload and render path | 20 |
| Authorship and trust signals (E-E-A-T proxies) | 40 |
| Crawl waste | 50 |
| What each agent receives | 57 |
| Sitemap coverage | 60 |
| Machine layer | 67 |
| Speed a crawler sees, and field data where it exists | 67 |
| Claim consistency | 75 |
| Schema and entity graph | 78 |
| Server and hosting | 80 |
| Entity corroboration | 80 |
| Naming and case consistency | 80 |
| Image signals | 80 |
| Accessibility structure (from the delivered HTML) | 83 |
| Indexability | 83 |
| RDF and linked-data surface | 100 |
| Page subject, the Webref question | 100 |
| AI and search agents | 100 |
| Machine-file trust chain | 100 |
| Agent instruction surface | 100 |
| Mobile surface | 100 |
| Exposed files and secrets | 100 |
| Error pages | 100 |
| Internal linking | 100 |
Shelves
| Shelf | State | Definition |
|---|---|---|
| llms.txt | on the shelf | What counts, and who has it |
| agents.md | not found | What counts, and who has it |
| Media kit | not found | What counts, and who has it |
| Entity graph | on the shelf | What counts, and who has it |
| AI access policy | on the shelf | What counts, and who has it |
| Agent-callable | on the shelf | What counts, and who has it |
Questions about att.com
Has the owner of att.com been verified?
Owner not verified. Nobody has proved to CrawlCheck that they run this site. Proving it is free and takes one DNS record or one meta tag.
Can AI assistants read att.com?
On 2026-11-16 it was graded C, 81 of 100, with 7 findings. It serves 4 of the 6 things the registry looks for: llms, entity, aipolicy, agentapi.
How current is this page?
CrawlCheck last read att.com on 2026-11-16. The page changes only when a new read does.
The full report for this fetch
Machine-readable: /api/registry?host=att.com. This row states what was served to CrawlCheck at that time. It is not an endorsement, and it says nothing this scan did not measure.