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
-
Pillar pages and blog pages
Hello, I was watching this video about pillar pages https://www.youtube.com/watch?v=Db3TpDZf_to and tried to apply it to my self but find it impossible to do (but maybe I am looking at it the wrong way). Let's say I want to rank on "Normandy bike tou"r. I created a pillar page about "Normandy bike tour" what would be the topics of the subpages boosting that pillar page. I know that it should be questions people have but in the tourism industry they don't have any, they just want us to make them dream !! I though about doing more general blog pages about things such as : Places to rent a bike in Normandy or in XYZ city ? ( related to biking) Or the landing sites in Normandy ? (not related to biking) Is it the way to do it, what do you recommend ? Thank you,
Intermediate & Advanced SEO | | seoanalytics0 -
Our client's web property recently switched over to secure pages (https) however there non secure pages (http) are still being indexed in Google. Should we request in GWMT to have the non secure pages deindexed?
Our client recently switched over to https via new SSL. They have also implemented rel canonicals for most of their internal webpages (that point to the https). However many of their non secure webpages are still being indexed by Google. We have access to their GWMT for both the secure and non secure pages.
Intermediate & Advanced SEO | | RosemaryB
Should we just let Google figure out what to do with the non secure pages? We would like to setup 301 redirects from the old non secure pages to the new secure pages, but were not sure if this is going to happen. We thought about requesting in GWMT for Google to remove the non secure pages. However we felt this was pretty drastic. Any recommendations would be much appreciated.0 -
Why extreme drop in number of pages indexed via GWMT sitemaps?
Any tips on why our GWMT Sitemaps indexed pages dropped to 27% of total submitted entries (2290 pages submitted, 622 indexed)? Already checked the obvious Test Sitemap, valid URLs etc. We had typically been at 95% of submitted getting indexed.
Intermediate & Advanced SEO | | jkinnisch0 -
De Index Section of Page?
Hey all! We're having a couple of issues with a certain section of our page that we don't want to index. Basically, our cross sells change really quickly, and big G is ranking them and linking to them even when they've long gone. Is it possible to put some kind of no index tag for a specific section of the page? See below 🙂 http://www.freestylextreme.com/uk/Home/Brands/DC-Shoe-Co-/Mens-DC-Shoe-Co-Hoodies-and-Sweaters/DC-Black-Rob-Dyrdek-Official-Sweater.aspx Thanks!
Intermediate & Advanced SEO | | elbeno0 -
Page indexed but not showing up at all in search results
I am currently working on the SEO for a roofing company. I have developed GEO targeted pages for both commercial and residential roofing (as well as attic insulation and gutters) and have hundreds of 1st page placements for the GEO targeted keywords. What is baffling me is that they are performing EXTREMELY poorly on the bigger cities, to the point of not evening showing up in the first 5 pages. I also target a page specifically for roof repair in Phoenix and it is not coming up AT ALL. This is not typically the results I get when directly targeting keywords. I'm working on implementing keyword variations as well as adding about 10 or so information pages (@ 700 words) regarding different roofing systems which I plan to cross link on the site, etc. I'm just wondering if there is a simple answer as to why the pages I want to be showing up the most are performing so poorly and what I would need to do to improve their rankings.
Intermediate & Advanced SEO | | dogstarweb0 -
HTTP Header Canonical Tags
I want to be able to add canonical tags to http headers of individual URL's using .htacess, but I can't find any examples for how to do this. The only example I found was when specifying a file: http://www.seomoz.org/blog/how-to-advanced-relcanonical-http-headers N.B. It's not possible to add regular canonical tags to the of my pages as they're dynamically generated. I was trying to add the following to the .htaccess in order to add a canonical tag in the header of the page http://frugal-father.com/is-finance-in-the-uk-too-london-centric/, but I've checked with Live HTTP headers and the canonical line isn't showing : <files "is-finance-in-the-uk-too-london-centric="" "="">Header add Link "<http: frugal-father.com="">; rel="canonical"'</http:></files> Any ideas?
Intermediate & Advanced SEO | | AndrewAkesson0 -
Is this structure valid for a canonical tag?
Working on a site, and noticed their canonical tags follow the structure: //www.domain.com/article They cited their reason for this as http://www.ietf.org/rfc/rfc3986.txt. Does anyone know if Google will recognize this as a valid canonical? Are there any issues with using this as a the canonical?
Intermediate & Advanced SEO | | nicole.healthline0 -
Scrolling Text Old School SEO and hidden index page
We have taken over a site and now find our self looking at the homepage of the site which has hidden scrolling text. A old school way of adding text without leaving loads of paragraphs. I have also removed all links to the index.htm page but somewhere visitors are still coming to this page in there droves. I am considering using a canonical url code but I would rather nip it in the bud. Would love some feedback from some other experts here is the site - http://www.radiatorcentre.com You never stop learning in seo and maybe we can all learn from this example. Thanks
Intermediate & Advanced SEO | | onlinemediadirect0