Google Business Profile basics
Rating, review count, website link, booking link, hours visibility, and profile activity — the signals patients see before they call.
Methodology
The snapshot is an outside-in, public-data report. It reads only what a patient, buyer, or search engine can already see. It never touches private practice systems, patient records, or login-protected pages.
Rating, review count, website link, booking link, hours visibility, and profile activity — the signals patients see before they call.
Visible phone number, tap-to-call, contact form, email visibility, and how many clicks a patient needs to reach a request path.
Booking or appointment-request links on the website and on the Google profile.
Whether a patient who looks after closing finds a 24/7 request path: online booking widget, request form, or chat — or phone-hours only. We never place calls.
Whether the website publicly mentions CDCP / the Canadian Dental Care Plan. Visibility only — we never claim a practice does or does not participate.
The Find → Open → Contact → Request path a new patient actually walks, step by step.
Publicly discoverable Facebook, Instagram, LinkedIn, YouTube, and similar profiles — flagged as unverified for monitoring.
robots.txt, sitemap, canonical, noindex, local-business structured data, AI-crawler access, and whether service/location content is readable.
When run, we ask web-search AI assistants for a dentist in the practice’s area and report how often the practice was mentioned in the test answers — a sampled presence check on the test date, never a ranking.
Anonymous comparison against cached nearby practices in the same category: rating and review medians, booking-link presence. Peers are never named.
Public hints of booking/practice-management platforms — always labeled low-confidence and directional.
These need internal systems or staff participation. The report says so explicitly instead of guessing — they are the “verify privately in Xona” items.
Every finding states what was actually observed and where: a profile field, a scanned page, or a cached public record.
High for direct observations, medium for inferred signals (like platform detection), low for partial or stale data. We band readiness instead of faking a precise 0–100 score.
Findings are labeled live-scan vs cached, with the scan time on the report. Public data changes; the report says when it looked.