When 'Please Click Here' Isn't Enough: The Hidden Cost of Poor Redirects

You've seen it a hundred times. A page loads, and there it is: 'Please click here if you are not redirected within a few seconds.' It's a tiny piece of web real estate, often overlooked. But here's the thing – that little message, and the redirect behind it, can make or break your user experience and search engine performance. And trust me, it's a bigger deal than most people realise.

I'm talking about redirect pages. The humble, invisible workhorses of the web. They move users from one URL to another. They tell search engines where content went. And when done poorly, they frustrate visitors and tank your SEO. Let's dig into why that simple Google Search redirect page is actually a masterclass in what to avoid – and what to aspire to.

The Anatomy of a Redirect: More Than Just a Forwarding Address

A redirect is a server response that sends a browser (or a search engine crawler) from one URL to another. There are several types: 301 (permanent), 302 (temporary), meta refresh (the kind that shows that 'click here' message), and JavaScript redirects. Each has its place, but the meta refresh is the one most likely to cause headaches. It's a client-side redirect, meaning the browser waits a few seconds (or relies on user action) before moving on. Sounds harmless, right? Not exactly.

Imagine you're a user searching for a specific product page. You click a search result, and instead of the product, you see a blank page with a link that says 'click here'. You might wait. You might click. Or you might hit the back button and try a competitor. That's a lost conversion. Fair enough, you might say – it's just a few seconds. But in the fast-paced world of e-commerce, every second counts. Research from Amazon found that every 100ms of delay costs them 1% in sales. So that 'few seconds' wait? It's not a few seconds. It's a revenue leak.

User Experience: The Silent Killer

Let's talk about the user experience (UX) of a redirect page. The Google Search redirect page is a good example. It's minimal, yes, but it's also inefficient. Why? Because it forces the user to make a decision. Do I click? Do I wait? The best UX is invisible. A proper server-side 301 redirect should happen instantly, with no visible intermediate page. The user shouldn't even know a redirect happened. That's the gold standard.

But sometimes, organisations use these intermediary pages for tracking, security (like Outbrain or Taboola), or to comply with certain regulations. Google itself uses a redirect page for external links in search results? Actually, no – Google now uses direct links in most cases, but historically they did. The point is, if you must have an intermediate page, make it fast, simple, and accessible. Don't rely on the user to click. Use a meta refresh with a short delay (like 1 second) and ensure it works with screen readers and keyboard navigation.

Accessibility is another big one. A message that says 'click here' assumes the user can see and use a mouse. What about someone using a keyboard? Or a screen reader? The link text should be descriptive, not just 'here'. And the automatic redirect should be the primary mechanism, not a fallback. The WCAG guidelines emphasise that users should have enough time to interact with content. A redirect that happens too fast can disorient people with cognitive disabilities. Too slow, and it annoys everyone.

SEO Implications: When Redirects Derail Your Rankings

Now, the SEO side. Search engines like Google treat redirects differently depending on the type. A 301 redirect passes most of the link equity (ranking power) from the old URL to the new one. A 302 does not – it's considered temporary, so the original URL stays in the index. A meta refresh? It's often treated like a 301 by Google (they've said so in the past), but it can be slower and less reliable. JavaScript redirects are even trickier. They may be executed or ignored depending on how the crawler renders the page.

If you're using a 'click here' page, you're essentially asking Googlebot to wait, parse the HTML, find the link, and then follow it. That's an extra step. And if your page has other content (like ads or tracking scripts), the crawler might get distracted. The result? Important pages might not get indexed promptly, or their link equity might be diluted. I've seen sites that lost rankings simply because they used poorly implemented redirects. It's not exactly groundbreaking, but it's a common mistake.

Another concern: redirect chains. If URL A redirects to B, which redirects to C, search engines will follow the chain but may stop after a few hops. Google's guidelines recommend avoiding chains longer than three. Each redirect adds latency. And a 'click here' page essentially creates an extra hop in the user's journey, even if it's just one. Prefer direct redirects. Use server-side 301s for permanent moves, like when you change your domain or restructure your site. You can check your redirects using tools like Google Search Console or Screaming Frog to ensure they're working correctly.

When a 'Click Here' Page Makes Sense: The Exceptions

I'm not saying every redirect page is evil. There are legit use cases. For example, some ad networks (like Outbrain, Taboola, or affiliate platforms) require an intermediate page to track clicks, enforce privacy policies, or apply referral parameters. Fair enough – they need to attribute the click. But even then, they could use a server-side redirect with a tracking parameter, rather than a full client-side page. The difference is often just a design choice.

Another scenario: security. If you're redirecting users from HTTP to HTTPS, you should always use a 301 or 302, not a meta refresh. Similarly, for country-specific redirects (like from example.com to example.co.uk), use server-side geolocation redirects that happen before the page loads. The goal is to make the redirect invisible. Users shouldn't see a 'please wait' message, because that raises suspicion and erodes trust. And trust is everything online.

What about the Google Search redirect page itself? Well, Google actually uses a sophisticated system for outbound links from search results. They used to show an intermediate page for tracking clicks, but now they use an interstitial with a URL parameter and a small delay? Actually, current Google search results link directly to the destination URL with a click-tracking URL that redirects server-side. So no click-here page. That's how it should be. The example we started with – 'Please click here if you are not redirected within a few seconds' – is more typical of older marketing platforms or poorly configured websites. It's an anti-pattern.

Best Practices: How to Implement Redirects Correctly

So, what should you do? Here's a checklist:

• Use 301 redirects for permanent moves. If you've changed your URL structure, moved a page, or merged sites, use server-side 301 redirects. They're fast, they preserve SEO value, and they're supported by all browsers and search engines. Configure them in your .htaccess file (Apache), IIS, or your web server's configuration.
• Use 302 redirects for temporary changes. For A/B testing, seasonal promotions, or scheduled maintenance, a 302 tells search engines to keep the original URL in the index. Don't use 302 for permanent changes or you'll lose ranking power.
• Avoid meta refresh redirects when possible. They're slower, less accessible, and can confuse users. If you must use one, set a very short delay (0 or 1 second) and provide a clear, actionable link. Ensure the link text is descriptive, like 'Go to the new page' rather than 'Click here'.
• Don't rely on JavaScript redirects. They depend on the browser executing JavaScript. Search engines may or may not render the JS. Some users disable JS for performance or security. Use server-side redirects as the primary method, and keep JS as a fallback if needed.
• Test your redirects. Use web-based tools like HTTP Status Checker or browser developer tools to verify that your redirects return the correct status code and final destination. Check for chains and loops.
• Monitor performance. A redirect adds an extra round trip. If you have many redirects on critical pages (like your homepage or checkout), users will experience lag. Audit your redirects regularly using PageSpeed Insights or similar tools.
• Communicate clearly. If your redirect takes more than a couple of seconds (e.g., due to complex server logic), show a loading indicator or a progress bar. But never force the user to click a link. That's the lazy way out.

Real World Examples: The Good, The Bad, and The Ugly

Let's look at some real-world cases. I recently visited a major retailer's site. I clicked a banner ad, and instead of going directly to the sale page, I landed on a 'please wait' page for 5 seconds. Then nothing happened. I had to click a small link. Why? Because their ad platform used a meta refresh with a long delay. It was a terrible experience. I left the site. Contrast that with how Amazon handles affiliate links. They use a server-side redirect that happens almost instantly. No intermediate page. No clicking required. The difference is night and day.

Another example: news websites that use 'click here' pages for external links. They often do this to track outbound clicks for analytics. But they could achieve the same with a simple server-side redirect that appends a tracking parameter. The intermediate page annoys users and adds latency. It's a trade-off between data and UX. And most of the time, data wins – but it shouldn't have to be that way. With modern analytics tools like Google Analytics, you can track outbound clicks via event tracking without a redirect page. So there's really no excuse.

The Psychology of Waiting: Why Milliseconds Matter

Human psychology plays a role here. We're impatient. Studies show that a delay of just 1 second can reduce customer satisfaction dramatically. And when a user sees a 'Click here' message, they often feel like the site is broken or untrustworthy. They wonder: 'Is this a phishing page? Why can't it just take me there?' Especially on mobile, where connectivity is variable, that extra waiting time feels like an eternity. The best redirect is the one the user never notices.

There's also the issue of perceived control. When you force a user to click, you're giving them a task. That's extra cognitive load. In an age of frictionless design, every micro-interaction should be streamlined. Remove unnecessary steps. Automate what you can. Your users will thank you with higher engagement and loyalty.

Conclusion: Redirect with Purpose, Not Lazy Design

Redirects are a fundamental part of web architecture. They're not going away. But the way you implement them speaks volumes about your attention to detail and respect for your users. A simple 'please click here if you are not redirected' message might seem harmless, but it's a symptom of a larger problem – a design that prioritises tracking or convenience over experience.

My advice? Audit your site's redirects today. Check for those sneaky intermediate pages. Replace them with proper 301 redirects or at least accelerate your meta refreshes. Use descriptive link text. Make it accessible. And if you're a developer or marketer, push your organisation to invest in better redirect practices. It's not rocket science. It's just good web hygiene. And your users – and your SEO rankings – will be better for it.

Remember, the goal is to get your visitors where they want to go as quickly and seamlessly as possible. That's the essence of good web design. So next time you see a 'Click here' page, don't just click – ask yourself: 'Could this be better?' The answer is almost always yes.