Service-Area Page Launch Checklist ================================== A pre-publish checklist that confirms a city or service-area page has the local substance, contact details, and technical basics it needs before it goes live. [ ] The page names the city plus the specific neighborhoods, subdivisions, or ZIP codes you actually serve there. [ ] The first screen states plainly that you serve this place, which services you offer there, and how to reach you. [ ] Any service you do not offer in this city, or only offer within a closer zone, is stated rather than hidden. [ ] At least one review from a customer in this city is quoted, and the city is named in or next to the review. [ ] At least one photo from a real job site in this city is on the page, with alt text that describes the job and the place. [ ] The page mentions at least three details that would be false for the neighboring town: housing age, water conditions, permit rules, common problems, or travel time from your base. [ ] The typical response or arrival time from your nearest base is stated, and whoever dispatches your crews agrees it is accurate. [ ] Read the page with the city name covered: if it could be about any city, go back and collect more specifics before publishing. [ ] Compare the page against the two most similar city pages on your site: the local half differs in substance, not just in the city name. [ ] Job counts, review counts, and years-in-service figures on the page are ones you can back up from your own records. [ ] The phone number is tap-to-call on mobile and matches the number on your business profile and other pages. [ ] The contact form asks only for what you need to call back: name, phone, address or ZIP, and a short description. [ ] Business hours, license number, and insurance statement match every other page on the site. [ ] The title tag and H1 name the service and the city once each, and read like something a person would write. [ ] The meta description says what you do in this city and invites a call; it is not a list of keywords. [ ] The page links to the relevant service pages, the regional page it belongs to, and one or two neighboring city pages that are genuinely related. [ ] The regional page and the site navigation or footer link back to this page, so it is not orphaned. [ ] The URL is short and stable, and the canonical tag points to the page itself. [ ] Images are compressed and sized for phones, and the page loads quickly on a mobile connection. [ ] Structured data for the business includes the area served, and it validates without errors. [ ] The page is not blocked by robots rules or a noindex tag, and it appears in the sitemap. [ ] A named person owns this page, and the date to re-check its details is on the calendar.