Skip to main content

Country Code Based Aliases Will Interfere With Filters

As the Country Code TLD aliases, for blogs published to "", become more and more noticed, incidental problems are being reported.

For people who are security minded, as well as people who are conscientious about what is permitted on their personal computer, a few domain based filter related problems should be obvious.
Where are the pencil / tool icons on my blog?
Why can't my readers comment on my blog?
are just a couple examples of the various questions being seen in Blogger Help Forum: Something Is Broken, since the CC TLD aliases went into effect last week.

As with any layered security feature on our computers, local country domains affect our blogs in several ways.

  • Content filtering.
  • Cookie filtering.
  • Script filtering.

These are all concerns, for both the blog owners, the blog readers, and of course Blogger Support.

Any filter, which permits cookies and / or scripts from "", needs to be checked - and to permit cookies and to permit scripts from the country local domain, that's relevant to the location of the computer being used. Note that with computers located near international borders, the owners may need to consider the country local domain for the countries on either side of the border.

  • "" - if the computer receives service in Australia.
  • "" - if the computer receives service in India.
  • "" / "" - if the computer is located in northern / southern USA (or Canada / Mexico).
  • Any future added CC TLD alias - if the computer receives service in the relevant country.

The blog owner, and the computer owner, must accept responsibility for filters.

As always, I will ask you to remember that Blogger Support cannot support the filters affecting your personal computer. Both blog owners, and blog readers, have to check all filters in their browsers, their computers and their networks.

Any local filters are the responsibility of the "owner" of the computer in use - whether the "owner" is the blog owner, the blog reader, or someone supporting the blog owner or reader. There are several problems, reported periodically.

All of these issues are related, in some way, to domain based cookie and / or script filters. And all of these issues, when reported, involve personal use of a computer - and can't be exclusively resolved by contacting Blogger / Google Support.

Some of the above problems, like a similar issue with custom domain publishing, may be seen on any computer used by the blog owner - or by any blog reader.

There may be workarounds, depending upon the actual problem.

If you are a blog owner, and the redirection is causing you problems, it's possible that you could work around the problem, by using the "No Country Redirect" modifier - if use of the "/ncr" modifier does not cause secondary problems, like language used.

If I had a problem with my blog, published as "", I could access it as "" in any country subject to the CC based redirect, by using the URL "". This is, unfortunately, not likely to help our readers with their problems.

Please, don't be misled by advice to use clever JavaScript based redirection of blog traffic, to the "/ncr" alias, as an alternative to Country Code alias redirection. Clever solutions will not work well for you, in the long run.


Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: