How AI reads TruGreen

trugreen.com Jun 15, 2026 6 min read Basic Web Presence

Short

28/ 100

AEO Level 2Basic Web Presence

The short answer

TruGreen earned an AEO score of 28 out of 100, placing it at Level 2. AI agents can parse some homepage content and detect reasonable page structure, but the absence of structured data, agent interfaces, and explicit crawler declarations leaves most of the site invisible to answer engines.

What AI sees

When an AI agent visits TruGreen's homepage today, it encounters a content-rich lawn care site with moderate structural clarity but almost no machine-readable metadata.

The homepage delivers usable text about TruGreen's lawn treatment plans, service areas, and seasonal offers — enough for a basic extraction of who the company is and what it sells. Content structure scores a respectable 70, meaning headings and copy are reasonably organized. Agent discovery reaches 60, partly because the domain is well-known and broadly crawlable. But beyond surface-level text, agents hit a wall: structured data is entirely absent (score 0), so product details, service areas, and pricing signals cannot be reliably extracted. There are no machine-readable interfaces, no authentication signals, and no well-known endpoints that would let an AI agent interact with or programmatically represent TruGreen's service offerings.

TruGreen homepage as seen by an AI crawler — content is present but structured data and agent interfaces are entirely absent

TruGreen robots.txt contains no AI crawler rules — GPTBot, ClaudeBot, and PerplexityBot receive no explicit guidance on what to index or cite

Where it loses points

The most damaging gaps are agent interfaces and structured data — both scoring zero — meaning AI tools cannot reliably cite, integrate, or represent TruGreen's lawn care plans inside automated answer workflows.

How to fix it

Three targeted changes would move TruGreen's AEO score meaningfully and signal to AI crawlers that this is a trusted, citable source worth surfacing to homeowners.

Declare AI crawler rules in robots.txt

Goal

Establish explicit per-agent permissions so AI crawlers know exactly which paths they may index and cite.

Issue

TruGreen's robots.txt contains no user-agent rules for GPTBot, ClaudeBot, PerplexityBot, or any other AI crawler.

Fix

Add individual User-agent blocks for each major AI crawler with Allow directives covering service pages, FAQs, and plan descriptions. Include a Content-Signal directive declaring preferences for ai-train, search, and ai-input so downstream models handle the content correctly.

Publish an MCP Server Card

Goal

Give AI agents a machine-readable endpoint describing TruGreen's available tools, transport protocol, and capabilities.

Issue

No MCP Server Card exists at /.well-known/mcp/server-card.json, so agent frameworks cannot auto-discover how to interact with TruGreen programmatically.

Fix

Serve /.well-known/mcp/server-card.json with serverInfo (name, version), a transport endpoint, and a capabilities block listing available actions such as quote lookup or service-area check. This single file unlocks integration with any MCP-compatible AI agent.

Publish an API catalog at /.well-known/api-catalog

Goal

Enable automated discovery of TruGreen's APIs so AI orchestration tools can invoke them without manual configuration.

Issue

No API catalog exists at /.well-known/api-catalog per RFC 9727, leaving any existing APIs completely invisible to agent pipelines.

Fix

Serve /.well-known/api-catalog as application/linkset+json containing a linkset array that references available APIs — at minimum a quote or service-area endpoint. Even a one-entry catalog signals to AI systems that TruGreen is agent-ready.

Common questions

Why does TruGreen score only 28/100 on AEO despite being a nationally recognized lawn care brand?

Brand recognition does not translate to AI readiness. TruGreen's agent_interfaces and structured_data categories both score zero, meaning AI agents cannot extract structured service data or interact with the site programmatically. High organic SEO authority does not compensate for the missing machine-readable signals that answer engines depend on to cite and surface information.

What would happen if TruGreen published an MCP Server Card today?

Adding /.well-known/mcp/server-card.json would immediately make TruGreen discoverable to AI agent frameworks that auto-probe well-known paths. Agents could surface service availability, plan pricing, and quote flows directly inside AI-driven interfaces — without the homeowner ever needing to navigate the website themselves.

Does TruGreen's content structure score of 70 mean AI agents can already understand its service pages?

Only partially. A score of 70 means headings and copy are organized well enough for basic text extraction. Without structured data markup, however, AI agents cannot reliably distinguish which text represents a product, a price, a service area, or a satisfaction guarantee — they are inferring context rather than reading declared facts.