The 12-page SMB website architecture that converts (and gets cited in AI answers)
If you’re building or overhauling a small-business site, ship these 12 pages first—each with a clear outcome, one primary CTA, and proof—so visitors convert and AI/search engines can quote you.
What to publish (the 12-page minimum)
- Home: Problem → outcome, primary CTA, top proof, and clear next steps for your 2–3 main personas.
- Core Service pages (3–5): One page per service; headline, process, pricing context, FAQs, and schema.
- Industries/Use cases (1–2): Tailor trust and language to verticals you actually serve; link to matching services.
- Pricing: Real ranges with scope drivers, terms, and one obvious next step.
- About: Why you exist, who leads the work, and how you operate (bios + credibility).
- Proof hub: Case snapshots/testimonials with outcomes and context; link proof near CTAs sitewide.
- Location/Service-area page(s): If you serve specific cities/regions, create a hub; link down to location pages when you have multiple offices.
- FAQs: 8–12 crisp answers to objections/logistics that come up on sales calls.
- Resources/Guides: Practical, buyer-led content (pricing explainers, comparisons, checklists) you can cite and AI can summarize.
- Contact/Book a consult: Low-friction booking, click-to-call, and office details.
- Privacy + Terms: Transparent policies build trust and enable partnerships/platform approvals.
- Conversational portal entry point (if used): Clear explanation of what visitors can do via chat, with crawlable summaries linking to the above pages.
Architecture and linking that make this work
- One URL per intent: Don’t cram multiple services into one page; map navigation and internal links to buyer intent.
- Lead with the answer: Each page opens with a 1–2 sentence takeaway users (and AI systems) can quote.
- Cross-linking: From Home → Services → Proof/FAQs → Pricing → Book. Use descriptive anchors (“SEO retainer pricing”) not “click here.”
- Schema: Organization/LocalBusiness on About/Contact; Service on service pages; FAQPage for real FAQs; HowTo where steps are explicit.
- Speed and crawlability: Server-render core content, keep pages lean, and maintain clean canonicals/sitemaps.
Content patterns (copy and adapt)
- Headline: [Service] for [who] → [outcome]
- Subhead: 1 proof point (review count, years, certifications)
- Primary CTA: Book a consult / Request estimate (repeat after major sections)
- Sections: What you get, Process (3–5 steps), Pricing ranges + scope drivers, Proof, FAQs
Measurement and upkeep
- Define one primary conversion (booked consult/estimate). Track click-to-call and form starts/completions.
- Review weekly: which pages create booked consults, which FAQs reduce back-and-forth, and what to expand next.
- Update quarterly: refresh stats, add new proof, polish FAQs from sales/chat insights.
FAQs
- Can I launch with fewer than 12 pages?
Yes—start with Home, 2–3 Services, Pricing, About, Contact, and one Proof page. Add the rest over 30–60 days. - Do I need separate industry pages if my services are the same?
If messaging, regulations, or proof differ by industry, yes. Otherwise, a short “Who we serve” section can suffice initially. - How long should each page be?
As long as it takes to answer buying questions clearly. Clarity and speed beat word count. - Will this help with AI Overviews or LLM citations?
It can—answer-first pages with clean structure, schema, and credible sources are more citeable.
Sources
- Service page blueprint: https://www.reformer.la/service-page-blueprint-that-converts-and-earns-citations-in-ai-answers
- Pricing page blueprint: https://www.reformer.la/service-pricing-pages-that-convert-a-simple-blueprint-you-can-copy-today
- Showing up in AI answers: https://www.reformer.la/how-to-show-up-in-ai-answers-google-ai-overviews-chatgpt-perplexity-the-practical-playbook
- Google SEO Starter Guide: https://developers.google.com/search/docs/fundamentals/seo-starter-guide
Summary
A simple site architecture for small and mid-size businesses: 12 core pages that answer buying questions, convert fast, and make your content easy for search and AI systems to cite.
Author
Peter Mertz