Duplicate titles make same-site tabs impossible to tell apart

What it is

The same site is often opened side by side: two tickets, two products, an article and its editor. If the tab strip shows two identical strings, recognition loses the object. Duplicate titles cannot be told apart in multi-tab: the failure is not that the title is insufficiently “on brand,” but that several documents share one name. People fall back on position memory (“second from the right”), which breaks as soon as the browser reorders the strip.

Why it happens

Parallel tabs change recognition from “is this the right page” to “which one in this set.” When titles collide, within-set discriminability drops to zero; only order and favicon remain. Same-site favicons are also identical, and order is rewritten by pinning, closing, and dragging. Dubroy and colleagues observed people parking unfinished tasks in tabs; collision makes parked tasks overlay each other visually, and retrieval becomes serial clicking. Collision also pollutes history: two rows with the same title, ten minutes later, cannot tell which was the edited one.

Three common sources: a site-wide brand string; list and detail both called “Orders”; blank editor pages sharing “New message” until data arrives. An SPA that clones a route and forgets to write the object id into the title gives two details the same name. People do not read the full title tooltip; they read the dozen characters on the tab—collision is likelier after crop, because the distinguishing segment was placed in the second half.

Studying it

Have people open three objects of the same template (three tickets) in parallel, then after an interrupting task retrieve a named one. Compare titles that each contain the object name, titles that are all the template name, and titles that differ only in the second half.

• Dependent variables: first-click hits on the target tab, corrections after a miss, switches to in-site search.
• Independent variables: whether the title contains an object identifier, identifier first or last, tab width.
• Methodological note: two tabs still hurt little; three or more is when guessing by position stabilizes. The interrupting task must last long enough for position memory to decay. Do not tell them “the titles are the same,” or they will switch strategy from the start.

Where it stops holding

If the side-by-side tabs are different sites that happen to share a name (“Sign in”), this site changing its title cannot help the neighbour. A single-tab workflow never hits this leaf. Preview and body designed to be understood as a pair may be named “Preview · Article” and “Article”; that is distinction, not collision.

Applying it

• Different objects of the same template must put that object’s own name or number in the title, in the front segment that survives cropping.
• Placeholder titles before data arrives should also carry an object id or “which one is loading,” not several “New order.”
• Verify: open three different tickets side by side, narrow the tab strip, ask someone to point at a named one. Three identical looks fail. Move the object name behind the brand and narrow again; if the object name is cropped away, the order is still wrong.

Related

• Within the group: G4.09.1 The document title should name this page, not repeat the site name · G4.09.2 The title is how tabs, history, and bookmarks recognize a page · 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: G2.07 Navigation consistency · G4.04 New window versus in-place navigation · T2.02 Predictability of headings and labels
• Search terms: duplicate title · tab collision · document.title