01
Step-by-step
- 01
Identify the page purpose
Describe what the page helps the reader understand or accomplish.
- 02
Use the primary topic naturally
Include the central topic when it improves clarity, not as a repeated formula.
- 03
Differentiate the page
Avoid reusing the same title across many pages.
- 04
Set expectations
Do not promise a guide, price, tool, location, or answer the page does not provide.
- 05
Review display risk
Search systems may rewrite titles and display length varies. Prioritize meaning.
02
Verification
- The visible page matches the intended topic and audience.
- The page can be crawled, rendered, and indexed when intended.
- Claims, examples, code, and links have been checked.
- The page has a measurable next action or outcome.
- A future reviewer can understand what changed and why.
03
Before you change the website
- Define the purpose and expected result of title tags.
- Capture the current state using audience task, search intent, factual support, page purpose, structure, examples, links, calls to action, and maintenance ownership.
- Identify the source template, component, plugin, content owner, and release path that controls the output.
- Prepare a test case, approval path, backup or rollback method, and post-release verification plan.
Next useful action
Turn title tags into an accountable record.
A tested implementation of title tags with deployment notes, rollback context, and retained verification.