Title tags help label a page in browser tabs, bookmarks, and search results before the visitor even opens the page. For a webmaster, the job is to give each important URL a clear page title that explains the page's topic and distinguishes it from similar pages on the same site.
The title is stored in the HTML <title> element inside the page <head>, but search engines do not rely on that field alone. Current Google guidance says title links can also be influenced by the main page heading, other prominent on-page text, and text in links that point to the page, so title-tag work has to stay aligned with the page's visible content instead of acting like a separate SEO label.
There is no fixed Google character limit for title tags, and long titles are truncated as needed to fit the device width. Repeated boilerplate, outdated years, generic labels such as Home, and titles that no longer match the live page are the patterns most likely to weaken the signal or cause Google to generate a different title link.
Steps to write title tags for your website:
- Choose the exact URL you are naming and define the page's main purpose, audience, and one detail that makes it different from the other pages on the site.
A service page, product page, category page, and homepage usually need different title patterns because they answer different search intents.
- Draft one descriptive title that starts with the page's clearest topic and adds the brand name only when the brand helps the page stand out.
<title>Emergency plumber in Bristol | Example Plumbing</title>
Google recommends concise descriptive text in the <title> element, and truncates longer title links as needed to fit the device width instead of enforcing one fixed length.
- Remove repeated boilerplate, stacked keyword variations, vague labels, and stale details such as an old year, retired offer, or location that no longer matches the live page.
When the <title> element is half-empty, inaccurate, or duplicated across similar pages, Google can replace the search-result title with text pulled from headings or other page content.
- Compare the draft title with the visible page heading, primary intro copy, and any large prominent text near the top of the page so the same main topic is expressed consistently.
Google says title links may also use the main visual title, <h1> headings, og:title metadata, other prominent text, and anchor text from links that point to the page.
- Save the final title in the page-level SEO or page-title field in the CMS, or update the HTML <title> element directly when the site is managed in code.
<title>Emergency plumber in Bristol | Example Plumbing</title>
Use a page-level field whenever the platform provides one so the title can stay specific to that URL instead of falling back to a site-wide template.
- Open the live URL and view the page source to confirm that one current <title> element appears in the HTML <head> and that the browser tab shows the expected page label.
Older themes, plugins, or custom templates can leave behind duplicate title logic, which makes it harder to tell which value is actually being published.
- Inspect the live URL in Google Search Console after publishing so the indexed result can be compared with the current page when the source looks correct but search results still show an older or different title.
Search Console > URL Inspection
Title-link changes depend on recrawling and reprocessing, so an updated <title> element does not guarantee an immediate search-result change.
- Review the most important page groups on the site for duplicates, near-duplicates, or template leftovers and rewrite titles that differ only by one weak token such as a city, season, or product code.
Concise branding is fine, but the unique page topic should still do most of the work for category pages, service pages, products, articles, and location pages.
- Recheck title tags whenever a page changes purpose, heading structure, language, or offer so the published <title> element stays synchronized with the current page rather than describing an older version of it.
If the page language changes, Google recommends using the same language and writing system in the <title> element as the primary content on the page.
Mohd Shakir Zakaria is a cloud architect with deep roots in software development and open-source advocacy. Certified in AWS, Red Hat, VMware, ITIL, and Linux, he specializes in designing and managing robust cloud and on-premises infrastructures.
