SEO & Search

Why Google Rewrites B2B Page Titles: A Title Link Diagnosis Worksheet

The search result names one service. The page heading names another. The editor opens the title field and finds a third version.

Start there. Before changing a title, put the competing descriptions beside each other. Decide what the page should communicate to a buyer.

Google generates title links automatically from several signals. These include the HTML title, prominent headings, og:title, page text, link text, and website structured data. An editor can influence those inputs without choosing the final display. Google documents its title-link sources.

The worksheet below is a proposed editorial process. Its four pages and search observations are fictional. Use it to diagnose one page, assign a correction, and preserve the evidence for a later review.

Name the Text You Are Comparing

Use four separate fields in the record: HTML title, visible main heading, other signals, and observed title link.

Copy the HTML title from the page under review. Copy the visible heading separately. In the other-signals field, record prominent banners, social metadata, and relevant link labels. Keep the observed search text in its own column.

Do not combine those fields into a single entry called “the title.” That shorthand prevents the next editor from knowing which text you inspected.

For this worksheet, also separate a replacement from a shortened display. Record the complete text you can see. Mark any cut-off text as incomplete evidence. Avoid reconstructing the missing words from memory.

The description beneath a result is a separate inspection target. Google describes that snippet as a summary drawn primarily from page content, sometimes from the meta description. Its snippet documentation covers that behavior. A complaint about the excerpt belongs in a separate record.

Start your investigation with the specific URL and the exact search observation. “Google changed our messaging” is too broad to assign.

Capture the Observation Before Editing

Open a record with the query, result destination, observed text, date, device, and search language. Save a screenshot with enough context to identify the result.

Treat these fields as evidence of one observation. Do not turn one screenshot into a statement about every searcher or every query.

Then inspect the destination page. Confirm that you are looking at the same URL recorded in the result. Note any redirect or different page version before interpreting the text.

Put the current source beside the screenshot. If the source changed yesterday, identify that revision. Comparing an older search observation with newer page text requires a date on both.

Use a short issue statement: “The observed title names the general service family; this page describes one assessment.” That statement explains the reader problem without claiming to know Google's internal reasoning.

The broader technical SEO checklist can organize a separate site review. Keep this record bounded to the page and the conflicting language you can inspect.

Compare Four Fictional Pages

Google lists repeated boilerplate, outdated titles, unclear main headings, and language mismatches among possible title-link problems. These are documented patterns, not proof of any individual rewrite's cause. Review Google's common issues.

Consider an invented consultancy with four public pages. The paths below are worksheet labels, not links to real pages. Every observed title in the table is invented.

Page and issue HTML title Visible page signals Fictional observed title link Proposed correction
/supplier-intake/, boilerplate Business Services and Solutions Main heading: Supplier Intake Assessment Supplier Intake Assessment Give the title the specific assessment name
/annual-readiness/, stale date Annual Readiness Guide 2025 Heading and reviewed content describe the 2026 edition Annual Readiness Guide 2026 Confirm the edition, then correct the title year
/process-review/, competing headings Process Review Workshop Equally prominent headings: Request a Consultation; Process Review Workshop Request a Consultation Make the workshop heading primary; subordinate the invitation
/es/revision/, language mismatch Supplier Process Review Spanish main copy; heading: Revisión del proceso de proveedores Revisión del proceso de proveedores Have the language editor align the title with the Spanish page

Use the table to choose an inspection path. It is not a prediction table. None of the proposed corrections promises that Google will use the replacement wording.

The first row needs a page-specific label. The second needs an edition check. The third needs an editorial hierarchy decision. The fourth needs a language owner.

Those are different assignments. Sending all four to a developer as “fix SEO titles” conceals the decisions that must happen first.

Resolve the Page's Meaning Before Its Wording

For the supplier-intake page, ask the service owner to finish this sentence: “This page helps a buyer decide whether to request...”

Suppose the answer is an assessment of supplier intake steps. Keep that object in the proposed title. Do not add implementation services unless the page offers them.

A useful draft is “Supplier Intake Assessment | Example Consultancy.” The invented brand supplies context. The assessment name distinguishes the page from the consultancy's other services.

Compare that draft with the first visible heading and the opening paragraph. Ask whether each describes the same service boundary. Record disagreements before selecting a final phrase.

Use search intent mapping as a prompt for that discussion. Write down the buyer's task in plain language. Avoid treating a keyword phrase as permission to expand the offer.

For the annual-readiness page, verify the edition against the body. A current year in the heading does not establish that the instructions were reviewed. Have the document owner identify which edition the page represents.

If the body mixes editions, return the page for a content decision. Changing one year would hide the unresolved inconsistency. Keep the title task open until the owner confirms the correct description.

Inspect Heading Hierarchy and Language Separately

On the fictional workshop page, compare the invitation and the service heading at the same viewport. Ask a reviewer which phrase appears to name the page.

If the invitation dominates, propose a limited layout correction. Keep the invitation available while making the service heading the clear entry point. Document the intended hierarchy before changing the template.

Check whether the component is shared. A correction meant for one page should have an explicit boundary. If changing the component would affect other pages, open a separate assignment for that larger scope.

For the Spanish page, ask a fluent reviewer to inspect the title against the main copy. Give them the page's purpose and the existing terminology. Do not approve a translation solely because an automated tool produced it.

The reviewer should confirm the subject, language, and writing system. If the page mixes languages intentionally, document which material is primary and why. Leave unresolved translation questions visible.

Keep these reviews independent. A heading hierarchy problem does not establish a language problem. The worksheet works when each diagnosis names the evidence that supports it.

Write a Change Log Someone Else Can Continue

Use one row for each approved correction. Keep the original observation intact. Add a separate follow-up entry when new evidence arrives.

The following record continues the fictional supplier-intake example. Its dates are editorial appointments, not predictions about Google.

Field Fictional entry
Observed query supplier intake assessment
Page /supplier-intake/
Observation date 2026.10.28
Observed title link Supplier Intake Assessment
Current HTML title Business Services and Solutions
Intended correction Supplier Intake Assessment | Example Consultancy
Page evidence Main heading and opening paragraph describe the assessment
Source evidence Google title-link documentation, common issues: repeated boilerplate
Decision owner Service editor
Implementation owner Website maintainer
Scope This page's title field; no shared-template change
Follow-up date 2026.11.11, chosen for the editorial review
Status Proposed; implementation and later search observation remain unconfirmed

In your working record, link the source evidence to the relevant Google documentation. Attach the exact before and after text separately from the rationale.

Give the implementation owner an acceptance condition they can inspect: the approved title appears in the delivered page, and the heading still describes the same assessment.

Give the follow-up owner a different task: record what the result displays when checked. Keeping those tasks separate prevents a completed code change from becoming a fictional search outcome.

Review the delivered page after the approved edit. Compare the title, heading, prominent text, and social title with the decision record. Preserve the revision identifier where your publishing system provides one.

Check the specific page that changed. Do not accept a screenshot of the CMS field as your only implementation evidence. Ask the maintainer to show the page readers receive.

If another field remains inconsistent, decide whether it belongs in this correction. Record the decision. Avoid quietly expanding a small task into a template or service-positioning rewrite.

Google must recrawl and reprocess changed sources before noticing their updates. Its documentation offers no page-specific completion date. The title-generation guidance explains that processing step.

Choose a follow-up date for your team's availability. Call it a review date. Do not label it the day the search result will change.

Keep the review open if there is no useful new observation. An unresolved result is a valid status. It is more useful than declaring failure and replacing the title again without evidence.

Keep the Result and the Explanation Apart

At follow-up, record the same fields as the original observation. State what you saw, when you saw it, and which page revision you inspected.

If the displayed title matches your preferred wording, report that observation narrowly. Do not claim that the edit caused a ranking or click-through improvement. This worksheet does not establish either outcome.

If the displayed title differs but accurately names the page, explain the difference to the owner. Ask whether any reader-facing defect remains. Matching the editor's preferred punctuation is a different objective from correcting an inaccurate service label.

If the result still appears misleading, reopen the evidence. Look for an overlooked version, conflicting text, or a source that changed after approval. Mark the cause unknown when the record cannot establish it.

For broader query analysis, keep a separate Search Console review. Do not use a performance chart as a substitute for the title text you observed.

Close the page-level correction when the approved implementation is verified. Keep search observations attached as follow-up evidence. A future editor should be able to distinguish the change you made from the display you saw.

Correct the page you can inspect.

Sources

Topic map: AI search and the changing results page

Articles in this cluster, then the 3 clusters that share the most topics with it.

This cluster: AI search and the changing results page

Neighbor: Technical SEO, crawling, and migrations

Neighbor: SEO by industry and location

Neighbor: Search measurement and reporting