301 Redirect Issue
-
I'm having an issue with 301 redirects:
Let's see if I can verbalize my thoughts on this one...
So we just recently moved our site to Wordpress. One of our new 301 commands is redirecting oursite.com/news to oursite.com/blog . However there are other links from our previous site that look like oursite.com/news/XYZ and the issue is that, because wordpress structures its links differently, that URL is not equivalent to oursite.com/blog/XYZ. Instead, it might look something more like oursite.com/blog/yaddayadda/XYZ or something. Does that make sense?
The issue is that when I find an old link of ours on google that looks something like "oursite.com/news/XYZ" or "oursite.com/news/ABC" it is automatically replacing "news" with "blog". When I try to go in manually and redirect anything that says "/news/XYZ" to "/blog/yaddayadda/XYZ" it still doesn't work. It still just replaces "news" with "blog."
Wow I realize that might not make sense to anyone but if it does - please advise!!
Thanks!!!!
-
I did try that. Not sure why it isn't working but I think it has something to do with Tom's answer below. Heh. Thanks though Daniel!!
-
Wow thanks so much. This might be way over my head (I know very little about web development) but I'm going to talk to our devs about it. Thanks again!!
-
Ah you have a parameter in the old URL. That ? is the real trick here. because you redirected /news to /blog it will redirect /news?anythingyouputhere to /blog?anythingyouputhere if that makes sense.
Did you try to redirect /blog?tag=business-2 to /blog/category/business yet?
-
Hi!
The problem you have is that you are using two different Apache extensions and I don't believe you can control the order the go in. You are using mod_alias and mod_rewrite.
It sounds like you have a line like:
Redirect permanent /news/dinosaur/ninja http://www.oursite.com/blog/ninja
This is the mod_alias rule, and it is firing before your mod_rewrite rules (and then it no longer fits their criteria, so they don't fire).
So, what you need to do is change your mod_alias rules into mod_rewrite rules, so then you can control the order (they execute top to bottom, so you just put your 'specific' redirects above your general ones). You rule should look something like this (I've not confirmed!):
RewriteRule ^/news/dinosaur/ninja/$ /blog/ninja/ [L,R=301]
I hope all that make sense. Let me know how you get on!
-
Hey Daniel. Thanks for your response - the only problem is that we already have /%postname% selected. It is working for mostly every blog entry except this one that I'm running into problems with. I'll show you the exact URL that's giving us the problem.
On google, it shows the URL as:
oursite.com/news?tag=business-2
Then it seems to be redirecting it to:
oursite.com/blog?tag=business-2
However, that site does not exist. It should be
http://oursite.com/category/business
I tried to literally 301 redirect both oursite.com/news?tag=business-2 and http://oursite.com/category/business to http://oursite.com/category/business but neither worked.
Thoughts?
-
It sounds like more of a permalink issue in wordpress than a redirect issue. Under settings on the left sidebar in your wordpress dashboard is a link called permalinks. Go there and let us know what it says there. You probably want a custom structure that says /%postname%/ so that your blog will make permalinks like site.com /blog/postname instead of site.com /blog/category/postname or whatever else might be going on there.
Get the simple 301 redirect plugin and make sure you do redirect every old URL to its new counterpart, but make sure your new ones look the way you want first.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Is 301 redirect the only way when using Vanity URLs?
We have been using vanity urls for some of our pages. Mostly the pages that have a vanity URL have a long URL length. But now the problem is, the vanity URL is getting displayed on the search engine when the particular keyword related to the page is entered. I checked the google search console, the vanity URL is indexed and the original URL remains unindexed. What should I do? Is adding 301 redirect to the vanity URLs are solution? Since some of vanity URLs are not redirecting to the original. Some of the original pages are not getting traffic. Also, can using canonical tag help?
Technical SEO | | tejasbansode0 -
Resolving 301 Redirect Chains from Different URL Versions (http, https, www, non-www)
Hi all, Our website has undergone both a redesign (with new URLs) and a migration to HTTPS in recent years. I'm having difficulties ensuring all URLs redirect to the correct version all the while preventing redirect chains. Right now everything is redirecting to the correct version but it usually takes up to two redirects to make this happen. See below for an example. How do I go about addressing this, or is this not even something I should concern myself with? Redirects (2) <colgroup><col width="123"><col width="302"></colgroup>
Technical SEO | | theyoungfirm
| Redirect Type | URL |
| | http://www.theyoungfirm.com/blog/2009/index.html 301 | https://theyoungfirm.com/blog/2009/index.html 301 | https://theyoungfirm.com/blog/ | This code below was what we added to our htaccess file. Prior to adding this, the various subdomain versions (www, non-www, http, etc.) were not redirecting properly. But ever since we added it, it's now created these additional URLs (see bolded URL above) as a middle step before resolving to the correct URL. RewriteEngine on RewriteCond %{HTTP_HOST} ^www.(.*)$ [NC] RewriteRule ^(.*)$ https://%1/$1 [R=301,L] RewriteCond %{HTTPS} !on RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L] Your feedback is much appreciated. Thanks in advance for your help. Sincerely, Bethany0 -
Removing Multiple 301 Redirects
During my last redesign (and migration to Drupal) some of the updated SEO friendly url's on the new site were misspelled. Rather than updating the 301 redirects to point to the correct page the developer just added an additional 301 redirect. So it was redirected like this website.com/oldpage (301 to) website.com/new-paige (301 to) website.com/new-page Instead of website.com/oldpage (301 to) website.com/new-page I'll be finishing another redesign and updating to https soon, should I remove the redirect to the misspelled domain and just have one 301 from the original page? These multiple redirects have been up for over a year. Thanks for any specific advice!
Technical SEO | | talltrees0 -
Redirects
Hello, i would like to ask which is the best redirect to use in a website now i have all my links to go to https://www.anavasis.gr Which is the best between: https://www.anavasis.gr https://anavasis.gr https://www.anavasis.gr/index.php https://anavasis.gr/index.php thanks in advance
Technical SEO | | anavasis0 -
Questions about the Sandbox and 301 Redirects
Does the sandbox still exist? What if you have a brand new URL and do a 301 redirect from another website because the name of the service business changed? Thanks for any insight and help.
Technical SEO | | SDSLaw0 -
302 to 301 redirect
Our site has quite a few 302 redirects that really ought to be 301's. Our IT department is really busy so the question is, given that the 302's have probably been in place for years, is it worth changing them to 301's now? Thanks
Technical SEO | | Houses0 -
301 redirect
What is a proper way to redirect any url containing a give word (anywhere in the url) to another sepcified url? Is it like this? RedirectMatch 301 ^thisword$ http://domain.com/newlocation
Technical SEO | | sesertin1 -
Drupal URL Aliases vs 301 Redirects + Do URL Aliases create duplicates?
Hi all! I have just begun work on a Drupal site which heavily uses the URL Aliases feature. I fear that it is creating duplicate links. For example:: we have http://www.URL.com/index.php and http://www.URL.com/ In addition we are about to switch a lot of links and want to keep the search engine benefit. Am I right in thinking URL aliases change the URL, while leaving the old URL live and without creating search engine friendly redirects such as 301s? Thanks for any help! Christian
Technical SEO | | ChristianMKTG0