Build a search-visibility baseline before you chase rankings

Before collecting a long keyword list, choose the pages that explain what your business does and help someone take the next step. Read each page on a phone. Can a visitor understand the offer, its limits and the next action without interpreting internal jargon? Record the missing information before changing titles or adding more copy.

Google's SEO Starter Guide recommends useful, well-organized content and makes clear that its advice does not guarantee a first-place ranking. Use that guidance as a foundation. For a service page, a practical baseline might include a clear scope, the questions a buyer needs answered and a working enquiry path. These are editorial checks, not a formula for a ranking system.

Open the website as a new visitor and follow the navigation to each selected page. If a useful resource has no link from another page, add one where it helps the reader. A service overview can lead to a detailed explanation; an article can link to the resource needed for its next step. Avoid building a menu that exposes every URL without context.

Google's link guidance recommends anchor elements with an href and descriptive, relevant link text. A label such as 'website maintenance scope' tells a reader more than 'learn more' repeated across a page. Have a developer check the actual link markup if navigation depends on scripted click handlers. A clickable visual is not enough to establish that a usable link exists.

Give each page a primary question to answer and a reader who needs that answer. Someone comparing maintenance providers needs different information from someone troubleshooting a broken contact form. Mixing those tasks can produce a page that mentions both topics but completes neither.

Write a page title that accurately describes its contents, following Google's starter guidance on clear, distinct titles. Then check the heading and opening paragraphs against that promise. Remove claims that the body cannot support, and add examples only when they explain a real decision. If two existing pages answer the same question, review their roles before commissioning another article.

Google's Search Console Performance report provides clicks, impressions, click-through rate and average position, with ways to group the data by pages and queries. Save a starting view for the selected pages and record its dates and filters. Use the same scope when returning to it so a change in the report setup does not masquerade as a change in performance.

Read these measures together. Impressions describe search exposure, while clicks describe visits from those results; neither alone tells you whether a visitor became a suitable enquiry. Review the query wording alongside the destination page. Google's documentation also warns that recent data can be preliminary, so use complete reporting periods for routine comparisons.

Turn the baseline into a short decision record. Name the page, the observed problem, the proposed edit and the result you will examine afterward. An unclear title calls for a different change from a page that is difficult to reach or a service explanation missing essential information. Assign one person to check that the edit actually appears on the live page.

Start with the issue you can substantiate most clearly, then review what changed before extending the work. Record other events that may affect interpretation, such as a promotion or a site migration. Search results can change for reasons outside your edit. The useful outcome is a better-supported next decision, not a promise that a particular position will arrive on a particular date.