START HERE
Name the specific question the page answers. Remove vague claims, preserve important distinctions and verify that the promised answer is on the page.
A title is often the first explanation a potential reader sees. If it sounds interchangeable with every competing page, people have little reason to choose it. The useful editing work starts with the page and the reader's question.
Write the promise in plain language
Complete this sentence privately: “After reading this page, you can decide or do…” If you cannot finish it, the page may need a clearer purpose before it needs a title.
Choose one main audience and decision. A guide for someone comparing two desk sizes should not pretend to be a complete guide to every standing desk. Narrow wording can be more useful than a broader promise that the content cannot satisfy.
Work through a concrete example
Illustrative original: “The Ultimate Desk Guide for Everyone.”
Possible revision: “120 cm or 140 cm desk: which fits your workspace?”
The revision is appropriate only if the article actually compares those sizes. It should discuss the monitor, keyboard, usable surface and room clearance. If the page covers electric motors instead, this title would mislead the reader even if the query is popular.
Another example: “Improve Your Analytics Today” becomes “Which pages bring enquiries from Google?” only when the page shows a way to answer that question and explains the limits of the data. Specificity must come from substance.
Keep the visible page consistent
Read the HTML title, main heading and opening together. They can use different wording, but they should describe the same task. Google's title documentation describes how page text and other signals can influence the displayed search title. You control your supplied title, not the final wording Google always shows.
Do not force an arbitrary character count at the expense of clarity. Put the useful distinction early and remove repeated brand language. Preview on a narrow screen to catch awkward wording, without claiming the preview guarantees a particular search appearance.
Use the query as evidence, not as a script
A search query can show what people are trying to solve. It does not oblige you to copy an unnatural phrase word for word. Group closely related queries around the underlying need, then write a title a person would say aloud.
In AbstractMetrics, open a search-related Next action and inspect the queries underneath. Copy the brief to ChatGPT, add the current page text and request three restrained alternatives. Ask it to identify which claim in each alternative needs verification. Reject unsupported superlatives and invented testing claims.
Publish with a record
Keep the old title, the new title and the change date. Check that the content management system saved the title in the right field. A headline change inside a page builder may not update the document title.
After the page has been processed and comparable data arrives, review the page's clicks, CTR and position. Keep an accurate title even if a small sample produces an inconclusive result. Accuracy is a publishing requirement, not a variable to trade for clicks.
What to watch afterwards
Review the same page and query group after processing and enough new impressions. Record any simultaneous ranking or content changes.
Take this to ChatGPT
Using the current page content I provide, draft three clear search titles. For each, explain the audience, the promise and any claim I must verify. Avoid superlatives and unsupported outcomes.
You choose what to share. Copying does not send anything or connect an account.
Sources and further reading
Official guidance checked on 16 October 2026. Examples and suggested workflows are our own.