: Is a "back" link on each page really needed? I saw some sites having a <<back link on each page below the site top level that basically just invokes a JScript function that gets the

@Frith620

When I see a "Back" link on a page, it usually has nothing to do with design or appearance. It is simply because the web site has broken the browser's back button. Typically, the site makes use of JavaScript or submission forms or some other complex behavior that adds state to the stateless HTTP protocol. Popping back to a previous page corrupts this state and leads to problems such as duplicate form submits. Rather than fixing the back button, web developers find it easier to add a "Back" link that gives them control over the transition and prevents the server from getting confused. Some evil developers go as far as trying to disable the browser's back button altogether! In short, there is no reason for a back button... unless you are a lazy web developer.

Vote Up Vote Down

@Si4351233

Such 'back' links are not useful.

As stated in the question, they merely repeat a function already available in the browser. More importantly, however, unlike the browser back button, users may be surprised by its behavior. For example, they might not expect to be sent back to Google when clicking a link on your site if they arrived there via a search. Such links do not add anything useful and can be confusing,

There is also considerable amount of UX research that indicates that most users are comfortable with the browser back button. So it is also redundant. But that is a lesser sin than being potentially confusing.

However, if the concept of going back is important to your navigation, there are numerous other approaches available that will not risk confusion, and do not depend on your user entering via the "front door" (so to speak). 'Breadcrumbs' being the most commonly used tool.

Breadcrumbs enable users to go "back" in terms of the sites hierarchy even if they enter via a deep link. They also provide immediate access to different levels of the site hierarchy without having to step through each layer. Finally, they also inform users of the site structure and thus facilitate discovery.

Vote Up Vote Down

@Pope3001725

An alternative method of doing this is to use breadcrumbs. Not only do they give your users an easy way to go back, but they show the hierarchy of the content which makes it easier for the user to find what they're looking for. Plus they're good for SEO as they:


create a natural hierarchy of pages
interlink your pages with good anchor text
when used with microdata can even make your listing in the search results more useful. (See image below)

Vote Up Vote Down

@Cody1181609

Is such link really helpful?


As ChrisF noted, this is entirely dependent upon whether or not your site's audience benefits from the feature.


How is it better than just a browser "Back" button?


Most implementations look like this:

<a href="#" onClick="javascript:history.go(-1);">back</a>


The practice of hard-coding a Javascript "back" link into an HTML document is counterproductive in at least two cases:


A user has Javascript disabled
A user who just arrived at your site clicks the link and is taken off-site (which may result in the user leaving for good)


For these reasons, it is not a good practice to hard-code links which depend upon Javascript functions - instead, (if you decide to implement) you might check with Javascript to ensure that document.referrer is either null or contains your domain name before drawing the link with Javascript so users with Javascript disabled and users who just arrived are not presented with the link.

Vote Up Vote Down

@Kimberly868

The question is really "are your users comfortable using the browser's back button?".

If they are then leave the link off your pages.

If not then you need to keep it there.

The only way you are going to find this out is by testing the different pages and see which ones your users prefer.

Vote Up Vote Down