Sample method photograph6documented observations
- 01SurfacePublic page and response
- 02ContextBroken mobile booking path
- 03DecisionEvidence-backed next step
← All industriesLaunch vertical
Common public-path risk · Broken mobile booking path
Home and Local Service Businesses
The booking and trust path is broken on mobile. Reviews, service-area pages, and the actual booking link disagree about who you serve and how to schedule. The visitor wants to call or book and instead gets a contact form, an off-site scheduler that fails, or a service page that does not match what they searched for.
Public pages only. The $97 report comes after the result.
Public pages onlyInspect the method →
Sample method photographObservation register · source-bound
What Revvye can inspect on this public path.
These are sector-specific observation prompts from the industry registry. Your result only includes signals the scan actually detects.
- 01
Whether the home and service pages render the booking or call CTA above the fold on a real mobile viewport.
- 02
Whether the local profile, the website, and the directory citations agree on NAP, hours, and service area.
- 03
Whether public reviews mention the actual services you want to be booked for, by name.
- 04
Whether the off-site scheduler embed survives a hard reload and returns a confirmation page that exists.
- 05
Whether the AI crawlers can read your service-area pages or are silently blocked by robots.txt.
- 06
Whether the public surface explains who you serve and where, in language a real customer would search for.
Public failure patterns
Described. Not claimed.
These are documented sector patterns, not customer findings. A scan must observe the signal on your URL before it becomes part of your result.
- 01
Service-area pages that share a single near-identical paragraph and only differ by city name.
- 02
A booking link in the navigation that opens an off-site widget which never loads on a hard reload from a different network.
- 03
A reviews block that lives only on the homepage and never appears on the service pages where the conversion happens.
- 04
A robots.txt that blocks the answer-engine crawler the operator most wants to be cited by.
- 05
A site that lists 'serving the greater metro area' without ever naming a city in the page body.
Fix posture · after observation
A sequence for deciding what to change first.
This is a sector playbook, not a promised outcome. The detected evidence still determines whether any step belongs in the actual work order.
- 01
Start with the booking and CTA path on mobile because a blocked primary action is the most direct public-path failure in this review.
- 02
Audit the service-area copy next. Cities the business actually serves should be named, not implied.
- 03
Place reviews on the service pages where the booking decision happens, not just the homepage.
- 04
Tighten the local schema and the directory NAP before assuming the search problem is rankings.
Published rule boundary
Sector context cannot invent a rule match.
The scan engine exposes 43 named public checks. Relevant rule definitions appear here only when the sector registry cites their real ids.
CRAWLER_BLOCKED_BY_ROBOTS_TXTAI crawler disallowed by robots.txt
Observes
robots.txt fetched from the domain root · per-bot Allow/Disallow evaluation via robots-parser · the matched robots.txt line number for the blocking rule
Does not measure
Detects only what robots.txt declares for the named bots Revvye tracks; it does not verify whether the engine actually honored the rule, nor whether the bot was blocked by a firewall/WAF the scanner cannot see.
structured-data.localbusiness.incompleteLocalBusiness schema missing required properties
Observes
presence of a LocalBusiness (or Restaurant/Store) node · required props: name, address, telephone (nested Offer flattened one level)
Does not measure
Checks for the required properties' presence, not their accuracy; it cannot verify the phone number or address is correct or matches your Google Business Profile.
markup.viewport-missingMissing viewport meta tag
Observes
<meta name="viewport"> presence
Does not measure
Checks the tag exists; the actual mobile rendering (overflow, CTA position) is graded by the mobile-experience worker checks.
Sector boundary questions
What the public scan can—and cannot—answer.
01Will Revvye know what my real conversion rate is for this vertical?+
No. Revvye does not see your CRM, your phone system, or your booking platform. It evaluates the public surface a stranger would meet. The conversion rate stays with the operator.
02What if my booking happens by phone, not online?+
The scan still applies. Revvye checks whether the call CTA is visible above the fold, whether the number is consistent across the site and the local profiles, and whether the public surface tells a stranger why they should pick up the phone.
03I serve a wide service area. Does that hurt my score?+
Not by itself. What hurts the score is when the public surface implies the service area instead of naming it. Revvye flags that pattern; the operator decides how to name the cities or zones in the copy.
04Can Google or an AI assistant cite my service-area pages if they exist?+
Only if those pages are crawlable and they actually name the cities and services you want to be found for. Google's current AI-feature guidance still starts with indexable, useful pages. Revvye checks robots.txt, LocalBusiness schema completeness, and whether the public copy answers a stranger's booking questions. It does not promise rankings or citations.
Observe the path before prescribing the fix.
The sector pattern is context. Your URL supplies the evidence.Return to the scanner →
Run this sector against your URL.
Public pages only. The $97 report comes after the result.