When you setup a Custom Domain, the setup wizard provides encouraging advice
Blogger accomplishes this bit of trickery, using standard Internet protocol - a 301 Redirect, which equates "mydomain.com" to "myblog.blogspot.com". The redirect is setup only after you setup a "CNAME" referral, pointing "mydomain.com" to "ghs.google.com". This means that anybody viewing "myblog.blogspot.com" gets "mydomain.com", published to a Google server and indexed through "ghs.google.com". And anyone viewing "mydomain.com", intentionally, gets it directly from the Google server, as indexed through "ghs.google.com".
Recently, however, hackers and spammers have started to setup their blog "myspammyblog.blogspot.com", publish that to a custom domain, then redirect the custom domain not to "ghs.google.com", but to "DNS.myhackingcampaign.com". The reader viewing "myspammyblog.blogspot.com", now gets "myhackingwebsite.com", indexed by "DNS.myhackingcampaign.com".
Blogger is looking for cases of this deviousness. Unfortunately, right now, they are looking too casually, and are seeing false positives. Legitimate blogs, that are genuinely published to a Google Custom Domain, are showing an alarming notice.
This isn't good for your readers.
This isn't good for your readers either.
Who wants to be warned that they will shortly be viewing an untrusted blog?
If you have an established custom domain, it's likely that everybody looking at your blog is using the custom domain URL, in my above example "martinezumc.org", and nobody sees this alert in any great number. If you just setup your custom domain, though, and are now seeing this, you're probably suffering two problems.
>> Top
We won't leave your readers behind!
http://myblog.blogspot.com will redirect to your custom domain.
Blogger accomplishes this bit of trickery, using standard Internet protocol - a 301 Redirect, which equates "mydomain.com" to "myblog.blogspot.com". The redirect is setup only after you setup a "CNAME" referral, pointing "mydomain.com" to "ghs.google.com". This means that anybody viewing "myblog.blogspot.com" gets "mydomain.com", published to a Google server and indexed through "ghs.google.com". And anyone viewing "mydomain.com", intentionally, gets it directly from the Google server, as indexed through "ghs.google.com".
Recently, however, hackers and spammers have started to setup their blog "myspammyblog.blogspot.com", publish that to a custom domain, then redirect the custom domain not to "ghs.google.com", but to "DNS.myhackingcampaign.com". The reader viewing "myspammyblog.blogspot.com", now gets "myhackingwebsite.com", indexed by "DNS.myhackingcampaign.com".
Blogger is looking for cases of this deviousness. Unfortunately, right now, they are looking too casually, and are seeing false positives. Legitimate blogs, that are genuinely published to a Google Custom Domain, are showing an alarming notice.
This isn't good for your readers.
This isn't good for your readers either.
Who wants to be warned that they will shortly be viewing an untrusted blog?
This blog is not hosted by Blogger and has not been checked for spam, viruses and other forms of malware.Visions of hacking abound in the minds of the readers seeing this.
If you have an established custom domain, it's likely that everybody looking at your blog is using the custom domain URL, in my above example "martinezumc.org", and nobody sees this alert in any great number. If you just setup your custom domain, though, and are now seeing this, you're probably suffering two problems.
- Your readers are a bit confused, if they use "myblog.blogspot.com".
- The search engine spiders aren't going to index your blog, as either "myblog.blogspot.com", or as "mydomain.com".
>> Top
Comments
I'd like to think that they were aware of the problem earlier, but maybe not...
what do i do?
i had started a thread
http://groups.google.com/group/blogger-help-publishing/browse_thread/thread/dd1d1ce4d74ef483
after that it was okey. but from few days it stated again to rediret problem.
We'll only be able to fix your problem once the overall problem is fixed.
If your problem continues, after Blogger fixes the problem described here, then we'll work on your problem. Be patient, you'll gain nothing from restating the issue.
People are out of luck because most bloggers, when they sign on to the idea of having a shiny feature like a non-BlogSpot URL for their blog, really don't want to go back to BlogSpot, even temporarily. Some bloggers have even given out the custom URL to friends, before experiencing the problem.
Playing ping pong with the URL won't help with search engine relationships, either. You need a consistent presence, to build up a reputation on the Internet.
Thanks for your help, both here and in the Blogger Help Group.
I moved a client's blog to a sub-folder on their site last week (FTP publishing), and their blog visitors immediately dropped 95%. I'm sure a big part of it is the IE "The page cannot be displayed" error.
Obviously, with spammers and hackers abusing the redirects, this will be a difficult problem for Google to tackle.
Do you know if they are doing any kind of manual verification on these redirects?
(Not that that may be worth anything, because people can just do another redirect once verified.)
I'd reported the issue to Google last week, but no response -- I didn't even get a "We've received your msg" auto-reply. Do you think it would be worth it to submit another report?
Thanks,
John