Pattern fixture

Contact Conversion Fixture

A contact page where an agent must expose the next step, contact options, fit qualifier, expectations, service area, fallback path, and privacy note.

Agent Question

How should a qualified person contact the business, what should they provide, and what fallback exists?

Pattern Contract

Give users, crawlers, and agents a clear next step with contact facts, qualification notes, service fit, and accessible interaction paths.

Visible Sections

Contact options
Expected next step
Fit qualifier
Service area
Privacy expectation
Fallback path
Source and claim notes

Metadata Checks

One H1 identifies the contact fixture
Title and description describe the contact path
Contact facts are visible to crawlers

Schema Checks

WebPage schema names contact-conversion-page as the pattern
ContactPage and Organization obligations are visible
Response-time claims require source-backed configuration

Traceability Checks

Email, phone, address, service area, response time, and availability claims require configured source facts
Form-only contact is blocked unless fallback is documented

Source Evidence

src/data/agent-reference.ts: pagePatterns.contact-conversion-page
/contact/schema.json
src/site.config.ts

Good Example

The contact page states who should reach out, what to include, what happens next, the privacy expectation, and a fallback path.

Bad Example

The contact page has only an embedded form, no fallback, no service-fit qualifier, and an unverified response-time promise.

Agent Instructions

Confirm contact facts come from config before publishing
Provide a crawler-visible fallback path
Keep privacy expectations close to the form path
Run qa:fixtures after changing contact pattern

QA Gates

npm run qa:fixtures
npm run qa:seo
npm run qa:aeo

Completion Criteria

Contact options and fallback are visible
Fit and expectations are clear
Contact claims trace to source configuration