Research Guides
Review Page Titles and Search Snippets With a Clear Worksheet
Someone searching for a service has to decide whether a result answers their question before they open the page. A useful review checks what the result promises, what the page actually provides and which edits would make the two easier to understand.
Start with a handful of important public pages you control. Keep an evidence record for each one, agree on a specific change and verify the published page afterward. This guide is an editorial workflow, not a promise that a search engine will display your chosen wording or send more traffic.
Keep the page and the search result separate
Record four items separately: the HTML title element, the visible page heading, the meta description and an observed search result. The first three belong to your website. The last is an observation made for a particular search at a particular time.
Google creates title links automatically using sources that can include the title element, headings, prominent page text and links pointing to the page. Its advice is to make titles descriptive, concise and distinct, avoid repetitive keywords and make the main page title clear. A title link can differ from the title element. There is no fixed title-character allowance that guarantees complete display; Google can shorten the result to fit the device. Google's title-link guidance explains these distinctions.
For this worksheet, preserve the observed text rather than replacing it with what you expected to see. If you have not checked a search result, write “not observed.” Do not turn a preview from an editing tool into evidence of what a search engine displayed.
Select pages by a real business question
Choose a manageable batch, such as five pages, and state why each matters. Perhaps customers keep confusing a consultation with a subscription, or an older guide still describes a service you have stopped offering. Five is a work limit for this exercise, not an SEO rule.
Give each page one primary question to answer: “What does the initial consultation include?” is more useful than “How can this page attract everyone?” Ask the person responsible for the service to confirm the answer before rewriting its description.
If you use Search Console, its performance report offers clicks, impressions, click-through rate and average position, with ways to filter by dimensions such as page, query, device and country. Search Console performance documentation.
Google also documents privacy omissions and other data limits. Use the report to choose questions to investigate, not as a complete inventory of every search.
For a first pass, favor a clear mismatch with a straightforward correction over a page that merely has a lower click-through rate. Different searches may represent different needs. A low rate alone does not tell you which words to replace.
Build one evidence row per page
Use these fields in a spreadsheet or shared document:
- Page address and owner: The exact public URL and the person who can confirm its claims.
- Reader's task: What the visitor should understand or accomplish on this page.
- Current page wording: Title element, main visible heading and meta description, copied separately.
- Search observation: Query, displayed title and snippet, observation date, device and relevant search context. Mark unobserved fields honestly.
- Promise check: Where the page supports each service, feature, date, location or outcome mentioned in the proposed wording.
- Proposed edit: Exact replacement text, reason and any page content that must change with it.
- Verification: Publication date, checked URL, reviewer and any unresolved mismatch.
Do not collect unnecessary personal details from customer enquiries. A general statement such as “visitors mistake the consultation for ongoing support” can preserve the useful issue without copying a person's private message into an editorial worksheet.
Write a description the destination can support
Google usually builds snippets from page content and sometimes uses the meta description when that is a better summary. The same page may receive different snippets for different searches. Google recommends descriptions specific to the page; a keyword list is less helpful than an informative summary. It does not prescribe a maximum description length that guarantees the full text will appear. Read Google's snippet guidance.
As an editing exercise, finish this sentence: “This page helps [reader] understand or do [specific task], using [information actually present].” Then remove the scaffolding and read the result aloud. If you cannot name the information, review the page before improving its sales language.
Check every attractive detail. “Download” requires an actual downloadable resource. “Same-day” needs support from the service owner and the page. A reference to a particular year should reflect the substance, not merely the date of the edit. Leave unsupported offers out.
Work through a fictional example
Imagine an invented consultancy with a page explaining a one-off website review. It provides a list of checks, a description of the written findings and instructions for enquiring. It does not promise continuing maintenance or a particular ranking increase.
Its current title is “Services | Example Studio.” Its description is “Everything you need for success online.” The problem is identifiable without traffic estimates: neither tells the reader which service this page explains.
A proposed title is “One-off Website Review | Example Studio.” A proposed description is “See what our one-off website review covers, what the written findings include and how to enquire.” The reviewer marks each phrase against the corresponding section of the page.
Now suppose a colleague proposes “Get ongoing support and guaranteed first-page rankings.” Reject that wording. It introduces promises absent from the described service. If the business later changes its offer, the service owner needs to settle those facts and update the page before the summary can reflect them.
Keep the discarded suggestion and its reason briefly in the review record. That prevents a later editor from restoring the same unsupported claim because it sounds more persuasive. These examples are fictional, not descriptions of Colquhoun.shop or its services.
Check technical restrictions before treating absence as a copy problem
If a snippet is missing or unusually short, ask the implementer to inspect the page's existing controls. Google documents nosnippet for suppressing a text snippet, max-snippet for limiting its length and data-nosnippet for excluding selected page content. These controls do not choose a preferred replacement sentence. Google's robots and snippet-control specifications explain their scope.
Record any relevant setting and why it exists. Do not remove a deliberate restriction just to make a search preview look fuller. If the setting is unexpected, hand the finding to the person responsible for the site and agree on the intended behavior before changing it.
Verify the edit in two stages
First, inspect the actual published page. Check the final title element, heading and description, and confirm that the promised information is present. A completed field in a content editor is not the final test. If a shared template supplies the wording, also inspect another page using that template for accidental duplication or misplaced details.
Second, distinguish the current page from the version known to Google. Search Console's URL Inspection tool separates indexed information from a live test. A live test does not guarantee inclusion in results, and requesting indexing does not guarantee indexing either. Use the report to investigate what has been processed, not to certify the future title or snippet. URL Inspection documentation.
Keep the change date and any later search observation in the same record. If traffic changes, treat that as a finding to investigate alongside other changes in the business and search demand. The immediate result of this review is more concrete: an accurate page summary, a checked destination and a clear record of what was changed.