¿Qué hacer cuando Firefox redirige a la página 301?

What to do when Firefox redirects to 301 page?

Revisit the obsessively cached 301 page. Reset the frequency back to 3 when finished. Firefox should now redirect to the new 301 page, no longer fetching the redirected page from cache.

When Google sees a permanent 301 or 308 redirect, it removes the old page from the index and replaces it with the page from the new location. The question is how this affects the ranking of the page?

Use the Skip Redirect extension. With Firefox restarted, your extension should now work. Skip Redirect will simply ignore most page redirects and take you to the destination page.

URL redirection, also known as URL forwarding, is a technique to give more than one URL address to a page, a form, or a whole Web site/application. HTTP has a special kind of response, called a HTTP redirect, for this operation.

All cached pages, images and redirects for only that site will be removed from the cache. This lets you clear the redirect for your development website without clearing the rest of your cache. As a side note, I think Firefox should only cache redirects for a few days at most. Caching them for over a month can make a simple mistake a big problem.

Prevention is better than cure – avoid a 301 redirect if you are not sure you want to permanently de-commission the old URL. To clear a permanent redirect, go to chrome://settings/clearBrowserData and from there only clearing “cached images and files” cleared the redirect.

Note that 302 and 307 redirects aren’t cached by default by browsers. If people still have the cached 301 redirect in their browser they will continue to be taken to the target page regardless of whether the source page still has the redirect in place. Your options for fixing this include: