Showing posts with label Canonical URL. Show all posts
Showing posts with label Canonical URL. Show all posts

Tuesday, March 8, 2016

Train Security Products, And Keep Your Blog Clean

Everybody who uses a computer - and expects to use their computer for any amount of time - has one or more protective products on their computer.

Anybody who publishes a blog, with an audience that has any need for security, is going to receive occasional reports from would be readers.

I can't read your blog! My computer displays an "Unsafe website!" warning!

All computer security products, unfortunately, will occasionally generate false positives. Analysing false positive malware reports is as much a part of every security product, as identifying the actual malware.

If you publish a blog, you need to know how to handle reader malware alert reports.

Know online tools, for researching reported problems.

Google provides 2 websites, for analysis of blog / website malware alerts. Both Google SafeBrowsing, and VirusTotal, are Google products that can help to identify actual problems with blogs and websites.

Besides the two Google products above, I use 3 security analysis websites, which can identify specific security problems in blog / website code. Quttera Online Website Malware Scanner, and Sucuri SiteCheck, and Trend Micro SIte Safety Center, have been useful at various times, when a security problem is reported.

You may, from time to time, use all of these - and possibly others - in identifying and verifying a security problem with your blog, or with blogs and websites that you link. For best results, always specify the canonical blog URL, when requesting security analysis - and when sharing the blog, or individual posts.


Specify the canonical URL.




Not a country local domain.



Know what you need to do, to keep your blog healthy.

As a blog publisher, you will occasionally have 2 jobs to do, when receiving a malware alert report which references your blog.

  1. Verify / identify / remove any actual malicious content.
  2. Report false positives, to the protective service displaying a false positive.


Everybody who publishes a blog, with any reader audience, has seen this advice, or something similar, when surfing their blog.



Know how to keep your blog clean - and your reputation clean.

You have to use online malware analysis services, to identify any problem which you may have created, by installing the latest "gotta have this!" accessory on your blog. And, you have to report any false positive alert, to the owners of any security product, that falsely identifies your blog as a problem.

You do both, to support your readers. You do not want your readers computers hacked, through your inappropriately accessorising your blog - but at the same time,you want your readers to be able to read your blog.

  1. Keep your blog content clean.
  2. Keep your blog reputation clean.

Do both - or you may not have readers, to read your blog.



Any #Blogger blog owner needs to support the blog readers, by publishing a blog clean of any malware, and with a good reputation with the various security products that prevent malicious action by dangerous blogs and websites. Your readers need the ability to use their computers to read your blog - and they need their security to not falsely identify your blog as a problem.

Tuesday, September 9, 2014

FaceBook Is Aggregating BlogSpot CC Aliases

We're seeing a few questions recently, in Blogger Help Forum: Something Is Broken, about FaceBook, and their treatment of Blogger URLs that are subject to local country domain redirection.
When I share a post on FaceBook, the URL used for my blog ends with "blogspot.in" instead of "blogspot.com".
Some people in Europe observe a variation.
When I share a post on FaceBook, the URL used for my blog ends with "blogspot.nl" instead of "blogspot.com".

We've been observing, for a long time, that FaceBook and other Internet services should start using the canonical tag - and aggregate BlogSpot URLs, that are subject to local country domain redirection.

With aggregation done properly, all BlogSpot URLs would be listed as "blogspot.com" - and all Likes, and similar references to a given Blogger blog, would be later counted under the proper "blogspot.com" URL - regardless where a given blog reader gets Internet access.

Apparently, FaceBook is now aggregating BlogSpot URLs - but they are not successfully using the canonical URL, as provided by the tag in the blog header. FaceBook now uses "blogspot.in" - or maybe "blogspot.nl" or "blogspot.pe" - as the final URL for some Blogger blogs, when shared.

If you share your blog to FaceBook and observe this problem, try using the FaceBook Sharing Debugger. Select "Scrape Again", when you see "blogspot.pe", or another alias, in the debugger log.

Selecting "Scrape Again", enough times, may lead to the Debugger displaying "blogspot.com" - and your actual canonical blog URL will be cached. This will provide a work around until FaceBook corrects their sharing feature.

When Blogger first started using local country domain redirection, only Google services such as Google Search would reliably aggregate all local country domain references, to "blogspot.com".

Many non Google services did not use canonical aggregation, immediately. Like every other newly developed Internet feature, it takes time for every web service to update their code.

With only Google using canonical aggregation, every Blogger URL subject to country code alias redirection would be shared using the country domain, as seen by the person doing the sharing. People in France might share a Blogger URL as "blogspot.fr", people in India as "blogspot.in", and so on.

People in the USA, of course, would share a Blogger URL as "blogspot.com". The USA, and various other countries, is not subject to country code alias redirection.

FaceBook is now aggregating BlogSpot URLs - but they are not using the canonical tag, in the blog header. They are aggregating to "blogspot.in", "blogspot.nl", or "blogspot.pe" for some or all BlogSpot URLs, shared to their service.

Maybe, FaceBook is resolving "blogspot.com" from various countries that are subject to local country domain redirection - and generates the redirection themselves?



Right now, for some blog owners who share a BlogSpot URL to FaceBook, the URL will be modified, to "blogspot.in", "blogspot.nl", or "blogspot.pe". Every Like, and similar activity against that URL, will then be counted under the "blogspot.in", "blogspot.nl", or "blogspot.pe" alias. This is probably slightly better than having every different URL shared by country code alias - but only slightly better.

Blogger blogs published to custom domains are not subject to URL modification, because custom domain URLs are not subject to local country domain redirection.

Some Blogger blogs will continue to appear to have at 3 URLs - "blogspot.com", "blogspot.in", "blogspot.nl", or "blogspot.pe", and any others under which FaceBook was sharing, originally. The search engines may index blog content, accessed from FaceBook shares, as "blogspot.com", "blogspot.in", "blogspot.nl", or "blogspot.pe".

If this is not acceptable, you may need to report this to FaceBook Support. Please, resist the temptation to install malicious code on your blog, that will later leave you asking for advice on having the blog unlocked, cleaned and reviewed.



https://productforums.google.com/d/topic/blogger/2UXBv3Q21YY/discussion

Saturday, February 25, 2012

Search Engines, Visitor Logs, And Country Domains

Some blog owners are seeing the recently added Country Code Top Level Domain Aliases in their visitor logs / meters, and various non Google search engines.

Possibly unaware of the aliases, they are afraid that their blog has been hacked.
My SiteMeter logs show that I've had incoming traffic from "mybloggerblog.blogspot.in". Clicking on one of the links in SiteMeter, I see my blog, "mybloggerblog.blogspot.com". Has somebody cloned my blog?
In reality, the scenario is not so ominous.

Those of us aware of the CC aliases, and how they are being used by Blogger, will understand that simply seeing a non canonical alias in our referer lists, in any search engine or visitor log / meter, is not an indication of malicious activity.

People unfamiliar with the country code aliases may be confused.

People long used to seeing only "blogspot.com" and "google.com", and not yet experienced with the CC aliases, may become confused, however. Blogger blogs owners with long established blogs that have audiences outside the USA are probably used to seeing all references to their blogs based on the canonical URL, such as "mybloggerblog.blogspot.com".

Now that BlogSpot published blogs are being served using the CC aliases, in many countries outside the USA, the readers of BlogSpot published blogs are seeing each blog under non "blogspot.com" URLs in some search engines, and in many visitor logs and meters.

Many search engines will aggregate search references, to the canonical URL.

Most major search engines, which reference the "canonical" tag in the blog header, are aggregating all SERP entries to use the "blogspot.com" URLs. Our important search reputation is not being fragmented, such that readers in Australia provide reputation to "blogspot.com.au", readers in India provide reputation to "blogspot.in", readers in New Zealand provide reputation to "blogspot.co.nz", and so on.

Every hit, from every reader in every country, still provides reputation to the canonical alias, "blogspot.com".

Some specialised search engines like Alexa, DMOZ, etc - and most visitor logs like SiteMeter, StatCounter, and Stats, may not be designed to reference the canonical tag. It's also possible that visitor logs, by their nature, should not aggregate CC aliases to the canonical URL - as the country code, relevant to the individual readers, may be important to some blog owners.

Until the canonical tag is used by every Internet service, there will be confusion.

Until the use of the canonical tag, and the CC aliases to our readers, becomes mature, it's possible that we will see various oddities like a perceived problem with Alexa, SiteMeter, or StatCounter. It's likely that not all Internet services will ever reference the canonical tag consistently, and aggregate all statistics and visitor demographics, canonically.

Given the latter probability, this may be yet one more reason why Blogger Help Forum: Something Is Broken may never go out of business.



Some Confusion Over Use Of The CC TLD Aliases, By Search Engines And Visitor Logs
http://blogging.nitecruzr.net/2012/02/some-confusion-over-use-of-cc-tld.html

Search Engines And Visitor Logs, And The Country Specific Domains
Search Engines, Visitor Logs, And Country Domains
http://blogging.nitecruzr.net/2012/02/search-engines-visitor-logs-and-country.html

Tuesday, January 31, 2012

What's The Canonical URL Of My Blog?

This blog is (for those of you not familiar with it) "The Real Blogger Status".

The URL of this blog is currently "http://blogging.nitecruzr.net". As long as I publish the blog properly (as "blogging.nitecruzr.net"), I am allowed to advertise the blog using any combination of lower case and upper case letters, that I like. This blog can be accessed as "blogging.nitecruzr.net", "Blogging.Nitecruzr.Net", or even "BlOgGiNg.nitecruzr.net". We say that Blogger URLs are case insensitive.

Even with my readers allowed to use any combination of lower and uppercase letters, to access this blog, I don't want the search engines to index (and determine page rank) my blog using the exact URLs, as typed by each different reader. Even with this blog being addressed as "blogging.nitecruzr.net", "Blogging.Nitecruzr.Net", or even "BlOgGiNg.nitecruzr.net", the search engines index this blog as "blogging.nitecruzr.net".

To help this happen, Blogger uses the "canonical" tag, in the blog header.

The "canonical" tag is not unique to Google.

The "canonical" tag is a cooperative standard.

It was developed as a standard in 2009, jointly, by Google, Microsoft, and Yahoo.

Every Blogger blog, which has a standard and up to date header, contains a "canonical" tag.

A Blogger "canonical" tag is used to convert the blog URL to lowercase characters.

The "canonical" tag provides the base URL of the blog, in all lower case letters, so the search engines know how to ignore various syntax variations.


All links are indexed under one unified URL, providing better SERP positioning, and more search engine generated traffic.

Look at the source for this blog home page, in the header. Note that you have to look at the online "source code" - not at the raw HTML, using the Template Editor!

Here's an excerpt of the header for this blog, with a few line breaks added - and some lines removed - to make it more readable.

<head>
<meta content='IE=EmulateIE7' http-equiv='X-UA-Compatible'/>
<meta content='width=1100' name='viewport'/>

...

<link href='http://blogging.nitecruzr.net/favicon.ico'
rel='icon' type='image/x-icon'/>
<link href='http://blogging.nitecruzr.net/' rel='canonical'/>
<link rel="alternate" type="application/atom+xml"
title="The Real Blogger Status - Atom"
href="http://blogging.nitecruzr.net/feeds/posts/default" />
<link rel="alternate" type="application/rss+xml"
title="The Real Blogger Status - RSS"
href="http://blogging.nitecruzr.net/feeds/posts/default?alt=rss" />
<link rel="service.post" type="application/atom+xml"
title="The Real Blogger Status - Atom"
href="http://www.blogger.com/feeds/24069595/posts/default" />
<link rel="EditURI" type="application/rsd+xml"
title="RSD" href="http://www.blogger.com/rsd.g?blogID=24069595" />
<link rel="openid.server" href="http://www.blogger.com/openid-server.g" />

There it is.

<link href='http://blogging.nitecruzr.net/' rel='canonical'/>

My test blog, "Nitecruzr New Template Laboratory", is still published to "nitecruzrtestnew.blogspot.com".

<link href='http://nitecruzrtestnew.blogspot.com/' rel='canonical'/>

The "canonical" tag is essential for the country code domains.

These records are essential, for blogs published to "blogspot.com", now that Blogger is aliasing our blogs using country code TLD URLs.

My test blog, for instance, published to "nitecruzrtestnew.blogspot.com", will be accessed as "nitecruzrtestnew.blogspot.in" in India - but the search engines, which observe the Canonical tag, will still index any links as "nitecruzrtestnew.blogspot.com".

Navigate» Become author for this Blog