Just recently, search engines like Google and Yahoo partnered with Live Search to introduce a breakthrough improvement in the search engine playing field: the Canonical Link Element. The Canonical Link Element enables web developers and search engines alike to eliminate the confusion in searches caused by different links that basically point to the same web site. Over the past few years, search engines have been focused on making … Read the Rest
Just recently, search engines like Google and Yahoo partnered with Live Search to introduce a breakthrough improvement in the search engine playing field: the Canonical Link Element. The Canonical Link Element enables web developers and search engines alike to eliminate the confusion in searches caused by different links that basically point to the same web site. Over the past few years, search engines have been focused on making … Read the Rest
Posted by randfish
Lately I’ve been surprised to hear concerns from a number of SEOs that using the canonical URL tag on the canonical version of the page can somehow cause problems. When I’ve talked to folks about it, there seems to be confusion that only duplicates should use the rel="canonical" specification and the original must remain rel="canonical"-free. This isn’t the case.
Let’s look at a few diagrams to help explain:

This is the standard way rel=canonical is employed. Different versions of a page, whether on your own site, on partner sites, or places you’re licensing content (note: this is an update Google launched on Dec. 17th, 2009) can all reference back to the original to help tell the search engines where to find that piece. However, it’s also perfectly OK to do this:

Looking through Google’s blog post on the subject, this isn’t explicitly stated. However, you can see that even the example website, Wikia, employs this practice on the page Google points out. You can also see Googler Maile Ohye answering a comment on this:
@Wade: Yes, it’s absolutely okay to have a self-referential rel="canonical". It won’t harm the system and additionally, by including a self-reference you better ensure that your mirrors have a rel=”canonical” to you.
Maile’s got really good advice here. If you run into situations where third parties are referencing your posts and appending strings of data to the URL, it can be really helpful to have the canonical URL tag on these by default. In fact, we’ve worked with many companies recently who found it helpful to employ sitewide as a best practice, just to prevent future iterations or less SEO savvy development from reproducing versions of the page that didn’t contain the rel=canonical and potentially losing link juice / causing canonicalization issues.
One last piece – it’s a really, really good way to make sure Google indexes the http rather than https version of your page (and counts link juice to the proper one). This had historically been a royal pain in the butt for many SEOs, and we’ve heard enough positive stories now to feel confident recommending it.
Welcome to 2010! Hope everyone had a great holiday break
Posted by randfish
Lately I’ve been surprised to hear concerns from a number of SEOs that using the canonical URL tag on the canonical version of the page can somehow cause problems. When I’ve talked to folks about it, there seems to be confusion that only duplicates should use the rel="canonical" specification and the original must remain rel="canonical"-free. This isn’t the case.
Let’s look at a few diagrams to help explain:

This is the standard way rel=canonical is employed. Different versions of a page, whether on your own site, on partner sites, or places you’re licensing content (note: this is an update Google launched on Dec. 17th, 2009) can all reference back to the original to help tell the search engines where to find that piece. However, it’s also perfectly OK to do this:

Looking through Google’s blog post on the subject, this isn’t explicitly stated. However, you can see that even the example website, Wikia, employs this practice on the page Google points out. You can also see Googler Maile Ohye answering a comment on this:
@Wade: Yes, it’s absolutely okay to have a self-referential rel="canonical". It won’t harm the system and additionally, by including a self-reference you better ensure that your mirrors have a rel=”canonical” to you.
Maile’s got really good advice here. If you run into situations where third parties are referencing your posts and appending strings of data to the URL, it can be really helpful to have the canonical URL tag on these by default. In fact, we’ve worked with many companies recently who found it helpful to employ sitewide as a best practice, just to prevent future iterations or less SEO savvy development from reproducing versions of the page that didn’t contain the rel=canonical and potentially losing link juice / causing canonicalization issues.
One last piece – it’s a really, really good way to make sure Google indexes the http rather than https version of your page (and counts link juice to the proper one). This had historically been a royal pain in the butt for many SEOs, and we’ve heard enough positive stories now to feel confident recommending it.
Welcome to 2010! Hope everyone had a great holiday break
Google sent an email to many publishers yesterday, including myself, explaining a reporting issue with Google mixing up some of the earnings for link units with regular ad units. The email’s subject line read, “Update to AdSense link unit reporting” and the email read:
As a publisher using link units on your pages, we’re writing to let you know about a recently resolved reporting issue that affected your account.
We discovered an issue with the way earnings from link units were being shown in publisher accounts, which resulted in some of your ad unit earnings being incorrectly attributed to link units instead. However, this was only a reporting display issue and so your overall earnings and payments were not affected. We’ve resolved the issue, and as a result, you may now notice slight differences when you look at reports for previous months. Specifically, when you generate separate reports for link units and ad units, you may see that earnings from link units on a particular day have decreased, but that the ad unit earnings for the same day have increased by the same amount.
Again, please be assured that your aggregate earnings and payments were unaffected, so you’ve been credited for all valid clicks and impressions. In addition, this issue has not affected your ad performance in any way.
Your reports will now accurately reflect your earnings from link units and ad units — we apologize for the inconvenience and any confusion caused.
So no damage was done on the earnings side. Some publishers who may have looked closely at their reports to make tweaks to their pages may be suffering a bit, but overall, this doesn’t seem like a major deal.
AdSenseAdvisor in a WebmasterWorld thread added a bit to it:
Just to clarify, there was a link units reporting discrepancy that we recently cleared up. Aggregate earnings were not affected AT ALL. It’s just that if you go back and pull reports on your historical performance, you may notice that a lower percentage of your earnings are now attributed to link units (and a larger percentage are attributed to regular ad units).
An email went out to all those who were affected, so I’m guessing a lot of you got it.
Your aggregate earnings have been correct all along, we were just a bit off in attributing them to link units vs. regular ad units. Now we’ve cleared it up and any reports you run now will correctly reflect exactly where your earnings came from.
Forum discussion at WebmasterWorld and DigitalPoint Forums.
Google sent an email to many publishers yesterday, including myself, explaining a reporting issue with Google mixing up some of the earnings for link units with regular ad units. The email’s subject line read, “Update to AdSense link unit reporting” and the email read:
As a publisher using link units on your pages, we’re writing to let you know about a recently resolved reporting issue that affected your account.
We discovered an issue with the way earnings from link units were being shown in publisher accounts, which resulted in some of your ad unit earnings being incorrectly attributed to link units instead. However, this was only a reporting display issue and so your overall earnings and payments were not affected. We’ve resolved the issue, and as a result, you may now notice slight differences when you look at reports for previous months. Specifically, when you generate separate reports for link units and ad units, you may see that earnings from link units on a particular day have decreased, but that the ad unit earnings for the same day have increased by the same amount.
Again, please be assured that your aggregate earnings and payments were unaffected, so you’ve been credited for all valid clicks and impressions. In addition, this issue has not affected your ad performance in any way.
Your reports will now accurately reflect your earnings from link units and ad units — we apologize for the inconvenience and any confusion caused.
So no damage was done on the earnings side. Some publishers who may have looked closely at their reports to make tweaks to their pages may be suffering a bit, but overall, this doesn’t seem like a major deal.
AdSenseAdvisor in a WebmasterWorld thread added a bit to it:
Just to clarify, there was a link units reporting discrepancy that we recently cleared up. Aggregate earnings were not affected AT ALL. It’s just that if you go back and pull reports on your historical performance, you may notice that a lower percentage of your earnings are now attributed to link units (and a larger percentage are attributed to regular ad units).
An email went out to all those who were affected, so I’m guessing a lot of you got it.
Your aggregate earnings have been correct all along, we were just a bit off in attributing them to link units vs. regular ad units. Now we’ve cleared it up and any reports you run now will correctly reflect exactly where your earnings came from.
Forum discussion at WebmasterWorld and DigitalPoint Forums.
Yesterday, Google adjusted their First Click Free program and wrote about it at both the Google Webmaster Central Blog and the Google News Blog.
In the past, the first click free program allowed you to show subscription content to Google even if you required users to login. The only requirement was that when users clicked from Google to the article, they should be able to see the content without having to pay or login. After that first click from Google, you can require them to login. The only issue was that anyone wanting to see any article on a paid subscription site, would simply go to Google and click over to the article from Google to the site to get it for free.
Google adjusted their policy to allow publishers to limit the clicks to the “five free accesses per user each day.” So after five clicks, the publisher can decide to require that user to login. Google does not determine how to calculate or code the first five free accesses per user, and leaves it up to the webmaster to figure out. So that means you will have some publishers who are more lax on that rule, allowing more than five and some might allow up to five in whatever 24 hour period they decide. Do they use cookies, IPs, or something else to track that access, that is up to the webmaster/publisher.
The first click free program is old, it dates back past 2007 or further, as far as I know. In mid-2008, there was confusion if it could be used in web search as well and the ultimate decision is that is applies both to News and Web search.
For more technical details on this program, click here.
Forum discussion at Google News Help and WebmasterWorld.
Yesterday, Google adjusted their First Click Free program and wrote about it at both the Google Webmaster Central Blog and the Google News Blog.
In the past, the first click free program allowed you to show subscription content to Google even if you required users to login. The only requirement was that when users clicked from Google to the article, they should be able to see the content without having to pay or login. After that first click from Google, you can require them to login. The only issue was that anyone wanting to see any article on a paid subscription site, would simply go to Google and click over to the article from Google to the site to get it for free.
Google adjusted their policy to allow publishers to limit the clicks to the “five free accesses per user each day.” So after five clicks, the publisher can decide to require that user to login. Google does not determine how to calculate or code the first five free accesses per user, and leaves it up to the webmaster to figure out. So that means you will have some publishers who are more lax on that rule, allowing more than five and some might allow up to five in whatever 24 hour period they decide. Do they use cookies, IPs, or something else to track that access, that is up to the webmaster/publisher.
The first click free program is old, it dates back past 2007 or further, as far as I know. In mid-2008, there was confusion if it could be used in web search as well and the ultimate decision is that is applies both to News and Web search.
For more technical details on this program, click here.
Forum discussion at Google News Help and WebmasterWorld.
About two weeks ago, we reported on rumors of Sitelinks linking to the wrong site. Well, those rumors have just been confirmed by a Googler.
JohnMu in a Google Webmaster Help thread confirmed a long standing rumor where a Sitelink, can link to a third-party site, likely a competitor. John said:
This looks like something that happened long ago because of a bug on our side that’s persisted because you’re blocking the Sitelinks. Once you unblock them, they can go away on their own
. Sorry about the confusion!
So yes, there was a bug when you blocked a Sitelink that you did not want. You had to unblock them to make the Sitelink go away. Go figure.
I doubt most people will know how to do this or even think this is logical, so I do hope the bug is fixed and Google does this for all sites that are impacted.
Forum discussion at Google Webmaster Help.
About two weeks ago, we reported on rumors of Sitelinks linking to the wrong site. Well, those rumors have just been confirmed by a Googler.
JohnMu in a Sitelink, can link to a third-party site, likely a competitor. John said:
This looks like something that happened long ago because of a bug on our side that’s persisted because you’re blocking the Sitelinks. Once you unblock them, they can go away on their own
. Sorry about the confusion!
So yes, there was a bug when you blocked a Sitelink that you did not want. You had to unblock them to make the Sitelink go away. Go figure.
I doubt most people will know how to do this or even think this is logical, so I do hope the bug is fixed and Google does this for all sites that are impacted.
Forum discussion at Google Webmaster Help.
I spotted this old thread at Google Maps Help that has very useful information and yet, we have not covered it (go figure). In short, the thread goes through the possibility of having a single business listed in your Google Local Business Center console multiple times. The questions are:
(1) Do you delete the repetitive listings?
(2) If so, which ones?
(3) If not, do you make sure they are in sync with each other?
For example, I have duplicate listings, two unverified, which I am afraid to delete:
Back in March, Joel H. from the Google Maps team wrote:
The only time you want to remove the listing from Maps is when the business is permanently closed OR you never want it to appear on Maps. If there are duplicates in your account, keep them. When I initially posted, I didn’t think about the ongoing process we have to merge duplicate listings on Maps. Because we do our best to merge duplicate listings on Maps, it’s possible that selecting Remove this listing from Google Maps may actually suppress a preferred listing in the future (the process of conflating listing happens regularly). We’ll keep our eye out for duplicate, Local Business Center verified listings, and work to refine our systems to merge the right listings as soon as we can. Until then, keep the conversation going on this topic, and we’ll be happy to continue to help as best we can.
————————————————————-
In the case of differing statistics (impressions/views), they are distinct listing on Maps, and Remove this listing from Google Maps is the right option. It’s likely you’ll want to choose the listing with less impressions or views.
Forum discussion at Google Maps Help.
Update: You also 100% want to check out Mike B’s post on this.
Update 2: See Joel’s comment (he works at Google):
There’s a bit of confusion here – the ‘Delete’ link has two options:
- Remove this listing from Google Maps
- Remove this listing from my Local Business Center accountThe first option should be avoided, per the warning you quoted. The second option won’t cause a listings to be removed from Maps.
The second option won’t cause a business to be removed from Maps entirely — it will just delete it from your account. That’s the option you should use to get rid of extra copies of your business in your Local Business Center account.
So, if you ever have more than one listing for the same business in your account, choose one to keep, and go ahead and select: ‘Delete’ > ‘Remove this listing from my Local Business Center account’ for the others. In this case, keep your verified listing and delete the others.
I spotted this old thread at Google Maps Help that has very useful information and yet, we have not covered it (go figure). In short, the thread goes through the possibility of having a single business listed in your Google Local Business Center console multiple times. The questions are:
(1) Do you delete the repetitive listings?
(2) If so, which ones?
(3) If not, do you make sure they are in sync with each other?
For example, I have duplicate listings, two unverified, which I am afraid to delete:
Back in March, Joel H. from the Google Maps team wrote:
The only time you want to remove the listing from Maps is when the business is permanently closed OR you never want it to appear on Maps. If there are duplicates in your account, keep them. When I initially posted, I didn’t think about the ongoing process we have to merge duplicate listings on Maps. Because we do our best to merge duplicate listings on Maps, it’s possible that selecting Remove this listing from Google Maps may actually suppress a preferred listing in the future (the process of conflating listing happens regularly). We’ll keep our eye out for duplicate, Local Business Center verified listings, and work to refine our systems to merge the right listings as soon as we can. Until then, keep the conversation going on this topic, and we’ll be happy to continue to help as best we can.
————————————————————-
In the case of differing statistics (impressions/views), they are distinct listing on Maps, and Remove this listing from Google Maps is the right option. It’s likely you’ll want to choose the listing with less impressions or views.
Forum discussion at Google Maps Help.
Update: You also 100% want to check out Mike B’s post on this.
Update 2: See Joel’s comment (he works at Google):
There’s a bit of confusion here – the ‘Delete’ link has two options:
- Remove this listing from Google Maps
- Remove this listing from my Local Business Center accountThe first option should be avoided, per the warning you quoted. The second option won’t cause a listings to be removed from Maps.
The second option won’t cause a business to be removed from Maps entirely — it will just delete it from your account. That’s the option you should use to get rid of extra copies of your business in your Local Business Center account.
So, if you ever have more than one listing for the same business in your account, choose one to keep, and go ahead and select: ‘Delete’ > ‘Remove this listing from my Local Business Center account’ for the others. In this case, keep your verified listing and delete the others.









