Skip to main content

BETANow in public beta.Public betaBeta

日本語Español

TAB-005 Published

Page-link tabs

A design that looks like tabs but where each tab is a link to a separate page.

Wireframe (desktop) | Page-link tabs

Page-link tabs UI design (desktop wireframe)

Wireframe (mobile) | Page-link tabs

Page-link tabs UI design (mobile wireframe)

What changes on mobile

  1. Links share the full width equally: Shows every page name on one line and makes them easy to press.
  2. Names shortened: Wrapping on mobile breaks the row and hurts readability.

Before you choose this pattern | Page-link tabs

Good fit

  • A few closely related pages that readers move between from the same row
  • About pages, service details: each page should have its own URL
  • Each page should open directly from search or a shared link

Poor fit

  • Switching content within the same page (the <a href="/patterns/en/tabs-top/">top tabs</a> work better)

Why this wireframe works | Page-link tabs

Related pages are easy to move between

Closely related pages are lined up as tabs, and the same row leads to the others from every page.

Each page has a URL and opens directly

Because each is a separate page, each has its own URL and can be opened directly from search or a shared link. With tabs that switch within one page, the second and later panels are hard to open directly.

The current page shown by underline and aria-current

The current page’s link has a thick underline and aria-current=”page”. Both visually and to screen readers, the current page is clear.

Built as links

Because they move between pages, they are built as links inside a nav with no role=”tab”. They look like tabs, but screen readers describe them correctly as links.

Common mistakes | Page-link tabs

The tab role on page navigation

With role=”tab” on a link, screen readers describe switching within the page, but the page actually changes. For moving between pages, keep them as links.

The current page shown visually only

A line or color alone does not tell screen readers which page is current. Add aria-current=”page”.

An order that changes from page to page

If the row changes order between pages, readers get lost. Use the same order and names on every page.

Too many pages for one row

At five or six pages, the row no longer fits on mobile. Keep to about four closely related pages and put the rest in a separate list.

FAQ | Page-link tabs

Page-link tabs or tabs within one page?

When content should open directly from search or a shared link, or there is a lot of it, separate pages suit better. For comparing short content, tabs within one page are enough.

After moving, the screen returns to the top rather than the tabs.

A new page is shown from its top. With the row of tabs near the top of the page, this is rarely a problem.

Is a breadcrumb needed too?

The row of tabs moves between pages at the same level; a breadcrumb goes back up the hierarchy. Because the roles differ, both are often used.

Related pages

Share this pattern

Send this page to your team or your design partner.

Was this pattern useful?

Written by

Yuta Okano

ENVY DESIGN Inc.

CEO / Director / Designer

14 years in the web industry. Has worked on more than 500 web projects, from corporate and recruiting sites to e-commerce. Focuses on information architecture, direction and design, from planning websites to improving them. In recent years he has focused on AIO (AI optimization) and GEO, helping sites get cited by generative AI search such as ChatGPT, Perplexity and Google AI Overviews.

Review and revision history

  1. Published AvatarYuta Okano Pattern published