Baseline · Broken variant
9successful tasks
out of 15 classified
6 task failures
- Completed / planned
- 15 / 15
- Excluded observations
- 0
Inside an executed demonstration
A missing contact page blocked the inquiry route. After repair, the same task checks reached the handoff.
Scripted browser test. No AI model or consumer assistant was run.
Baseline · Broken variant
9successful tasks
out of 15 classified
6 task failures
Retest · Repaired variant
15successful tasks
out of 15 classified
0 task failures
5 journeys × 3 repetitions per variant. All planned trials ran; completion is separate from task success.
01 · The finding
The observed contact link points to /contact-missing and returns HTTP 404. Contact entry and inquiry handoff fail in all three repetitions each.
“The requested contact route is unavailable. No contact or booking was completed.”

/contact-missingOpen full-size screenshot 
/inquiryOpen full-size screenshot 02 · The bounded repair
Point the visible contact navigation to /contact, make that page available, and provide its visible /inquiry handoff link and destination.
//contact/inquiryRetest: 3 / 3 contact tasks and 3 / 3 handoff tasks succeeded. The browser stopped before form entry or submission.
Inspect the contact pageStructured-data syntax also changed and was not evaluated. The retest does not isolate the effect of a single change.
03 · The complete picture
Each task was repeated 3 times per variant. Success means its recorded fixture condition was met.
| Journey | Baseline | Retest |
|---|---|---|
| Named service disclosure | 3 / 30 task failures0 excluded | 3 / 30 task failures0 excluded |
| Office and service area | 3 / 30 task failures0 excluded | 3 / 30 task failures0 excluded |
| Consultation process and fee policy | 3 / 30 task failures0 excluded | 3 / 30 task failures0 excluded |
| Contact entry route | 0 / 33 task failures0 excluded | 3 / 30 task failures0 excluded |
| Approved inquiry handoff | 0 / 33 task failures0 excluded | 3 / 30 task failures0 excluded |
An unchanged limitation
Fees and availability stayed undisclosed. These tasks succeeded by reporting the unknowns accurately. A successful extraction does not establish adequate pricing disclosure.
Method and evidence
This local fixture tests the collection and reporting workflow. It does not measure a real business or predict consumer AI behavior. Repetitions are controlled checks, not a statistical sample.
bf701300d99eb704487708327882168b87036b08fe886e64fd90b4594a2189e5The repaired variant changed both navigation and JSON-LD syntax. The journey evaluator did not assess JSON-LD, so this comparison cannot attribute the results to a single change. Fees and availability were neither invented nor added; an authorized owner would need to confirm any future disclosure.
The same original configuration was retained. Public JSON replaces the temporary local origin with [local fixture]; screenshots are unmodified. This is a scripted fixture evaluation, not an approved customer assessment, accessibility certification or readiness score.
Public records include every trial, capture reference and integrity check.
Start with your own website