Match a page to a real search need
List the task the page serves, the questions visitors bring, and the next action they should be able to take. Choose a descriptive page title and main heading. A service page should quickly explain scope and eligibility; a guide should answer the question with enough detail to be useful.
Match the page to the intent behind the query
Choose one main job for each page. If the site sells office cleaning, the service page should explain capacity, location, supervision and how quoting works. A guide to cleaning frequency can answer planning questions. Review current results for the queries you care about and compare the page formats you see, then decide whether users need information, a price range, a product or a provider.
- Match the queryIdentify the specific decision the page helps with
- Improve the pageConnect title, headings, evidence and useful links
- Validate liveCheck the phone journey and search directives
Make the page easy to find and use
Add internal links from genuinely relevant pages with descriptive anchor text. Check the preferred URL and indexing controls. Give useful images accurate alt text. Keep prices, specifications or service areas visible as text where customers need them.
Improve the title, headings and content together
Write a distinct title that names the service or product and adds meaningful context. Use a readable H1 and descriptive subheadings. The opening paragraph should confirm that visitors landed on the right page. Make specimen photos, specifications or trust information easy to find. Use relevant phrases naturally and write descriptions that represent the page. Google may use page content to generate the snippet instead.
Check before and after release
Read the mobile page through to its primary action, then inspect the live URL and record the release date. Review impressions, clicks and conversions for that page. If it gains visibility for the wrong searches, revisit the copy and intent rather than adding more variations of the same keyword.
Check links and accessibility on a real phone
Link from pages with a sensible customer path. Use descriptive link wording and check important navigation in rendered HTML. Write alt text for images that convey unique information and leave decorative images empty. Check your form, pricing information and call button on a small phone. Inspect the live URL after release and annotate your analytics so you can compare post-change performance.
Map one primary purpose to each page
Identify the customer question, intended audience, and next action before editing metadata. A service page and an informational guide can discuss the same subject while serving different needs. Avoid making several pages compete for an identical purpose without a clear distinction.
Write a title that matches the content
Describe the specific offer or answer, then add the brand where useful. Check how the title reads alongside the visible heading and introduction. Do not promise a comparison, calculator, or free resource that the page does not actually provide.
Use headings as an outline
Organize the explanation into useful decisions and steps. A reader should understand the page’s structure by scanning its headings. Use emphasis and brand colours for presentation while retaining real heading elements and a sensible hierarchy in the underlying HTML.
Review links and image descriptions
Link to relevant next steps with descriptive text. Give informative images concise alternative text describing their purpose; decorative artwork can use an empty alt attribute. Compress images and reserve their dimensions so accessibility and loading performance improve together.
Check the whole mobile journey
Test navigation, tables, forms, and confirmation messages on a narrow screen. Confirm that the form saves and reaches the team rather than judging success by a button animation. Track meaningful actions so on-page changes can be evaluated against enquiry quality.
An on-page refresh for an HVAC contractor
A contractor sees impressions for emergency repairs but few clicks. Instead of adding the phrase everywhere, it creates a concise title, defines the service area, states staffed hours and links to a scheduling page. It tracks calls and completed forms alongside clicks to learn whether the clearer page attracts the right visitors.
Record the current title, canonical, primary heading, conversion action and performance before changing a page. After publishing, check the rendered HTML as well as what the CMS preview shows. For shared templates, compare at least one example from each page type. Check empty metadata fields and very long titles. A tweak that improves one service page can produce titles with missing locations or repeated words across dozens of others if the template assumes every record has the same fields.
| Element | What to inspect | Practical fix |
|---|---|---|
| Title and H1 | Can readers tell what the page delivers? | Describe the offer and distinguish it from neighbouring pages |
| Primary content | Does it answer the questions before an enquiry? | Add examples, requirements or practical limits |
| Internal links | Are there useful next steps? | Link from a related service or guide with descriptive wording |
Common questions
Do I need an exact keyword density?
No target density is needed. Check whether the content covers the topic accurately and uses the terms customers use where they help the reader.
Should every page target the same city and service?
Give each page its own purpose. A service-area hub and a detailed service page can complement each other with different questions and links.
How often should I run the checklist?
Run it when you launch a new template, after material changes to an important page, and when performance suggests a particular page type needs attention.
What to check next
- ContentAnswer the visitor’s real question
- DiscoverabilityAudit link paths, canonical and index status
- ExperienceTest the main action on a phone




