On-page SEO for service pages: a section-by-section checklist

What on-page SEO covers on a service page

On-page SEO covers everything a business controls inside a single page. Off-page work happens somewhere else, such as reviews on your Google Business Profile and links from other websites, while technical SEO looks after the site as a whole: crawling, indexing, speed and redirects.

The three overlap, but the split matters when you're deciding who fixes what. A slow site is a technical SEO job. A hot water page that never says which areas it covers is an on-page job, and usually the quicker of the two to fix, because it's a matter of rewriting words you already own.

Most local service sites have a homepage, a contact page and a set of service pages. The service page is where someone who typed a job and a place lands, and where they decide whether to call. Generic on-page guides are written for blogs and online shops, so they spend their time on keyword placement. A service page has a narrower job: show that you do this exact work, in this area, for people like the reader, and make the next step obvious.

Google's SEO starter guide has a section on things it suggests you shouldn't focus on. It says the length of the content alone doesn't matter for ranking, that keywords in the domain or URL path alone have hardly any effect, and that the order of your headings doesn't matter from Google Search's perspective. Its guidance on helpful content asks instead whether a page clearly shows first-hand expertise and depth of knowledge. That moves the effort away from counting keywords and towards proving you do the work.

The checklist below follows the order a visitor reads a service page in. Work through one page first, ideally the service closest to your revenue, then repeat it across the rest.

• A title and H1 that name the service and the area in plain words.
• An opening paragraph that answers the search directly, in one or two sentences.
• Proof near the top: licence details, real reviews and real job photos.
• Scope and process: what the job includes, what it doesn't, and what happens after someone calls.
• The area you serve, written as a fact rather than a list of suburbs.
• FAQs drawn from real customer questions, with any markup matching the visible text.
• Links up to the hub, across to related services and suburb pages, and a tap-to-call phone link.

Title, H1 and URL: name the service and the area

The title and H1 should say which service the page covers and where, in words a customer would use. 'Hot water repairs in Caboolture' tells a searcher and Google far more than 'Services' or 'Our expertise'.

Google's title link documentation asks for descriptive and concise title elements, distinct text on each page, concise branding, and no keyword stuffing. It also says there's no limit on how long a title element can be, and that Google truncates the title link in results to fit the device. So the 60-character rule quoted in many checklists is a display habit, not a Google rule. What follows from truncation is simple: put the service and the area first, so they survive on a phone screen, and keep the business name short at the end.

Google builds title links from several sources, including the title element and heading elements such as the H1. If the title and the H1 describe different things, Google has more reason to write its own version. Make them agree. The title can carry the brand and the H1 can read a little more naturally, but both should name the same service and place.

URLs matter less than people think. The starter guide says keywords in a URL path alone have hardly any effect and mostly show up as breadcrumbs. A short, readable path such as /hot-water-repairs/ is tidy for people, but don't rename a URL that already ranks just to squeeze a suburb into it. If two of your pages target the same service, read when to merge overlapping pages before you rewrite either of them.

The meta description is a suggestion, not a guarantee of what appears. Google's snippet documentation says snippets are primarily created from the page content itself, and that a meta description is used when it describes the page more accurately. Write one that describes this specific page; long strings of keywords are less likely to be shown. Snippet controls, and how they affect AI features, are covered in search snippets and AI eligibility.

The opening paragraph and proof near the top

The paragraph under the H1 should answer the search in one or two sentences: what you do, where, and for whom. It's the passage most visitors read, and the one a search feature can quote without needing the rest of the page.

At the time of writing (October 2026), Google says a page needs to be indexed and eligible to be shown with a snippet to appear as a supporting link in AI Overviews and AI Mode, and that there are no additional technical requirements. Google's newer guide on generative AI search says ordinary SEO practice still applies, that structured data isn't required for these features, and that there's no need to break content into tiny pieces. There's no trick here. A clear opening helps the reader first, and it happens to be easy to quote. How the feature picks its sources is covered in how Google AI Overviews work.

Compare two openings for the same page. 'With years of experience and a commitment to quality, we're proud to offer a wide range of hot water services' answers nothing. 'We repair and replace electric, gas, heat pump and solar hot water systems across Caboolture and the surrounding Moreton Bay suburbs, and most repairs are booked by phone' answers what, where and how in one sentence. The second version is also the one a person can check against what they need.

Proof comes next. Someone comparing three service pages is checking whether you're real, licensed and any good, and they do it in the first screen. Put that proof where they're already looking rather than in the footer, and keep every item true and current.

• Your licence or registration number, if your trade is licensed in your state, written in text so it can be read and checked.
• Your Google rating or a short excerpt from a real review, linked to where the review lives. Never change a review's meaning, and never write one yourself. Getting more of them is covered in how to get more Google reviews.
• Photos from real jobs of this service, not stock images. Google's image guidance asks for useful, information-rich alt text in the context of the page, and says keyword-filled alt text makes for a poor experience.
• Insurance, memberships or years trading, only where they're accurate and you can back them up.
• A phone number and a quote button visible in the first screen on a mobile.

Scope, process and the area you serve

The middle of a service page should say what the job includes, what it doesn't, and what happens after someone gets in touch. This is where first-hand detail lives, and it's the part a competitor can't lift from a template.

Google's helpful content guidance asks whether content shows first-hand expertise, and lists writing to a particular word count as a sign of search-engine-first content: Google says it has no preferred word count. So write as much as the job needs and stop. A hot water page might cover the system types you work on, the signs that point to repair rather than replacement, what you check when you arrive, and what affects how long a job takes. It doesn't need a history of plumbing.

For the process, three to five steps from first call to finished job is usually enough. Be specific about the things customers worry about: when you'll turn up, whether you quote before starting, what happens to the old unit, and how you leave the site. Don't promise arrival times or turnaround you can't keep every time.

The area served is where many service pages go wrong. Google's spam policies give 'blocks of text that list cities and regions that a web page is trying to rank for' as an example of keyword stuffing, and name pages targeted at specific regions or cities that funnel users to one page as doorway abuse. A paragraph of 40 suburb names doesn't help a reader, and it's exactly the pattern those policies describe.

Describe your area the way you would on the phone instead: where you're based, the regions you cover, any limits, and links to the suburb pages that genuinely exist. Whether those suburb pages should exist at all is a separate decision, covered in when local landing pages deserve indexing and the service area page guide.

FAQs and structured data that match the page

Write FAQs from questions customers actually ask you, answer each one in its first sentence, and make sure any FAQ markup repeats the visible text. Don't add FAQs to chase a rich result: at the time of writing (October 2026), Google no longer shows one.

Google's Search Central changelog records that FAQ rich results were limited to well-known, authoritative government and health websites in September 2023, that the feature would no longer appear in Google Search from 7 May 2026, and that the documentation was removed on 15 June 2026. Plenty of on-page checklists still sell FAQ schema as a way to take up more of the results page. That advice is out of date.

FAQs still earn their place on a service page. They answer the objections that stop someone calling, and an answer that leads with the direct reply is quick to scan. Take them from your phone calls and quote requests: whether you charge a call-out fee, whether you can replace a unit on the same day, whether you take the old one away. Answer what you actually do. If the honest answer is 'it depends' and you can't say on what, leave the question out.

For structured data in general, Google's structured data guidelines say not to mark up content that isn't visible to readers, that markup must be a true representation of the page content, and that Google doesn't guarantee your structured data will show up in results even when it tests correctly. On a service business site, the useful markup describes the business itself: LocalBusiness, or a more specific type, with its name and address. Google's LocalBusiness documentation recommends a telephone number that includes the country code and area code. Schema.org's areaServed property describes 'the geographic area where a service or offered item is provided', which is a cleaner home for coverage than a list of suburbs in the copy. The full picture is in local business schema.

Run these checks after any change to a page's FAQs or markup.

• Every question and answer in the markup appears on the page, word for word.
• The phone number and address in the markup match the page and your Google Business Profile exactly.
• Nothing is marked up that the page doesn't show, such as hours, services or areas that aren't on it.
• The site describes one business entity, not a new business for every suburb page.
• The page still passes Google's Rich Results Test, bearing in mind that a pass doesn't mean any feature will appear.

Links up, across and to the phone

Every service page should link up to its parent hub, across to related services and the suburb pages that exist, and out to a tap-to-call phone number. Those links are how both visitors and crawlers find the rest of your site, and how a ready customer reaches you.

Google's link documentation says Google can generally only crawl a link that's an HTML anchor element with an href attribute, that good anchor text is descriptive, reasonably concise and relevant to both pages, and that every page you care about should have a link from at least one other page on your site. Menus help, but links inside the copy carry the context. 'Hot water repairs in Morayfield' tells a reader where they're going. 'Click here' doesn't.

For a business with several locations or a wide service area, link structure matters more because the pages multiply. A pattern that holds up: the service page links up to the services hub, across to two to four related services, and down to the suburb pages for that service, and each suburb page links back up. The location hub internal links guide covers the full structure.

• Up: the parent services page or hub, linked in the copy as well as the menu.
• Across: two to four related services that a customer for this job often needs next.
• Down: the suburb or location pages for this service that exist and deserve indexing.
• Out: the phone number as a tel: link, so a tap on a mobile opens the dialler.
• Forward: a quote or booking form near the top of the page and again at the end.

Worked example: a plumber's hot water page, before and after

Here's the checklist applied to one page. The business is hypothetical: a plumber based in Caboolture whose hot water page gets visits but few calls. Nothing below describes a real client or a real result; it shows what changes on the page and why.

The before page has the title 'Hot Water | Services' and an H1 reading 'Quality Hot Water Solutions'. The opening paragraph is about the company's commitment to customers. The only image is a stock photo of a smiling plumber, there's a paragraph of 35 suburb names near the bottom, and a contact form sits at the very end. The phone number appears once, in the header, as plain text that can't be tapped.

The after page keeps the same URL, so nothing that already points at it breaks. Each change maps to a step in the checklist, and the table sets them side by side.

On the phone link, the after page wraps every visible number in a tel: link written in international format, so +61 followed by the number with the first 0 dropped, while the visible number stays in the local format people recognise. The same number appears in the hero, after the process steps and in the closing call to action, and it matches the Business Profile and the markup. Wider conversion checks are in the website conversion checklist.

The after page is longer, but length was never the aim. Every addition answers something a caller asks or removes a reason to hesitate. What it can't do is promise a ranking or a number of calls. On-page work makes a page clear and eligible; how it performs still depends on competition, reviews, distance and the rest of the site. If you'd rather someone else worked through your service pages with you, talk to us about SEO.