Prompt

7 minute read

Title Tag Prompt: Rewrite Titles for Search Intent

A reusable title tag prompt that rewrites page titles to match the searcher's task and the page's real content, with options, reasons and intent warnings. Includes a real test run.

Abstract illustration for Title Tag Prompt: Rewrite Titles for Search Intent

This title tag prompt rewrites page titles so each one matches what the searcher wants and what the page actually offers. It returns two or three options per page, explains the choice and flags titles that would promise something the page does not deliver. You pick, edit and publish the final title.

The page explains each variable, gives the full prompt and shows one real run on invented pages. It also lists the checks that keep titles honest. Google may still show a different title link, so a better title tag improves your odds rather than guaranteeing the result.

What this title tag prompt does

The prompt asks the model to name the searcher's task for each page before writing anything. Then it writes titles that state the page's real topic early, keep a distinctive detail and avoid repeated boilerplate. Each option comes with its character count and a one-line reason.

It follows Google's guidance on title links: titles should be descriptive, concise and unique, without keyword stuffing. It also refuses to add claims, such as "best" or a year, that the page does not support.

When to use it

Use it when titles are vague, duplicated or out of step with the queries a page receives. It works well after a Search Console review or before refreshing a group of pages.

  • Several pages share the same title pattern and differ only by a word.
  • A page gets impressions for queries its title does not reflect.
  • Google often rewrites a page's title link, which can signal a weak title.

However, do not use it to chase every query a page appears for. If a page truly serves a different task than the query, the fix is content or a new page, not a new title.

Inputs and variables

Replace every bracketed variable before you run the prompt. The more accurate the page summaries, the better the titles.

  • [SITE_NAME]: the brand name, and whether you add it to titles, for example "SEOVision, added after a vertical bar".
  • [PAGES]: one block per page with URL, current title, H1, a two-sentence summary of what the page covers and, if you have them, its top queries from Search Console.
  • [AUDIENCE]: who searches, for example "small business owners in the United States".
  • [LENGTH_TARGET]: a soft character target, for example "about 50 to 60 characters". Google sets no fixed limit; long titles may be shortened in results.

Copy queries from your own Search Console account, not from a guess. Leave out any private or unpublished information.

Reusable prompt — version 1.0

Copy the prompt below as it is. It asks for reasoning per page before the options, which makes weak titles easier to spot.

You are helping an SEO editor rewrite title tags for [SITE_NAME].

<task>
For each page in <pages>, write 2 or 3 title tag options that match the searcher's task and the page's real content.
</task>

<context>
Audience: [AUDIENCE]
Length target: [LENGTH_TARGET]
</context>

<rules>
1. First state the searcher's task for the page in one sentence, using the summary and queries given.
2. Put the page's main topic near the start. Keep one detail that makes this page different from similar pages.
3. Use only facts in the page summary. Do not add "best", years, numbers, prices or promises that the summary does not support.
4. No keyword stuffing, no ALL CAPS and no repeated boilerplate across pages.
5. Make every title unique across the whole list.
6. If the summary and the queries describe different tasks, say so and do not force the query into the title.
</rules>

<output_format>
For each page:
- URL
- Searcher task (one sentence)
- Options: title | character count | reason
- Recommended option and why
- Warning, if the page content does not match its queries
</output_format>

<pages>
[PAGES]
</pages>

Rule 6 is the important safeguard. It stops the model from writing a title that wins a click the page cannot satisfy.

How to use it

Any capable chat model can run this title tag prompt. Batches of 10 to 20 pages keep the comparison across titles manageable.

  1. Export current titles, H1s and top queries for the pages you want to review.
  2. Write a two-sentence summary for each page from its actual content.
  3. Fill in the variables, paste the prompt into a new chat and run it.
  4. Pick or edit one option per page, and read it next to the page before you publish.
  5. Record the change date, then compare clicks and CTR in Search Console after a few weeks.

Example input and output

We ran version 1.0 once on Claude Opus 5.5 on November 15, 2026. The pages are invented for this example; the output is trimmed, and trims are marked with "…".

SITE_NAME: Northwind Bikes, added after a vertical bar
AUDIENCE: home bike mechanics in the United States
LENGTH_TARGET: about 50 to 60 characters
PAGES:
URL: /guides/adjust-disc-brakes
Current title: Brakes | Northwind Bikes
H1: How to adjust disc brakes
Summary: Step-by-step guide to centring a mechanical or hydraulic
disc brake caliper and stopping rub, with the tools needed.
Top queries: disc brake rubbing, how to adjust disc brakes
…
URL: /guides/adjust-disc-brakes
Searcher task: stop a disc brake from rubbing by adjusting it at home.
Options:
- How to Adjust Disc Brakes and Stop Rubbing | Northwind Bikes | 58 | names both the task and the symptom people search for
- Adjust Mechanical or Hydraulic Disc Brakes | Northwind Bikes | 59 | signals that both brake types are covered
Recommended: the first option, because "rubbing" appears in the top query and the guide fixes it.
Warning: none.
…

In this run, both options stayed within the facts of the summary. However, the character counts were off: both titles are 60 characters, not 58 and 59. That is why the checklist below says to count them yourself. This single run is an illustration, not a benchmark.

How to check the output

Read each title next to its page before publishing. The checks below catch most problems.

  • Accuracy: every word is true of the page, with no added claims, years or numbers.
  • Uniqueness: no two pages share a title or near-identical pattern.
  • Focus: the main topic appears early and matches the H1's subject.
  • Length: the count is right and the key words survive if the end is cut off.
  • Intent warnings: any page flagged under rule 6 gets a content review instead of a new title.

Troubleshooting

These fixes address the bad outputs we see most often.

  • Titles sound like ads: add "plain, factual wording" to rule 4.
  • The same phrase opens every title: ask the model to start no more than two titles with the same word.
  • Character counts are wrong: count them with a spreadsheet formula; models often miscount.
  • The model ignores the queries: put the top query first in each page block.

Limitations

Google may generate a different title link from other text on the page, such as headings or anchor text. Therefore, a new title tag can change what searchers see, but nothing guarantees it. Clicks also depend on position, competition and the snippet.

The model only knows what you tell it about each page. Outputs vary by model, version and input, so every title is a draft for a person to check and edit before it goes live.

Version history

Each version is dated so you can tell which prompt produced older titles.

  • 1.0: November 15, 2026. First version, tested once on Claude Opus 5.5.

Frequently asked questions

Quick answers to the questions readers ask most about this topic.

Which AI models does this title tag prompt work with?

Any capable chat model that follows structured instructions, such as current models from OpenAI, Anthropic or Google. We tested it once on Claude Opus 5.5. Check every title and count characters yourself, because models often miscount.

How long should a title tag be?

Google sets no fixed character limit, but long titles may be shortened in search results. Keep the main topic near the start so it survives truncation, and set your own soft target in the LENGTH_TARGET variable.

Will Google show the title I write?

Not always. Google may build the title link from other page text, such as headings or anchor text. Clear, accurate and unique titles make it more likely that Google uses yours.

Can I add the year or the word best to my titles?

Only when the page supports it. The prompt blocks years, numbers and claims like best unless your page summary contains them, because a misleading title can cost trust and clicks.

Sources

These pages support the title guidance and the prompting approach above.

  1. Google Search Central: Influencing your title links in search results developers.google.com
  2. Google Search Central: Guidance on using generative AI content developers.google.com
  3. OpenAI: Prompt engineering guide developers.openai.com
  4. Anthropic: Claude prompting best practices platform.claude.com