What it is
This check looks at the same <title> tag covered elsewhere from technical and SEO angles, but specifically from the standpoint of a visitor's very first, split-second impression: what does the browser tab actually say the instant this page opens? A generic fallback like "Untitled Document", a bare web address, or a placeholder left over from a template are all things a visitor can notice before they've engaged with the page's actual content at all.
This is a small detail in isolation, but it's one of the very first things visible when a page opens — arriving even before the page has finished loading its images or design.
Why it matters
First impressions form quickly and are hard to fully undo once made — a browser tab that reads as generic or broken plants a small, immediate seed of doubt before a visitor has given the actual content any real chance. It's a tiny detail, but it's exactly the kind of tiny detail that adds up alongside other small signs of an unfinished site, each individually minor but collectively suggesting the whole thing wasn't fully finished before launch.
Because it costs almost nothing to fix — writing one short, real sentence — there's little reason for any page a visitor might actually land on to skip this, however minor it may seem in isolation.
How to fix it
- Open your own site in a new browser tab and actually look at what the tab itself displays, rather than just the page content.
- If it shows something generic like "Untitled Document", your site's raw address, or a placeholder phrase, write and add a real
<title>for that page. - Keep it short, specific, and readable — a real page name recognizable at a glance, even when the tab is narrow and the text gets cut off.
- Check a handful of other pages too, since a generic title on one page built from a shared template often means several others have the same gap.
- Re-run your Launch Readiness check to confirm real titles are now detected across your key pages.