The document title should name this page, not repeat the site name

What it is

document.title is this document’s name in the browser. It must say what this page is: which article, which product, which settings step—not the same brand on every page of the site. The site name may be a suffix; it cannot be the only content. The title answers “what is this document called,” not “what is this product called.”

Why it happens

Browsers, operating systems, and screen readers treat document.title as the primary key they display and speak for this document. If that key is constant across the site, documents cannot be indexed. After leaving the page, working memory holds “I was reading that piece on the back stack,” not the brand. A site-wide name welds every history row, every tab, and every screen-reader window list into one sentence; retrieval can only use remembered order. An SPA that sets title once on the shell and never changes it on route change is worse: the object inside already changed, the OS still thinks it is the same document.

Putting the brand first (Acme — Invoice #1842) crops to Acme on a narrow tab. Specific content first may still name the object after the crop. The title is not an ad slot; using it for a slogan abandons this document’s name in the system.

Studying it

Collect document.title from several interior pages of one site. Run a “find the page you were just on from titles only” task. Compare site-wide identical, brand-first, and object-first.

• Dependent variables: rate of retrieving the right page, whether a screen-reader window list can name the current page, recognizability after a narrow-tab crop.
• Independent variables: title template (brand only / brand+object / object+brand), tab width.
• Methodological note: participants who just saw the in-page H1 will pad a poor title from short-term memory. Measure after leaving the page, with only a title list. Do not use home as a stimulus; home may legally be the site name. Heading-contract studies in the writing domain ask whether the in-page heading previews content; this leaf asks whether the document name itself varies by page.

Where it stops holding

Login, error, and an empty dashboard can use a stable class name (“Sign in,” “Dashboard”) without forging an object name. A single-page branded tool whose brand is the product has site name = page name. A brief loading state may keep the previous route’s title, but on landing it must become this page’s. SERP titles shown by a search engine may be rewritten and need not match document.title word for word, but the object identity should still line up.

Applying it

• Write a title template per route: specific object or task first, brand as an optional suffix. Do not hard-code one string for the whole site.
• An SPA updates document.title when the route completes and data arrives, not only once in index.html.
• Verify: open three different products and two different articles. Tab names and OS window names should split them without looking at the page body. All brand is a failure. Move the brand first and narrow the tab; if only the brand remains, the template order is wrong.

Related

• Within the group: G4.09.2 The title is how tabs, history, and bookmarks recognize a page · G4.09.3 Duplicate titles make same-site tabs impossible to tell apart · G4.09.4 The document title should match the in-page heading, or people suspect the wrong page · G4.09.5 Dynamic titles must not jitter so hard they break tab scanning
• Adjacent: T2.02 Predictability of headings and labels · G2.05 Location indication · G4.02 Deep linking
• Search terms: document.title · page title · unique title