The Local SEO Checklist for Service Businesses

Most "local SEO checklists" are 40 items long, mix trivial and critical fixes together, and give you no sense of what actually moves the needle. This one is ordered by leverage: the things that affect whether you show up in the map pack and organic results at all come first. Formatting nice-to-haves come last.

If you only have a weekend, do sections 1 and 2. That's where most of the ranking impact lives for a business that hasn't touched local SEO before.

1. Google Business Profile — the foundation

For most "near me" and "[service] in [city]" searches, Google shows the map pack (three local results with a map) above the organic listings. Your Google Business Profile is what feeds that map pack. If it's incomplete, inconsistent, or dormant, nothing else on this list can fully compensate.

• Claim and verify it if you haven't — this alone is table stakes, not an optimization.
• Match your business name exactly to your signage and legal name. Adding keywords to your GBP name ("Smith Plumbing — Emergency 24/7 Plumber") violates Google's guidelines and risks a suspension.
• Pick the most specific primary category available ("Emergency Plumber" over "Plumber" if that's genuinely your focus), plus every accurate secondary category.
• Fill in every field: services, service area, hours (including holiday hours), attributes, and a complete business description.
• Upload real photos regularly — team, vehicles, completed jobs, the physical location if you have one. Stock photos are worse than no photos.
• Post weekly, at minimum. GBP Posts are a direct signal that the profile is active, and they give you a place to put offers, recent jobs, and seasonal messaging.

2. Citations and NAP consistency

"NAP" is Name, Address, Phone. Google cross-references your NAP across the web — Yelp, Apple Maps, Facebook, industry-specific directories, the Better Business Bureau — as a trust signal. Inconsistent listings (an old suite number here, a missing area code there) dilute that signal and can actively confuse Google about which business is real.

• Search your business name + old addresses/phone numbers to surface outdated listings you forgot existed.
• Fix or claim the major generalist directories first: Google, Bing Places, Apple Maps, Facebook, Yelp.
• Add 5–10 relevant industry-specific directories (e.g. Angi and HomeAdvisor for home services, Avvo for legal, Healthgrades for medical).
• Use the exact same format everywhere — if it's "St." on your GBP, don't let it become "Street" on Yelp.

3. On-page fundamentals for service + location pages

If you serve multiple cities or offer multiple services, this is where most sites either compound their advantage or accidentally build duplicate-content problems.

Build one page per service/city combination that's genuinely distinct

A page for "HVAC repair in Newark" and one for "HVAC repair in Jersey City" should not be the same template with the city name swapped. Include real local context — service area specifics, response-time expectations for that area, local landmarks or neighborhoods if relevant. Thin, swapped-city pages are a well-documented pattern Google's Helpful Content systems are built to detect and suppress.

Title tags and meta descriptions

• Include the service and the city in the title tag, close to the front: "Emergency Plumber in Newark, NJ | [Business]."
• Write a meta description that gives a reason to click — not just a repeat of the title. It doesn't affect rankings directly, but it affects click-through, which does.
• Keep titles under ~60 characters and descriptions under ~155 so Google doesn't truncate them.

Headings and structure

• One H1 per page, containing the primary service + location term naturally.
• Use H2s to break the page into scannable sections (pricing, process, service area, FAQ) — this also helps AI answer engines extract and cite specific sections.
• Add FAQ content with real questions customers actually ask, marked up with FAQPage structured data.

4. Reviews — volume, recency, and response

Review count and rating are a direct local ranking factor and the single biggest trust signal for anyone comparing you against competitors in the map pack.

• Ask at the right moment — right after the job is done and the customer has expressed satisfaction, not three weeks later in a generic email blast.
• Make it a two-tap process. A direct link to your GBP review form removes the single biggest source of drop-off.
• Respond to every review, positive and negative. A thoughtful response to a negative review, visible to every future prospect, often does more for conversion than the review itself did damage.
• Never buy or incentivize reviews. It violates Google's policies, and the detection has gotten good enough that it's not worth the risk to the whole profile.

5. Technical basics that quietly cap everything above

None of these are glamorous, and none of them will single-handedly rank you — but a failure in any one of them puts a ceiling on how much the other four sections can achieve.

• Mobile page speed. Most local searches happen on a phone, often on the go. A slow-loading page loses visitors before Google's ranking algorithm even becomes relevant.
• A real XML sitemap, submitted to Google Search Console, so new and updated pages get discovered promptly.
• HTTPS — non-negotiable at this point, both for trust and because Google treats it as a baseline ranking signal.
• LocalBusiness structured data on your site, matching your GBP details exactly.
• Internal links from your homepage and relevant service pages into your city/service pages — pages that only exist in a sitemap and are never linked to from anywhere else on the site get crawled less often and treated as lower priority.

The order to actually do this in

If you're starting from zero: Google Business Profile completeness first (it's free and fast), then citation cleanup, then on-page fixes to your top 3–5 service/city pages, then start the review-request habit — and keep it running indefinitely, since reviews decay in relevance and recency matters. Technical basics can happen in parallel since they're mostly one-time fixes.