Labels must match the target page's heading

What it is

Entry-to-destination concept alignment means that expectations created by navigation, search results, notifications, email, or deep links are confirmed by the landing heading and current state. The stable concept, object, and promised state align; the strings need not be verbatim. “Manage notifications” may open “Notification settings,” and a personalized entry may include an object name, as long as people can immediately verify the correct object, task, and state.

Why it happens

The source label predicts; the destination heading verifies. Unrelated names, changed scope, or conflicting state tense make people suspect a wrong turn, backtrack, or continue on the wrong object. Sources extend beyond in-product menus: search snippets, pushes, shared links, and bookmarks may enter a deep object with a stale name or state from generation time. A stable page concept ID and declared state qualifier let each channel use appropriate wording while the landing verifies the same semantics without sharing one literal string.

Studying it

Build a source × destination × object/state matrix across main navigation, search, push, email, breadcrumbs, sharing, and direct URLs. Include personalization, permission change, rename, deletion, and expiry. After landing, ask participants where they came from, where they are, what object and state they see, and what comes next; record misidentification, backtracking, repeated search, and wrong action. Rapid-back telemetry is only a clue—it also reflects slow loading, irrelevant content, or accidental taps—so join it with path replay, page state, and qualitative evidence.

Where it stops holding

Alignment does not require identical grammar. Entries face space and action context, while headings must orient independently; a parent entry may also lead to a specific child. Counts, names, and timestamps need not repeat, but core object and state cannot conflict. Privacy or permission may prevent the landing from repeating a sensitive source name; show a safe, clear state such as “Content unavailable” without revealing existence. External deep-link wording is not controlled, so the landing heading, breadcrumb, and recovery path must be self-sufficient.

Applying it

• Maintain a stable concept ID, allowed states, and heading template per route or content object. For every controlled source, record destination, promised object or state, and generation version instead of comparing first words.
• Synchronize navigation, search indexes, push/email templates, breadcrumbs, and headings on rename, personalization, or state change. Map old deep links to the current concept by version; otherwise use a safe recovery page.
• Permit channel-specific wording while validating a shared concept and state contract. Object, scope, and completed/pending state promised at entry must be confirmed at landing, with dynamic values from the same authoritative state.
• Regress deep links, shares, old notifications, revoked access, and deleted objects end to end. Acceptance requires orientation and a valid next step; trace failures to stale source, routing, title template, or state data.

Related

• Same group: T2.02.1 Headings must accurately preview page content · T2.02.2 Creative headings undermine predictability
• Adjacent: G4.02.1 Deep links may skip intermediate levels · T1.04.3 Term changes require global replacement and migration notes
• Search terms: label-heading alignment · destination confirmation · deep-link landing