Google title link rewrites deserve investigation when they misrepresent a page, omit a useful distinction or expose outdated information. Start by comparing the search result with the published browser title and main heading. Correct inconsistencies, verify the delivered metadata, then allow time for Google to process the change. You can influence the result, but you cannot prescribe its exact wording.
This guide applies to public service pages, product categories and editorial content. It addresses the clickable search headline. For the descriptive excerpt beneath it, see SBS's separate guide to search snippet controls and meta descriptions.
1. Establish which title is different
A title review often begins with a screenshot and an instruction to "fix the SEO title." That is insufficient evidence for a sitewide change. Record the exact destination URL, search query, displayed wording and observation date. Note the device too, because a shortened headline can look like a rewrite.
Separate the browser title, the visible page heading and the search result headline in your review sheet. They have different jobs. MDN's document title reference explains that the document title appears in the browser tab or title bar. It also helps people using assistive technology identify a page's purpose. Improving it should therefore make the page easier to recognize beyond search.
Use this proposed triage table before assigning work. It describes review criteria, not a prediction of Google's behavior.
| What you observe | What to inspect | Practical response |
|---|---|---|
| The ending disappears on a narrow screen | Whether the visible beginning still identifies the page | Put essential distinctions earlier; avoid assuming shortening means a metadata fault |
| An old year or retired service name appears | Published title, main heading and reusable template fields | Correct stale wording wherever it remains |
| Several different pages show generic wording | Shared title rules and missing page-specific fields | Repair the template and review representative pages |
| Google omits the brand but preserves the subject | Whether the result still identifies the destination accurately | Record it; prioritize misleading results first |
| The headline describes a different offer | Destination URL, page content and title sources | Investigate the mismatch before making cosmetic edits |
2. Compare the signals readers can see
Google generates title links automatically. Its title link documentation identifies several possible inputs, including the document title, prominent headings, social title metadata and link text. The title entered in a CMS is one input rather than an instruction Google must reproduce.
For each affected URL, write down the promise made by the title and the promise made by the opening screen. Would a reader expect the same service, product range or answer from both? A hypothetical page titled "Application maintenance" should not open with a dominant heading about building a new application if maintenance is the page's purpose.
The wording need not be identical. A browser title can include a concise brand suffix while the heading uses a more readable sentence. Preserve the same subject and scope. Ask a colleague who did not write the page to describe its purpose after reading each version separately. A disagreement gives the editor something concrete to resolve.
Also inspect repeated banners and oversized promotional headings. Keep the page's main heading visually clear rather than letting a campaign slogan compete with it. Google lists competing prominent headings, obsolete titles and inaccurate descriptions among potential title-link issues.
3. Fix the publishing route before polishing copy
Check the public page rather than relying on the CMS preview. An editor may save the intended title while a layout, extension or application route publishes something else. Compare the initial page response with the browser's rendered document, particularly when JavaScript changes metadata after navigation.
Ask the developer to confirm that the page delivers one intended document title, places metadata correctly and does not retain the previous route's wording. Test both a direct visit and navigation from another page. Treat any difference as a reproducible publishing issue, with the URL and steps attached to the task.
Google's valid page metadata guidance warns that invalid elements in the document head can cause it to ignore subsequent metadata. This makes structural inspection worthwhile when a correctly completed CMS field seems to have no effect. Rewriting the same field repeatedly will not repair malformed output.
If the page depends heavily on client rendering, use the checks in SBS's JavaScript SEO audit to investigate what Google can access. Keep the title ticket narrow, but attach evidence of broader rendering problems when you find them.
4. Write titles that distinguish neighboring pages
Once publishing works, improve the wording around an actual reader decision. What makes this destination different from the pages beside it? For a service business, that might be the task being offered. For a category, it could be the product type. For an article, state the question it answers.
As an editorial exercise, compare a hypothetical title such as "Web services and digital solutions" with "Website maintenance and support." The second is more useful if the page actually explains maintenance. If it primarily sells new builds, changing the title alone would create another mismatch. Resolve the content brief first.
Review titles as a group. Export or collect the titles for one page family and read them without their URLs. Can an account manager tell which destination handles each enquiry? If several sound interchangeable, identify the missing distinction before adding more adjectives.
Avoid turning the title into a list of related phrases. Keep supporting detail in the page itself. Use brand wording consistently, but do not let a long corporate suffix crowd out the subject. For translated pages, have someone who understands the language review the title alongside the visible content rather than approving the metadata in isolation.
Do not treat a character counter as a pass or fail test. Google says displayed title links can be shortened to fit device width. A preview tool is useful for spotting awkward ordering, but it cannot certify the final search presentation.
5. Publish with a review record and a checklist
Choose a small, representative group before changing a shared template. Include a clear mismatch, a generic title and a page whose result already reads accurately. This gives the team a useful comparison and reduces the chance of replacing good titles with a weaker formula.
Use this checklist for the release:
- Record each URL, observed search headline and intended page purpose.
- Compare the public browser title, main heading and opening content.
- Check that neighboring pages have meaningful distinctions.
- Verify metadata output on a direct visit and through internal navigation.
- Review mobile presentation and the language of translated pages.
- Assign an owner for copy approval and another for publishing verification when practical.
- Save the final wording, release date and reason for each change.
- Set a follow-up review rather than making daily wording changes.
For a few corrected URLs, an authorized Search Console user can request indexing through URL Inspection. Google's recrawl guidance says crawling can take days to weeks, repeated requests do not accelerate it, and a request does not guarantee inclusion. For many URLs, use an appropriate sitemap submission instead of treating individual requests as a bulk workflow.
6. Avoid false fixes and judge the next step
A common mistake is treating every difference as a defect. If the displayed headline accurately describes the destination, a rewrite alone is a weak reason to change a functioning page. Prioritize stale or misleading wording, then address template repetition.
Another mistake is editing the title, heading and whole page at once while expecting to identify which change affected clicks. Keep a change record and be cautious about attribution. A before-and-after comparison can guide further investigation, but it does not isolate the effect of the title when rankings, query mix or other page changes also differ.
Do not move a URL merely to chase a preferred headline. That introduces a separate migration task without establishing why the title differs. Similarly, changing the meta description is not a substitute for diagnosing the clickable title.
The next step is a focused review of one commercially useful page family. Produce a short issue list with the observed wording, evidence, proposed correction and owner. Approve changes that improve accuracy and recognition even if Google ultimately selects different text. The deliverable is a clearer page and a verified publishing process, with search appearance monitored afterward.
India
UAE
KSA
USA
UK
Canada
Oman
Kuwait
Australia
Thailand