Redirects using a Meta refresh
This means that the URL in question uses a meta refresh to redirect the page.
Why is this important?
The Meta refresh is a simple on page redirect, and is usually used when it is not possible to implement a HTTP redirect. Search engines will follow a meta refresh, and pass on some link equity, but they offer a poor user experience (typically associated with a five-second countdown and the text "If you are not redirected in five seconds, click here").
We recommend using a 301 redirect wherever possible, which matches Google's recommendations.
Google has also been known to show the URL of the original page in the search results if it has a higher PageRank than the location of the destination page.
What does the Hint check?
This Hint will trigger for any internal URL which has a meta refresh in the <head> which specifies a destination URL.
Examples that trigger this Hint:
Consider the URL: https://example.com/page-a
The Hint would trigger for this URL if it contained a meta refresh redirect in the head:
How do you resolve this issue?
Ideally, remove the meta refresh and utilise a 301 permanent redirect instead. A 301 redirect happens at the server level, rather than at the client level, and are generally the best way to handle redirects.
However, if there is genuinely no way to control server-side redirects (e.g. you cannot get access to the .htaccess file), then the meta redirect is unlikely to hurt you from a crawling and indexing perspective.
However, the redirecting page should still not be part of the overall site architecture - i.e. it should not have internal links pointing at it, instead of the destination URL.
The way to handle internal redirects is identify all the links that currently point to the redirecting URL, and change the href target to instead point to the new destination URL.
How do you get more data from Sitebulb?
From the URL List, you can click on the 'URL Details' button for any individual URL. From here you can see the redirect chain, which will show you the final destination URL (with status code 200).
You can also then view the Internal Links, which will need to be updated to the destination URL:
This allows you to handle each redirect individually. But if you want to deal with them in bulk, the best way to do this is to export the data and work from there.
From the URL List, click on the green button Export Hint Data.
Then the export file will give you everything you need to resolve each one, including example URLs that link to the redirect, and clarification if the links are part of the navigation or in-content.