Keeping old links active - 301 vs. Additional URL
Permalink
Quite often, I'm converting an existing site with, say, /page-name.php and would like to keep existing pages to point to the new /something/page-name/ URL, to prevent broken links.
I completely understand the 301 .htaccess method, but I'm wondering what exactly the "Add URL" feature in Concrete does. Is this permissible in this case?
By using "Add URL", will search engines still keep the old, out-dated /page-name.php links active because it still goes somewhere? If so, is there an easier way built-in to Concrete that allows an actual 301, or am I stuck manually editing .htaccess for this?
Any confirmed info would be appreciated!
I completely understand the 301 .htaccess method, but I'm wondering what exactly the "Add URL" feature in Concrete does. Is this permissible in this case?
By using "Add URL", will search engines still keep the old, out-dated /page-name.php links active because it still goes somewhere? If so, is there an easier way built-in to Concrete that allows an actual 301, or am I stuck manually editing .htaccess for this?
Any confirmed info would be appreciated!
I tested this before with the FireFox live http headers add on. The additional URLs do send a 301 and are not listed in the sitemap.xml, so the old pages should get dropped out for the new ones.
It must redirect using something other than .htaccess? I don't see anything additional in it other than the standard Pretty URL rewriting.
I imagine it's using the dispatcher (totally a guess), but since it is sending 301 headers - you should be fine. Your "link juice" will get redirected to the page with the additional URL and the old URL will eventually be removed from indexes.
I've used additional page URLs to completely "move" a website to a different site structure on many occasions.
I've used additional page URLs to completely "move" a website to a different site structure on many occasions.
you want to set additional page paths underneath the page properties. You have your standard url but you can define others.
htaccess will rewrite everything to index.php which hits dispatcher.php for anything that doesn't resolve to a resource(file or php file or whatever) so concrete5 will intercept these requests if there's a page that matches and then redirects or renders those.
htaccess will rewrite everything to index.php which hits dispatcher.php for anything that doesn't resolve to a resource(file or php file or whatever) so concrete5 will intercept these requests if there's a page that matches and then redirects or renders those.
