Start with the difference from neighbouring pages
Identify the page’s main question and compare nearby URLs. A service about commissioning a website and a guide about planning content make different promises. If the same title fits both unchanged, review their focus before polishing metadata.
Write an understandable working version first. A redirect guide can say that it helps build a URL map. It should not promise guaranteed search performance. Add the brand consistently when it helps identification without allowing the brand phrase to dominate every title.
Select the information that helps a visitor choose
A useful description highlights a method, example or relevant limitation. It need not repeat the title word for word. Avoid claims unsupported by the page, particularly free, complete or guaranteed when those conditions do not actually apply.
Google may display a different title or snippet. Treat metadata as editorial input rather than a fixed advertisement. Review the H1 and introduction as well so the resource delivers what its summary promises. A field can pass a technical validation and still mislead readers.
| Check | Useful question |
|---|---|
| Title | Can readers distinguish this resource from nearby topics? |
| Description | Does it state concrete value and relevant scope? |
| Visible page | Do the heading and content match the promise? |
| Language | Does the wording sound natural in this version? |
Try a before-and-after reading exercise
A vague working version might be titled Services with a description about high quality and satisfied customers. A more useful version identifies the actual offer, audience and next step. For a consultancy, this could mean clear engagement types and how an initial scoping discussion works, without a fabricated customer outcome.
Ask someone to read only the metadata and explain what they expect to find. Then compare their expectation with the page. Improve either the summary or the content when they do not match. The exercise is useful even before search data is available.
Review the whole site, not just individual fields
Find duplicate titles and descriptions within each language, but also assess whether the resources have the same intent. Changing two words cannot resolve a genuine content duplicate. Localise metadata naturally and keep it on the appropriate language URL with its own canonical. After a separately authorised launch, actual search reports can provide feedback. Avoid conclusions based on one impression or promises that a particular result appearance will be preserved.