td.com
Gemini · gemini-2.5-flash · HTTP · Target td.comA measurement at one moment, not a verdict · MethodologyTD.com is highly accessible to AI agents, but struggles to provide authoritative answers for eligibility and latest news without relying on external search.
Make “am I eligible” findable on the site+390 → 93
All of them together: 99 (A)
Projected from the audit record. After fixing, re-run the task or re-measure to confirm.
AI agents successfully accessed TD.com, benefiting from a clear robots.txt, an available sitemap, and a newly adopted llms.txt file. The site performs exceptionally well for core banking intents like support, signup, policy, and comparisons, allowing agents to navigate natively and cite official pages. However, agents failed to complete tasks related to eligibility and latest updates, forcing them to rely on external search engines and third-party sources. Additionally, finding specific locations and documentation yielded only partial success, often requiring heavy search bridging. Overall, while the technical foundation is strong, specific content areas lack clear, discoverable pathways for automated agents.
What works
- Excellent technical accessibility with no bot blocking, a valid robots.txt, and an available sitemap.xml.
- Proactive AI readiness demonstrated by the presence of an /llms.txt file.
- High success rates for core intents (support, signup, policy, contact, compare) using native site navigation.
- Strong internal linking on the homepage (505 anchors) facilitates discovery for most topics.
What to fix
For each item: its current state, why it matters, how to fix it and how to check. The same content comes as files you can hand straight to whoever does the work.
Putting the items together…
Fix files
Files generated from this audit. Paste them in, or hand them to a coding agent. Have someone review them before they go live.
Building the fix files…
Detailed results
The results behind the score, and the measurement record.
Evidence
- homepage HTTP 200
- redirect hops: 2
Evidence
- no bot blocking observed
- Cookie consent banner: OneTrust
- First byte after 86ms
Evidence
- /llms.txt — present
- /llms-full.txt — absent (HTTP 404)
- /sitemap.xml — present
- /sitemap-index.xml — absent (HTTP 404)
- /sitemap_index.xml — absent (HTTP 404)
- /robots.txt — present
Evidence
- 505 links in the raw HTML
Evidence
- outcome success · verdict full
- the final answer cited this site
- site-guided navigation 40%
- 2xx rate 100%
- done_big_detour
Evidence
- outcome success · verdict failed
- the final answer cited no URL from this site
- site-guided navigation 0%
- 2xx rate 0%
- done_small_detour
Evidence
- outcome success · verdict full
- the final answer cited this site
- site-guided navigation 100%
- 2xx rate 100%
- done_unaided
Evidence
- outcome success · verdict partial
- the final answer cited this site
- site-guided navigation 50%
- 2xx rate 100%
- done_big_detour
Evidence
- outcome success · verdict full
- the final answer cited this site
- site-guided navigation 100%
- 2xx rate 100%
- done_unaided
Evidence
- outcome success · verdict full
- the final answer cited this site
- site-guided navigation 100%
- 2xx rate 100%
- done_unaided
Evidence
- outcome success · verdict partial
- the final answer cited this site
- site-guided navigation 100%
- 2xx rate 100%
- done_unaided
Evidence
- outcome success · verdict full
- the final answer cited this site
- site-guided navigation 100%
- 2xx rate 100%
- done_unaided
Evidence
- outcome success · verdict failed
- the final answer cited no URL from this site
- site-guided navigation 0%
- 2xx rate 100%
- done_big_detour
Evidence
- outcome success · verdict full
- the final answer cited this site
- site-guided navigation 100%
- 2xx rate 100%
- done_unaided
WebMCP — what the site declares about itself
navigator.modelContext was not found on this page. Not adopted yet.
Put the content in the first HTML and add llms.txt first; then declare the tasks that failed above as tools.
Open it yourself with AOO Lens →Act-stage check (nothing submitted)
Checks whether an agent could fill in the forms and press the buttons, up to the point of pressing. No form was submitted, nothing added to a cart, nothing paid. Report only; not scored.
Per-task results
| Task | Verdict | Own-site share | Request success | Followed guidance | Cited own site | |
|---|---|---|---|---|---|---|
| fees & rates | Full | 100% | 100% | 40% | Yes | |
| am I eligible | Failed | 0% | 0% | 0% | No | |
| get support | Full | 100% | 100% | 100% | Yes | |
| find a branch | Partial | 100% | 100% | 50% | Yes | |
| create an account | Full | 100% | 100% | 100% | Yes | |
| refund policy | Full | 100% | 100% | 100% | Yes | |
| find a document | Partial | 100% | 100% | 100% | Yes | |
| contact a human | Full | 100% | 100% | 100% | Yes | |
| latest notice | Failed | 0% | 100% | 0% | No | |
| compare two options | Full | 100% | 100% | 100% | Yes |
About this report
- Measured
- 9/26/2026, 12:25:21 AM GMT+9
- Engine
- Gemini · gemini-2.5-flash · HTTP
This is what AI agents could do on the site at the time above, measured by actually using it. It is not a verdict on the site or the company, and the result can change when the site does.