Google also indexed trailing slash version - PLEASE HELP
-
Hi Guys,
We redesigned the website and somehow our canonical extension decided to add a trailing slash to all URLs. Previously our canonical URLs didn't have a trailing slash.
During the redesign we haven't changed the URLs. They remained same but we have now two versions indexed. One with trailing slash one without.
I've now fixed the issue and removed the the trailing slash from canonical URLs.
Is this the correct way of fixing it? Will our rankings be effected in a negative way?
Is there anything else I need to do.
The website went live last Tuesday.
Thanks
-
Thats great! The canonical URLs are showing URLs without slash as they are probably reflecting their original URL which is without slash. Hope Google clears them soon..
-
Seems like you got the 301-redirect resolved below - if you've got that in place and fixed the canonical tag, it should be ok. It'll just take some time (usually longer than you'd like) for Google to clear out the pages, especially the deeper ones. If you see gradual de-indexation, though, you'll probably be fine.
-
-
Actual rel="canonical" tags.
-
As soon as we relised everything was fixed. Canonical tag is showing urls without slash and also aplied to htaccess to redirect slash version to non slash version.
<cite>we're using www.shopify.com</cite>
-
-
Could you clarify a couple of things:
(1) When you say canonical URLs, do you mean your internal links, or the actual URLs in your rel="canonical" tags?
(2) If it was just the canonical tags, is everything consistent now (tags, internal links, etc.)?
Since both version will resolve, just fixing the canonical tags (if that's the issue) should be enough - it's just going to take a little time. They should be as effective as a 301-redirect in this case. Either way, though, it can take Google a while to kick out the duplicates. I'd just monitor the index closely and make sure the top-level pages are clearing up (i.e. your home-page and major category duplicates should be disappearing). If that's happening, you're ok - you just need to wait a bit. If that's not happening, then you may have some other mixed signals in play.
-
You are welcome.
Well, the first time you did submit the sitemap right, but now since Google has found new URLs on your website and indexed them, it would be good to notify the big G that they are no longer a part of your website and resubmitting would not hurt.
About the redirections, Google does take a bit of time to understand that the URLs have permanently moved and will gradually remove them from the index. So, keep checking the index for the trailing slash URLs and when they are gone, you can remove the redirections.
Cheers,
-
Thanks a lot.
Now when i click the slash version of the indexed URL from google goes to nonslash version. So it seems we're safe now.
The other thing is when I submitted the sitemap.xml after launch it was without slash. Also all internal links are targeting nonslash URLs. I think google should understand that this is a technical issue and now it has been solved.
When should i remove that redirect?
-
Yups, its done. Just need to be sure if the Home Page is fine. The indexed version of the Home Page stays as it is without any redirection.
Cheers,
-
I checked with this website: http://www.internetofficer.com/seo-tool/redirect-check/
It says:
http://www.mydomain.com/jason.html/
Type of redirect: 301 Moved Permanently
http://www.mydomain.com/jason.html
So looks as if it's done the job. Right?
-
Sounds good, do keep a check to make it 100% sure. I believe the SE's will be fine now.
Cheers,
-
RewriteRule ^([^/]+/)*([^/.]+).html/ http://www.mydomain.com/$2.html [R=301,L]
Looks like above did the trick
-
I think some of these posts can help you understand:
http://html5boilerplate.com/docs/Proper-usage-of-trailing-slash-redirects/
Do try this a test environment and take a backup of the .htaccess file before making any changes, Have it go through a programmer.
Cheers,
-
Please can you tell me how to redirect urls with slash to non slash urls using .htaccess.
-
Jvalops,
This is a common scenario in SEO when you have 2 versions indexed of the same URL. This bascially creates a duplicate issue. Now, this situation has a solution which includes 2 things to implement:
1. Fix it from the search engines's perspective.
2. Make changes at the server level.
You did remove the trailing slash so you fixed it at the server level but you left the search engines to think - Where did the URL go? Am I supposed to show a 404 for that or what?.
So, it is important that you first fix them for the SE's and then make any server level changes because you never know how quick the crawlers can re-visit the disappeared URL and take their own action. Since this is just a recent change I hope that the SE;s will not evaluate it in a negative way but you should be quick to inform them. Now, since you have already removed it, do add a code in the .htaccess file stating that any URL with a slash redirects it to the URL without slash. I hope there are no URLs that have to end with a slash (just have a re-look on this, the home page and others).
After this is done, to make things more clear to the search engines, resubmit your XML sitemap with all the correct URLs on the website and I think you will be just fine.
On the rankings, I don't think it will be affected, unless there was a re-crawl after the indexation.
Cheers,
-
I'm not 100% sure how to answer your question, but an .htaccess 301 might work.
/example.html/ example.html
Try that to see if it works.
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
-
Hiding content until user scrolls - Will Google penalize me?
I've used: "opacity:0;" to hide sections of my content, which are triggered to show (using Javascript) once the user scrolls over these sections. I remember reading a while back that Google essentially ignores content which is hidden from your page (it mentioned they don't index it, so it's close to impossible to rank for it). Is this still the case? Thanks, Sam
Web Design | | Sam.at.Moz0 -
Curious why site isn't ranking, rather seems like being penalized for duplicate content but no issues via Google Webmaster...
So we have a site ThePowerBoard.com and it has some pretty impressive links pointing back to it. It is obviously optimized for the keyword "Powerboard", but in no way is it even in the top 10 pages of Google ranking. If you site:thepowerboard.com the site, and/or Google just the URL thepowerboard.com you will see that it populates in the search results. However if you quote search just the title of the home page, you will see oddly that the domain doesn't show up rather at the bottom of the results you will see where Google places "In order to show you the most relevant results, we have omitted some entries very similar to the 7 already displayed". If you click on the link below that, then the site shows up toward the bottom of those results. Is this the case of duplicate content? Also from the developer that built the site said the following: "The domain name is www.thepowerboard.com and it is on a shared server in a folder named thehoverboard.com. This has caused issues trying to ssh into the server which forces us to ssh into it via it’s ip address rather than by domain name. So I think it may also be causing your search bot indexing problem. Again, I am only speculating at this point. The folder name difference is the only thing different between this site and any other site that we have set up." (Would this be the culprit? Looking for some expert advice as it makes no sense to us why this domain isn't ranking?
Web Design | | izepper0 -
Dealing with the impending Google mobile compliance update - is bMobilized any good as a temporary measure?
We've been caught a bit off guard with the upcoming Google mobile compliance issue and received the warnings in webmasters about fixing mobile usability issues. It will still be some time before we can have the site re-coded as responsive. I have stumbled upon a converter tool (which turns any site into one that's mobile friendly) called bMobilized, which essentially turns your site into one that's mobile friendly. Have you used bMobilized? Is it a safe idea to use this service temporarily until our new responsive site is ready in a few months? Do you have any suggestions for temporarily getting around the mobile compliance issue while our new responsive site is being built? Thanks
Web Design | | Martin_S0 -
Is it necessary to Remove 301 redirects from Wordpress after removing the 404 url from Google Webmaster?
There were many 404 urls in my site found by Google Webmaster. I've redirected these urls to the relevant urls with 301 redirect in wordpress. After that I removed these 404 urls from Google Index through Webmaster. "Should I cleanup these 301 redirects from Wordpress or not? ". Help Needed.
Web Design | | SangeetaC0 -
Duplicate Content? Designing new site, but all content got indexed on developer's sandbox
An ecommerce I'm helping is getting a complete redesign. Their developer had a sandbox version of their new site for design & testing. Several thousand products were loaded into the sandbox site. Then Google/Bing crawled and indexed the site (because developer didn't have a robots.txt), picking up and caching about 7,200 pages. There were even 2-3 orders placed on the sandbox site, so people were finding it. So what happens now?
Web Design | | trafficmotion
When the sandbox site is transferred to the final version on the proper domain, is there a duplicate content issue?
How can the developer fix this?0 -
301 forwarding during site migration problem - several url versions of the same page....
Hello, I'm migrating from an old site to a new site, and 301 forwarding many of the pages... My key problem is this I'm seeing www.website.com/ indexed in SE and www.website.com/default.aspx in showing as URL when I'm on homepage - should I simply 301 forward both of these? Then for several internal pages there are 2/3 versions of each page indexed. Canonicalization issues. Again, I'm wondering whether I should 301 forward each URL even if there are several different indexed URLs for the same page? Your advice will be welcome! Thanks in advance - Luke
Web Design | | McTaggart0 -
Question #1: Does Google index https:// pages? I thought they didn't because....
generally the difference between https:// and http:// is that the s (stands for secure I think) is usually reserved for payment pages, and other similar types of pages that search engines aren't supposed to index. (like any page where private data is stored) My site that all of my questions are revolving around is built with Volusion (i'm used to wordpress) and I keep finding problems like this one. The site was hardcoded to have all MENU internal links (which was 90% of our internal links) lead to **https://**www.example.com/example-page/ instead of **http://**www.example.com/example-page/ To double check that this was causing a loss in Link Juice. I jumped over to OSE. Sure enough, the internal links were not being indexed, only the links that were manually created and set to NOT include the httpS:// were being indexed. So if OSE wasn't counting the links, and based on the general ideology behind secure http access, that would infer that no link juice is being passed... Right?? Thanks for your time. Screens are available if necessary, but the OSE has already been updated since then and the new internal links ARE STILL NOT being indexed. The problem is.. is this a volusion problem? Should I switch to Wordpress? here's the site URL (please excuse the design, it's pretty ugly considering how basic volusion is compared to wordpress) http://www.uncommonthread.com/
Web Design | | TylerAbernethy0 -
Is it worth upgrading php to accomodate new WP version?
my client revisitors.com has a blog blog.revisitors.com that we cannot update to a newer WP version 3.5.1 because his php version apparently must be upgraded first. You cannot update because WordPress 3.5.1 requires PHP version 5.2.4 or higher. You are running version 5.1.6. according to client it would be potentially hazarardous for him to upgrade the php but we cant update or add new plugins because we arent running the current version of WP what is worse? i am responsible for his blog but i feel handicapped bigtime - at the same time i dont want him to do something that could wreck his site functionality either any suggestions? or advice here? thanks
Web Design | | Ezpro90