All insightsWeb Design

Should Website Links Open in a New Tab?

External links do not all need a new tab. Decide around unfinished work, useful warnings and the customer’s return path, then test the actual behaviour.

Hinged ivory and lavender-glass page sculptures with a chrome return arrow, beside Keep the return path. and Choose where links open. ZXP is embedded in the base.
Original conceptual illustration of choosing where website links open and how visitors return.

A customer is halfway through an enquiry form when they follow a link to check a measurement. Should that link replace the form or open somewhere else? The answer depends on the work they need to keep, not simply on whether the destination belongs to another company.

For a business website in Canada or the United States, start with ordinary browsing in the current tab. Make exceptions around a specific customer task. The useful question is: after following this link, can the person understand where they are and continue what they were doing?

Start with the current tab

A link does not need to open a new tab just because it leads to another website. An external reference may be the next thing someone wants to read, with no unfinished work on the original page. Keeping that journey in the current tab gives them a familiar route through their browsing history.

W3C's G200 technique recommends limiting new windows and tabs because unexpected changes can be disorienting. It also recognises exceptions, such as consulting help while completing a form. This is advisory guidance, not a rule that every new-tab link fails WCAG.

Avoid treating “keep visitors on our website” as the whole reason for forcing new tabs. Leaving your page open does not show that someone will return or send an enquiry. Describe the customer benefit you expect, then check whether the actual behaviour supports it.

Ask what the visitor needs to preserve

Use three questions before approving an exception. Is there unfinished work on the current page? Is the destination needed alongside that work, rather than as its replacement? How will the visitor find their way back?

The first question separates browsing from an interrupted task. Reading a supplier's product explanation from a general service page is different from checking a specification after entering several details into a form. In the second case, losing those entries would matter. Identify that risk before deciding how the link should behave.

The second question can also reveal a simpler solution. If the visitor needs one short instruction, could it appear beside the relevant field? If they need a substantial reference owned by another organisation, linking to that source may be more appropriate. Do not copy a whole document into your form merely to avoid a tab decision.

The third question keeps the return journey in view. A new tab leaves the original page elsewhere in the browser; it does not give the new page a Back-button route to it. A visitor may need to switch tabs or windows instead. W3C's G201 guidance explains why warning people about that change helps them orient themselves.

Imagine a fictional window-screen repair business. The examples below are proposed design decisions, not a client project or observed test results.

Its service page links to a manufacturer's explanation of mesh materials. The customer is browsing options and has not entered anything. The proposed choice is an ordinary same-tab link labelled with the manufacturer and subject. Being an external website is not, on its own, a reason to override that behaviour.

Later, the business's enquiry form asks for a frame measurement. A separate illustrated guide explains where to measure. If the explanation cannot fit usefully beside the field, a clearly announced new-tab link may let the customer consult it while keeping the form available. That is a reason to evaluate an exception, not proof that it works.

A new tab is not an autosave feature. It does not guarantee that entered information survives a reload, a closed tab or an expired session. Ask the developer how the form actually retains work, then test the relevant journey with invented data. If entries disappear on return, revise the implementation rather than claiming the opening setting solved the problem.

Record the choice for each exception

Keep a short link-decision record with six fields: the source page and task, the destination and its owner, any unfinished work, the chosen opening behaviour, the warning shown before activation, and the way back. Add an owner for checking the decision after the destination or form changes.

For the fictional measurement guide, the source task is “finish the repair enquiry”. The destination task is “find the correct measurement points”. The work to preserve is the information already entered. The proposed behaviour is a new tab, with a warning in the link text. The return instruction is to switch back to the enquiry tab. The observed outcome stays blank until someone tests it.

For the manufacturer's materials page, the record is simpler: browsing information, no entered work, same-tab navigation. The intended way back is browser history. This comparison stops a site-wide “all external links” setting from substituting for a decision about each important task.

Make a new context clear before the click

When the site deliberately opens another tab or window, give the visitor advance notice. GOV.UK's link guidance recommends including “opens in new tab” in the link text when that behaviour is necessary. For example: “Read the measurement guide (opens in new tab)”.

If the design uses an icon instead, ask how its meaning is communicated both visually and to someone using a screen reader. G201 describes those two checks. A small arrow that nobody has explained should not be the only information the customer receives.

Distinguish that site-imposed behaviour from the visitor's own choice. Someone may use their browser's menu to open an ordinary link in a new tab. G201 does not require the same warning for that user-initiated choice. W3C's H83 technique also notes that leaving out a forced target lets the visitor decide.

G200 and G201 are advisory techniques. Following these suggestions alone does not establish accessibility conformance or legal compliance. Ask for the actual implementation to be assessed within the website's agreed accessibility scope.

Give the developer a behaviour brief

Specify the intended behaviour in ordinary language rather than only asking for a checkbox in the editor. A setting may affect one link, a reusable component or every external link on the site. Confirm which scope is being changed before approving it.

MDN's anchor reference explains that a target value of _blank usually opens a new tab, but browser settings can make it a new window. Do not promise that the presentation will be identical everywhere.

Ask the developer to check appropriate protections for links that open a new context. MDN's noopener reference describes how it prevents the opened page from gaining access through window.opener. Modern _blank links already receive equivalent behaviour in supporting browsers. The practical request is to verify the implementation and supported browsers, not to assume every new-tab link is vulnerable.

Test the outward and return journeys together

In an authorised preview, follow the link with a normal click and with the keyboard. Check the announced behaviour, destination, and how someone returns. Repeat the important path on a supported narrow-screen browser, where switching tabs may look different from the desktop experience.

Where work is meant to stay available, enter fictional information before leaving and compare it after returning. Do not submit a real enquiry or place an order just to check a tab. Arrange any end-to-end submission test separately with the site's owner.

Record the environment, opening behaviour, return steps and what happened to the entered information. Keep expected and observed results separate. A successful check on one browser is useful evidence for that configuration, not a guarantee for every visitor.

Bring the link-decision record when you prepare a website project brief for ZXP. Include the page, the destination and the work a customer needs to preserve. Those details give the design discussion a clearer starting point than a blanket instruction to open every external link in a new tab.

THE READING LIST

Sources & references

  1. 01
  2. 02
  3. 04
  4. 05
  5. 06
ZXP

A perspective from the ZXP team.
Designed to help you ask better questions and take a clearer next step.

FROM IDEAS TO ACTION

Plan a clear outward and return journey

Bring the page, destination and work a customer needs to preserve to your website discussion.

Prepare your project brief