How to Write Title Tags: Length, H1 Alignment, and Google Title Links

Published:
Last Updated:
Category: SEO & Content
Authors: Shusaku Yosa
A title tag helps readers understand what a page offers. Start with the page’s purpose, headings, and audience question before imposing a length target. Google’s displayed title link is not a fixed copy of your title element, so verify the implementation and the search appearance separately.
Separate the title element, H1, and Google title link
Element | Location and purpose | How to inspect it |
|---|---|---|
title | HTML head; names the document | Published HTML and browser tab |
H1 | Main visible heading | Rendered page and DOM |
og:title | Title information for sharing | Published HTML and the sharing surface |
Google title link | Clickable title in search | Relevant search result |
These elements need not be identical, but they should describe the same subject. Check what each CMS field actually outputs. Google’s title-link documentation lists several possible sources, including title elements, prominent headings, and other visible text. Editing one field does not directly lock the search-result wording.
Understand length and truncation without a character quota
Google does not prescribe a fixed character limit for the title element. Search results can truncate titles to fit the available display space. Device width and the shapes of the characters affect that presentation, so a Japanese editing convention cannot simply become an English character quota.
Use an internal length guideline only as a prompt to make the topic clear early. A preview illustrates one display, not a guarantee. Excessive brand wording or repeated boilerplate can push the information that distinguishes the page toward the end.
Build a title around the page’s actual purpose
Write one sentence describing what a reader can do after using the page. Extract the audience, problem, and concrete material it provides. If the page teaches a small shop to set up and test a booking form, those details can shape the title. Do not add a free download or research finding that the page does not contain.
- Choose the central reader question.
- Use necessary search terms in natural language.
- Name the actual offer: a procedure, comparison, or worked example.
- Keep enough detail to distinguish the page from neighboring guides.
The SEO Starter Guide supports clear descriptions that help readers judge relevance, rather than keyword repetition for its own sake.
Rewrite vague, stuffed, and outdated examples
The following fictional editing examples assume the revised page genuinely provides the named material. Check the content as well as the label.
Before | Possible revision | Reason |
|---|---|---|
The Complete SEO Guide | SEO Checks for Small Websites: Crawling, Indexing, and Content | Defines audience and scope |
Booking Forms Booking Form Builder Booking | How to Build a Store Booking Form and Test Submissions | Replaces repetition with a task |
Latest Booking Setup for 2022 | Booking Form Setup: Notifications and Submission Tests | Avoids an unsupported freshness claim |
Free Templates | Consultation Reply Examples: First Response and Scheduling | Explains the intended use |
The final title is appropriate only when reply examples actually exist on the page. Do not imply a downloadable file without providing one, or promise a guaranteed commercial outcome.
Investigate why Google shows a different title
If Google shows different wording, inspect the currently published title, H1, prominent text, og:title, and internal anchor text. Look for stale dates, empty values, repeated boilerplate, or a topic that conflicts with the main content. Record the search conditions and checking date.
A difference alone is not proof of a penalty or a failed implementation. Google may generate a title from another source. Make the page’s descriptions coherent rather than repeatedly changing the field to chase a single result. Updates require recrawling and processing, with no universal turnaround promise.
Check page output and allow time for reprocessing
Before release, check the document name, duplicated branding, unresolved template variables, and page-specific information. After release, read the public HTML rather than relying only on the editor. Verify the intended title output and its relationship to the H1 and body. Inspect each language version for accidental boilerplate from the other language.
Record the URL, old and new titles, H1, release date, and simultaneous content or navigation changes. Keep implementation acceptance separate from observation of search appearance. This makes it easier to identify whether a problem is in the output or in subsequent search processing.
Evaluate CTR with a matched comparison sheet
CTR equals clicks divided by impressions. In a fictional example, 20 clicks from 1,000 impressions is 2%, while 30 from 1,000 is 3%: a one-percentage-point difference. This comparison alone does not establish that the title caused the change. Position, queries, country, device, search type, seasonality, and other edits can affect it.
Record | Entry or fictional example |
|---|---|
URL, old/new title, H1, date | [Fill in] |
Periods, country, device, search type, query group | Use matched conditions |
Before impressions, clicks, CTR | 1,000; 20; 2% |
After impressions, clicks, CTR | 1,000; 30; 3% |
Position, other changes, unresolved factors | [Fill in] |
Use the Performance report for matched observations. If traffic declines, consult Google’s traffic-drop guidance rather than treating a CTR change as proof of a ranking effect.
Continue with the guide that matches your next task: How to Build a Keyword Map: Intent, Page Ownership, and Update Decisions; How to Diagnose a Search Ranking Drop: Data, Indexing, and Site Changes; Mobile SEO Audit: Content Parity, Core Web Vitals, and Usability.




