Google's AI agent dropped local firms with vague pages in a test

JSON-LD line: "makesOffer": [{

Summary

In one practitioner's tests, Google's agentic search dropped local businesses from its answer when their pages stated nothing it could check against what the user asked for, even after those businesses had ranked.

State each service page's services, service areas, hours and pricing in plain text, so the agent has specific claims to check.

A practitioner who tested Google’s agentic search on home service clients reported in a Reddit thread on r/TechSEO that the agent drops businesses whose sites give it no specific claims to work with. Agentic search narrows its recommendations to what the user asked for, explains why each business fits, and in some cases offers to call the business for the user. In the tester’s runs, generic positioning disappeared during that narrowing.

Claims such as “fixed price quotes with no hidden fees”, “same-day service” and “manual calculations” were what the agent kept and used. The filtering also continued after a business had first been cited, so an early mention did not guarantee a place in the final answer.

The thread is one person’s tests on their own clients, not a statement from Google. It is still a hands-on account of what can happen between a local ranking and the agent’s final answer.

The tester’s results point to a second step after ranking. Ranking decides which businesses the agent looks at. The agent then checks each one against the user’s requirements, such as budget, timeline or service type, and drops the ones whose pages give it nothing to check. On that account, a business in position one can vanish from the answer because its site never states the thing the user asked about.

Take a made-up example. Two roofing contractors rank for the same local query. The first lists “inspection, repair, replacement” on its service page with no prices. The second says small repairs run $2K to $4K. A user who gives the agent a budget has handed it a constraint, and only the second contractor offers anything to test that constraint against. The first is the kind of business the tester saw filtered out, however well it ranks.

Service areas work the same way. “Serving the metro area” gives the agent nothing to match a user’s location against, while a list of ZIP codes or city names does. The thread does not say whether Google’s agent renders JavaScript, so plain HTML text is the safer home for prices and areas. Other agents may not run scripts at all: Cloudflare’s new agent tools may not run your JavaScript.

The agent also picks the landing page

When the agent moved toward booking, the tester found it sometimes surfaced the right service page and sometimes pushed the user to a generic contact page, which broke the booking flow. The likelier explanation is that the agent sends users to whichever page best matches their stated intent, not to the page with the most authority. A dedicated page per service has been good practice for years. The difference now is that a site without one can lose the booking at the last step.

The calling behavior raises the stakes on accuracy. An agent that phones a business on the user’s behalf will find out quickly whether “same-day service” is true, and a claim that fails during that call fails in front of the customer.

What to do

Page copy comes first, because agents built on large language models read page text directly. Structured data adds explicit attributes on top of it.

  1. Audit each service page for plain, crawlable answers to five questions: which services the business offers, which it does not, which areas it covers, what its hours are, and how it prices.
  2. Give each service type its own page with specific claims, pricing context and a clear booking action, so the agent has something better than the contact page to send users to.
  3. Add LocalBusiness structured data with openingHoursSpecification and an explicit areaServed. priceRange only gives a general indication. For per-service prices, attach an Offer or AggregateOffer with a price and priceCurrency through makesOffer. The schema.org LocalBusiness page lists every inherited property.
  4. Check that the site, the Google Business Profile and the markup agree. A page promising round-the-clock emergency service next to a profile showing office hours could lower the agent’s confidence in every claim.
  5. Spot-check constraint-heavy queries by hand. Rank tracking only shows the ranking step, not whether the business survived the filtering.

A minimal version of step 3, with made-up values:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Example Roofing",
  "priceRange": "$$",
  "areaServed": ["Springfield", "Shelbyville"],
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "08:00",
    "closes": "17:00"
  }],
  "makesOffer": [{
    "@type": "AggregateOffer",
    "itemOffered": { "@type": "Service", "name": "Small roof repair" },
    "lowPrice": "2000",
    "highPrice": "4000",
    "priceCurrency": "USD"
  }]
}

Watch out for

Specific claims only help when the business can deliver them. Adding “fixed pricing” or “same-day service” to get through the filtering, without the operations behind it, swaps a loss nobody sees for one the customer hears about when the agent calls.