I Write the Meta Title Before I Write the Article
The title tag gets treated as paperwork. Something you fill in once the real work is done, usually by whoever is closest to the publish button, usually in a hurry.
It is the first line of copy a reader ever sees, and for most pages it is the only line the majority of searchers will ever see.
I started writing titles first partly as a discipline exercise. If you cannot compress the page into sixty characters before writing it, the page does not have a single clear job yet, and that shows up later in the body copy too.
Here are the five patterns that survive Google’s rewrites, how the description pairs with each, and the mistakes that get both replaced.
The Title and Description Are One Unit, Not Two Fields
A title and description pair is ad copy your page already owns, written once and displayed free every time the page ranks. The title is the headline. The description is the single line of body copy underneath it.
Most editorial checklists still review them separately. An SEO specialist checks the title for keyword placement. A copywriter drafts the description weeks later with no memory of what the title promised. The result reads like two people describing the same page to each other over a bad connection.
Write both in one sitting, against the same intent, before either is considered finished.
You are writing an instruction, not a guarantee
Google does not promise to show what you wrote. Its documentation states there is no fixed length for a snippet and that it gets rewritten to fit the device and the query (Source).
Independent tracking puts the rewrite rate at roughly six in ten pages.
That number changes how I think about the task. You are writing a strong instruction, not a locked field. AI Overviews pull from the same on-page signals, so a pair that clearly states the page’s answer is more likely to survive both the rewrite and the extraction.
Five Title Formulas
Benefit-first
Lead with the outcome, then name the topic.
“Cut Page Load Time in Half: A Core Web Vitals Checklist” beats the plain checklist version because the benefit sits inside the first 30 characters, where it survives truncation on desktop and mobile alike.
Best for how-to and comparison content, where the reader already knows the pain and is scanning for the fastest exit.
Question
Mirror the query, interrogative word included. “How Long Should a Meta Title Be in 2026?” matches the searcher’s own phrasing more closely than any statement version of the same idea.
It is also the format most likely to get pulled into a People Also Ask box.
Use it only when the primary keyword is naturally phrased as a question. Forcing a question mark onto a transactional query reads as clickbait and gets rewritten quickly.
Number plus outcome
A count sets scope before the click: “7 Meta Title Formulas That Held Up After the May 2026 Update.”
Numbers answer an unspoken question, which is how much am I signing up to read, and that lowers the perceived cost of clicking.
Keep the number specific rather than round. Seven and eleven test better than five and ten, because they read as counted rather than chosen for symmetry.
Direct answer
State the answer inside the title. “Meta Titles: 50 to 60 Characters, Not 70.”
This one is built for featured snippets and AI Overview extraction, since the title resolves the query without a click. Use it for definitional or numeric questions where the honest answer is genuinely short.
Get Content Whale’s stories in your inbox
Join Medium for free to get updates from this writer.
Yes, it costs you some clicks. It buys visibility on queries where you were never getting the click anyway.
Comparison
Put both sides of the decision in the title. “Meta Title vs. Title Tag: Are They the Same Thing?”
It earns clicks from people actively choosing between two options, and it holds position well because it matches a narrow, well-defined intent that generic titles cannot serve as precisely.
Then the Description Does the Other Half
Once the title is set, the description has exactly one job: confirm the promise and add the detail the title had no room for. A price, a timeframe, a proof point, a named method.
The 150-character rule is shrinking
Google has never published a hard limit. Its guidance says there is no length cap, but the snippet is truncated to fit the device (Source).
In practice that lands around 155 to 160 characters on desktop and closer to 120 on mobile, since mobile renders in a narrower column.
Testing published by SEO analyst Cyrus Shepard found descriptions written tight to roughly 120 characters outperformed longer versions on mobile-heavy queries (Source).
Write the sentence that matters most first. Treat everything past 120 characters as a bonus that may not survive a phone screen.
Stop restating the title
A description that rephrases the title wastes the only extra line Google gives you.
If the title says “7 Meta Title Formulas,” the description should not say “Learn 7 formulas for writing meta titles.” It should answer the next question: who this is for, what makes the list different, or what happens after applying it.
Worked Pairs Across Page Types
- Ecommerce product page. Title: “Merino Wool Base Layer | Ships Free Over $75.” Description: “Odor-resistant, breathable merino built for 30F to 60F. True-to-size fit, free returns within 60 days.” The title leads with the product rather than a superlative, because product-page searchers already know what they want and are comparing sellers on specifics. The description adds the two things a comparison shopper actually checks, temperature range and returns, neither of which fits in a title.
- Blog how-to. Title: “How Long Should a Meta Title Be in 2026?” Description: “50 to 60 characters, but pixel width decides the real cutoff. See five formulas and ten worked examples.” The description answers the question in its first four words, so a scanning reader gets the fact without clicking. The second sentence supplies the reason to click anyway.
- Local service. Title: “Emergency Plumber in Austin, TX | 24/7 Dispatch.” Description: “Licensed, bonded, dispatched within the hour. Flat-rate quote before any work starts.” Local intent is transactional, so the title front-loads service and city, the two tokens Google bolds most reliably. The description answers the three questions every emergency caller has: are you licensed, how fast, and will the quote change when you arrive.
- Comparison page. Title: “SEO Consultant vs. SEO Agency: What Changes.” Description: “Same deliverables, different accountability. Compare scope, pricing bands, and when each option runs out of runway.”
- Definitional page. Title: “What Is a Meta Keywords Tag? (2026 Update).” Description: “A legacy HTML tag Google stopped using in 2009. Here is what actually influences rankings and AI citation now.”
What Gets Both Rewritten?
Three mistakes account for most of the rewrites I see during audits.
- Keyword-stuffed titles built as terms separated by pipes. They read as spam and get replaced more often than titles written as sentences.
- Duplicate descriptions repeated across catalogue or location pages, which damage every page in the set because Google cannot identify which is authoritative.
- Titles past roughly 580 to 600 pixels, which get cut mid-word rather than mid-sentence and look broken even when the copy underneath is fine.
There is a fourth that deserves its own mention. A description describing the tag rather than the page, “This page is about running shoes,” is functionally empty and gets discarded in favour of an auto-generated snippet nearly every time.
Preview the rendered snippet before publishing. A character counter will not catch pixel-width truncation.
The Reframe Worth Keeping
A rewritten title is not a failed copy. It is Google telling you the page answered a real query better than your metadata did.
Treat it as feedback, tighten the pair, republish. Teams reviewing title and description performance in Search Console monthly catch that drift before it costs a quarter of rankings.
If you would rather have both written as one unit from your own keyword data, that is a conversation our team is happy to have.
