Quick Links: Designing Shortcut Navigation

The phrase means at least four things. On a company intranet, quick links are the tiled panel near the top of the homepage with Payroll, Holiday Request and IT Support in it. In a browser, they are the shortcut grid on a new tab. In an app, they are the long-press menu on the icon. On a marketing site, "Quick Links" is usually the heading someone put above a column in the footer.

The design question is the same in all four: out of everything a person could go to from here, which few destinations get promoted, and what does promoting them cost? The answer is where most implementations fall apart, because a quick links module is one of the easiest things in an interface to add and one of the hardest to keep short.

A quick links module is a claim about frequency

Regular navigation makes a claim about structure: these are the areas of this product, arranged how we think about them. A quick links module makes a different and much riskier claim: these specific destinations are where most of you are going right now.

That claim is testable, and it is usually wrong at launch. It gets made by a team looking at an org chart, not at traffic. The intranet panel ends up holding one tile per department that asked for one. The footer column ends up holding whatever didn't fit in the header.

The useful test before you build one: can you name the top five destinations from this page with numbers to back it, and does the fifth get meaningfully less traffic than the first? If the top twenty are all within a few percent of each other, you don't have a frequency problem to solve with shortcuts. You have a structure problem, and it belongs in the information architecture work instead.

What earns a slot

Importance to the business is not what earns a slot. What does:

It is visited often. Analytics, not intuition. Search logs beat page views here: a query typed into an internal search box is somebody telling you the navigation failed them.

It is hard to reach otherwise. A page that sits four levels deep but gets used weekly is the ideal candidate. A page already linked from the main nav gains almost nothing from a second link and costs a slot.

It is used under time pressure. "Report an outage". Urgency is its own argument for promotion even when the raw numbers are modest, because the cost of a slow path is highest exactly then.

The new product launch, the CEO's memo: the organisation wants people to visit these. That is a different job, and it belongs in a promotional slot that looks like one. Mix announcements into quick links and people stop scanning the module altogether.

How many, and what happens past that number

A scannable set is roughly four to eight. Past that, the module reads as a list and people work through it top to bottom. That is the behaviour the shortcut was supposed to kill.

The failure mode is predictable: the panel launches with six entries, each request for a seventh is reasonable in isolation, and a year later it runs to twenty, sorted alphabetically. Alphabetical ordering in a quick links panel is the tell. It means the team stopped being able to say which entries matter most, and the two or three carrying the traffic are now somewhere in the middle of the list.

If you cannot get under eight, the honest options are to split the module by audience (what a new starter needs is not what a manager needs), or to admit this is a directory page and link to it with one entry.

Whatever the count, give the module a hard cap in the CMS. When something new goes in, somebody then has to say what comes out.

Where the module sits

On an intranet or dashboard homepage, above the fold and left-aligned with the main content column. These are pages people open dozens of times a week, and the module is the reason many of them opened it.

On a content page, quick links belong near the top if they are navigational, and in the footer if they are reference. A footer column labelled "Quick Links" is fine as a courtesy — nobody arrives at a page planning to scroll to the bottom for it, so it isn't really a shortcut, and it shouldn't be counted as one in your navigation model.

In the header is usually the wrong answer. Header space is expensive and already carries the primary navigation; a second row of shortcuts there competes with the thing it is meant to support. The exception is a single high-frequency action, like Search or Report an issue, promoted to a button rather than a link.

Keep the module in the same position across pages. A panel that drifts down the page as the layout changes is a panel people have to look for.

Labels people can scan

Quick links get scanned, not read. The first word or two of each label carries the load.

Lead with the noun or the verb that identifies the destination: "Expenses", "Reset password". Avoid a shared prefix across entries. "HR: Expenses", "HR: Holiday", "HR: Payroll", "HR: Benefits", "HR: Performance Review" spends the scannable position on a word that distinguishes nothing, and groups the set by who owns it instead of by the task.

Use the words people use. If everyone in the company says "annual leave", the tile says Annual Leave, even if the policy document calls it Paid Time Off. Internal search queries will tell you which is which. The same discipline that governs a taxonomy in information architecture applies here, on a smaller and more visible surface.

Keep the capitalisation consistent with the rest of the product — our take on sentence case versus title case covers the trade-off.

Icons are optional and frequently harmful. A distinct, conventional icon (an envelope, a calendar) speeds recognition on a repeat visit. A generic one — the same document glyph on six tiles — adds visual noise and pushes the labels apart, making the set harder to scan. If you can't find a distinct icon for every entry, use none. More on that in iconography in UI design.

Static, personalised, or recent

There are a few ways to fill the slots, and they fail differently.

Static is a fixed list, the same for everyone. It is predictable, memorable and easy to govern. Its weakness is averaging: a list tuned for everyone fits nobody especially well.

Personalised varies by role, team or location — a warehouse worker and a finance manager get different tiles. It fits better and costs more: you need reliable role data, a rule for people who fall into two roles, and a sensible default for people who match nothing. Get any of those wrong and someone's homepage is missing the one link they need.

Recent or frequent is generated from the person's own behaviour, like the shortcut grid on a browser's new tab page. It needs no configuration and adapts on its own. The trade-off is instability: entries move, so the position you learned last week is wrong this week, and a single unusual visit can displace something you use every day. It also fails on the first visit, when there is no history. That is a new starter's first morning.

Most workplace homepages do best with a static core plus a small recent section underneath, clearly separated. Mixing the two in one grid produces a panel where some tiles are stable and some aren't, and people can't tell which is which.

If you change the set, change it visibly and rarely. People who have learned a position will keep clicking it for weeks.

The neighbours it gets confused with

Quick links are one of several shortcut mechanisms, and the overlap causes a lot of duplicated work.

A table of contents shortcuts within a single page. It is generated from the content's own headings, so it stays accurate with nobody maintaining it.

Breadcrumbs shortcut upward — they show where you are and let you jump to an ancestor. They answer a different question from quick links and they don't compete; see breadcrumb navigation patterns.

A mega menu is the main navigation opened up, showing many destinations at once. If your mega menu already surfaces the popular entries, a quick links panel on the same page is duplication. We cover the choice in when and how to use mega menus.

A hamburger menu hides navigation behind a control. On a page that uses one, a visible quick links module is a partial fix for what the hamburger hid. If those shortcuts are essential enough to show, the navigation behind the icon may be in the wrong place.

Skip links are a shortcut for keyboard and screen reader users. They are a requirement, and skip navigation links for accessibility covers what conformance takes.

Pick one mechanism per job. Two modules pointing at the same destinations from one page split the traffic between them, and then neither number can tell you what to keep.

Quicklinks on workplace homepages

The intranet version — often written as one word, quicklinks, in SharePoint and similar platforms — has its own failure pattern. Because the panel is easy to edit and everyone can request an entry, it becomes the political surface of the homepage. Departments lobby for tiles. Nothing is ever removed, because a removal has a named victim and an addition doesn't.

Two things keep it usable. First, an owner: one person or team who decides what is in the panel and can say no. Second, a review on a schedule, where every entry has to justify its slot against last quarter's click data. Without both, the cap you set in the CMS gets raised instead of enforced.

Structure the underlying site so the panel isn't load-bearing. If the only way to find the expenses form is the quick links tile, the tile is compensating for navigation that doesn't work — a problem covered properly in designing intranet information architecture.

Knowing whether they work

Instrument each entry separately. Aggregate module clicks tell you the panel gets used; per-entry clicks tell you which two entries are doing all the work.

Click share per entry is the one that decides things. A couple of others are worth watching alongside it:

• Click share per entry. Under 2% of module clicks over a full quarter, the entry comes out. Moving it up the list is the reflex, and it rarely works.
• Internal search for things already in the panel. People searching for "expenses" on a page that has an Expenses tile means the tile is there and nobody sees it. Check where it sits and what it is called before you touch the content.
• Time to first click on the page. If the module is working, it should shorten it.

Treat changes as experiments where the traffic supports it. The mechanics are in our guide to A/B testing.

Then act on the numbers. That means removing entries, and the quarterly review is the only place anyone looks at the panel as a whole.

Frequently asked questions

What are quick links?

Quick links are a small set of promoted shortcuts to frequently used destinations, shown as a list or tile grid separate from the main navigation. They exist to cut the path to the handful of pages most people on that screen are heading for.

Is it "quick links" or "quicklinks"?

Both are in common use. "Quicklinks" as one word shows up most in intranet platforms, where it is often the name of the component itself. In prose, two words is the safer default. Pick one spelling and use it consistently in your own interface.

How many quick links should a page have?

Four to eight is the range that stays scannable. Beyond that people read the module as a list rather than a set of shortcuts, which removes most of its speed advantage. If you need more, split by audience or link to a directory page.

Where should a quick links section go?

Near the top of the page for anything navigational, and in the same position on every page so it can be learned. The footer is acceptable for reference links. A footer module isn't really functioning as a shortcut, though: nobody scrolls to the bottom to go somewhere faster.

How are quick links different from bookmarks?

Bookmarks are chosen by the individual and live in their browser. Quick links are chosen by whoever designs the page and are the same for everyone who sees them, or for everyone in a role. A recent-items module sits between the two: personal, but the system saves it for you.

Do quick links help SEO?

On a public site, a small set of internal links from a high-traffic page passes authority to the destinations and helps them get crawled. The effect is modest and it is not a reason to expand the module. A footer column stuffed with two dozen links to dilute nothing in particular is a long-solved pattern that no longer earns its space.

Should quick links use icons?

Only where every entry can have a distinct, conventional icon. Repeating a generic glyph across several tiles adds noise and spreads the labels out, which makes the set slower to scan than plain text would be.

Where to go next

Menus, wayfinding and the rest of the shortcut family are collected under navigation design. If you are deciding between a shortcut module and fixing the structure underneath it, the structural side lives in information architecture.

If your homepage has a quick links panel that has been growing for two years and nobody can say which entries still earn their slot, that audit is what a Full UX Audit → starts with.