Digital & IT
Create SEO metadata that matches the page
Write distinct titles and descriptions grounded in the actual content and search intent.
IGS Editorial · 3 min read · Updated 17 November 2026

SEO metadata helps describe a page to search systems and people reviewing results. It cannot compensate for a page that does not answer a useful question. Begin with the content and intended audience, then write metadata that accurately represents it.
A title and description should set expectations the page can meet. Misleading promises may attract a click but create disappointment. Avoid adding locations, credentials or service claims that are not supported by the business and page.
Give each page a distinct title
Use the main topic in natural language and add the brand where it helps identification. Important pages should not all share a generic title such as Home or Our Company. Distinct titles make the site easier to understand in search results, browser tabs and saved links.
Keep the wording focused rather than repeating several near-identical keywords. The useful length depends on display conditions, so prioritise clarity and put the essential topic early. Do not treat a particular character count as a guarantee of display.
Write a useful description
Summarise what the visitor will find and why it may help. For an operational guide, mention the specific problem and approach. For a service page, describe the scope rather than claiming outcomes the page cannot substantiate.
Search systems may choose a different excerpt for a query, so the description is not fully under the publisher's control. Keep the visible page content equally clear. Avoid using metadata as a place to hide claims that would be inappropriate in the body.
Keep canonical URLs coherent
A canonical URL identifies the preferred version of a page. Use a consistent URL strategy and review duplicates created by filters, tracking parameters or alternate paths. Do not point unrelated pages to one canonical merely to simplify the setup.
When URLs change, plan appropriate redirects and update internal links. A new slug without a migration plan can leave old references broken. The content manager should understand that a published URL is part of the site's interface.
Validate technical output
Inspect the rendered page source for title, description, canonical and relevant social metadata. Check that dynamic values are escaped safely and that missing fields receive a sensible fallback. A CMS field is not useful if the template never outputs it.
Review sitemaps and publication rules. Draft pages should not be promoted as public URLs. If a page requires authentication, metadata alone does not protect it; access control must enforce the restriction.
Maintain metadata with content
When a page changes focus, update its metadata too. A guide revised from general advice to a specific workflow should not retain a description promising something else. Use periodic reviews to find duplicate titles and stale descriptions.
Assess search performance in context when reliable data is available. A change in clicks may reflect ranking, demand or result presentation, not only the description. Good metadata is accurate, distinct and consistent with a page that provides substantive value.
Audit a small set of published pages
Choose the homepage, one service page and one article. Compare their visible headings with their titles and descriptions. Check whether a search visitor would receive the information promised by the metadata. Look for copied descriptions that no longer match the page.
Inspect canonical URLs and publication status. A draft should not appear in the public sitemap, and a page should not identify an unrelated destination as its preferred version. Review links after any slug change.
Keep a short issue list with the page, mismatch and intended correction. Verify the rendered output after saving the CMS fields; a database update alone does not prove the template uses the value. Where search data is available, use it to identify relevant questions rather than forcing keywords into every field. Metadata maintenance works best as part of content review. It should preserve accurate expectations as the website evolves, not become a disconnected optimisation task measured only by whether fields are filled.
