Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Trailing Slashes on Home Pages
-
I do not think I have a problem here, but a second opinion would be welcomed...
I have a site which has a the rel=canonical tag with the trailing slash displayed. ie www.example.com/
The sitemap has it without the trailing slash. www.example.com
Google has it's cached copy with the trailing slash but the browser displays it without.
I want to say it's perfectly fine (for the home page) as I tend to think they are treated (with/without trailing slashes) as the same canonical URL.
-
Totally agree, it's kind of a non issue, improve the canonical if you can but really, don't sweat it.
-
Oh yes, thanks for that. I've read that page a few times. :S
Apologies for the confusion Alex.
Don't have a crisis of confidence anyway! If there's a canonical 99 times out of 100 (probably more) I'm sure Google would get this right whether it's the homepage or not.
What server is the site hosted on Alex? Or are the URLs controlled by a CMS?
-
That is certainly my understanding - the homepage is a special case.
This pretty much details it in full:
-
Hi Alex
Ah, crisis of confidence again!
I didn't think that this was the case though for the index page. I thought normalisation meant they were treated as the same page. As Marcus said, I can't 301 the example.com page to example.com/ .
-
Hey,
in an ideal world, make sure it is has no trailing slash. But, as per the Google specific recommendations, make sure both resolve as a 200 OK rather than redirecting / to non /.
Think about it -
The browser removes the trailing slash. Also, go to any big site, Google, SEOMoz - the all have no slash. But.. check it in webbug and they resolve on both.
For me, having a trailing slash on the root or anywhere is just something else for folks to forget to add if they are linking or some such.
Here I would just remove the trailing slash in your canonical if you can just to be sure but the usual rules don't apply on the homepage and www.example.com & www.example.com/ are regarded as the same thing.
I have constant crisis of confidence - i often wonder if I am making it up as I go along or somewhere down the history of all the hundreds of SEO audits I have done I actually learned something along the way! I have actually googled something that I was unsure about and found my own blog post about it before. I think, much like Homer Simpson, every new thing I learn now pushes out an older thing!
Hope that helps!
Marcus -
Hi Marcus
I agree out outside of the home page it's an issue (& good answer btw) but it's only the index page I'm worried about.
It's that crisis of confidence that I'm sure we all get from time to time as to whether something rather simple/fundamental is actually as we believe it to be.
I've been re-reading this document http://tools.ietf.org/html/rfc3986 and I think it's section 3.2.6 (if I remember right) that covers normalization of the root URL's.
-
The two versions you speak of are treated as duplicate content. Ideally you should make sure the URL is the same everywhere, and 301 redirect to your preferred version. Are you sure the browser itself isn't removing the trailing slash? I know Chrome does on non-directory pages.
Saying that, if you have a canonical tag it shouldn't cause a massive problem, but it will help to do everything properly. Do everything you can to make sure all links under your control are the same version.
-
Hey Alex
There is a good overview of this here:
http://googlewebmastercentral.blogspot.co.uk/2010/04/to-slash-or-not-to-slash.html
Outside of the homepage, a slash url and a non slash URL are regarded as two seperate pages so are technically duplicates. Now, Google will generally deal with this but it is not optimal (which is what we are all about eh) so you should make a call and either go / or no / and then 301 the other version to the default.
The homepage should resolve on both and 200 for both and not redirect to the non slash. The browser will generally remove the slash on a root URL.
This is from the above link:
Rest assured that for your root URL specifically, http://example.com is equivalent to http://example.com/ and can’t be redirected even if you’re Chuck Norris.
If you are using a CMS there are usually plugins or configuration options to enforce a slash if that is your preferred option.
The big deal here is to
A - be consistent
B - 301 the alternative to the preferred for crawl optimisation and to ensure no daft duplication issues crop up.
Hope that helps!
Marcus
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
-
Can you 301 redirect a page to an already existing/old page ?
If you delete a page (say a sub department/category page on an ecommerce store) should you 301 redirect its url to the nearest equivalent page still on the site or just delete and forget about it ? Generally should you try and 301 redirect any old pages your deleting if you can find suitable page with similar content to redirect to. Wont G consider it weird if you say a page has moved permenantly to such and such an address if that page/address existed before ? I presume its fine since say in the scenario of consolidating departments on your store you want to redirect the department page your going to delete to the existing pages/department you are consolidating old departments products into ?
Technical SEO | | Dan-Lawrence0 -
Home Page .index.htm and .com Duplicate Page Content/Title
I have been whittling away at the duplicate content on my clients' sites, thanks to SEOmoz's pro report, and have been getting push back from the account manager at register.com (the site was built here and the owner doesn't want to move it). He says these are the exact same page and he can't access one to redirect to the other. Any suggestions? The SEOmoz report says there is duplicate content on both these urls: Durango Mountain Biking | Durango Mountain Resort - Cascade Village http://www.cascadevillagehotel.com/index.htm Durango Mountain Biking | Durango Mountain Resort - Cascade Village http://www.cascadevillagehotel.com/ Your help is greatly appreciated! Sheryl
Technical SEO | | TOMMarketingLtd.0 -
Where to put Schema On Page
What part of my page should I put Schema data? Header? Footer? Also All pages? or just home page?
Technical SEO | | bozzie3114 -
Handling 301s: Multiple pages to a single page (consolidation)
Been scouring the interwebs and haven't found much information on redirecting two serparate pages to a single new page. Here is what it boils down to: Let's say a website has two pages, both with good page authority of products that are becoming fazed out. The products, Widget A and Widget B, are still popular search terms, but they are being combined into ONE product, Widget C. While Widget A and Widget B STILL have plenty to do with Widget C, Widget C is now the new page, the main focus page, and the page you want everyone to see and Google to recognize. Now, do I 301 Widget A and Widget B pages to Widget C, ALTHOUGH Widgets A and B previously had nothing to do with one another? (Remember, we want to try and keep some of that authority the two page have had.) OR do we keep Widget A and Widget B pages "alive", take them off the main navigation, and then put a "disclaimer" on the pages announcing they are now part of Widget C and link to Widget C? OR Should Widgets A and B page be canonicalized to Widget C? Again, keep in mind, widgets A and B previously were not similar, but NOW they are and result in Widget C. (If you are confused, we can provide a REAL work example of what we are talkinga about, but decided to not be specific to our industry for this.) Appreciate any and all thoughts on this.
Technical SEO | | JU19850 -
Web config redirects not working where a trailing slash is involved
I'm having real trouble with getting working redirects in place to use on a site we're re-launching with a modified url structure. Old URL: http://www.example.com/example_folder/ New URL: http://www.example.com/example-of-new-folder/ Now, where the old URL's have a trailing slash the web.config simply will not accept it. It says the URL can start with a slash, but not end with a slash. However, many of my URL's do end with a slash so I need a workaround. These are the rules I'm putting in place: <location path="example_folder/"></location> Thanks
Technical SEO | | AndrewAkesson0 -
How to force a trailing slash after the domain name
My campaign analysis is predictably listing domain.com and domain.com/ as repeated content. I've searched and searched but cannot find a way to force a trailing slash on the end of the domain name unless there's a file or directory after it.. Is there a way to accomplish this using .htaccess
Technical SEO | | JollyBoy0 -
Trailing Slashes In Url use Canonical Url or 301 Redirect?
I was thinking of using 301 redirects for trailing slahes to no trailing slashes for my urls. EG: www.url.com/page1/ 301 redirect to www.url.com/page1 Already got a redirect for non-www to www already. Just wondering in my case would it be best to continue using htacces for the trailing slash redirect or just go with Canonical URLs?
Technical SEO | | upick-1623910