Pattern catalog

Examples agents can reuse

These are not visual designs yet. They are technical/content patterns that define required pages, schema, proof needs, and routing expectations.

Local service website

Use when a company serves a geography and needs clear local relevance, proof, service detail, and contact conversion.

Required pages

Home
Services
Service detail
Service area
Proof
FAQ
Contact

Schema

LocalBusiness
Service
FAQPage
BreadcrumbList

Source assumptions

Verified service list
Service-area list
Contact details
Licensing or qualification facts
Customer proof

SEO requirements

Local title modifiers where true
Canonical service URLs
Internal links between service and proof pages

AEO requirements

Direct service answers
Plain-language eligibility/scope details
FAQPage schema for visible FAQs

QA requirements

qa:all
Screaming Frog crawl before launch
Mobile contact path check

B2B SaaS website

Use when buyers need category clarity, use-case mapping, objections, proof, and integration/entity pages.

Required pages

Home
Product
Use cases
Integrations
Comparison
Proof
Resources
Contact

Schema

Organization
SoftwareApplication
Product
FAQPage
Article

Source assumptions

Product positioning
Feature facts
Integration list
Security/compliance notes
Customer proof

SEO requirements

Category and use-case page metadata
Comparison pages avoid unsupported claims
Resource pages use Article schema

AEO requirements

Definition-ready product description
Feature and integration facts in visible copy
Comparison FAQs with caveats

QA requirements

qa:all
Structured data review
Claim/proof traceability review

Professional services website

Use when trust, qualifications, service scope, and proof matter more than product-style feature grids.

Required pages

Home
Services
Industries
About
Proof
Insights
Contact

Schema

ProfessionalService
Person
Organization
FAQPage
Article

Source assumptions

Service scope
Practitioner or team credentials
Industry experience
Client proof
Engagement process

SEO requirements

Service and industry URLs are distinct
Author or organization attribution is explicit
Proof pages support trust claims

AEO requirements

Clear who/what/where fit answers
Visible process and qualification details
FAQ schema for service objections

QA requirements

qa:all
Accessibility review for dense content
Proof claim review

Proof page

Use to make claims inspectable. Every claim should point to an example, artifact, metric, review, screenshot, or source note.

Required pages

Proof index
Case study
Testimonials
Before-after evidence

Schema

Review
CreativeWork
Article

Source assumptions

Approved testimonials
Case-study facts
Before/after artifacts
Metrics with dates
Permission notes

SEO requirements

Case-study titles include specific outcome when approved
No invented metrics
Canonical proof URLs

AEO requirements

Claims are answerable with context
Dates and conditions are visible when metrics are used
Review schema only for eligible visible reviews

QA requirements

qa:all
Claim/source audit
Permission/privacy review

Answer-ready resource page

Use for AEO/GEO pages that answer concrete questions and expose stable facts agents can quote or reason over.

Required pages

Guide
Comparison
Glossary/entity page
FAQ

Schema

Article
FAQPage
DefinedTerm
BreadcrumbList

Source assumptions

Topic definitions
Approved recommendations
Comparison criteria
Public source references
Entity glossary

SEO requirements

Search-intent-aligned titles
Stable URLs for glossary/entity pages
Internal links from guide to definitions

AEO requirements

Direct answers before nuance
Caveats visible near recommendations
Machine-readable schema for FAQs/articles/terms

QA requirements

qa:all
Internal-link crawl
Schema review

Canonical demo builds

Two complete worked implementations of these patterns exist, each fictional, each executing its playbook from source manifest through pages, schema, claim instrumentation, and QA evidence, and each carrying its own brand token set:

Brightline Gutter Co. — the local-service playbook (steel-blue light brand).
LogPilot — the B2B SaaS playbook, where unsupported integration, security, and comparison claims are the dominant risk (dark SaaS brand).

The machine-readable build records are at /demo-build.json and the QA gate is npm run qa:demo.

Live sample routes

These routes are the working demonstration of the patterns above, built into this reference with visible claim IDs, schema endpoints, and traceability notes. Inspect them as rendered HTML, then compare against their schema endpoints. Without these links the routes exist only in the sitemap, which the crawl stress suite treats as an orphan failure.

Services with /services/schema.json: service scope, claim-ID instrumentation, and Service schema.
Proof with /proof/schema.json: evidence artifacts and source-backed trust patterns.
Resources with /resources/schema.json: answer-ready resource and FAQ patterns.
Contact with /contact/schema.json: conversion path with ContactPage schema.