Getting indexed and getting ranked are two problems. Getting clicked is a third, and it's the one most people never work on. A page can hold a decent position, appear in a social feed, and sit on a bookmarking site all week — and still get passed over, because the words representing it give nobody a reason to stop.
The core idea: your title's job is not to describe the page, it's to answer "is this the one?" faster than the results around it. That means front-loading what makes your page different, matching what the reader wants instead of teasing it, and writing a description that echoes their question rather than summarising your article.
Three surfaces, three sets of rules
A search result is a comparison screen. Your title sits inches from nine alternatives and the reader is scanning for a match to their intent. Specificity wins; cleverness loses, because nobody is charmed mid-scan.
A social preview is an interruption. Nobody searched for you — your card appeared between a friend's photo and a video. The image carries more weight than it ever does in search, and the title works with no query for context.
A link or bookmark listing is a browse surface: a column of submissions, often with no image and a short snippet. This is where a title leaning on your brand ("Our thoughts on…") disappears completely, and where plain phrasing punches above its weight — which is why the honest submissions described in our content promotion guide do better when the title was written for browsing rather than for your homepage.
One title can serve all three, but only if you write it for the hardest case: a stranger, with no context, scanning fast.
Title tag, H1, and social title are three different fields
They're often filled with the same string, and that's usually fine — but they aren't the same job. The title tag (<title>) is what engines display in results and browsers show in the tab; written for a stranger comparing options, it carries the differentiator and the query language. The H1 is read by someone who already clicked, so it can be shorter or warmer. The social title (og:title) appears with no query behind it, so it needs to be self-contained. If you maintain only one, maintain the title tag — it does the most work, and it's the one that most often defaults to your site name plus a slug.
Why engines rewrite your title
Search engines routinely display something other than the title tag you wrote. It isn't a penalty and it isn't random: rewrites happen when a title is a poor fit for the query or a poor representation of the page — stuffed with keywords, padded with boilerplate, duplicated across pages, very long or very short, or when an on-page heading matches the query more closely.
Don't fight it; remove the reasons. Cut the site-name suffixes that make every title look templated, make every title unique, keep it aligned with the page's main heading, and drop the repeated keyword — it reads as spam to systems and to people.
Length, truncation, and front-loading
Truncation isn't measured in characters. It's measured in pixels, and it changes by device and surface; a title full of wide letters gets cut sooner than one of narrow letters at the same character count. The rules of thumb you'll see quoted (commonly around sixty characters) approximate that pixel budget rather than defining a limit.
Which leaves one tactic that reliably works: front-load. Put the differentiator in the first few words and treat everything after as a bonus that may not survive. Test it by covering the back half of your title and asking whether what remains still says what the page is and why it's different. Put the specific before the generic — "Reset a locked account without support" beats "A guide to account access issues" — and stop spending your first words on your brand.
Match the intent — don't tease it
The most common title mistake isn't length, it's genre. Curiosity-gap headlines are optimised for a feed, where the only alternative to clicking is scrolling. In a search result the reader has a specific need and nine other options, so a title that withholds the answer loses to one that signals it. Match the shape of the query: the action and outcome for a how-to, the plainly named concept for an explainer, both options and the deciding factor for a comparison, the symptom in the reader's own words for troubleshooting.
That last one matters more than it sounds. Users search the symptom; writers title the diagnosis. Which is why why your pages aren't getting indexed works as a title — it's the reader's sentence, not the system's.
Numbers and brackets add scannable structure until two things happen. Saturation: when every result uses the same device it becomes wallpaper, so check the real results first. And dishonesty: a number that doesn't match the page buys a click and loses the reader immediately.
The description is a query echo, not a summary
Meta descriptions aren't a direct ranking factor, and engines often generate their own snippet. That leads many people to skip them, which is a mistake: when yours is used, it's the sentence that closes the click.
Write it as a query echo — restate the reader's problem in their language, then say what the page gives them and what they'll be able to do afterwards. Don't repeat the title, keep the useful part early because the tail gets cut, write a distinct one per page, and be honest: a description promising a checklist had better describe a page that has one.
Open Graph: the minimum that stops previews looking broken
When a page is shared, most platforms read Open Graph tags to build the card. Without them they guess, and the guess is often your logo or a navigation fragment. The core set is small: og:title, og:description, og:image (a wide landscape image — the widely used ratio is roughly 1.91:1 — with any text large enough to survive being shrunk into a feed), og:url set to the canonical address, and og:type, usually article.
Requirements change and platforms read their own card tags alongside Open Graph, so check each platform's current documentation and use its preview tool. Most cache what they fetched first, so fixing tags after sharing usually means asking the platform to re-scrape the URL.
Build a testing loop from your own data
Guessing is optional, because Search Console gives you the raw material for a real feedback loop.
- Find the gap. Look for pages with solid impressions and weak clicks relative to their average position. People see it and don't choose it — that's a title problem, not a ranking problem.
- Read the queries, not your assumptions. The language people actually used is your title vocabulary, and it's often not the language you wrote in.
- Change one thing. Rewrite the title or the description, not both, on a handful of pages. Note the date.
- Compare like for like. Give it a few weeks, compare equal-length date ranges, and watch position too — if position moved, clicks moved for reasons unrelated to your edit.
- Keep what worked. One win on one page is noise; the same pattern winning across several is a rule you've earned.
Don't rewrite everything at once, or you'll learn nothing. And search isn't your only click source — referral traffic from social and listing sites responds to the same edits, which is why it's worth tracking referral traffic properly alongside your search numbers.
FAQ
Should the title tag and H1 be identical?
They can be, and for most pages that's a reasonable default. Diverging is worth it when the query language is clunky as an on-page headline: keep the searchable phrasing in the title tag and let the H1 read naturally for someone who has already arrived.
Does Google always use my meta description?
No. Engines frequently generate a snippet from page content when it matches the query better. Write one anyway: it's used often enough to matter, and many social and listing surfaces fall back on it when nothing else is available.
Do titles matter for bookmarking and directory listings?
Yes, arguably more, because those surfaces show less. With no image and a short snippet, the title carries almost the whole decision. Submit with the same front-loaded phrasing you'd use for search, and write a genuine one-line description rather than pasting your first paragraph.
Rewrite five titles this week
Pick five pages with real impressions and disappointing clicks. Read the queries they already attract, rewrite each title so the differentiator lands in the first few words, write a description that echoes the reader's question, and check the social card renders as you expect. Then leave them alone for a few weeks. Unlike a ranking change, a better title improves every impression the page will ever get.
Once the titles are worth clicking, put those pages where people browse: see the curated lists of social bookmarking and content discovery sites at SocialBookmarkKey and pick the ones that fit your topic.
