Before writing a service page, collect the real service facts: what is offered, who it helps, where it is available, what proof exists, what is not included, and what the visitor should do next.
Give owners a copyable brief that turns real service facts into one useful web page without stuffing, duplicate pages, or invented proof.
Audience: Small-business owners preparing a website build, redesign, or SEO content sprint.
Distinct from redesign, AI-search, indexing, structured-data, accessibility, and contact-form pages: this page owns source gathering before writing one service page.
Name one service and the customer problem it solves. Avoid building a page around a keyword alone; the page should explain a real offer, process, limitation, and next step.
Decide whether the page is a core service, a local service-area page, a resource, or a comparison. That choice determines links, proof, CTA, and whether the page risks duplicating another page.
Gather photos, process details, service-area notes, FAQs, constraints, certifications, before/after examples, or owner experience that can be shown truthfully. Do not invent reviews, years in business, rankings, awards, prices, or client results.
A useful brief also lists what the service does not include, what details require a conversation, and which related pages should be linked for context.
Fill in title, H1, meta description, visitor problem, included/not included, proof block, common questions, internal links, and CTA. Keep the structure helpful before asking how many words it should be.
Review the draft against search guidance: no stuffing, no fake expertise, no magical word count target, and no content made only because a tool suggested it.
Use this as a review checklist before publishing, automating, or handing the work to a vendor.
No new form fields or guarantee of rankings.
These references support the public planning guidance above.
