Service pages

When to use a service page

Use a service page for:

• A specific service offering you want to win prompts for.
• Pages where the buyer intent is "buy" or "hire," not "learn."
• Anything you'd describe to a sales prospect as "we do X."

Skip service pages for:

• Educational content (use articles).
• Geographic targeting (use location pages).
• Head-to-head (use comparison pages).

Anatomy of a generated service page

1. H1 — service-noun first. "Penetration testing services" beats "We offer pen testing."
2. One-paragraph value statement. Who it's for, what they get, why us.
3. What's included. Specific deliverables, named, in a list.
4. Process or methodology. 4–6 steps with timing estimates.
5. Proof. Logos, case-study link, certifications, headcount with the relevant expertise.
6. Pricing or pricing model. Even a range ("starts at $X" / "engagements typically $X–Y") helps both buyer trust and AI citation.
7. FAQ. 4–6 buyer questions with concise answers.
8. CTA. A specific next step — "book a discovery call" beats "contact us."

Starting a service page

Content → New → Service page.

• Service name. Use the exact phrase a buyer would type.
• What's included. Bullet list of deliverables; the engine elaborates.
• Audience. Industry, company size, role.
• Pricing model. Fixed / hourly / project / retainer / "let's talk."
• Proof you can share. Logos, certifications, case studies, customer counts.

Pricing transparency vs. opacity

Buyer research shows transparent ranges build more trust than "contact us." The engine prefers a range when you supply one. If your pricing is genuinely bespoke, it writes a hedged version ("typical engagements run $X–Y depending on scope") that still gives the buyer a frame.

The compliance scanner blocks invented numbers. If you don't supply pricing, the section is omitted.

CTAs that convert

Specific beats vague. The engine generates:

• "Book a 30-minute discovery call" (better than "contact sales")
• "See a sample report" (better than "learn more")
• "Get a quote in 1 business day" (better than "request a quote")

CTAs are configurable per service in Settings → Conversions → CTAs.

Multiple services

A typical agency or consultancy has 6–20 distinct services. Generate one page per service, link them from a hub page, and submit the hub to your CMS sitemap. The engine handles the cross-linking automatically when you use the Service hub content type (Domination).

Schema

Every service page emits Service schema with the right provider, areaServed (if applicable), and offers blocks. Schema is validated before publish.

What service pages do NOT do

A service page is not an article. The engine resists turning it into one:

• No padding paragraphs.
• No "what is X?" definitional intros — the buyer already knows.
• No off-topic context.

If you want educational depth on the topic, write a sibling article and link from the service page. The two pages support each other.

Updating

Services evolve. Refresh from sources re-pulls your latest service offerings list (from your workspace settings) and proposes diffs to existing service pages. Useful when you launch a new tier, retire a service, or change pricing.