Jakob's Law for article discovery: familiar paths, clearer choices
Use familiar navigation and search patterns to help readers find articles, then test whether your distinctive design still makes the next step obvious.
People bring expectations from other websites to yours. Put search, topic navigation, article titles and reading controls where readers can recognise them, then use visual character around those predictable routes rather than making discovery itself a puzzle.
A new library may have its own beautiful architecture, but visitors still look for a catalogue, signs and clearly labelled shelves. Familiar signs let them enjoy the building and find the book they came for.
An article library asks a visitor to make a small series of decisions before they ever begin reading: Where are the topics? Is this a search box? Does this card lead to an article? Can I get back? A page can be visually remarkable and still make each answer harder than it needs to be. Jakob’s Law is a useful check on that tension: readers arrive with expectations formed elsewhere, and those expectations shape where they look first.
The expectation readers bring#
People learn a rough model of a website by using many sites, not by reading a new site’s instructions. On an editorial site, they expect a visible way to search, names for subjects, article titles that describe the subject, and links that behave like links. A familiar pattern lets them spend attention on choosing a subject. An unfamiliar pattern asks them to learn the interface first.
This is about the behavior of the route, not one approved visual style. A search control can fit an unusual layout; it still needs to look and act like search. A subject index can be presented beautifully; a reader should still be able to tell what each subject contains. If the page labels a collection “Atlas” or hides search behind an unexplained symbol, a visitor may not know which familiar action that invention represents.
The book’s account of Jakob’s Law also has a useful limit: conventions are a starting point, not an order to make every product identical. A new pattern can be better for a specific audience or task. The burden is to show that readers understand it in use.
A discovery route in practice#
Imagine a reader who remembers that an article explained database indexes but not its title. They start at the home page. A clear “Search articles” entry gives them one route. A visible “Data” subject gives them another. On the results page, each item names the specific question it answers, includes a short description, and looks clickable. After opening one article, a topic breadcrumb and related links provide a way to continue browsing without starting over.
Every step has a recognizable counterpart on other reading sites: search, subject navigation, result, article, related reading. That familiarity does not decide the site’s colors, typefaces or voice. It simply keeps the route legible. If “Data” contains only broad slogans while the precise index article is buried in an unrelated section, the visual treatment cannot repair the reader’s mental model of the library.
A useful audit is to draw the route as five boxes and label each link with the words a reader actually sees. If the link words do not let someone predict the next box, rename or reposition them before adding more decoration. This is especially useful for article cards: a clever title may be memorable after reading, but the card must first tell an unfamiliar visitor why to open it.
Where to be distinctive#
Distinctive design earns its place when it makes the material easier to recognise or understand. A strong illustration can distinguish a subject. A generous type scale can show which sentence is the article title and which is supporting context. A recurring visual motif can make a series feel connected. None of those requires turning the search button into a riddle or making the article title compete with decorative labels.
This also applies when redesigning a familiar site. A reader who used to find subjects in the main navigation may lose that route if subjects move into a new, opaque menu. If a large structural change is necessary, test the old and new routes with representative readers and preserve clear signposts during the transition. The aim is to let existing knowledge carry over.
Test the route#
Give someone a realistic task: “Find a practical explanation of clustered indexes, then find another article about databases you would read next.” Start them at the home page and avoid pointing at the intended controls. Note their first click, whether they use search or topics, where they pause, and whether the destination matches what the link promised. Ask what they expected to find before revealing the answer.
This small observation is more useful than asking whether the navigation looks modern. It reveals whether the site’s labels and structure match readers’ expectations. If several readers take a wrong turn at the same label, change that label or the structure behind it. If they reach the article quickly and then explore further, the familiar route is doing its job and the visual design has room to be adventurous.
Try the route in the article library, then consider how visual appeal changes a reader’s first impression. Both checks matter when a redesign feels polished but is difficult to browse.
Next, use a consistent spacing system to make the groups within that familiar route easier to see.
Questions people also ask
2 QUESTIONSDoes Jakob's Law mean every website should look the same?
No. It is a prompt to preserve recognisable interactions where readers rely on prior experience. Editorial voice, typography, illustration and composition can be distinctive while search and navigation remain easy to recognise.
What should an editorial site check first?
Ask a new reader to find an article on a named topic, switch to a related topic, and return to where they started. Watch the route they take and where they hesitate; do not infer success from a polished appearance alone.