Write clear titles, headings and page addresses

In the last lesson, Sam planned what ClearFlow's service pages should explain. The water heater repair page will help Austin homeowners understand that service and get in touch. The drain cleaning page has its own job. Both pages keep their existing addresses.

Sam is ready to work on the small pieces of information that tell people what each page is about: the SEO title, meta description, headings and URL.

These may look like tiny details in a website editor. But they need to agree with the actual page. If the title promises one thing and the page explains something else, the visitor gets a confusing experience.

Open a page in your usual website builder and you may see fields labeled SEO title and meta description. On the page itself, you see headings. The browser has a page address.

Here's how Sam thinks about them:

Think of it this way: the SEO title introduces the page in its settings; the H1 introduces it on the page; the H2s help visitors find the details. All of them should tell the same basic story.

The SEO title and H1 don't have to use identical wording. Their job is to describe the same page clearly.

Sam opens the draft for the existing page at clearflow.example/water-heater-repair.

Notice what Sam hasn't done. Sam hasn't introduced an extra service, created a second repair page or changed the address. The SEO title, summary and visible headings describe the service that was already agreed in the page plan.

Sam checks how the information would read as a search result.

This helps Sam judge whether the result would make sense to the right visitor.

One useful thing to know: Google chooses the search-result title and description. It can build the title from the title element, headings and other signals. It usually draws the description from page content and may use the meta description when that provides a useful summary. So Sam writes accurate, helpful fields rather than trying to force an exact search appearance.

Now Sam checks the two service pages side by side.

The pages use a similar format because they belong to the same website. Their purpose and content are different because a water heater problem is not a drain problem.

The homepage still introduces the company and both services. Its main heading from the page plan remains “Plumbing help for Austin homeowners.” It doesn't need to become another detailed water heater repair page.

A small amount of shared wording is normal across a website. What matters is that each page is useful for its own visitor need.

That clarity is useful beyond a traditional Google search too. If someone discovers ClearFlow through an AI-powered search experience, the website still needs to explain the real services clearly. Sam does not need a separate “AI version” of the page.

Sam looks at the water heater page in the design editor.

A large font doesn't automatically make text an H1. The heading level is part of the page structure, and Sam should set it deliberately.

For this page, a clear layout is:

• H1: Water heater repair in Austin
• H2: Ask about water heater repair
• Body text: What ClearFlow offers, who it serves and how someone can make an inquiry

Later, when the owner provides more service details, Sam may add another relevant section. But extra headings are useful only when there is something meaningful to explain beneath them.

The rule isn't to stuff keywords into every heading. Make the page easy to scan and keep the sections in a sensible order.

Sam notices that the existing URL is /water-heater-repair rather than /austin-water-heater-repair.

Would adding “Austin” to the address make it better?

The current address is already short, readable and accurate. The page's SEO title, H1 and actual content explain the Austin service area. Sam keeps the existing URL.

Changing an established page address can affect old links and requires a proper plan for the old address. That becomes especially important in a redesign, which we'll cover later in the course.

Sam also keeps the earlier indexing issue on the technical follow-up list. A better SEO title won't fix an instruction that prevents a page from appearing in Google. The current setting still needs to be checked before any technical change is approved.

Sam returns to Cedarline's /services draft from Lesson 2.

It has one job: explain Cedarline's website design, redesign and care services. Its visible main heading already says that clearly.

Sam can give it an SEO title that matches:

SEO title: Website Design, Redesign & Care | Cedarline Web Studio
Existing draft H1: Website design, redesign and care
URL: /services

Cedarline's homepage still introduces the overall studio. The /services page explains each offer in more detail, including the Redesign an existing website section. No extra page is needed just because two pages mention web design.

Try the same check on your own studio website: does the title match the page's main job, and would the visitor find what it promises?

Sam now has a useful page specification: what the SEO title says, how the description introduces the service, which heading visitors see and which existing address should remain.

The same thinking applies to Cedarline's studio website. Start with the page's job, then choose the words that help people understand it.

These are still drafts for owner review. Sam hasn't published a redesign or cleared the indexing follow-up. The next step is to check how the pages work on actual screens.