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.
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
-
302 to a page and rel=canonical back to the original (to preserve url juice)?
Bit of a weird case, but let me explain. We use unbounce.com to create our landing pages, which are on a separate sub-domain (get.domain.com).
Intermediate & Advanced SEO | | dragonlawhq
Some of these landing pages have a substantial amount of useful information and are part of our content building strategy (our content marketers are able to deploy them without going through the dev team cycle). We'd like to make sure the seo page-juice is counting towards our primary domain and not the subdomain.
(It would also help if we one day stop using unbounce and just migrate our landing page content to our primary website). Would it be an SEO faux-pas to do the following:
domain.com/awesome-page ---[302]---> get.domain.com/awesome-page
get.domain.com/awesome-page ---[rel=canonical]---> domain.com/awesome-page My understanding is that our primary domain would hold all the "page juice" whilst sending users to the unbounce landing page - and the day we stop using unbounce, we just kill the redirect and host the content on our primary domain.0 -
"noindex, follow" or "robots.txt" for thin content pages
Does anyone have any testing evidence what is better to use for pages with thin content, yet important pages to keep on a website? I am referring to content shared across multiple websites (such as e-commerce, real estate etc). Imagine a website with 300 high quality pages indexed and 5,000 thin product type pages, which are pages that would not generate relevant search traffic. Question goes: Does the interlinking value achieved by "noindex, follow" outweigh the negative of Google having to crawl all those "noindex" pages? With robots.txt one has Google's crawling focus on just the important pages that are indexed and that may give ranking a boost. Any experiments with insight to this would be great. I do get the story about "make the pages unique", "get customer reviews and comments" etc....but the above question is the important question here.
Intermediate & Advanced SEO | | khi50 -
Rel=next/prev for paginated pages then no need for "no index, follow"?
I have a real estate website and use rel=next/prev for paginated real estate result pages. I understand "no index, follow" is not needed for the paginated pages. However, my case is a bit unique: this is real estate site where the listings also show on competitors sites. So, I thought, if I "no index, follow" the paginated pages that would reduce the amount of duplicate content on my site and ultimately support my site ranking well. Again, I understand "no index, follow" is not needed for paginated pages when using rel=next/prev, but since my content will probably be considered fairly duplicate, I question if I should do anyway.
Intermediate & Advanced SEO | | khi50 -
Ranking slipped to page 6 from page 1 over the weekend?
My site has been on page one for 2 phrases consistently from May onwards this year. The site has fewer than 100 backlinks and the link profile looks fairly even. On Friday we were on page 1, we even had a position 1, however now we are on page 6. Do you think this is Penguin or some strange Google blip? We have no webmaster tools messages at all. Thanks for any help!
Intermediate & Advanced SEO | | onlinechester0 -
Yoast & rel canonical for paginated Wordpress URLs
Hello, our Wordpress blog at http://www.jobs.ca/career-resources has a rel canonical issue since we added pagination to the front page and category-pages. We're using Yoast and it's incorrectly applying a rel-canonical meta tag referencing page 1 on page 2, 3, etc. This is a known misuse of the rel-canonical tag (per Google's Webmaster Blog - http://googlewebmastercentral.blogspot.ca/2013/04/5-common-mistakes-with-relcanonical.html, which says rel-canonical should be replaced with rel-prev and rel-next for page 2, 3, etc.). We don't see a way to specify anywhere in Yoast's options to correct this behaviour for page 2, 3, etc. Yoast allows you to override a page's canonical URL, otherwise it automatically uses the Wordpress permalink. My question is, does anyone know how to configure Yoast to properly replace rel-canonical tags with rel-prev and rel-next for paginated URLs, or do I need to look at another plugin or customize the behavior directly in my child theme code? This issue was brought up here as well: http://moz.com/community/q/canonical-help, but the only response did not relate to Yoast. (We're using Wordpress 3.6.1 and Yoast "Wordpress SEO" 1.4.18)
Intermediate & Advanced SEO | | aactive0 -
Rel=canonical
I have seen that almost all of my website pages need rel=canonical tag. Seems that something's wrong here since I have unique content to every page. Even show the homepage as a rel=canonical which doesnt make sense. Can anyone suggest anything? or just ignore those issues.
Intermediate & Advanced SEO | | arcade880 -
What is a "good" dwell time?
I know there isn't any official documentation from Google about exact number of seconds a user should spend on a site, but does anyone have any case studies that looks at what might be a good "dwell time" to shoot for? We're looking on integrating an exact time on site into or Google Analytics metrics to count as a 'non-bounce'--so, for example, if a user spends 45 seconds on an article, then, we wouldn't count it as a bounce, since the reader likely read through all the content.
Intermediate & Advanced SEO | | nicole.healthline0 -
Where to point Rel = Canonical?
I have a client who is using the rel=canonical tag across their e-commerce site. Here is an example of how it is set up. URLs 1. http://www.beautybrands.com/category/makeup/face/bronzer.do?nType=22. http://www.beautybrands.com/category/makeup/face/bronzer.doThe canonical tag points to the second URL. Both pages are indexed by Google.The first page has a higher page authority (most of the internal site links go to the first URL) than the second one. Should the page with the highest authority be the one that the canonical tag points to? Is there a better way to handle these situations? Does any authority get passed through the tag?Thanks!
Intermediate & Advanced SEO | | AlightAnalytics0