Paste a page URL and see the title tag search engines are served: its length in characters, its estimated width in pixels, whether it sits inside Verand's 30 to 60 character range, and a preview of where a desktop result may cut it off.
4 checks, on the served title. Is there a title, is it over 60 characters, is it under 30, and is it identical to the H1. One GET of the URL as VerandBot/1.0, redirects followed, 12 second timeout, the served HTML only: no JavaScript is run. The first <title> in the document is the one read.
In your browser, from Arial's published character widths at 20px, with no kerning. Roughly 600 px is the desktop line this preview assumes. Google publishes no pixel limit and font rendering varies, so the width is an estimate beside the result, never one of the four checks.
A title set by JavaScript after load. Duplicate titles across your site, since it reads one URL. Whether Google will rewrite the title. Mobile results. HTML entities such as & are read as a space, so a title that uses them can count a character or two short. The H1 check passes when a page has no H1; the card says so.
One fetch, one title, four checks and a measurement. The card is the tool in motion on an example page, looped, and each step lights up while the card is doing it.
The tool asks for the URL you typed as VerandBot, follows redirects to the final address, and gives up after twelve seconds. It reads the HTML the server sends. It does not run the page's JavaScript.
The first <title> element in the document is taken, tags inside it stripped and runs of whitespace collapsed to one space, then trimmed. The page's first H1 is read the same way, for comparison.
Is there a title at all. Is it longer than 60 characters. Is it shorter than 30. Is it identical to the H1, ignoring case and spacing. The same four questions Verand's site audit asks of every page it crawls.
Your browser adds up each character's width in 20px Arial and draws the result as a desktop listing, cut with an ellipsis where roughly 600 px runs out. It is an estimate, shown beside the checks rather than scored.
The title tag is one line of HTML, and it is the line a searcher reads before deciding whether to visit. Here is what it does, how long it should be, why Google sometimes replaces it, and what changes when the page is selling a regulated service.
A title tag is the <title> element inside a page's <head>. It never appears in the page body. Browsers put it on the tab and in bookmarks, and search engines use it as the first candidate for the blue headline of a result, which Google calls the title link. One page should carry one title, written for that page alone.
<head> <title>Break-Even Ratio: What It Tells You About a Rental | Your Firm</title> <meta name="description" content="..."> </head> <body> <h1>How to read a property's break-even ratio</h1>
Three things are easy to confuse with it. The H1 is the visible headline at the top of the page, written for someone already reading. The og:title meta tag is the headline social platforms show when the link is shared. The meta description is the grey text under the title in a result. All four can say different things, and often should, but they should never contradict each other.
There is no official number. Google's documentation says title links are "truncated in Google Search results as needed, typically to fit the device width", and states no character limit for the element itself. The ranges on the pages that rank for this topic disagree: 50 to 60 characters, 20 to 70 characters, or about 580 to 600 pixels. Each is an observation of where results tend to cut, not a rule.
Verand's audit uses a range: a title under 30 characters is flagged as likely to under-describe the page, and a title over 60 is flagged as likely to be cut. The low end matters as much as the high end. A title like "Pricing | Your Firm" wastes the one line where a searcher decides whether this is the page they wanted. The high end is a soft limit: a title a few characters over often shows in full, and a title well under can still be cut if it is built from wide letters. That is why this checker reports the meta title length in characters and the estimated width in pixels side by side.
Results are laid out in a proportional font, so a character count is only a proxy. In Arial, the face this preview uses, a capital W is 944 thousandths of the type size wide and a lowercase i is 222, more than four times narrower. At 20px that is roughly 19 px against 4 px. A title heavy in capitals, digits and wide words runs out of room long before one written in lowercase.
Two real runs from this page show the gap. Verand's own home page title is 66 characters and fails the 60-character check, yet its estimated width is about 591 px, inside a 600 px line. Willowdale Equity's break-even ratio article is 67 characters, one more, and its estimated width is about 643 px, well past it. Nearly the same character count, a different outcome in the preview. The character check is the stable rule Verand scores; the pixel figure tells you which side of the line a borderline title probably falls on. Treat the pixel figure as an estimate: Google can bold words that match the query, fonts render differently across systems, and Google has never published a pixel limit.
Google does not always use your title tag. Its documentation lists what it draws on to build a title link: the <title> element, the main visual title on the page, heading elements such as the H1, the og:title tag, other large and prominent text, anchor text on the page and in links pointing to it, and WebSite structured data. In August 2021 Google published an update to how it generates web page titles, and a title tag has been a strong suggestion rather than a guarantee ever since.
The same documentation names the patterns that invite a rewrite: a half-empty title with little more than the site name, an obsolete title that no longer matches the page (a year that has passed is the usual culprit), a title that is inaccurate about what the page covers, micro-boilerplate where many pages share nearly the same title, and the site name repeated inside the title. None of these is a length problem, and a checker that measures length, this one included, will pass most of them. The fix for each is the same: make the title describe this page, specifically, and keep it current.
Many sites never write their title in the HTML the server sends. A single-page app may ship a default title, the framework's name or a placeholder, and replace it with JavaScript once the page runs. A theme may print one title and an SEO plugin a second. Google says you can set or change the title with JavaScript, and Googlebot does render pages in a headless Chromium, but it queues pages for rendering, and "it can take longer" than a few seconds before that happens. Not every crawler that reads your page runs JavaScript at all, and link previews built from the served HTML will show whatever the server sent.
This checker reads the served HTML and does not run scripts, which is a limit and, for this question, the useful view. If the title on the card is not the title you see in the browser tab, your real title only exists after JavaScript runs. The durable fix is to have the server, or the static build, write the final title into the HTML so every reader gets the same line. If the card shows a title you do not recognise, look for a second <title> printed by a theme or plugin: the tool takes the first one in the document, which is the order a simple parser reads them in.
Most titles end with the firm's name after a pipe or a hyphen, and Google's guidance supports putting the site name at the beginning or end, separated by a delimiter. The trouble starts when the suffix is long. "| Willowdale Equity" is 19 characters of a 60-character budget; a two-partner law practice with "LLP" and a city can spend 30. Put the words that describe the page first, so that if the end is cut, the part that goes is the name the searcher can already see in the result's site line.
Firms with several offices meet a second problem: duplicate titles. A practice with six office pages that all read "Estate Planning Attorney | Smith Law" has six pages competing on one headline, and Google's micro-boilerplate warning describes exactly that. Put the location in the title ("Estate Planning Attorney in Oak Park") and make each page say something only that office can say. One-URL checkers cannot see this; it takes a comparison across pages, which is what Verand's full site audit does.
For a financial adviser, an attorney or a medical practice, the title tag is often the first piece of advertising a prospect reads, and it is written in the least reviewed part of the page. Words that are routine in marketing, "best", "top-rated", "guaranteed", "results", are the ones advertising rules for advisers, lawyers and healthcare providers often restrict. A title that says "Guaranteed Retirement Income Strategies" can make a promise that the careful body copy below it never makes.
Two habits keep titles safe to publish. Keep them factual: what the page covers and for whom, not how good the firm is. And remember that Google may replace the title with the H1 or other prominent text, so the H1 needs to be something your compliance reviewer would sign off on as a headline in search results too. Have your reviewer confirm title wording the way they confirm body copy. This page is not legal advice, and the checker does not judge wording; it measures the title and flags what is missing or out of range.
Specific to one page, led by the words a searcher would use, between roughly 30 and 60 characters, with the brand at the end where a cut costs least. Factual rather than superlative, consistent with the H1 without copying it, and written into the HTML the server sends. Then check it again after a redesign or a plugin update, because titles are generated by templates and templates change.
Six things that are true of this tool, each one backed by the code that runs it.
The request carries a URL and nothing else. There is no account and no session behind the tool, and the whole result is on the page.
The character checks come from the audit; the pixel width is estimated in your browser and labelled as an estimate. When the two disagree, the card shows both rather than picking one.
Every check is a comparison on the title's text, and the width comes from a fixed table of character widths. No model reads the page, so the same title gives the same answer every time.
These are the title checks Verand's deep crawl runs on every page of every customer site every two weeks, called directly on one URL. Not a lighter demo version.
Titles set by JavaScript, duplicates across pages, Google's rewrites and mobile results are out of scope, and the card says so beside the result rather than in a footnote.
Each run is one page fetch and a parse, so it is never metered. The one limit is a courtesy to the sites being fetched: 20 checks a minute per visitor.
How long a title should be, why Google changes it, and what this tool can and cannot tell you.
Google publishes no limit; it truncates title links to fit the device width. Verand's audit flags a title under 30 characters as likely to under-describe the page and one over 60 as likely to be cut, and most published advice lands in a similar range. Treat 60 as a soft limit: a title a little over can still show in full if its letters are narrow, which is why this checker also estimates the width in pixels.
Results are cut by the space the text takes up, so pixels are closer to what happens, and characters are the stable proxy. This page works as a title tag pixel width checker as well: it counts characters for the four checks and, separately, estimates the width in 20px Arial against a desktop line of roughly 600 px. The pixel figure is an estimate, since Google states no pixel limit, can bold words that match the query, and fonts render differently across systems.
Google builds title links from several sources, not only the title tag: the main visible title, heading elements, the og:title tag, prominent text, anchor text and WebSite structured data. It tends to replace titles that are half-empty, out of date, inaccurate, repeated across many pages, or that repeat the site name. Rewrites are not something any checker can predict. Making the title specific to the page and current is the part within your control.
The pages compete on the same headline and a searcher cannot tell them apart, and Google lists repeated, boilerplate titles as one of the reasons it writes its own. This tool reads a single URL, so it cannot detect duplicates. Verand's full site audit compares titles across every page it crawls and flags the ones that match.
The title tag sits in the head and is shown in the browser tab and as the candidate headline of a search result. The H1 is the visible headline at the top of the page. They should agree on the topic, and they can differ in wording: the title written for someone scanning results, the H1 for someone already reading. This checker flags a title identical to the H1 at low severity, and passes the check when the page has no H1 to compare.
Nothing on this page predicts whether an assistant will cite you, and no operator has published a rule about title tags. What is observable: an assistant that fetches your page reads the served HTML, where the title is the page's own one-line summary, and some assistants show a source's title beside a citation. An accurate, specific title that is present in the served HTML is the safer choice either way. Verand tracks where ChatGPT, Gemini, Perplexity, Claude and Google's AI answers actually name you, which is how you find out.
Verand writes articles from your own expertise and credentials, titles included, so the page behind the headline is worth landing on. It gets them found on Google and in AI answers, then tracks where you rank and where ChatGPT, Gemini, Perplexity, Claude and Google's AI answers mention you. And every draft passes a compliance gate, so a claim your regulator would not allow never reaches a title or anywhere else.
Content built to rank in
Google and get cited by
ChatGPT
Perplexity
Gemini
Claude, with every claim checked before it goes live.