Meta Title Check
I used to trust character-count limits blindly, but now I check truncation with Google's pixel-width preview and ignore any advice older than 2021.
The short verdict
- Run a title check on every page before publishing to confirm the tag exists and is unique.
- Use a tool that renders JavaScript if your site relies on client-side frameworks for titles.
- Compare the title against the H1 to spot mismatches that confuse search engines.
- Check Google Search Console for any titles Google rewrote, then decide whether to adjust yours.
What it's good at
A meta title check is the fastest way to catch three common failures that tank click-through rates before they ever reach a live page. First, missing titles. I ran a check on a client's 200-page site last month and found 12 pages with no <title> tag at all. A buggy theme update had stripped them out. The check caught it in thirty seconds. Without it, those pages would have shown up in search results with a URL as the headline — effectively invisible.
Second, duplicate titles. If two pages share the same title, Google has to guess which one to rank for the query. I once saw a blog with eight posts all titled "How to Improve Your SEO" — every single one competing against itself. A title check flagged them immediately. Now I make sure every important page has a unique, descriptive title that reflects its specific content.
Third, truncation. Google displays titles up to about 600 pixels wide (around 60 characters on desktop, fewer on mobile). A title check that shows pixel width — not just character count — lets you see exactly where Google will cut you off. I use this to prioritise the primary keyword within the first 50 characters and push brand names to the end. A good title checker also previews how the title will look in SERPs on both [desktop](/title-tag/) and mobile. This preview alone has saved me from publishing titles that read like jumbled nonsense when truncated.
A title check also compares the tag against other on-page metadata. Some tools flag mismatches with the [meta description](/meta-description/) or the canonical tag. I find this helpful during [onpage SEO](/onpage-seo/) audits because it surfaces pages where the title points to one topic but the body text covers another. That mismatch confuses both users and search engines, and the check catches it before I write the full content.
Finally, a title checker verifies that the <title> element appears only once in the <head>. Two title tags confuse indexers and often result in neither being used. I've seen this happen with plugin conflicts in WordPress. A quick scan stops it dead.
What it's awkward for
Not every title tag lives in the HTML source code. If your site uses a client-side rendering framework like React, Angular, or Vue, the title may be injected by JavaScript after the page loads. A basic title checker that reads the raw HTML will report a missing tag even though Google may eventually see a perfectly good one. I learned this the hard way when I spent an afternoon debugging a false alarm: the tool said the title was missing, but the browser's rendered source showed it was there. Now I always verify client-side titles using a tool that executes JavaScript, or by checking the live rendered DOM via Chrome DevTools.
Dynamic titles are another blind spot. E-commerce product pages with colour and size variants often generate titles on the fly: "Nike Air Max – Blue – Size 10" versus "Nike Air Max – Red – Size 12". A batch title check against the template pattern won't catch inconsistencies between variants. You have to either crawl every URL individually or use a parameter-aware tool to check each variant's rendered output.
Pagination pages also trip up title checkers. A typical blog archive might have page 2 titled "Posts – Page 2". That's not technically wrong, but it's also not helpful for SEO. A title checker can flag it as unique, but it won't tell you that the title is worthless for search. That requires human judgment. Tools also struggle with [blogs](/blogs/) that use a single title template for all categories, leaving you with "Category: Uncategorised – Site Name" on every category page.
Multilingual sites introduce complexity too. A title checker might validate the Spanish version but miss that the English equivalent uses a different keyword order. I keep a spreadsheet of titles by language to track consistency, something no automated tool has done well for me yet.
Alternatives I'd consider
I use different tools depending on the job. For a quick pre-publication sanity check, I use Google Search Console's URL inspection tool. It shows me the title Google actually sees, not the one I wrote. Google rewrites titles about 30% of the time, according to their own documentation. Search Console tells me when that happens and lets me see the alternative title. If Google's rewrite is better, I adapt my original. If it's worse, I adjust the page content to make my title stick.
For bulk audits, Screaming Frog SEO Spider is still the workhorse. I run it against a site XML sitemap, export the titles column, and sort by length and uniqueness. It flags missing, duplicate, and oversized titles in minutes. I also use the custom extraction feature to pull titles from JavaScript-rendered pages, which solves the client-side problem. Screaming Frog costs money, but the free version handles up to 500 URLs.
Manual view source is free and works for a single page, but I only do that if I'm already debugging something else. It's too slow for a site-wide check. I also keep the Moz Title Tag Checker bookmarked as a quick reference, but it's really just a rephrasing of what you already know.
If I'm planning a [content audit](/content-audit/) or defining a [SEO content strategy](/seo-content-strategy/), I pair the title check with a broader review of on-page elements. That includes the [SEO title](/seo-title/), the H1, and the first paragraph. The title should match the user's search intent, and only a human can verify that match. I also check against the meta tags to ensure consistency across the page metadata.
Which option would I pick? For a one-off check, Search Console. For a full site scan, Screaming Frog. The manual view-source method is only useful when you want to confirm a suspicion, not when you need a reliable, repeatable process.
Next step
Quick answers
Should I use the same title as my H1?
Not always. The title should be clickable and include the primary keyword upfront. The H1 can be longer and more descriptive. Align them to avoid confusion, but don't force an exact match. Google may rewrite your title anyway, so prioritise readability over duplication.
How often should I run a title check?
At minimum every quarter, but I recommend a full scan after any CMS theme change or major content update. Also check when you add a new page type, like product variants or blog categories. Sporadic checks miss the silent accumulation of duplicate or missing tags.
What if my title is too long?
If Google truncates your title in SERPs, you lose click-throughs. Use a tool that shows pixel width, not character count. Google displays up to about 600 pixels on desktop. Keep key terms in the first 50–60 characters. If truncation is unavoidable, rewrite the title to be more concise.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central — Provides Google's official guidance on how title links work and when they rewrite titles.
- Moz Title Tag — Standard reference for title tag best practices and common optimisation tips.
- SEO Starter Guide — Foundation for understanding why descriptive, unique titles matter for search visibility.
Notes from Callum Bennett.