Are pages with a canonical tag indexed?
-
Hello here,
here are my questions for you related to the canonical tag:
1. If I put online a new webpage with a canonical tag pointing to a different page, will this new page be indexed by Google and will I be able to find it in the index?
2. If instead I apply the canonical tag to a page already in the index, will this page be removed from the index?
Thank you in advance for any insights!
Fabrizio
-
Yes, I will look into doing that on GWT.
Was a nice and useful chat indeed! Thank you again.
-
Sorry Fabrizio I got mad with my old answer
that canonical doesn't make sense with a noindex, with noindex follow.you're completely fine.
Summing up I think that you have many parameters so you should try to write them down and define the role of each one.
Then add them in GWT and choose there which are the ones which doesn't add any value and which you want to "block" (instead of putting a noindex).
The valuable ones (the one which adds value and changes content) should contain the self canonical and paginated next/prev. If you can get rid of unesful parameters it could be better so to have cleaner and shorter urls.
Just be sure that you're mainly using the most important parameters so you're consistent with your strategy.
Hope this will clear your doubts, it was a nice chat!
-
Yes, actually I could get rid of the lpg parameter (it wasn't really needed!), so now the tag definitions are (for the 3rd page of the Guitar index):
<LINK rel="<a class="attribute-value">next</a>" href="[http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=4](view-source:http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=4)"> <LINK rel="<a class="attribute-value">prev</a>" href="[http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2](view-source:http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2)"> <LINK rel="<a class="attribute-value">canonical</a>" href="[http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3](view-source:http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3)">
Now, the only doubt I still have is to add or not add the noindex tag to the page when it is requested to be displayed in a different way (such as the "table view" or a different item display order). In my opinion, if I stick with the canonical tag I don't need a noindex directive. What do you think?
-
Yeah, to be fair, I'm not clear on what all of the additional parameters (like "lpg=") do, so this can get tricky fast. Basically, look at it this way:
If the URL is:
example.com/page=3?param=xThen the tags should point to:
Rel=prev:
example.com/page=2?param=xRel=next:
example.com/page=4?param=xRel=canonical:
example.com/page=3 (no parameters)Some parameters may not be indexed and/or functional, though, so individual cases can vary. You may choose to ignore some parameters in Google Webmaster Tools, for example. It gets tricky as the parameter list grows.
-
Mememax, after thinking I have some doubts though about what you have suggested.
Why I want to put a noindex tag to the page displaying the list in "table view" if I already have a canonical tag pointing to the "regular view" page? Wouldn't the canonical tag be enough for the purpose of telling that the "real" canonical page is the "regular view" version? I am asking this because if I want to apply a noindex tag to that kind of different view, I may want to do the same to the list displayed with a different order, and for any other different way of displaying the list, etc... hence just using the canonical tag would be appropriate, pointing always to the "regular list" view, no matter what kind of "filtering" or "different view' option is selected. What do you think?
In other words, I don't think I need to include a noindex tag for any different kind of view the user requests as long as I provide a canonical tag pointing to the regular view list.
Am I correct?
-
Yes, thank you Mememax, I agree with you 100%. That makes perfect sense and I will work on that tomorrow morning. I am eager to know Dr. Peter thoughts and confirmation.
On my side, I think I got it cleared-up now. Thank you very much again!
-
Thank you ! That makes sense now.
-
Hey Fabrizio, I think that what Google states in their guidelines is that you have two choices:
- if you have a view all page, you should noindex and follow all your other pages so google will deliver only that page
- if you don't have a view all page or if you prefer to show paginated series (i.e. to make pages lighter and quicker to deliver to users) you may consider to use rel next/prev.
In this second case it may happen that you also add filters or session ids in the urls of those pages, in that case you should consider adding a self referentail canonical tag to avoid duplicates. But this is only if you cover this case, if you're looking to canonicalize correctly your paginated series you may not use the self canonical tag, because if not properly implemented this may get you a bit of extra work.
In this page for example
I found this:
http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3&lpg=0">
Which I don't think is what you want to do.
Also if you set the page to view as a table: your url changes to http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3&viewlistflag=1
and while the canonical should remain the same (well done but I think you should get rid of the lpg parameter in the canonical), the rel next prev should change accordingly IMO.
So instead of being:
prev: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2&lpg=20
next: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=4&lpg=60you should offer the next and prev page of the filtered url:
next: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=4&lpg=60&viewlistflag=1
prev: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2&lpg=20&viewlistflag=1Or in this case (since the content is almost the same you may consider the list page as the canonical of the table one putting there a noindex.
Summing up, IMO: in this page http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3
you'll have:
prev: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=4&lpg=60
next: http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2&lpg=20
(optional) a self canonical to http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3In this page (and in other filtered pages if you have apply the same idea):
http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3&viewlistflag=1You'll have:
noindex,follow and canonical to the list page:
http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3maybe dr peter can correct me if I'm wrong but I think this should be more consistent like this. Sorry for the huge answer
-
Wow, yes - sorry about that. I've updated it. Google original write-up actually covers this case, too (it's toward the end):
http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html
-
Please, have a look at the page below, I have modified the canonical tag as suggested:
http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3&lpg=40
Is that correct?
Thank you again very much.
-
Thank you Peter, I guess you meant to have the "canonical" tag as last tag in your example above, and also the previous rel=next and rel=prev definitions should be inverted:
Am I correct? That makes sense. If so, I will update my site to reflect this.
Thank you for the link!
-
This gets tricky fast. Google currently wants rel=prev/next to contain the parameters currently in use (like sorts) for the page you're on and then wants you rel-canonical to the non-parameterized version. So, if the URL is:
http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=3&lpg=40
...then the tags should be...
Yeah, it's a bit strange. They have suggested that it's ok to rel-canonical to a "View All" page, but with the kind of product volume you have, that's generally a bad idea (for users and search). The have specifically recommended against setting rel-canonical to Page 1 of search results, especially if you use rel=prev/next.
Rel=prev/next will still show pages in the index, but I've found it to work pretty well. The other option is the more classic approach to simple META NOINDEX, FOLLOW pages 2+. That can still be effective, but it's getting less common.
Adam Audette has generally strong posts about this topic - here's a good, recent one:
http://searchengineland.com/the-latest-greatest-on-seo-pagination-114284
-
Thank you for your post, and I think you have just opened a doubt I had, and that's exactly what also concerned me.
Have a look at this typical category page of ours:
http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html
For that category pagination, I have implemented the rel=prev/next as suggested by Google, but being afraid to be penalized for duplicate content, I also put a canonical tag pointing at the first page of that index. Should I have put the canonical tag pointing to the page series itself?
Something like:
http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html?cp=2
for the second page instead of the general:
http://www.virtualsheetmusic.com/downloads/Indici/Guitar.html
as I am currently doing?
Thanks!
-
I have to disagree on this one. If Google honors a canonical tag, the non-canonical page will generally disappear from the index, at least inasmuch as we can measure it (with "site:", getting it to rank, etc.). It's a strong signal in many cases.
This is part of the reason Google introduced rel=prev/next for paginated content. With canonical, pages in the series aren't usually able to rank. Rel=prev/next allows them to rank without clogging up the index (theoretically). For search pagination, it's generally a better solution.
If your paginated content is still showing in large quantities in the index, Google may not be honoring the canonical tag properly, and they could be causing duplicate content issues. It depends on the implementation, but they recommend these days that you don't canonical to the first page of search results. Google may choose to ignore the tag in some cases.
-
Thank you very much, that makes perfect sense. In my case, I am talking exactly about paginated content, and that's probably why all pages are in the index despite they are canonicalized to point to the main page. So, I guess that even if you have thousands of paginated pages indexed (mine is a pretty big e-commerce website), that's not going to be an issue. Am I right?
-
Normally the only thing which will prevent a page from ranking is noindex tag. If you don't want to have it indexed just noindex it, if that page has been laready indexed, put the noindex tag and delete from index using GWT option.
Concerning the canonical tag thing, it will consolidate the seo value in one page but it won't prevent those page to appear in rankings, however you may have two cases:
- the two or more pages are identical. In that case google may accept the canonicalization and show always the original page.
- the two or more pages are slightly different, it's the case of paginated pages which are canonicalized using rel next/prev. In that sense the whole value will be consolidated in page 1 but then the page which will be shown in the rankings will be the one which responds to that query, for example if someone is looking for blue glass, google will return the page which shows blue glass listing if that's different from the first one.
Hope this may help you!
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
-
Taken a canonical off a page to let it rank with new unique content - what more can I do?
A week ago, I took a canonical off of a page that was pointing to the homepage for a very big, generic search term for my brand as we felt that it could have been harming our rankings (as it wasn't a true canonical page). A week in and our rankings for the term have dropped 7 positions out of page 1 and the page we want to rank instead is nowhere to be seen. Do I hang fire? As such a big search term, it's affecting traffic, but I don't want to make any rash decisions. Here's a bit more info: For arguments sake, let's call the search term we're going after 'Boots', with the URL where the canonical was placed of /boots. The canonical went to the root domain as we sell, well... boots. At the time, the homepage was ranking for Boots on page 1 and we wanted to change this so that the Boots page ranked for that term... all logical right? We did the following: Took off mentions of Boots from meta on the homepage and made sure it was optimised for on the boots page. Took the canonical off of /boots. Used GSC to fetch & ask Google to recrawl "/boots". Resubmitted the sitemap. Do I hang fire on running back to the safety of ranking for boots on the homepage? Do I risk keyword cannibalisation by adding the search terms back to the homepage?
Intermediate & Advanced SEO | | Kelly_Edwards0 -
Putting rel=canonical tags on blogpost pointing to product pages
I came across an article mentioning this as a strategy for getting product pages (which are tough to get links for) some link equity. See #21: content flipping: https://www.matthewbarby.com/customer-acquisition-strategies Has anyone done this? Seems like this isn't what the tag is meant for, and Google may see this as deceptive? Any thoughts? Jim
Intermediate & Advanced SEO | | jim_shook0 -
Only 4 of my pages have been indexed out of 64 in total
Hi there, I submitted a sitemap for a new 64 page website 6 weeks ago and only a few pages have been indexed. The website shows in Google search but with a large amount of information on the website it should show higher. I have fetched and rendered 30 plus pages on the 9th September and others on the 16th September, today is the 5th October but in Webmaster tools, Google only acknowledge 1 page as indexed. I have checked the robots txt file which shows it is allowed. There are no messages for problems with crawl and no errors showing. The domain is www.urbaneforms.com . Can you offer a suggestion as to why we are not being indexed?
Intermediate & Advanced SEO | | simplyworld0 -
HTTPS pages - To meta no-index or not to meta no-index?
I am working on a client's site at the moment and I noticed that both HTTP and HTTPS versions of certain pages are indexed by Google and both show in the SERPS when you search for the content of these pages. I just wanted to get various opinions on whether HTTPS pages should have a meta no-index tag through an htaccess rule or whether they should be left as is.
Intermediate & Advanced SEO | | Jamie.Stevens0 -
Whats the best way to remove search indexed pages on magento?
A new client ( aqmp.com.br/ )call me yestarday and she told me since they moved on magento they droped down more than US$ 20.000 in sales revenue ( monthly)... I´ve just checked the webmaster tool and I´ve just discovered the number of crawled pages went from 3.260 to 75.000 since magento started... magento is creating lots of pages with queries like search and filters. Example: http://aqmp.com.br/acessorios/lencos.html http://aqmp.com.br/acessorios/lencos.html?mode=grid http://aqmp.com.br/acessorios/lencos.html?dir=desc&order=name Add a instruction on robots.txt is the best way to remove unnecessary pages of the search engine?
Intermediate & Advanced SEO | | SeoMartin10 -
What happen if a canonical tag points to a noindex page?
Hello,
Intermediate & Advanced SEO | | fablau
I have question. We have hundreds of affiliates that have implemented our datafeed on their websites, and to avoid duplicate content issues we are requiring them to put a canonical tag on their own product pages pointing to our own original product page. So, for example, if an affiliate has a page about our Product 101, they will have to add a canonical tag pointing to the corresponding product page on our own website: www.ourwebsite.com/products/product101 Now, since many of our product pages have defined a "noindex" tag (due to Panda issues), may that be a problem? In other words: what kind of problems could cause having our affiliates defining a canonical tag on their own product pages pointing to the original product page on our website which have a "noindex" met tag defined? Maybe it is a stupid question we shouldn't worry about, but any thoughts about this scenario are very welcome! Thank you in advance.0 -
Multilingual sites: Canonical and Alternate tag implementation question
Hello, I would like some clarification about the correct implementation of the rel="alternate" tag and the canonical tag. The example given at http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077 recommends implementing the canonical tag on all region specific sub-domains, and have it point to the www version of the website Here's the example given by Google. My question is the following. Would this technique also apply if I have region specific sites site local TLD. In other words, if I have www.example.com, www.example.co.uk, www.example.ca – all with the same content in English, but prices and delivery options tailored for US, UK and Canada residents, should I go ahead and implement the canonical tag and alternate tag as follows: I am a bit concerned about canonicalizing an entire local TLD to the .com site.
Intermediate & Advanced SEO | | Amiee0 -
Index.php canonical/dup issues
Hello my fellow SEOs! I would LOVE some additional insight/opinions on the following... I have a client who is an industry leader, big site, ranks for many competitive phrases, blah blah..you get the picture. However, they have a big dup content/canonical issue. Most pages resolve with and without the /index.php at the end of the URL. Obviously this is a dup content issue but more importantly they SEs sometimes serve an "index.php" version of the page, sometimes they don't, and it is constantly changing which version it serves and the rank goes up and down. Now, I've instructed them that we are going to need to write a sitewide redirect to attempt a uniform structure. Most people would say, redirect to the non index.php version buttttt 1. The index.php pages consistently outperforms the non index.php versions, except the homepage. 2. The client really would prefer to have the "index.php" at the end of the URL The homepage performs extremely well for a lot of competitive phrases. I'd like to redirect all pages to the "index.php" version except the homepage and I'm thinking that if I redirect all pages EXCEPT the homepage to the index.php version, it could cause some unforeseen issues. I can not use rel=canonical because they have many different versions of the their pages with different country codes in the URL..example, if I make the US version canonical, it will hurt the pages trying to rank with a fr URL, de URL, (where fr/de are country codes in the URL depending where the user is, it serves the correct version). Any advice would be GREATLY appreciated. Thanks in advance! Mike
Intermediate & Advanced SEO | | MikeCoughlin0