How AI assistants read dga.org
An automated read of dga.org against the signals AI search engines use to crawl, parse, and cite a website.
AI assistants can only partially read this site.
The four signals
Whether AI crawlers (GPTBot, ClaudeBot, PerplexityBot and others) are allowed to fetch the site in robots.txt.
Whether Schema.org markup tells AI what the business is and what it offers.
Whether key content is server-rendered and cleanly structured for agents that do not run JavaScript.
Whether the site signposts agents with /llms.txt and a sitemap in robots.txt.
What we found
- ✓ Content is server-rendered
- ✗ No /llms.txt
- ✗ No Organization schema
- ✗ No Product / Service schema
- ✗ No FAQ schema
- ✓ Sitemap in robots.txt
- ✓ Has a page title
- ✗ No meta description
No Schema.org structured data detected.
Priority fixes
- highNo Product/Offer/Service schema.Add Schema.org Product or Service JSON-LD with name, description, and offers (price, availability).
- mediumNo Organization/WebSite schema.Add Organization JSON-LD with name, url, logo, and sameAs links.
- mediumNo FAQ/QA schema.Add FAQPage JSON-LD for the questions agents are likely to ask.
- mediumNo /llms.txt.Publish /llms.txt pointing agents to your key pages and policies.
- lowNo BreadcrumbList schema.Add BreadcrumbList JSON-LD so agents understand site structure.
- lowMissing meta description.Add a meta description summarizing the page.
- lowPage has 0 H1 headings (expected exactly 1).Use exactly one H1 that states the page topic.
- lowNo canonical link.Add a rel=canonical link.
This readiness check shows whether AI can read dga.org. The full audit goes further: it tests whether ChatGPT, Perplexity, Claude, and Google AI actually cite dga.org across real buyer questions.
Is this your site? Request a re-scan or removal →
Automated assessment of publicly observable signals only. RankEcho is independent and not affiliated with dga.org. How scoring works →