Foundational pillar / check title-quality

Title presence and our title length guideline

A missing title is a measured gap. The 30 to 60 character band is our editorial guideline, not a Google rule: Google says there is no title length limit and truncates long titles as needed, while Bing says overly short titles may reduce indexing reliability and eligibility for grounding and citations.

By Shimon Carroll, Founder, SEO for AI Agents · Last updated

What this check measures

Two things, kept separate. First, whether the document <title> is present and non-empty: that is a measured fact. Second, its visible length against our editorial guideline of 30 to 60 characters. We read the raw HTML returned by the crawler, where the title is server-rendered in practically every stack.

Why it matters

Google uses the title element as a main source for the title link and asks for titles that are descriptive and concise. It says there is no limit on title length and truncates long title links to fit the device width. Bing's Webmaster Guidelines say missing, duplicate or overly short title tags may reduce indexing reliability, ranking and eligibility for grounding results and citations. Our 30 to 60 character band sits between the two: long enough to describe the page, short enough that the words a searcher needs survive truncation. It is our editorial guideline, not a Google rule.

How we score it

Missing or empty title: HIGH severity, high confidence (a measured gap). Under 30 characters: MEDIUM, medium confidence (a clear gap Bing names). Over 60 characters: LOW, medium confidence (a truncation preference). Length findings are never high or critical, vertical overrides cannot raise them, and they never take the first action-plan slot while a measured defect exists.

Confidence-flag rules

Confidence is HIGH on all PASS / FAIL outcomes for titles found in the raw HTML (the typical case). Confidence drops to MEDIUM if the title appears only after JS hydration, which is rare and usually indicates a framework misconfiguration.

Common mistakes

  • Setting the title to just the brand name on every page ("Acme Inc."), which surrenders the intent-match click to every competitor with a more specific title.
  • Leaving the default framework title ("Next.js App", "create-react-app", "untitled") on production pages because the metadata API was never wired up.
  • Stuffing the title past 60 characters with a long keyword string, causing the trailing brand suffix to be truncated in the SERP.
  • Mirroring the H1 verbatim, which wastes the disambiguation signal both surfaces could provide.

How to fix it

If the title is missing, add one that names the page topic and the brand. If it is long, check that the words a searcher needs come first so truncation does not cut them, and shorten only if it is verbose. If it is short, make sure it still says what the page is about. For Next.js, the title.template pattern in the root layout metadata adds the brand suffix to every route.

Primary sources

Changelog

  • · Split the measured fact (a title exists) from our editorial length guideline, with Google and Bing sources. A short title is medium (Bing names overly short titles as a grounding risk), a long title is low (a truncation preference). Neither is ever high or critical.
  • · Initial publication. Length bounds locked at 30 to 60 visible characters per the prevailing SERP pixel-width study (Moz, 2024 update).
← Back to the methodology indexRun an audit