Files
veripath/docs/validation/2026-08-15-diamond-springs-dental/REPORT-final.md
T
Leonard 394d5dae3f feat(auditing): pipeline v1.1 — report generation + scripted gate + temporal delta
- report_generate.py: REPORT-final.md + VALIDATION.md from findings + raw
  capture; per-surface status from summary.surfaces_ok; Data Limitations
- report_gate.py: §6 gate scripted (count/evidence/identity/material
  support); non-zero exit blocks delivery
- audit_diff.py: before/after capture comparison -> DELTA.md
- audit_pipeline.sh: 2 steps -> 4; collision-safe capture copy (re-runs
  preserve baseline); relative output dir resolved to absolute
- beta-audit-process.md: locked v1.0 -> v1.1 (+ dated decision record)
- all 9 runs of the 2026-08-15 batch regenerated + gated (9/9 PASS)
- live end-to-end proof: Gilmore re-run, DELTA.md 0 changes (same day)
2026-08-15 16:52:23 +00:00

98 lines
3.6 KiB
Markdown

# Diamond Springs Dental Center
## Online Presence Audit
**Location:** El Dorado, CA
**Vertical:** Dental
**Audit date:** 15 August 2026
**Prepared for:** Diamond Springs Dental Center
**Prepared by:** VeriPath
---
## Executive Summary
We audited Diamond Springs Dental Center across its primary online surfaces: Google Business Profile, Apple Maps and Website. The business shows 3.4 ★ across 49 Google reviews.
**4 material integrity issues were identified:**
1. Phone numbers are inconsistent across directories.
2. Address details differ between Google and Apple.
3. Average rating is below the 4.0 trust threshold.
4. The website lacks LocalBusiness structured data.
---
## Surfaces Reviewed
| Surface | Status | Rating | Reviews |
|---------|--------|--------|---------|
| Google Business Profile | ✓ | 3.4 ★ | 49 |
| Apple Maps | ✓ | 3.3 ★ | 28 |
| Bing Places | ✗ | capture blocked (bot-wall) — excluded, not verified | — |
| Website | ✓ | — | — |
---
## Findings
### Finding 1: Phone number inconsistent across directories
**Observation:**
Google lists **(530) 291-1888**. Apple lists **+1 (530) 344-0290**. Website lists **551-0858478**.
**Impact:**
Customers reaching the business through a single directory may call a disconnected or wrong number. Inconsistent NAP (name-address-phone) signals reduce local search ranking across all surfaces.
**Recommendation:**
Confirm the correct primary number, then update every directory to match. Keep the verified number identical across Google, Apple, and the website.
---
### Finding 2: Address inconsistent across directories
**Observation:**
Google lists “6400 Pleasant Valley Rd, El Dorado, CA 95623”. Apple Maps lists “493 Pleasant Valley Rd, Ste 110, Diamond Springs, CA 95619”.
**Impact:**
Conflicting addresses split local search signals and can send customers or service vehicles to the wrong location. NAP consistency is a core local-ranking factor.
**Recommendation:**
Confirm the canonical street address (including unit) with the business, then align Google and Apple to the same string.
---
### Finding 3: Average rating 3.3 — below 4.0 threshold
**Observation:**
Blended average is **3.35** (Google 3.4, Apple 3.3) — below the 4.0 trust threshold.
**Impact:**
A sub-4.0 average is below the trust threshold for most local verticals and suppresses click-through in the local pack regardless of review volume.
**Recommendation:**
Review the lower-rated reviews for recurring service issues; respond publicly to negative reviews and prioritize the service gaps they describe.
---
### Finding 4: No JSON-LD schema found on website
**Observation:**
{"url": "https://www.diamondspringsdental.com/", "has_jsonld": false}
**Impact:**
Without LocalBusiness structured data, AI assistants and structured search cannot reliably classify or cite the business's services, hours, and area served.
**Recommendation:**
Add LocalBusiness JSON-LD (Dentist/Plumber/Contractor type) with name, address, phone, hours, and areaServed.
---
## Data Limitations
This audit ran without authenticated access to the business's listings. Known ceilings:
- **Review text and dates** were not captured; ratings and counts only.
- **Bing Places** is bot-walled for headless capture in most runs; where it shows ✗ above, that surface is excluded from this audit, not verified.
- This is a **point-in-time snapshot**; directory data changes after the audit date.
*Prepared under the VeriPath beta audit process v1.1. Findings reflect reviewed engine output; format-level discrepancies were normalized before inclusion.*