Title Tag Rewriting - When Google Ignores Your Title

Google rewrites the majority of title tags it encounters. Zyppy's study of 80,959 titles found a 61.6% rewrite rate. Search Engine Land reported that by Q1 2025, Google changed 76% of title tags. The trend is accelerating because AI Overviews need concise, consistent titles to display in generated answers.

A rewritten title is not just cosmetic. When Google changes your title, it controls how your page appears in search results. That controls click-through rate. And click-through rate feeds directly into NavBoost, Google's click-based ranking signal. A bad title rewrite can start a downward spiral: worse title, fewer clicks, lower NavBoost score, lower ranking, even fewer clicks.

Wire prevents title rewrites through three mechanisms: prompt rules that teach Claude to write compliant titles, auto-fixes that correct known triggers on save, and audit detection that flags violations across the entire site.

What Triggers a Rewrite

Length

Titles over 60 characters get truncated in search results. But truncation is not the same as rewriting. Google often rewrites the entire title when truncation would produce a meaningless fragment.

The Zyppy study found the sweet spot: 51-60 characters had the lowest rewrite rate at 39-42%. Titles under 20 characters were rewritten almost universally because they lack enough context for Google to confirm relevance.

Wire enforces 51-55 characters in the styleguide. The narrower range (55 instead of 60) leaves room for Google to append a site name without triggering truncation.

Brackets and Pipes

Brackets in titles ([Guide], [2026], [Updated]) trigger rewrites 77.6% of the time. Google removes the bracketed portion entirely in 32.9% of cases. What was meant as a trust signal becomes a liability.

Pipes (|) fare slightly better but still trigger more rewrites than dashes. Google frequently replaces pipes with dashes anyway, so the original intent is lost.

Wire's auto-fix pipeline converts pipes to dashes and strips brackets on every save. No manual review needed.

H1 Mismatch

The Google API leak revealed a titleMatchScore feature that measures alignment between <title> and the page's primary heading. When the title says "Complete Guide to Invoice Processing" but the H1 says "Invoice Automation," Google rewrites the title to match what it detects as the page's actual topic.

Zyppy confirmed this: pages where H1 matches the title have significantly lower rewrite rates across the board.

Wire handles this two ways. For sites using markdown H1 (# Title), the auto-fix system aligns H1 text to match the frontmatter title. For sites using template-rendered H1 (<h1>{{ page.title }}</h1>), both tags are automatically identical because they come from the same source.

Brand Name in Title

Most sites append - Brand Name or | Brand Name to every title tag. This is a legacy pattern from before Google started displaying the site name separately in search results. Google now shows the site name above the title in its own line (sourced from WebSite JSON-LD, OG tags, or the domain itself). The screenshot below any Google result confirms this: the brand appears in the favicon row, not in the blue title link.

Appending the brand to <title> burns 7-15 characters on every page. On a 55-character title, that is 13-27% of your space consumed by information Google already displays. Worse, it creates a boilerplate pattern across every page, which is itself a rewrite trigger.

Wire does not append the site name to title tags. The <title> contains only the page title from frontmatter. The brand is communicated through JSON-LD (publisher.name), Open Graph tags, and the domain. This is an opinionated choice. Most static site generators and CMS platforms append the brand by default. Wire deliberately does not because the evidence shows it wastes characters and increases rewrite risk.

Keyword Stuffing

Titles that repeat keywords or stack multiple keyword variations trigger rewrites. Google's rewrite system detects when a title is optimized for search engines rather than users. The irony: writing a title "for SEO" is now the fastest way to lose control of it.

Wire's styleguide instructs Claude to write titles for clarity, not keyword density. The evidence from the API leak confirms that NavBoost (user behavior) matters more than keyword matching for ranking.

Boilerplate Patterns

Titles that follow a rigid template across every page ({Product} | {Category} | {Site}) signal low editorial effort. Google rewrites these to differentiate pages in search results.

Wire generates unique titles per page through Claude, not through templates. Each title reflects the page's specific content, not a site-wide pattern.

The AI Overviews Factor

AI Overviews reduce organic CTR by 34-61% depending on the query. When CTR was 28% at position 1, a bad title cost you clicks. When CTR is 2.8% at position 1, every click matters exponentially more.

Ahrefs' December 2025 update found that AI Overviews reduce position-one CTR by 58%. In this environment, title optimization is not about marginal gains. It is about survival. A title that gets rewritten into something generic may lose 30-50% of already-diminished clicks.

Pages cited in AI Overviews earn 35% more organic clicks. The title displayed in the AI Overview citation matters because it is the primary decision factor for whether users click through to the source.

Wire's Title Protection Stack

Layer 1: Prevention (Styleguide)

The styleguide teaches Claude these rules before it writes any title:

• 51-55 characters
• Use dashes, not pipes or brackets
• Match the H1 exactly
• Lead with the most important concept
• No keyword stacking

Layer 2: Auto-Fix (Sanitizer)

Three of Wire's nine auto-fixes target titles:

Layer 3: Detection (Audit)

The audit system flags:

• Long titles. Over 60 characters, likely to be truncated or rewritten.
• Duplicate titles. Two pages competing for the same SERP slot.
• H1 mismatch. Detected across all pages, reported in HEALTH section.

The build-time linter adds RULE-05 (title present, unique, 20-65 characters) as a hard build failure.

Measuring Rewrite Exposure

Wire does not currently check whether Google has rewritten your titles (that requires GSC data comparison). But the audit prevents the known triggers:

Sites running Wire's full pipeline (styleguide + auto-fix + audit) eliminate every known rewrite trigger before pages reach production.