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.
Should pages with rel="canonical" be put in a sitemap?
- 
					
					
					
					
 I am working on an ecommerce site and I am going to add different views to the category pages. The views will all have different urls so I would like to add the rel="canonical" tag to them. Should I still add these pages to the sitemap? 
- 
					
					
					
					
 I would just title them according to their view type. Try to put your most informative words as close to the front as possible so that it's easy to read in browser tabs, for example: Red Widgets, All Widgets, <$25 Widgets... etc. Meta description could probably be a repeat of the title tag. Make the title as UX friendly as possible. 
- 
					
					
					
					
 - What are your thoughts on title tag and meta description on these pages? The only thing that changes on these pages is how the item is displayed. Should I change the title tag and meta description even though they should never be the organic landing page?
 
- 
					
					
					
					
 What are your thoughts on title tag and meta description on these pages? The only thing that changes on these pages is how the item is displayed. Should I change the title tag and meta description even though they should never be the organic landing page? 
- 
					
					
					
					
 Yes, I would not put them in the sitemap. Main goal of a sitemap is to make it easier for bots to discover the different pages of the site. The pages that have a canonical url pointing to another page don't really need this, as you don't want the search engines to index them anyway. 
- 
					
					
					
					
 Since my preference is always to have people land on the page with thumbnails that is what I was thinking but wanted to double check. Thank you. 
- 
					
					
					
					
 Based on how you're describing it, I'd leave them out of the sitemap. 
- 
					
					
					
					
 These pages will be almost identical. They are category pages for ecommerce and the only difference is it will display all items and there will be no thumbnails. It sounds like you are saying not to put them in the sitemap in this instance? 
- 
					
					
					
					
 They are category pages for an ecommerce site. Currently we list the items 25 to a page with a thumbnail. The second view will be all of the items in a basic list view with no thumbnails. We have some categories with several hundred items and our users have requested a way to see them all on one page. 
- 
					
					
					
					
 Hi, Agree with the arguments of Ryan on the whether or not to put the canonical. However, if you decide that these pages are almost identical, and that you will use a canonical, it has no use to put all the variations of these pages in the sitemap. However, you should add the canonical version to the sitemap. It's not a big problem if these pages are in the sitemap, you'll just notice it webmaster tools a low % of indexed pages for this sitemap. rgds, Dirk 
- 
					
					
					
					
 Are the different views going to be substantially different pages or a reordering of products seen throughout each view? If the latter is the case I wouldn't use rel="canonical" for each view. If the pages are substantially different, like one is just displaying widgets, while the other is displaying widget maintenance tools, the having each of those pages as categorical sections to your store is worth it and worth being in the sitemap. 
Browse Questions
Explore more categories
- 
		
		Moz ToolsChat with the community about the Moz tools. 
- 
		
		SEO TacticsDiscuss the SEO process with fellow marketers 
- 
		
		CommunityDiscuss industry events, jobs, and news! 
- 
		
		Digital MarketingChat about tactics outside of SEO 
- 
		
		Research & TrendsDive into research and trends in the search industry. 
- 
		
		SupportConnect on product support and feature requests. 
Related Questions
- 
		
		
		
		
		
		Rel canonical tag from shopify page to wordpress site page
 We have pages on our shopify site example - https://shop.example.com/collections/cast-aluminum-plaques/products/cast-aluminum-address-plaque That we want to put a rel canonical tag on to direct to our wordpress site page - https://www.example.com/aluminum-plaques/ We have links form the wordpress page to the shop page, and over time ahve found that google has ranked the shop pages over the wp pages, which we do not want. So we want to put rel canonical tags on the shop pages to say the wp page is the authority. I hope that makes sense, and I would appreciate your feeback and best solution. Thanks! Is that possible? Intermediate & Advanced SEO | | shabbirmoosa0
- 
		
		
		
		
		
		Should I apply Canonical Links from my Landing Pages to Core Website Pages?
 I am working on an SEO project for the website: https://wave.com.au/ There are some core website pages, which we want to target for organic traffic, like this one: https://wave.com.au/doctors/medical-specialties/anaesthetist-jobs/ Then we have basically have another version that is set up as a landing page and used for CPC campaigns. https://wave.com.au/anaesthetists/ Essentially, my question is should I apply canonical links from the landing page versions to the core website pages (especially if I know they are only utilising them for CPC campaigns) so as to push link equity/juice across? Here is the GA data from January 1 - April 30, 2019 (Behavior > Site Content > All Pages😞 Intermediate & Advanced SEO | | Wavelength_International0
- 
		
		
		
		
		
		Switching from HTTP to HTTPS: 301 redirect or keep both & rel canonical?
 Hey Mozzers, I'll be moving several sites from HTTP to HTTPS in the coming weeks (same brand, multiple ccTLDs). We'll start on a low traffic site and test it for 2-4 weeks to see the impact before rolling out across all 8 sites. Ideally, I'd like to simply 301 redirect the HTTP version page to the HTTPS version of the page (to get that potential SEO rankings boost). However, I'm concerned about the potential drop in rankings, links and traffic. I'm thinking of alternative ways and so instead of the 301 redirect approach, I would keep both sites live and accessible, and then add rel canonical on the HTTPS pages to point towards HTTP so that Google keeps the current pages/ links/ indexed as they are today (in this case, HTTPS is more UX than for SEO). Has anyone tried the rel canonical approach, and if so, what were the results? Do you recommend it? Also, for those who have implemented HTTPS, how long did it take for Google to index those pages over the older HTTP pages? Intermediate & Advanced SEO | | Steven_Macdonald0
- 
		
		
		
		
		
		Rel="canonical" and rel="alternate" both necessary?
 We are fighting some duplicate content issues across multiple domains. We have a few magento stores that have different country codes. For example: domain.com and domain.ca, domain.com is the "main" domain. We have set up different rel="alternative codes like: The question is, do we need to add custom rel="canonical" tags to domain.ca that points to domain.com? For example for domain.ca/product.html to point to: Also how far does rel="canonical" follow? For example if we have: Intermediate & Advanced SEO | | AlliedComputer
 domain.ca/sub/product.html canonical to domain.com/sub/product.html
 then,
 domain.com/sub/product.html canonical to domain.com/product.html0
- 
		
		
		
		
		
		Do I need to use rel="canonical" on pages with no external links?
 I know having rel="canonical" for each page on my website is not a bad practice... but how necessary is it for pages that don't have any external links pointing to them? I have my own opinions on this, to be fair - but I'd love to get a consensus before I start trying to customize which URLs have/don't have it included. Thank you. Intermediate & Advanced SEO | | Netrepid0
- 
		
		
		
		
		
		Can too many "noindex" pages compared to "index" pages be a problem?
 Hello, I have a question for you: our website virtualsheetmusic.com includes thousands of product pages, and due to Panda penalties in the past, we have no-indexed most of the product pages hoping in a sort of recovery (not yet seen though!). So, currently we have about 4,000 "index" page compared to about 80,000 "noindex" pages. Now, we plan to add additional 100,000 new product pages from a new publisher to offer our customers more music choice, and these new pages will still be marked as "noindex, follow". At the end of the integration process, we will end up having something like 180,000 "noindex, follow" pages compared to about 4,000 "index, follow" pages. Here is my question: can this huge discrepancy between 180,000 "noindex" pages and 4,000 "index" pages be a problem? Can this kind of scenario have or cause any negative effect on our current natural SEs profile? or is this something that doesn't actually matter? Any thoughts on this issue are very welcome. Thank you! Fabrizio Intermediate & Advanced SEO | | fablau0
- 
		
		
		
		
		
		What is the best way to optimize/setup a teaser "coming soon" page for a new product launch?
 Within the context of a physical product launch what are some ideas around creating a /coming-soon page that "teases" the launch. Ideally I'd like to optimize a page around the product, but the client wants to try build consumer anticipation without giving too many details away. Any thoughts? Intermediate & Advanced SEO | | GSI0
- 
		
		
		
		
		
		Using the Word "Free" in Metadata
 Hi Forum! I've searched previous questions, and couldn't find anything related to this. I know the word "free" when used in email marketing can trigger spam filters. If I use the word "free" in my metadata (title tag, description, and keywords just for fun) will I be penalized in any way? Thanks! Intermediate & Advanced SEO | | Travis-W0
 
			
		 
			
		 
			
		 
					
				 
					
				 
					
				 
					
				 
					
				