Skip to main content

The Nine Signals

Action path

Whether an assistant can move the user from an answer to a completable next step.

SignalAction path
What it checksCall, directions, booking, quote, order, reserve, and deep-link readiness
MovesRecommended
Fix cardNext step is unclear or not machine-detectable
VerifyTest action completion
At risk
Needs work
Strong
04070100

What it measures​

Action path measures the shortest reliable route from the assistant answer to a user action. For local businesses, that may be call, directions, book, reserve, request a quote, order, waitlist, message, or open a deep link.

The research separates action path into presence, clarity, machine-detectability, and completion quality. A CTA button is not enough if the destination is a generic homepage, login wall, broken deep link, or mismatched location.

Why it moves your EAC​

Assistants prefer answers that can satisfy the user's task. If one business has a clear appointment URL, verified hours, correct phone, and a location-specific landing page, it is a safer recommendation than a business with only vague "Contact us" copy.

Action path often determines whether a recommendation becomes a lead. The score should therefore measure both detection and completion.

What the agent sees​

Weak read

The business appears relevant, but the booking link goes to a homepage, the phone number differs from the profile, and hours are missing from the page.

Strong read

The assistant can identify the exact location, current hours, call link, booking URL, and service-specific appointment path.

How to improve​

  1. Make each action location-specific. Booking, order, quote, and reservation links should land on the exact merchant or location.
  2. Expose direct web actions. Use visible tel: links, canonical booking URLs, clear quote forms, and direction links.
  3. Add structured action hints where appropriate. Use ContactPoint, OpeningHoursSpecification, and potentialAction with ScheduleAction, ReserveAction, or QuoteAction when accurate.
  4. Remove first-step friction. Avoid login walls, forced account creation, broken mobile fallbacks, and generic provider pages.
  5. Keep platform actions aligned. Google, Apple, Bing, and provider feeds should point to the same current actions.

How to verify​

Can the user complete the next step?

Test the assistant prompt, then test the surfaced action on mobile and desktop. The action should resolve to the correct location and complete without detours.

Re-run check

Research basis: docs/research/deep-research-report(12).md