Title tags and headings that match search intent

A title can be tidy and still describe the wrong page. A heading can contain the expected phrase and still leave the reader wondering where the answer is. Before adjusting either, decide what someone came to the page to do. The useful question is specific: are they trying to complete a task, compare alternatives, understand a concept, or find a particular resource?

This guide uses an invented example throughout: a help article for a scheduling application, written for someone who wants to let customers reschedule an appointment. The exercise is editorial. It shows how to connect a title, main heading, and introduction to one reader task. It does not predict a ranking outcome or suggest that one wording choice will produce a particular amount of traffic.

Start with the page you actually have

Open the draft and write a plain sentence about its purpose. For the example, that sentence could be: “Help an account administrator enable customer rescheduling and understand the cutoff setting.” That is more useful than “target appointment scheduling keywords.” It names the person, the action, and the important condition. You can now compare each prominent part of the page with that purpose.

Check whether the body can deliver the stated outcome. If it only explains why flexible appointments matter, it is not yet a setup guide. You have two reasonable choices: add the missing instructions or describe the existing explanatory article accurately. Rewriting the title to promise a task the body cannot support creates a mismatch that better phrasing alone cannot repair.

Look at the reader's likely starting point as well. An administrator who already has an account may need a menu path and a permission requirement. Someone comparing products may want to know whether rescheduling is available at all. Those readers can share vocabulary while needing different pages. Choose the primary job and link to the neighboring task when it genuinely helps.

Write a title that stands alone

Suppose the draft title is “Flexible appointments for modern teams.” It sounds pleasant, but it does not identify the setup task. A more descriptive option is “Let customers reschedule appointments: setup guide.” If the page is tied to a specific product, a concise product name can help distinguish it. Use a real name only when it accurately identifies the software being documented.

Google's title-link guidance recommends descriptive, concise title text and explains that its search result titles can draw on several page signals. The title element is an input, not a guarantee of the exact text shown in search. Google may use the visible main title or other relevant text when generating a title link.

For your own edit, read the proposed title without the website around it. Does it still identify the subject? Does it promise a guide, comparison, checklist, or explanation that the page actually contains? Remove repeated phrases that add no distinction. A brand suffix can be useful, but it should not consume so much attention that the page's specific subject becomes hard to recognize.

Let the H1 orient the arriving reader

The H1 can closely resemble the title without being forced into an identical string. In the example, “Set up customer rescheduling” is a direct visible heading. It confirms the task as soon as someone arrives. A subtitle can supply a qualification, such as which account role can change the setting, if that qualification is accurate and important to the instructions.

Avoid giving several headings the visual prominence of a main title. A page can contain a large promotional message, a product name, and an article heading, but their roles should be clear. For this help article, the task heading should be the obvious entry point. The surrounding design should help a reader locate the instructions rather than make them choose between competing introductions.

Read the title and H1 together. They should describe the same page even when they use different phrasing. A title promising a comparison of scheduling tools would not fit an H1 about changing one setting. If the pair feels inconsistent, revisit the page purpose before trying to solve the mismatch by repeating a keyword in both places.

Use the introduction to confirm scope

A weak introduction often repeats the heading and then delays the useful detail. “Rescheduling is important in today's busy world” does little for someone already looking for instructions. A more useful opening for the example would explain what the setting allows, who can change it, and what the reader should have ready. Keep any claims tied to the actual product behavior.

An illustrative opening could read: “Enable customer rescheduling in your booking settings, then choose how close to the appointment a change is allowed. You will need an administrator account. This guide covers the customer link and cutoff setting.” A real page would need to verify those details against the product. The point is the structure: outcome, prerequisite, and boundary.

Do not put every possible exception in the first paragraph. If a rule only affects a particular booking type, introduce it where the reader makes that decision. The opening should help someone judge whether they are in the right place. It should also make a wrong fit easy to recognize, with a useful link to the related task when one exists.

Build the H2 outline in the order of the task

For the example page, a sensible outline might be “Check your account permissions,” “Enable the customer rescheduling link,” “Set the change cutoff,” and “Test the customer experience.” That sequence follows the work. A final troubleshooting section can address common obstacles after the main path is complete. Each heading should introduce material that belongs under it.

Compare that outline with vague labels such as “Overview,” “Our solution,” and “Get started.” Those labels may work in some contexts, but here they hide the practical steps. Specific headings let a returning reader jump to the cutoff setting without rereading the full article. They also make it easier for the editor to notice that a required step has been omitted.

Use subordinate headings where they clarify a real grouping. If the testing section has separate instructions for desktop and mobile, those could be H3s beneath the same H2. Do not choose a heading level simply because its default font looks right. Keep the document structure understandable, and let the page styling control the visual size of each level.

Review links and examples against the same intent

A setup guide may need links to account permissions, cancellation rules, or customer notifications. Place those links where the reader needs the related detail. Descriptive link text can explain the destination before the click. A long list of loosely related articles at the top would interrupt the task; a relevant reference beside a decision can support it.

Examples should reduce ambiguity. If the cutoff setting is expressed in hours, a verified example could show what one setting means for a particular appointment time. Check that the example respects the product's timezone behavior and other rules. When those details are unknown, flag them for a product expert rather than filling the gap with an assumption that sounds plausible.

Finish with a short rewrite check

Read only the title, H1, introduction, and H2s. A colleague should be able to tell who the page is for and what it will help them do. Then read the body and confirm that every promise in that short version is fulfilled. This two-pass check catches both an unclear outline and an appealing outline attached to incomplete instructions.

Save the previous wording with the reason for the change. That record is useful when a stakeholder asks why a familiar heading moved or when the product changes again. After publication, check the rendered page and any relevant feedback from readers. Treat a revision as a considered editorial decision that can be reviewed, rather than as a formula that must work everywhere.

Choose one page today. Write its purpose in a sentence, revise the title to describe it, align the H1, and rebuild the opening and outline around the reader's next action. If you cannot make those pieces agree, the page may be trying to do two jobs. Splitting or narrowing the content may be the most useful edit.