/seo-content-service-page

name: seo-content-service-page
description: "Spec, audit, competitor benchmark and build for service pages and service landing pages (agencies, consultants, coaches, trades, clinics, law firms, SaaS), plus region and city pages. Input: a service, the business, a target area, the page URL if any. Runs four phases: the spec (SVC-01 to SVC-24 on top of the common C rows), the audit of the existing page with seo_audit.py and section_audit.py --type service, the competitor benchmark with page_benchmark.py on the pages that rank and the providers AI assistants name, and the build on a field-tested 9-block wireframe (hero + CTA, proof, benefits, process, founder with checkable credentials, 750+ word question-led text with price, dated reviews, FAQ, final CTA), with metadata patterns, Service JSON-LD, a GEO layer and a scripted acceptance test. Delivers a spec scorecard, audit findings, benchmark, build and acceptance. Use for a service page, landing page, lead-generation page or city page that gets no organic leads."
license: MIT
metadata:
  author: "Sorank (https://sorank.com)"
  version: "2.0.0"

Service Page SEO: Money Pages That Rank and Convert

Service pages are where rankings turn into revenue. A blog post attracts readers; a service page attracts buyers typing "web design agency", "divorce lawyer geneva" or "emergency plumber lyon", and AI assistants now recommend providers directly from these pages. They usually fail the same way: one page for every service, a slogan instead of the keyword, no price, no named human, 300 words against competitors at 1500, and a single contact form at the bottom.

This skill runs the four phases of the page skill standard (`docs/page-skill-standard.md`): spec, audit, competitor benchmark, build. Two evidence levels are labeled throughout:

• **Field heuristic**: rules derived from 115+ real agency audits of service-business websites (2024-2026). Consistently observed, not lab-measured.
• **Measured**: claims backed by a published study, a benchmark with its date, or official documentation, with the source.

Company knowledge first (Obsidian)

If the working environment contains an Obsidian vault or any local knowledge base (a folder of .md notes, often with a .obsidian directory), read the relevant notes before acting: brand and product facts, target keywords, competitors, and the SEO action log of what was already tried. Ground every recommendation in that context instead of asking the user for facts the vault already holds. At the end of the session, append the actions taken to the vault's SEO action log so the next session starts informed.

When to use this skill

Use it to create a new service page, rewrite an underperforming one, split a one-page site into service pages, plan city or region pages for a multi-area business, or audit an existing money page against the spec below.

Stay in scope. Hand adjacent work to the right skill:

| Task | Skill | |---|---| | Service pages, service landing pages, city pages (this skill) | seo-content-service-page | | Homepage and flagship offer (sales) page | seo-content-homepage | | Blog articles and informational content | seo-content-blog | | Ecommerce product pages | seo-content-product-page | | Category and collection pages | seo-content-collection-page | | "X vs Y", alternatives and segment pages | seo-content-comparison-page | | Block-by-block gap audit of any page type | seo-page-sections | | Keyword selection and SERP intent analysis | seo-keyword-research | | Google Business Profile, reviews, Maps, NAP | seo-local | | Crawlability, Core Web Vitals, AI crawler access | seo-technical | | Structured data implementation details | seo-schema-markup | | Site-wide internal link architecture | seo-internal-linking | | Citation and directory link building | seo-backlinks | | Writing rules for AI answer citability | geo-visibility | | Measuring AI assistant visibility | geo-tracking | | Full-site audit | seo-geo-audit |

Phase 1. The spec

1a. Map services to pages first (one service = one page)

The single most common audit finding (field heuristic): a brochure site with one page that lists every service, invisible on all of them. Each service has its own keyword, its own SERP and its own search intent; one page cannot win five different SERPs.

1. List every billable service the business sells. 2. For each, identify the query a buyer actually types, in buyer language, not internal jargon ("emergency plumber", not "rapid hydraulic intervention"); see seo-keyword-research. 3. Apply the SERP test: if two service names show different top 10 results, they need two pages. If Google returns the same results for both, one page covers both. 4. Plan one URL per service, plus a parent "Services" hub page that links to all of them. 5. If splitting an existing page, 301-redirect nothing that ranks; build the new pages first, then re-point internal links.

Competitor page mapping (field heuristic): to surface missing service and sector pages fast, paste the sitemap or page list of the 10 largest competitors into an AI model and ask it to list the page types they have that the audited site lacks. This exposes one-page sites and absent service, sector and use-case pages in one pass, before manual SERP testing. Cross-check each suggested page against real buyer demand before committing it.

Why: Google ranks pages, not sites, for transactional queries. A page about everything has diluted relevance for each thing. Splitting also gives each service its own title, H1, FAQ and proof, which a combined page cannot do.

1b. The service page spec

Common requirements C-01 to C-27: skills/seo-geo-audit/references/common-page-spec.md. Every C row applies to a service page; the rows below add what is specific to it. "Verified by" is a `seo_audit.py` finding code, a `section_audit.py --type service` block, or manual.

| ID | Requirement | Threshold | Verified by | Why | |---|---|---|---|---| | SVC-01 | One service