Skill LibraryPrompt Skill1 DesignsTop Views

Information Scent Link Labels

Create predictable, accessible, searchable link-label and destination contracts for navigation, cards, resource lists, search results, and inline links.

Skill Uses0

Recorded selections across prompt workflows.

Public Designs1

Ranked by views, then community favorites.

Prompt Lines10

Reusable instruction lines for generation.

Author@Interface Lab

Information Architecture

Skill Directive

Description

Create predictable, accessible, searchable link-label and destination contracts for navigation, cards, resource lists, search results, and inline links.

TagsInformation Architecture

Skill Prompt

- Use for navigation, knowledge bases, resource libraries, card lists, search results, documentation links, external links, and permission gates; inputs must include target URL/object, user task, link context, and whether the target is external, download, login-gated, or new-window.
- Inventory every clickable entry and classify destinations: internal navigation, object detail, filtered query, external resource, download, permission request, or dangerous action; different destinations cannot share one vague label.
- Primary links should use the object or page name, such as resource title, knowledge item title, or product name; button labels use verb plus object, such as Open resource map or View table disclosure rules.
- Before click, each link answers destination, value, and cost: where it goes, what users get, whether it leaves the site, requires login, downloads, or opens a new tab.
- Avoid labels like Learn more, View, Open, Details, Here, and Read more; keep them only when the destination is fully stated in the same sentence and the label is unique.
- When cards are clickable, the title is the primary link; whole-card click and inner buttons must not conflict, and secondary actions stay visually and semantically separate.
- Accessible implementation: link text should be meaningful on its own; repeated labels on one page must lead to the same kind of target; external/download/new-window/login-required cues need visible text or aria support, not only icon or color.
- Frontend implementation should define a LinkLabelContract: visibleLabel, objectName, destinationType, external, requiresAuth, download, opensNewTab, ariaLabel, and contextSummary.
- Output: link inventory, label rewrite table, destination cost flags, card click contract, ARIA notes, removed bad labels, and QA checklist.
- Common mistakes: cards with only Read more, many different URLs named View details, external links without warning, access blocked only after click, and title/destination mismatch. Sources: NN/g Information Scent, USWDS Link, WCAG Link Purpose.

Public directive summary shown; Pro unlocks the full prompt.

Layout Info

Designs below are ordered by views. Top items use live previews; the rest stay fast thumbnail cards.

Unlock Pro All Skills

Information Scent Link Labels

More pages using Information Scent Link Labels