One job. One page. One phone call.

Page type

Which page is this? Two rules settle it.

People mix up two page types constantly, and building the wrong one wastes months. Here are the 2 rules.

Why it matters that much. A service page answers can you fix this? A town page answers are you actually here? Those are different questions from different people, and a page that tries to answer both answers neither.

There is a second reason, and it is the expensive one. When you build 7 pages that are the same job with a different town pasted in, and nothing links to them, you have built what Google calls a doorway. Their spam policy names it directly.

Doorways are sites or pages created to rank for specific, similar search queries. They lead users to intermediate pages that are not as useful as the final destination. Google Search spam policies, read September 3, 2026 · 1 source

The defense is not writing better copies. The defense is a real structure where each page has its own job.

Intent

The buying question is "can you fix this?"

Somebody standing in a cold shower is not shopping for a plumbing company. They are trying to make one thing stop. They are not reading about your 30 years in business until they believe you can fix the thing.

So every block on the page answers one of 4 questions, or it gets cut.

1. Do you fix this exact thing?
2. Do you know why it happens?
3. What happens if I wait?
4. What do I do next?

Read your current service page and mark which question each paragraph answers. The paragraphs that answer none of them are why the page is long and still not working.

Architecture

The order of the page, and what each block is for.

The order is fixed. 9 blocks. Writers do not get to reorder it, because the order follows how a worried person actually reads.

The hero

The first screen has to do three things.

You get about 3 seconds. In that space the page has to say what it is, prove it is local, and give them a way to call.

• The headline names the service and the city. "Water Heater Repair in Austin, TX." Not "Welcome" and not "Quality You Can Trust."
• One sentence that answers the question. Say you fix it and roughly how fast.
• A phone number they can tap. Not a form. Not a chat bubble. The number.

The title tag and the headline are not the same string

This one gets missed on almost every page we audit. The title tag is what competes in the results list against 9 other titles. The headline is what confirms they landed in the right place. Those are two different jobs, and one string cannot do both.

The title adds the thing that makes somebody click, and it ends with the company name. The headline stays clean. Keep the title between 50 and 60 characters or the end gets cut off.

Key takeaways

Five bullets at the top, and why they are not decoration.

Under the hero, put a short box of 3 to 5 bullets. Most people will read that box and nothing else until they decide to stay.

What does not belong in it: your founding year, your mission, or the phrase "we pride ourselves." Those are about you. The box is about them.

This box is also the block most likely to get read out loud by a voice assistant, because it is short, it is near the top, and it is already in list form.

The mechanism

Say why it happens here, or a machine will paraphrase you.

The mechanism block explains why the problem happens. It is the block that separates a real service page from a template, and it is worth more than everything else on the page.

Here is the part most people miss. When an AI assistant answers a question, it either quotes a source or it paraphrases one. A quote usually carries the business name. A paraphrase does not.

Generic text gets paraphrased, because the assistant can safely reword it. Text with a specific local detail in it gets quoted, because rewording it risks getting the detail wrong. So the local detail is what earns you the mention.

Both sentences are true. Only one of them could have been written by this company.

Where that detail comes from: the service facts interview

Nobody can invent these at a desk. They come out of a technician in about 15 minutes. Ask these 8 questions and write the answers down verbatim.

Every answer has to fail the swap test. Rewrite it for a competitor in the next town. If it is still true, it was never a fact about you, and it does not go on the page.

We should be straight about something here. We built this interview for town pages first, and the version for service pages is new. It is the piece most companies are missing, including companies with otherwise good pages.

Proof, process, waiting

The three blocks everybody writes badly.

Blocks 5, 6 and 7 are where most service pages turn into brochure copy. They are also the blocks that answer the questions a nervous person is actually holding.

Proof means proof of this job, not of the company

A proof block that says "family owned since 1998" is company proof. It appears on every page of the site and it says nothing about whether you can fix a water heater.

Service proof is different. It is the warranty on this repair, the license that covers this work, and what your reviews say about this specific job. Pull the sentence out of a real review that mentions the actual service. That beats a star rating, because a star rating is a number and a sentence is evidence.

The test: if the proof block would read exactly the same on your drain cleaning page, it is not proof, it is a footer that wandered up the page.

Process removes the fear of letting a stranger in

People are not only worried about the repair. They are worried about a stranger in the house, a mess, and a bill that grows once the work starts. The process block exists to remove those three worries in order.

• What you ask on the phone, so they know the call is short.
• Whether they get an arrival window, and what happens if you run late.
• When they find out the price, and whether it can change after that.
• What you do about the mess and the old parts.

Number the steps. It is a sequence, and a numbered list tells somebody it has an end. Keep it to 5 steps or fewer. A 9 step process reads as bureaucracy, not care.

The cost of waiting is a story, not a warning

This is the block that moves somebody from reading to calling, and almost nobody writes it. The mistake is writing a threat. "Don't wait until it's too late" is a threat and everyone ignores it.

Write what actually happens instead. A water heater that drips for a month does not flood a house. It soaks the subfloor, the baseboard, and whatever is stacked beside it in the garage. The heater is the cheap part of that repair. The flooring is not.

That is concrete, it is true, and it does the work a warning cannot. Then give them the one thing they can do right now, even if they do not call you. Tell them where the shutoff valve is. Being useful before the sale is the most persuasive thing on the page.

One caution on this block. Do not put a number on the damage unless you can stand behind it. A made up repair cost is the fastest way to lose somebody who has just had a quote from a competitor and knows what the real figure looks like.

The copy

How it should sound, and the words that get cut.

Write it the way you would say it standing in somebody's garage. That is the whole rule. Here is what it means in practice.

• Sentences average under 18 words. Ours on this page average 11.
• If a plumber on a job site cannot read it in 3 seconds, rewrite it.
• One idea per sentence. Two ideas need two sentences.
• Say the plain word. "Booked jobs," not "conversions." "Missed calls," not "lost leads."

The words that get cut

Two more rules that catch a lot of bad copy. No em dashes. They are a writing tic and they read as machine written now. Use a period. And no claim without a source. If the page says 500 jobs a year, somebody has to be able to point at where that number came from. A number nobody can trace is worse than no number, because it is the one a customer will check.

Images

Pictures that prove something, and where they go.

Aim for 5 to 7 images on the page. Fewer than 3 and the page reads as a wall of text on a phone.

The rule for what they show is short: your own work, your own trucks, your own people. A stock photo of a smiling man in clean coveralls does nothing, and most homeowners recognize it instantly.

The two things people get wrong

Alt text describes the picture, it does not repeat the keyword. "Plumber draining sediment from a water heater tank into a bucket" is right. "water heater repair austin tx" is not, and it helps nobody using a screen reader.

The picture in the mechanism block is the one that earns its place. If you only ever get 1 real photo from a job, make it that one. It shows the thing you just spent three paragraphs explaining.

Styling

How it should look, and what not to let a designer do.

This is not a brand guide. It is the short list of layout decisions that change whether the page works on a phone at 7 in the morning.

• One column of text, about 70 characters wide. Long lines are why people stop reading on a laptop.
• Body text at 16 to 18 pixels, line height near 1.6. Smaller than that is a phone accessibility problem, not a style choice.
• Headings clearly bigger than body. If someone scrolls fast, the headings alone should tell the story.
• Separate sections with space, not lines. Horizontal rules everywhere is a tell that nobody thought about spacing.
• The fix block is a two column checklist, not paragraphs. It is the block that answers "what am I paying for," so it has to be scannable.
• Tap targets at least 44 pixels tall. That is a thumb, not a mouse.

Bullets

Bullets or paragraphs? The block decides.

This is not a style preference, it depends on the block. We measured 7 well written service pages recently and found 0 bullet lists in the body of any of them. Every one was paragraphs under a lot of subheadings. They were still good pages, and they were still harder to scan than they needed to be.

The test: if a reader could skip your bullets and lose nothing, they were decoration. If a reader could skip your paragraph and lose nothing, it should have been bullets.

Calls to action

The phone goes in four places.

This is the one that costs the most money when it is wrong. Of the 7 pages we measured, 4 had 0 tappable phone links anywhere in the body. On emergency service pages. That is not a small miss.

Put the number in 4 places, minimum 2 of them tappable links inside the page body.

1. The header. Visible before any scrolling.
2. The hero. As a real button, next to the headline.
3. After the fix block. They now know what you do. Ask.
4. The final call block. The last thing on the page.

On a phone, add a sticky bar at the bottom with the number in it. It follows them down the page, and it is the single highest value thing on a service page for a trade where people call in a panic.

Say what happens next to it. "We answer at night" beats "Contact us today" because one of them is information.

The FAQ

Questions people actually ask, and the code that counts them.

Between 3 and 6 questions. Answers between 40 and 100 words, with the answer in the first sentence.

Get the questions from the phone, not from a keyword tool. Ask whoever answers the phone what people ask before they book. Those are the real ones, and they are usually about time, mess, cost and whether they have to be home.

Answer the second one and you have a page a person trusts. Answer the first one and you have filler.

Be honest about what the code does for you here

Mark the FAQ up with FAQPage structured data. But know what it now buys you, because a lot of advice on this is out of date. Google restricted FAQ rich results in 2023.

Updated the FAQ structured data documentation to state that the feature is only shown for well-known, authoritative government and health websites. Google Search Central changelog, read September 3, 2026 · 1 source

So a plumbing company will not get the expandable questions in the search result. Anyone promising you that is selling something. Keep the markup anyway. It is clean, machine readable question and answer text, which is exactly the shape an AI assistant wants to read. The rich result is gone. The value to answer engines is not.

Schema

The code the page carries.

4 blocks of structured data. This is the one section of this playbook where nearly every rule comes from published documentation rather than from us.

Three rules that catch most of the mistakes we see.

• The business gets a stable id and the service points at it. Give LocalBusiness an @id like https://yoursite.com/#business, then have Service.provider reference that id. Otherwise every page invents a new company.
• The markup can only say what the page says. Structured data describing content that is not visible is a 1 documented violation, and it is also just lying in a format machines read literally.
• Every value has to be true. A wrong phone number in schema is the wrong number an AI assistant will read out loud. Schema is the one place an error gets repeated perfectly.

The reference pages are worth reading rather than trusting a plugin: local business, breadcrumbs, and Service on schema.org.

Internal links

Links go sideways and out, never in a ring.

At least 3 links from the body to your own pages. The direction matters more than the count.

• Sideways, to 2 or 3 other services the same customer plausibly needs next. Water heater repair links to tankless installation and to water softeners.
• Out, to the town page for the city this page names, if you have one.
• Onward, to booking or contact.

What fails: 3 links that all go to the contact page. That satisfies a checklist and helps nobody. The test is whether a reader who finishes this page still holding a problem can get where they need to go in one click.

Never link to a page that does not exist yet. A broken internal link is worse than no link.

Length

How long, and why length is not the lever.

Target 1,200 to 2,500 words. Most good service pages land in the middle.

Now the honest part, because length advice is where most SEO writing goes wrong. We looked at 626 pages across 10 client sites joined to Search Console. Service pages under 600 words sat at a median position of 11 with a median of 1 click in 90 days. So thin pages really do lose.

But pages over 600 words sat deeper on average, not higher. Length alone did not rank anything. The range above is room to be specific, not a lever to pull. A 2,000 word page that says nothing only wastes more of somebody's morning.

Write until the 4 buying questions are answered with facts only you have. Then stop. If that takes 1,300 words, you are done.

What to fix first

The stop doing list.

These are the 7 things we find most often. We found them by measuring our own client pages against our own rules, and they failed. That is where this list comes from, not from a competitor's site.

1. No tappable phone number in the body. 4 of 7 pages we measured. Fix first.
2. An FAQ on the page with no FAQ markup. 6 of 7 rendered questions and told machines nothing.
3. No breadcrumb markup. 0 of 7 had it.
4. The title tag and the headline are the same string. All 7. One of the two jobs is not being done.
5. No takeaways box. The block most likely to be read, missing entirely.
6. Zero bullets in the body. Everything as prose, which makes the page unscannable on a phone.
7. A town in a service page address. That makes it a town page, and it belongs in a different structure.

Score under 7 out of 10 and the page is leaving calls on the table. The first 4 rows are the ones worth fixing this week.

Two readers

Two ways in. One per reader.

Sources

What we do not know yet.

Every number on this page carries a small mark. A red mark means it comes from a published source we link. A gray mark means it is our own standard or our own measurement.

Most of the marks here are gray, and we would rather say that than dress opinion up as research. There is very little published research about service pages for local trades specifically. What exists is mostly about big publishers, and it does not transfer.

How this page is built to age

We split the rules into 2 kinds on purpose. Some are machine facts: the markup exists or it does not, the phone link is tappable or it is not. Those do not go stale. The rest are house taste, like a word count range or a heading limit, and those are dated so you know what to question later.

When we raised our own heading ceiling from 8 to 14 in September 2026, it was because our own best pages broke the old number and read fine. The number was ours, it was never sourced, and it was wrong. Assume the same about any other unsourced number here, including ours.