Using 301 for only some content on a site that eventually will delete those pages?
My company is migrating content from one section "A" of its gigantic website to a new website "B" which is focused only on this type of content. Eventually, they want to delete this old section "A" completely but the gigantic website will otherwise remain.
Is it worth using 301 redirects to help users get to the new site B, rather than pull the rug out one day, and to retain some of the page rank?
What about when that section A on the old site is completely deleted? Will the 301 rank stay with the new site?
Yes, it's a good practice to create 301 redirect. It's good for both users and Search Engines. Also, it shows that you're not duplicating content, and Search Engines really don't like websites that "copy-paste" content from others.
As soon as search engines detect the 301, the rank will stay and they won't considerer it as duplicated content.
- → OctoberCMS Rain User plugin not working or redirecting
- → Redirect wrong url laravel 5.1
- → Laravel 4.2 application occurs unnecessary redirection after uploading live server
- → laravel 4 filter route not working
- → redux how to redirect on componentWillMount using react-router
- → 301 Redirection from no-www to www in wordpress
- → Cyclical redirection at the start laravel 5 project
- → Get parameters from Stripe page redirect URL Node.js
- → what type of redirect to a connection page should I use?
- → Lumen Request has session app('session') is empty. Redirect not working
- → File Upload Redirect with Error Not Display
- → React Router redirect using alternate route configuration
- → In React, How do I redirect a user back to the index with altered state