You search Google for your article and the title in the SERP isn’t what you put in <title>. Sometimes it’s the H1; sometimes it’s a chunk Google synthesized from your headings; sometimes it’s just shorter. This is not rare: Zyppy’s 80,000-title study found Google rewrites roughly 61% of titles (Zyppy study), and broader tracking put the Q1 2025 rate as high as 76%. So if Google touched your title, you are in the majority, not a special case.
Google’s own Title Link documentation lists the nine sources it pulls from — your <title> element, the on-page main heading, <h1> tags, og:title, anchor text pointing at the page, WebSite structured data, and other large/prominent text — and says it rewrites “if we detect a problem” with the title element. The job here is to figure out which of those problems your page triggered, fix it, and push Google back toward your <title>.
This guide goes through the rewrite triggers in the order they actually fire, with the diagnostic for each. It also covers the new wrinkle from 2026: a Google AI experiment that rewrites headlines beyond what’s on your page — that one behaves differently, and (as of June 2026) has no opt-out.
TL;DR
- As of June 2026, Google rewrites 6 to 8 titles out of 10 (61% in Zyppy’s study, up to 76% in Q1 2025 tracking). A rewrite alone is normal; only act if it’s hurting your click-through.
- The single highest-hit trigger is length: keep titles under ~600px desktop (≈50–60 English characters, ≈28–30 CJK characters). Titles in the 51–60 character band have the lowest observed rewrite rate (~40%) — every other band is rewritten more.
- Other common triggers: brand/boilerplate buried in front of the topic,
<title>↔<h1>mismatch, pipe-stuffing (|), boilerplate repeated across sibling pages, and stale year prefixes. - Google added
og:titleas a title source in 2024, so a mismatched Open Graph title can now override your<title>. - The 2026 AI-headline experiment can rewrite your title into wording that changes its meaning. As of June 2026 there is no opt-out — not a robots tag, not a Search Console toggle. A tight, query-matched
<title>is your only lever. - After editing, request indexing and wait 2–4 weeks before judging — Google re-evaluates titles on its own crawl cycle, not on save.
Which bucket are you in?
A 20-second triage before you read the full list. Compare your <title> to the SERP title:
| What you see in the SERP | Most likely trigger | Jump to |
|---|---|---|
| Just a shorter slice of your title | Over the length budget | Cause 1 |
Your H1, not your <title> | Title/H1 mismatch or H1 wins | Cause 4 |
| The brand moved to the front/back, topic now first | Boilerplate buried the topic | Cause 2 |
| Wording from your social/share card | og:title overriding | Cause 5 |
| A query you rank for, added to your title | Title didn’t match the query | Cause 3 |
| Pipes swapped for dashes, fragments dropped | Pipe-stuffing | Cause 6 |
| A differentiated title vs near-identical siblings | Boilerplate across sibling pages | Cause 7 |
| Wording that appears nowhere on your page | 2026 AI-headline experiment | Section below |
Common causes
Ordered by hit rate, highest first.
1. Title is over ~60 characters (or ~600px desktop)
The most common trigger, and the one with the clearest data. Google measures titles in pixels, not characters — the desktop display budget is about 600px (mobile truncates around the same point). In English that works out to roughly 50–60 characters; CJK characters are wider, so the practical ceiling is about 28–30 characters. Anything past that and Google frequently substitutes a shorter version built from your H1, og:title, or first heading.
Length also predicts whether a title survives, not just whether it’s truncated. In Zyppy’s study, the 51–60 character band had the lowest rewrite rate (around 40%), while titles over 70 characters were rewritten 99.9% of the time and very short titles (1–5 chars) 96.6% of the time. The sweet spot is narrow, and it’s not “as short as possible.”
How to spot it: Count characters in your <title>. If > 60 English chars (or > 30 CJK), this is likely it. To be precise, measure pixel width with a SERP-preview tool — character count is only an approximation because W is far wider than i.
2. Title contains brand or boilerplate that drowns the page topic
"AI Productivity Tools — Best 2026 Edition — Site Name | Site Tagline". By the time Google parses past the brand and tagline, the actual topic is at character 30+. Google rewrites to put the topic first.
How to spot it: Read your title aloud. If a stranger needs to read past 4+ words before learning what the page is about, the front is bloated.
3. Title doesn’t match the dominant search query
Google looks at the queries that actually rank your page. If your title says “Five productivity hacks” but most clicks come from “ChatGPT productivity tips,” Google synthesizes a title containing “ChatGPT productivity.”
How to spot it: Search Console → Performance → pick the URL → Queries tab. If the top queries don’t appear in your title, Google may rewrite using them.
4. Title and H1 conflict
If your <title> says one thing and your <h1> says something noticeably different, Google considers the H1 the more reliable signal (it’s visible on the page) and may use it instead.
How to spot it:
curl -s "https://yourdomain.com/your-page" | grep -oE '<title>[^<]+</title>|<h1[^>]*>[^<]+</h1>'Compare. If the two diverge in topic, that’s the trigger.
5. og:title disagrees with your <title>
Easy to miss because it’s invisible in the rendered page. Since 2024, Google’s documentation lists og:title (your Open Graph title meta tag, used by social shares) as one of the nine sources it can pull a title link from. If a plugin, theme, or CMS injects an og:title that differs from your <title> — a common mismatch on WordPress and many static-site setups — Google may surface the Open Graph version instead.
How to spot it:
curl -s "https://yourdomain.com/your-page" | grep -oE '<title>[^<]+</title>|property="og:title" content="[^"]+"'If the two strings don’t match, align them (or remove the stray og:title override).
6. Title uses pipe-separated keyword stuffing
"AI tools | productivity | best 2026 | for developers | ChatGPT alternatives". Multiple pipes with disconnected fragments read as keyword stuffing, which Google’s docs flag directly. Zyppy’s data also quantified the separator gap: Google removed or replaced the pipe | 41.0% of the time versus only 19.7% for a dash — pipes are touched more than twice as often, usually swapped for a dash. If you must add a brand, a dash (- or –) survives best.
How to spot it: Count | or — separators. More than one, and the trigger is likely.
7. Title is identical or near-identical to siblings
If your /category/ page and 10 articles in it have very similar titles, Google de-duplicates by synthesizing differentiated titles per article from H1 / content. Google’s docs call this out explicitly as “repeated or boilerplate text in <title> elements.”
How to spot it: site:yourdomain.com/category/ and look at the title list. If 5+ are 80% similar, it’s duplication.
8. Date prefix or suffix that’s now stale
Titles like "2023: Best AI tools" get rewritten when Google detects the year is stale relative to the page’s freshness. Even non-date suffixes like “(Updated 2024)” can trigger.
How to spot it: Any year in your title that’s > 1 year behind publishedAt or dateModified. Update both the title and the date.
Shortest path to fix
Step 1: Find rewritten pages in Search Console
Search Console → Performance → Pages tab → sort by impressions descending. Take top 20. For each:
# Pull your current title
curl -s "https://yourdomain.com/url-path" | grep -oP '<title>\K[^<]+'Then search Google for site:yourdomain.com/url-path and copy the SERP title. Any mismatch = rewritten.
Step 2: Use the “topic + value + length” formula
For each rewritten title, follow this template:
[primary keyword phrase] — [unique value or number] [optional brand]Examples:
| Bad | Good |
|---|---|
| ”Best AI Tools 2026 | Site Name | Productivity Guide" | "12 AI tools I paid for in 2026 (and 8 I dropped)" |
| "How to deploy Astro" | "Deploy Astro to Vercel: 6 traps no one warns about" |
| "Authentication" | "Fix Firebase auth-redirect loop in 3 steps” |
Hard limits (as of June 2026):
- English: aim for 51–60 characters — Zyppy found this band has the lowest rewrite rate; ~580px desktop is the truncation wall.
- Chinese / Japanese / Korean: 28–30 characters (CJK glyphs are wider, so you hit the pixel wall sooner).
- Prefer a dash (
-/–) over a pipe|for the brand separator, and use at most one.
Step 3: Align the H1 with the new title
Your H1 should be the title’s twin, not its echo. Acceptable differences: capitalization, slight rewording. Unacceptable: different topic.
Example:
- Title: “Deploy Astro to Vercel: 6 traps no one warns about”
- H1: “6 Astro-on-Vercel deployment traps you should know”
Same topic, slightly different framing — fine. Both reinforce the same intent.
Step 4: Add the queries that are actually ranking
If Search Console shows your page ranking for “ChatGPT productivity” but your title says “AI productivity,” include “ChatGPT” in the title. This is the single most impactful change for most rewrites.
Step 5: Request indexing for changed URLs
Search Console → URL Inspection → enter the URL → “Request indexing.” This triggers a re-crawl within hours instead of days.
Step 6: Wait 2-4 weeks and verify
Google doesn’t re-evaluate immediately. After editing:
- Day 0: edit + request indexing.
- Day 3-7: re-run
site:yourdomain.com/pathand check the new title. - Day 14: if still rewritten, your title is genuinely losing the auction — go shorter, more specific.
- Day 30: check CTR in Search Console for the URL. Should move 10-30% if the rewrite was costing you clicks.
Step 7: Cap snippet length if Google keeps lengthening
If Google is appending an “explainer” beyond your title length budget, add to <head>:
<meta name="robots" content="max-snippet:60">This won’t help if Google is replacing your title; only if it’s padding.
The 2026 AI-headline rewrite is a different animal
Everything above is the classic, deterministic rewrite: Google swaps in text it can already see on your page (H1, og:title, anchor text). On March 20, 2026, Google confirmed a separate live experiment where AI rewrites the headline to better match the searcher’s query — sometimes producing wording that appears nowhere on your page, and in documented cases changing the meaning, not just the formatting (Google rewrote one article’s headline in a way that flipped its sense). Google calls it “small” and “narrow”; it started with news sites but reportedly extends to other sites too.
How to tell the two apart:
- Classic rewrite: the SERP title is verbatim from your
<title>, H1, og:title, or a heading. Fixable with the steps above. - AI rewrite: the SERP title is wording that exists nowhere in your HTML, or it keeps your words but warps the meaning. The diagnostics above won’t find a matching source string.
What you can do about the AI version (as of June 2026):
- There is no opt-out. Google has published no robots directive, no
metatag, and no Search Console toggle to exempt your site from headline rewrites in regular Search. (Don’t reach fornosnippet/data-nosnippeteither — those strip your entire organic snippet and still don’t govern the title link.) - The real, related change: on June 3, 2026 the UK CMA ordered Google to give publishers opt-out tools for AI features, and Google launched a Generative AI performance report in Search Console — but that’s AI Overviews / AI Mode reporting (initially a subset of UK site owners), not a headline-rewrite switch.
- Your only real lever is the fundamentals: a tight, accurate, query-matched
<title>gives the AI less reason to reach for its own phrasing. Make the words it would want to use the words you already wrote.
When this is not on you
Some title rewrites stick despite excellent titles. If your page genuinely ranks well and the rewritten title accurately represents the page, accept Google’s choice — the CTR is what matters, not whose exact words appear.
Easy to misdiagnose as
This looks like a bug. It’s usually intentional algorithm behavior. Don’t escalate or report — adjust your title.
Prevention
- Write titles for search intent first, branding second.
- Keep titles in the 51–60 character band (≈28–30 CJK), under ~600px desktop.
- One H1 per page that closely echoes the title, and keep
og:titlematched to<title>. - Prefer a dash over a pipe for the brand separator, and use at most one.
- Audit Search Console quarterly: for any page in the top 20 by impressions with a rewritten title, fix the title to match the dominant query.
FAQ
Does a rewritten title hurt my rankings?
No. Google has repeatedly said the title link is a display choice and your <title> element still feeds ranking. A rewrite changes what searchers see, not where you rank. Only act if the rewrite is costing clicks (check CTR in Search Console).
How long does it take for an edited title to show up?
Plan for 2–4 weeks. Requesting indexing in URL Inspection triggers a re-crawl within hours, but Google re-evaluates the title link on its own schedule. If it’s still rewritten after ~14 days, the title is genuinely losing the auction — go shorter and more query-specific.
What’s the safest title length in 2026?
Roughly 51–60 characters for English (the band with the lowest observed rewrite rate, ~40%) and 28–30 characters for Chinese/Japanese/Korean. The real wall is pixel width (~600px desktop), so verify with a SERP-preview tool rather than trusting character count alone — W is far wider than i.
Can I force Google to use my exact title?
You can’t force it, but you can win the auction: match the title to your dominant search query, keep it in the 51–60 character band, align H1 and og:title, drop boilerplate, and use one dash separator at most. For the separate 2026 AI-headline experiment there’s no override at all — no robots tag, no Search Console toggle (as of June 2026). The same fundamentals are still your best defense.
Why is the rewritten title text not anywhere on my page?
That’s the signature of the 2026 AI-headline rewrite, which can generate new phrasing rather than reusing your H1 or og:title. The classic fixes won’t find a matching source string. As of June 2026 there’s no opt-out for it, so the only thing that helps is a tighter, query-matched <title> that leaves the AI less room to improvise.