bollywood latest news

If you are trying to make your custom domain published blog work, see my guide Troubleshooting Your Custom Domain Problems.

If you want to know how to setup a custom domain properly, from the beginning - and avoid the need for Troubleshooting - read Setting Up A Custom Domain. Avoid the most basic mistakes made - read The Simplicity Of A Custom Domain Setup.

If you just setup your custom domain - and want to minimise the effects of the URL change upon your search engine relationships - read Managing The Migration.

If you're just browsing, then read on - but get a good cup of coffee first. And welcome, to Nitecruzr Dot Net.

>> Top

Of the many accessories and features in Blogger, Custom Domain Publishing is possibly the most problematic.

Looking at the Labels index in this blog, I see the Custom Domains label on 317 posts (as of 2013/11/21) - which makes it one of the most heavily labeled single topics here. There are several challenges with diagnosing and resolving a custom domain problem.

• It has various different causes.
• It leads to many different symptoms, which can easily be confused for other problems.
• Its symptoms can be chronic or intermittent- and may be immediate, or may take months to exhibit themselves.
• It may require resolution by any blog guest, by the blog owner, by Blogger Support, and / or by a third party such as the domain registrar.

---

As you read this article, click on some of the many links in the text, and read the linked articles. Please think of this article as the first chapter in a very large book - right now, a book with 317 chapters.

---

How To Use This Guide

• Always start properly, with righteous DNS addresses.
• Verify DNS addresses, using Dig. If any doubt about Dig results, compare logs from multiple Dig utilities, including a Dig against the authoritative domain server. Possibly 90% of all custom domain problems are caused, directly or indirectly, by spurious DNS addresses.
  
• If examination of multiple Dig logs shows righteous DNS addresses, look at HTTP traces against the BlogSpot and domain URLs.
  
• If neither Dig nor HTTP traces provide a definitive diagnosis, consider that you have internal database corruption.
• As you diagnose your DNS setup, only look at "A" and "CNAME" records.
• As you diagnose and / or fix the problem, do not delete the Google Apps administrative desktop account.

These are the known custom domain publishing diagnoses. Here's a brief, one line summary of the problems, which are discussed, in some detail, farther below. Click on any one, if it looks promising, to jump to the detail discussion.

• Domain Purchase Unsuccessful
• Only Name Registration Purchased, No DNS Hosting
• Domain Addresses Not Defined
• Domain Ownership Not Verified
• Non Google DNS server Part Of Configuration
• Domain Addresses Not Properly Chosen
• Domain Previously Registered, And Used In Blogger
• Domain Registration Expired
• Blog Published To Domain, Using Mixed Case URL
• Blog Published To Domain Root, With Asymmetrical DNS
• Domain Redirected To Google Ad Services, Sites, or Start Page URL
• Domain Published, Partially
• Internal Blogger Database Corruption
• The Blog And Domain Are In Transition
• All Issues May Not Be Discussed Here

Domain Purchase Unsuccessful

• The domain will not be setup. The blog may, or may not, be published to the domain.
• This will follow use of "Buy a domain".
• The primary symptoms will vary. We see both "404 Not Found", and "Another blog is already hosted at this address", fairly common for this problem.
• This will be an issue for newly purchased domains.
• It will be diagnosed by use of the WhoIs log showing "xxxxxxx.xxx appears to be available", and verified by examination of the Google Checkout logs, and bank account ledger entries.
• The blog owner generally has to correct a problem with his bank account, then repeat the purchase of the domain.

Only Name Registration Purchased, No DNS Hosting

• The domain will not be setup, nor the blog published to the domain.
• This will follow domain registration, purchased from a third party registrar.
• The primary symptom will be the query "What are the DNS servers for Google?", "I need 2 IP addresses for my domain!", or "I can only change NameServer1, NameServer2 in my domain setup!".
• This will be an issue for newly purchased domains.
• It will be diagnosed by the stated symptom, with the blogger confirming the diagnosis by checking the registrar's invoice to see what services were paid for.
• The blogger will have to arrange for DNS hosting - free or paid - but choose the right DNS hosting service. A free third party DNS hosting service may be useful, in this case.

Domain Addresses Not Defined

• The blog will not be successfully published to the domain.
• This will follow domain registration using "Buy a domain".
• The primary symptom will be "Another blog is already hosted at this address", in the Settings - Basic - Publishing display.
• This will occur for new custom domains.
• It will be diagnosed using an excerpted Dig log, for both domain URLs.
• Here, the blogger will be advised to contact Google Apps Support, for any domain purchase issues.

Domain Ownership Not Verified

• The blog will not be successfully published to the domain.
• The primary symptom will be an "Error 12" or variant (we have observed "Error 12", "Error 13", "Error 14", and "Error 32", in reported various forum topics), when using the the Settings - Basic - Publishing wizard.
• This may follow domain registration, purchased from a third party registrar, or using "Buy a domain".
• This will occur for new custom domains - as well as for mature domain being re published.
• This will be diagnosed using an excerpted Dig log, for both domain URLs. Base DNS addresses should also be verified, to ensure a righteous setup.
• The blog owner will be advised to add or verify presence of the proper domain ownership verification "CNAME". This may involve adding an updated "CNAME", and / or carefully examining the format of the "CNAME", as entered in the "Zone Edit" registrar display. Some blog owners may need to use a free third party DNS hosting service, to allow for registrars who cannot support the necessary "CNAME".

Non Google DNS server Part Of Configuration

• The blog may, or may not, be successfully published to the domain.
• This will follow domain registration, purchased from a third party registrar.
• The primary symptom may be "Another blog is already hosted at this address" (for new custom domains, in the Settings - Basic - Publishing display), or conversely "404 Not Found" (for long existing custom domains, when viewing the blog). The symptoms will be observed intermittently, when the non Google server is referenced.
• Possible secondary symptoms:
  • Blog feeds, intermittently not redirected from the native BlogSpot URL.
  • Commenting problems.
• It will be diagnosed using an excerpted Dig log, for the domain root.
• It is typically resolved by a 4 step process. For best results, follow this procedure religiously.
  1. Publish the blog back to BlogSpot.
  2. Correct the DNS addresses.
  3. Wait for the DNS latency period to expire. This is important. Failure to consider DNS latency may later lead to Internal Database Corruption. This period will vary, as a result of the TTL setting in the "A" / "CNAME" referral.
  4. Republish to the domain URL.

Domain Addresses Not Properly Chosen

• The blog may, or may not, be successfully published to the domain.
• This will follow domain registration, purchased from a third party registrar.
• The primary symptom may be "Another blog is already hosted at this address" (for new custom domains, in the Settings - Basic - Publishing display), or conversely "404 Not Found" (for long existing custom domains, when viewing the blog).
• Possible secondary symptoms:
  • Blog feeds, unreliably redirected from the native BlogSpot URL.
  • Commenting problems.
• It will be diagnosed using an excerpted Dig log, for both domain URLs.
• It is typically resolved by a 4 step process. For best results, follow this procedure religiously.
  1. Publish the blog back to BlogSpot.
  2. Correct the DNS addresses.
  3. Wait for the DNS latency period to expire. This is important. Failure to consider DNS latency may later lead to Internal Database Corruption. This period will vary, as a result of the TTL setting in the "A" / "CNAME" referral.
  4. Republish to the domain URL.

Domain Previously Registered, And Used In Blogger

• A Blogger blog was successfully published to the domain, at one time - by a different person. It is now not successfully published.
• This may follow domain registration, purchased from a third party registrar, or using "Buy a domain".
• The primary symptom will be "Another blog ...", when attempting to publish / re publish the blog to the domain.
• It will be diagnosed using an excerpted Dig log, for the BlogSpot, and both domain, URLs.
• It will be resolved using the Custom Domain Reset form - and much patience by the current domain owner.

Domain Registration Expired

• The blog was successfully published to the domain, at one time.
• This may follow domain registration, long ago purchased from a third party registrar, or using "Buy a domain".
• The primary symptom may be unexpected content, displayed by the blog. The nature of the unexpected content will vary.
  1. In most cases, and when the blog owner is lucky, the domain will be dead, or maybe display a page of ads or an "Offsite Warning" interstitial display.
  2. In rare cases, and when the blog owner is not lucky, the blog will display contents of another blog, another website, or an "Offsite Warning" interstitial display.
• It will be diagnosed using a WhoIs log, which shows expiry and last update dates, for the domain.
• There are two possible resolutions (see two primary symptoms, above, for possible variants).
  1. With the blog owner being lucky, it is in the control of the registrar. After domain registration is renewed, the problem is resolved by the 4 step process. For best results, follow this procedure religiously.
     1. Publish the blog back to BlogSpot.
     2. If necessary (and possible), contact the registrar, and renew the registration. Then, correct the DNS addresses.
     3. Wait for the DNS latency period to expire. This is important. Failure to consider DNS latency may later lead to Internal Database Corruption. This period will vary, as a result of the TTL setting in the "A" / "CNAME" referral.
     4. Republish to the domain URL.
  2. If the blog owner was not lucky, the domain may now be in the hand of an unknown party. This will be a subject for another article.

Blog Published To Domain, Using Mixed Case URL

• The blog will be successfully published to the domain, but will not be visible from either BlogSpot or domain URLs.
• This may follow domain registration, purchased from a third party registrar, or using "Buy a domain".
• The primary symptom will be a "404 Not Found", when attempting to view the blog using either the BlogSpot or domain URLs.
• This will, typically, occur for new custom domains, immediately after the end of the 3 Day Transition Period.
• It will be diagnosed using a RexSwain HTTP Trace set, starting from the BlogSpot URL.
• It is typically resolved by publishing the blog back to BlogSpot, then re publishing to the correct URL, using all lower case letters.

Blog Published To Domain Root, But Asymmetrical DNS Used

• The blog will not be successfully published to the domain.
• This may follow domain registration, purchased from a third party registrar, or using "Buy a domain" - though "Buy a domain" will be far more commonly seen.
• The primary symptom will be a "404 Not Found", when attempting to view the blog using either the BlogSpot or domain URLs - or the warning "Blogs may not be hosted at naked domains." or "Another blog or Google Site is already using this address.", when trying to publish or re publish the blog to the domain.
• This will, typically, occur for new custom domains.
• It will be diagnosed using a RexSwain HTTP Trace set, starting from the BlogSpot URL, and confirmed with a screen print of the Publishing wizard display, taken as the blog owner sees the error message in question.
• It is typically resolved by publishing to the "www" alias.

Domain Redirected To Google Ad Services, Sites, or Start Page URL

• The blog will not be successfully published to the domain.
• This may follow domain registration, purchased from a third party registrar, or using "Buy a domain".
• The primary symptom will be "Another blog is already hosted at this address", in the Settings - Basic - Publishing display.
• This will typically occur for new custom domains.
• It will be diagnosed using a RexSwain HTTP Trace, starting from either domain URL.
• It is typically resolved by deactivating or resetting the Ad Services, Sites, or Start Page service, using Google Apps.

Blog Published Partially, To The Custom Domain URL

• The blog will appear successfully published to the domain.
• This may follow domain registration, purchased from a third party registrar, or using "Buy a domain".
• The primary symptom will be "404 Not Found", when viewing the blog using one of the domain URLs - and the blog will still be published to the BlogSpot URL.
• It will be diagnosed using an excerpted Dig log, for the BlogSpot, and both domain, URLs. If each of the above diagnoses are eliminated, one by one, and "404 Not Found" is still observed, internal database corruption is the only remaining possibility.
• It is typically resolved by re publishing the blog to the domain. This symptom may mask a Service Redirect, or Internal Database Corruption.
• As you diagnose the problem, re publish the blog to the domain, and / or recycle the domain settings, please do not delete the Apps desktop account.

Internal Blogger Database Corruption

• The blog will not be successfully published to the domain.
• This may follow domain registration, purchased from a third party registrar, or using "Buy a domain".
• The primary symptom will be "Another blog or Google Site is already using this address." (or a similar phrasing), in the Settings - Basic - Publishing display.
• It will be diagnosed using an excerpted Dig log, for both domain URLs. If the above diagnoses are all eliminated, one by one, and "Another blog ..." is still observed, database corruption is the only remaining possibility.
• It is typically resolved by recycling the domain settings in Google Apps, and / or use of the Custom Domain Reset form.
• As you diagnose the problem and / or recycle the domain settings, please do not delete the Apps desktop account.

The Blog And Domain Are In Transition

• The domain will be setup - but will not redirect. The blog will be published to the domain URL.
• This will follow use of "Buy a domain".
• The primary symptom will be seen only by the owner (when properly logged in to Blogger). When clicking on the "View Blog" dashboard button / link, the owner will see an "In Transition" display.
• This will be a temporary issue, for newly purchased domains, successful purchased.
• It will be diagnosed using an excerpted Dig log, for the BlogSpot, and both domain, URLs.
• It will go away, when Transition expires, 72 to 96 hours after successful domain purchase and registration. The blog, and the domain, will then redirect properly.
• While you wait for Transition to expire, spend time reading what you will want to do, when Transition is complete.

All Issues May Not Be Yet Discussed Here
You could, occasionally, have a problem which is not diagnosed in this Guide - and in that case, please ask for help, politely, in Blogger Help Forum: Something Is Broken.

Before asking for help, you can help the helpers if you have tried some affinity diagnostics or maybe some differential diagnostics - and if you are aware that not all problems may be exclusively caused by Blogger.

---

And if it's not too late, read Setting Up A Custom Domain, before you start.

---

>> Top

We see occasional signs of naivete, in Blogger Help Forum: How Do I?, about custom domain publishing.

Can I publish to a custom domain - and still use the Blogger dashboard?

and

Can I publish to a custom domain - and keep my comments and posts?

and

Can I publish to a custom domain - and avoid TOS restrictions?

Some blog owners seem to see custom domain publishing as more than it actually is.

When you publish your blog to a non BlogSpot URL (aka custom domain), using a proper setup, your blog now has a new URL.

The BlogSpot URL continues to work - and to direct search engines bots, search query results, and visitors, to the blog.

If your blog uses Google+ Comments, you won't see the comments published to the BlogSpot URL - although the comments will still exist, and be visible, in Google+.

Some accessory gadgets will stop working, temporarily, shortly after the new URL starts working. This is an unavoidable result of the Internet address lookup infrastructure, aka DNS.

Other than those details, you'll have the same blog as before - just with an extra URL, that may be more valuable to the search engines.

• The Blogger blog will still be hosted by Blogger / Google, and will use the Blogger dashboard for maintenance and publishing.
• The blog will be served subject to Auto Pagination.
• The blog will be subject to the same content restrictions - both porn labeling, and malware / spam deletion, will be consequences of any infractions.
• The blog will be subject to the same deletion recovery restrictions.

Just as any time you change the URL of your blog, you'll face changes in external relationships, such as with your readers, and with search engines and other services. Don't do this without careful planning, and methodical execution!

For the few times when your domain fails, see my troubleshooting check list - but prevent problems best, by first setting it up properly, and by observing your own limitations.

>> Top

Occasionally in Blogger Help Forum: How Do I?, we see evidence of confusion and doubt.

Do I really need a sitemap, for my blog?

This question, when asked, may help us to design our blogs better.

WikiPedia defines a sitemap as

a list of pages of a web site accessible to crawlers or users

Classically, a sitemap is a visual index, to help the people viewing a static website, to easily identify and access a specific article in the website.

A sitemap provides an alternate index, to a non Blogger website. Most websites are static, with a hierarchically accessed, single structure. A well designed sitemap allows people and crawlers to more efficiently locate specific articles (pages or posts), in a static website.

Most Blogger blogs provide much more than a hierarchical, single, static structure. By default, a Blogger blog links its pages and posts dynamically, using several alternate indexes.

• Archives (posts listed hierarchically, by date).
• Labels (posts listed hierarchically, by topic).
• Extended main page (posts listed sequentially, by "Newer Posts" / "Older Posts").

Any blog, which provides one or more of these features, is effectively its own sitemap - for viewer access.

For crawler access, the options are simpler.

• Archives (posts listed hierarchically, by date).
• Extended main page (posts listed sequentially, by "Newer Posts" / "Older Posts").

Label searches, which use a different URL structure from the base blog design, are not used for indexing a Blogger blog.

If you look at the main page of a typical blog, you can follow the "Newer Posts" / "Older Posts" links from page to page, repeatedly - and eventually, see every post in the blog. With a new blog, with few posts, and predominantly "first visit" viewer traffic, the main page makes a passible sitemap. For an older blog, with many posts, and more "repeat" viewer traffic, the main page makes a less efficient sitemap.

For crawlers, which will generally follow a limited number of links within any single blog or website, the main page makes a still less efficient sitemap. Most blogs with any appreciable search engine reputation, however, only need new posts indexed by the crawlers - as older posts are already indexed, and remain in search engine cache.

Blogger provides a good, default gadget which serves as a sitemap, on most blogs - the Archives index. Look in the sidebar of this blog, about halfway down, for the "Contents" gadget. This is an HTML based gadget, which produces a set of hierarchical, date structured links, exhaustively enumerating each post in the blog. It's an ideal structure, for search engine bots (crawlers) to follow. If your blog includes this accessory, that's probably sufficient for indexing.

Blogs which contain one or more features can provide search engine access, organically.

• Well written, regularly published posts.
• The standard Archives gadget.
• The standard "Newer Posts" / "Older Posts" links.

Such blogs may not need a sitemap, to provide good access to both people and crawlers.

Both the Archives, Labels, and "Newer Posts" / "Older Posts" links are subject, on some blogs, to customisation. A blog with Javascript driven Archives, Labels, and / or custom pagination ("Newer Posts" / "Older Posts") gadgets may not provide easy crawler access. This also affects blogs which use dynamic templates. If you tweak your blog extensively, you may want to consider these issues.

There is one special case where a sitemap is always needed. Any time the URL of your blog is changed - whether to a new BlogSpot URL, or to a non BlogSpot custom domain - prompt re indexing, under the new URL, is a necessity to regain search engine reputation. A robust sitemap set, which directly references all posts in the blog, helps the crawlers to re index each post, under the new URL, much faster.

Other than that special case, a blog with standard, well designed, features may not actually need a sitemap.

A sitemap, setup through Google Webmaster Tools - and using the blog posts newsfeed, defined through "robots.txt" - is a simple accessory to add, and requires no ongoing maintenance. Given this reasoning, most blog owners simply setup a sitemap, and don't worry about the above issues and questions.

>> Top

In some cases, the earlier provided procedure, for accessing the limited access domain administrator account, may not work, for your Google Apps domain.

For some Google Apps domains, you will need to reset the password using the Google administrative reset. Instead of the wizard at "accounts.google.com", you may need the administrative reset wizard, at "https://admin.google.com".

A Google Apps administrative account reset uses the same set of displays, as the previously discussed limited access account reset.

When you request administrative account reset, you first try the using default account name.

For my domain, if it had been purchased after November 2012, the default account name would be "bloggeradmin@nitecruzr.net". Yours will be "bloggeradmin@yourdomainURL" - whatever "yourdomainURL" actually is.

Domains purchased before December 2012 will apparently still use a Google Apps token sent in email or linked from Google Wallet.

As previously advised, always use one browser for Blogger and other Google activity like GMail, and the second for the Google Apps session. For best results, first clear cache, cookies and sessions (yes, all 3!), and restart the second browser.

Use the same account name, as advised - just substitute the administrative reset sequence.

https://admin.google.com/

Click on "Need help?".

Select "I don't know my password".

Enter your limited access Google Apps account name.
In most cases, you will go into the expected administrative account reset sequence.

With a mature account, where you have previously setup a custom administrative account, "bloggeradmin@yourdomainURL" may not be accepted. Now, you must try an extended administrative account reset.


If the limited access account, for your domain, is not operational, don't panic.

Return to the previous screen, and select "I don't know my username".

Now, you have other details to provide.


Whether you use the standard administrative reset - or the extended administrative reset - Google will send a password reset email message, to the backup email account associated with the domain. The email account should be the one used by the Blogger account, under which you purchased the domain.

Other than the previously enumerated cases where you can't use the recovery email address, this should be a reasonably straightforward process.

1. Access the new Google Administrator Login screen.
2. Click on "Need help?".
3. Request password reset.
4. Access the right email account.
5. Open, and execute the password reset email.
6. Hopefully, you're done.
7. If necessary, return to the previous screen.
8. Select "I don't know my username".
9. Provide additional details.
10. Go to Step 3.

Once you're in the Admin Console, you can check / set the auto renewal option setting, or you can retrieve the login instructions to access the registrar's zone editor - or do whatever else you need to do.

The next time you need to access the Admin Console, try to remember the previously set account name and password. And, if you feel up to it, add recovery options to your administrator account.

>> Top

This article describes options for making link to a blog's old URL automatically point to the blog's new URL after a custom domain change.



If you have a blog made with Blogger which has a custom domain, then it's easy enough to switch this blog to use a different domain. Doing this moves both the content (posts and pages) and template (layout, structure, colour-scheme).

Often when people make this type of change, they want to set up re-directs so that if anyone clicks an external link to the old custom domain, they are re-directed to the same content on the new domain.
For example, www.old-domain.com/current-Page.html should redirect to www.new-domain.com/current-page.html.)

With many other website building tools, the .htaccess file for the site lets you set up re-directs like this. But things are little different when you use Blogger.

Your Blogspot address VS your custom domain

Your blog always has a blogspot addresss - let's call it: www.yourBlog.blogspot.com

When you publish to a custom domain, Blogger automatically handles the re-direction from www.yourBlog.blogspot.com to www.yourCustomdomain.com for you. This works at all levels, so the home page and every individual post/page are all redirected correctly.

To move your blog from from www.yourCustomDomain.com to www.newCustomDomain.com, you simply tell Blogger to

1. Stop publishing your blog to www.oldCustomDomain.com and then to
2. Start publishing it to www.newCustomDomain.com

(See Switching your blog to a different custom domain for more information about this.)

Once you have done this (and afer a little bit of transition time), Blogger handles the re-direction from www.yourBlog.blogspot.com to www.newCustomdomain.com for you - as before, this works at all levels, so the home page and every individual post/page are redirected correctly.

One point that many people mis-understand, is that after you have done this, there is no connection between Blogger and your old custom domain. You have various options (listed below) for what to do with www.oldCustomDomain.com - and you aren't limited to the features that Blogger offers. The only limits are based on what your domain registrar allows, and what tools you can (learn to) use.

Options for re-directing your old custom domain

Option 1: Registrar re-direction

Once you have stopped publishing your blog to www.yourCustomDomain.com, Blogger has no connection with it at all.

How you manage re-directions from it is totally up to the tools provided by the domain registrar. The simplest approach is to set up a "301 redirect" on the domain, which simply sends all traffic to it to another domain of your choice.

The method for setting this up depends on the tools used by your domain registrar - search their help files for terms like "301 redirect" to find out what is possible with tools.

See Using a custom domain for something other than your blog for advice about accessing your domain registrar account for the domain.

Advantages

• This is the easiest approach, and doesn't require you to make a website of any type.
• Visitors are automatically re-directed.

Disadvantages

• Depending on how the registrar's tools work, visitors may be automatically redirected to your new home page, not the the post that they specifically followed a link to.

Option 2: Another website tool

If you know how to use another website development tool that does provide access to the .htaccess file for the site, then you could make a "site" that just contains page-and-post level redirections for all your existing posts and pages.

Advantages

• This approach sends people to the exact content that they followed a link to.

Disadvantages

• It could be tedious setting this up for every post and page, if you have a lot of them at the time when you change domains.
• You need to choose and learn a very different type of website building tool to do this.

Option 3: use Blogger to make a site-level re-direction message

Make a totally new blog (eg    www.myBlogHasMoved.blogspot.com),

Publish it to your old custom domain

Give it one post that says

"www.oldCustomDomain.com has moved to www.newCustomDomain.com please update your links"

Use the Settings > Search preferences > Errors and redirections > Custom Redirect Custom Page Not Found  option to explain that your blog has moved, and send any traffic to that one post.

Advantages

• This is a simple approach, using tools that you already know.
• It will work forever (because blogspot domains don't expire).

Disadvantages

• Visitors will not be automatically redirected: the best you can do is show a link which goes to a selected post or page in your blog, which the visitor needs to click to go to the blog.
• The re-direction link is only to one specific page, not to the exact content that was linked to iniitially.  This is quite different from what many people want to achieve - blogger simply does not have that functionality.

A non-option: Blogger's custom redirect tool

Blogger has a function under Settings > Search preferences > Errors and redirections > Custom Redirects  that lets you set up custom redirects for individual pages.

However this isn't suitable when you change your custom-domain totally, because it only supports re-direction within the same blog, not to an external URL.

(And anyway, if you have a significant number of posts, it would not be practical.)

Other options?

Have you found any other ways around this? Or any good tool for setting up .htaccess redirects on a domain that you used to use for a blog?  Share your experience in the comments area below.

---

Related Articles:

Using a custom domain for something other than your blog

Linking your blog and your website.

How to make a real website using Blogger

Switching your blog to a different custom domain

SEO Basics for Bloggers

This Quick-Tip is about an issue that some people have had with their "naked" custom domain not re-directing to the www-at-the-start version, and how to fix it using a feature in your Google Apps account.

Since Blogger released their initial fix to the custom-domain mapping problem of mid-September 2012, some people have found that it's not possible to set up the custom domain so that my-domain.xxx works as well as www.my-domain.xxx does.

There is an option for this in Blogger's Settings > Publishing area.  But last night, when I set up a "subdomain" style entry for news.my-domain.xxx and directed my latest-updates blog from my-domain.blogspot.com to news.my-domain.com, found that this didn't work.
(Obviously I didn't use my-domain.com - but the principle applies.)

However today I found an approach that does seem to fix this:

1   Log in to the Google Apps domain administration account (the same one you used to set up the 2nd CNAME record - if you don't know how to get into it, some of the information here may help)

2   Go to Domain Settings > Domain Names, a

3   Sroll down to where it says:  Redirect the naked domain (http://YOUR-DOMAIN.INFO) to ... (whatever it says now)

4   Click the Change Redirect link under this.

5   Make sure that www (lower case) is entered in the field.

6   Click save.


I cannot guarantee that this will always fix the problem.   But it did for me just now, and I've seen a couple of other posters saying that it helped them too.    So I thought it was worth sharing.

This article is about how to use a domain (URL) that was purchased outside of Blogger / Google as the custom-domain for your blog.
 
Blogger and custom domains


The easiest way to give your Blogger blog a custom domain is to pick an URL that is currently available and purchase it through the Settings > Publishing  tab.   If that is s successful, all you need to do is set up an administrator account for your domain.   (Sept 2012:  this option is currently unavailable - hopefully it will be back soon.)

But sometimes the URL you want will not be available through Google / Blogger:

• Maybe it's owned by someone else
• Maybe you own it  already, because you purchased it through another domain registrar.  
• Maybe you don't have a credit-card so cannot purchase through  Google.  
• Maybe it's for a country that Blogger doesn't sell domains for (eg Ireland).

In these cases, you can't use Blogger to manage the domain.  Instead, you need to buy it another way - or get control of it if someone else already owns it.

Then after you own the domain, you need to set it up with the correct settings to work with Blogger.   To do this, you need to use the settings information that Blogger provides and the domain management tools (usually a control panel, aka CPanel) provided by your domain registrar.

If you are buying a domain from a registrar

If you need to (or already have) obtained them domain name through a domain registrar, you need to  purchase both:

• Name registration, and 
• DNS Hosting

You do not need to purchase file-hosting from them, because Blogger provides this for our blogs.

There are some registrars that don't offer domain hosting separately from other hosting packages.   In this case, it's your choice whether to use this company or to use another one.   There is no harm in purchasing file hosting that you are are not going to use - except that it's a waste of money.

If you find that your registrar doesn't offer DNS Hosting at all (unlikely) or that you don't want to pay the fee that the charge (which may be quite high if they only sell it with file hosting), then you need to transfer the domain to another registrar (which does offer DNS hosting) before you can use it for your blog.



Setting up a domain for your blog

Once you have control of the URL, follow these steps to set up your blog on it:


Go into www.Blogger.com and using the now-standard (ie post Sept 2011) interface.  


In  Settings > Basic >  Publishing > + Add a custom domain >  Switch to Custom Domain > 

1. Fill in your domain name, then
2. Click Settings instructions
3. If you are told "You have unsaved changes that will be lost.   Leave this page anyway"  (or similar) - choose OK / Leave this page.

This opens a page of instructions which contains the values you need to use in the next step.


At the top of the page, you are asked the following question.

Where would you like to host your blog?

•  On a top-level domain (www.example.com).

•  On a subdomain (foo.example.com).

If you don't understand this, just click on the top-level-domain option.   (If you do understand it, you don't need me to tell you which option to choose!)



2)    In the domain-management tool for your domain, set up the DNS records (ie CNAME and AName records), using the values from the page that is opened.

The way of setting up the domain records is different for every registrar.  You may need to read the help file, or ask the domain registrar's customer services department for help.   Or, if your domain registrar is GoDaddy, then this tool makes it especially easy.  (That said - at the moment it is not setting up the 2nd CNAME record for you - still need to do it yourself.)

You need to setup up two CNAME records.

• The first CNAME record should have your domain URL and ghs.google.com
• The values for the second CNAME record are buried in the text of the instructions page - I've underlined them in the following picture to help you find them.   (Hopefully Blogger will make this easier to read soon.)

You also need to set up four ANAME records - see further down in Google's instructions page for the values to use for these.


Wait an hour, and then go into www.Blogger.com again   (NB  you may not need to wait the full hour, but it's safer).  
NB   If you wait too long, then the 2nd CNAME combination that Google gave you will have expired, and you will have to do that step again,    So I'd suggest waiting an hour, and no more.


In Blogger, go to  Settings > Basic > Publishing > + Add a custom domain >  Switch to Custom Domain > 

• Fill in your domain name (yes, again).
• Click Save (just under the pane)

If get a message

We have not been able to verify your authority to this domain. Error 32. Please follow the settings instructions.

then you did not get the set-up in correct in your domain-registrar (or maybe you haven't waited long enough - or waited too long!)


If you do not see that message, then your re-direction was successful.   However you may need to allow a bit of time (maybe a few minutes, maybe as long as three days) for the changes to take effect.

Test whether they have been applied by typing your custom-domain into a web-browser:  you should be taken to your Blogger blog.

Ask for help if you need it:

There are many things that can go wrong when you are setting up a custom domain, and error messages like "Another blog is already hosted at this address" are quite common.

If the process described above doesn't work after three days (72 hours), or if you get an error message other than "site not found" before that,  the post a new question in the Blogger Product Forum:  Include these details:

• Your custom-domain name / URL, 
• Your blogsplot URL 
• The date andtime that you made the change (don't forget to include your timezone)
• A description of what's happening.

Some of the helpers in BPF are expert at diagnosing what's wrong and telling you how to fix the domain, and very happy to help provide you give them the information that the need to work out what's wrong. 

What if someone else owns the domain

Before you start, you need to own, or at least control, the domain.

If someone else currently owns a URL that you want to use, you need to:

• Negotiate with them, and get them to agree to transfer the domain to you
• Set up an account with a domain registrar
  (GoDaddy are the registrars that Google currently uses for Blogger users:  if you use them, you can be certain that the domain-management tools provided will do everything Blogger needs you to do.
  GoDaddy also have a tool that makes it extra easy to use one of their domains for Blogger - log in to your GoDaddy account, and go here to access it).
• Using that domain-registrar account, request that the domain is transferred to you
• Do anything else (eg make a payment) that you told the current owner that you would do (eg make a payment)
• Make sure that the current owner does whatever is needed to transfer the account to you.

Even though Blogger provides some "nice" tools that make URL management easier for "first time buyers" of custom domains, they are not a domain registrar themselves.  This means you cannot transfer a domain that was purchased through another domain registrar to Blogger / Google.   Instead, you need to follow the steps below to use the domain-name for your blog.



A note about Google Apps and Sites domains:
If you purchased a domain through Google Apps or Google Sites, then you already have control over it.

But you may need to disable sites in the account management screen before you can use the domain for your blog.

And after you have done this, you can go straight to Step 3 of the next section, because the CName and AName records are (already set up to use Google's servers.

---

Related Articles:

Setting up an administrator account for your new custom domain.

Switching your blog from one custom domain to another.

Using a custom domain that you own for something other than Blogger

Why RSS / Subscribe to Posts matters for your blog.

Putting a custom search engine on your blog

Stop malicious use of your AdSense account ID.

For Google Apps accounts, access to Blogger is controlled by the domain administrator.  This article shows why domain administrators may want to turn off Blogger access, for their domains - and describes how to enable Blogger access if required.

Blogger and Google Apps Domains

Previously I've described Google Accounts,  the difference between Google and Google Apps accounts, and the work being done to resolve conflicting accounts.  

People who have Google accounts can use Blogger by going to www.Blogger.com.   But for Google Apps account users, access to Blogger is controlled by the domain administrator.  There are reasons why domain administrators may not want their users to have Blogger.    But there may be times when it is appropriate, so this post shows how to enable Blogger access, too.

Why limit Blogger access:

• It doesn't feel like work:

Other Google products accessed with domain accounts can be set to use the domain-owner's logo.  So they look like a company tool, even though they're provided by Google.   This reminds people that they should only use the accounts to do things that are appropriate "at work".   But Blogger cannot (currently) be set up in this way - people who are using it may forget that they are using a work / organisation tool, and may be tempted to publish personal material using the account.

• Access control:

Firstly, there is currently no way to use Blogger to publish a blog that can be read by everyone using the domain, and not seen by anyone outside it.    This means that Blogger cannot be used for company businesses that should not be shared outside the company.    (The closest option in Blogger is to set up a private blog and invite people to read it - but there is a maximum of 100 invitations ever, and besides this option does open some security holes.)

• What happens when people leave

In well-managed companies, when a person leaves their domain account is deleted (perhaps after a month or two, in case they come back).    If someone has made a document or blog using domain account, and that domain account is deleted, then it's likely that the document or blog will be deleted too.   This isn't such a big deal for documents:  they can be transferred to other accounts.    But even though there is a procedure for transferring ownership of blogs, there are some items commonly found inside blogs (eg pictures, videos) that cannot be transferred given the tools that Google offer at the moment.

This article is about Google Apps:  what it is, how to access it, and what the account-names look like.   It discusses the great similarity between Google and Google Apps accounts, and looks at some of the small differences between them and how these relate to Blogger.


What is Google Apps?

Google Apps is a group of on-line applications and services that Google package together.  They are sold as a service to companies and other organisations, and people (individuals and companies/organisations) can use services on Apps for free, for up to 10 users.

You can sign up for Google Apps, using either a custom-domain that you purchased from another domain registrar, or by purchasing a domain-name (ie URL) through Google.

Also, people who purchase a custom-domain through Google / Blogger or Sites are strongly recommended to set up one Google Apps account to administer their domain with, and may create up to 10 user-accounts in the domain.  

Google Apps account-names are  groups of letters and numbers that look like an email address,  for example, Joe.bloggs@ACompany.com.

Initially Google Apps included things like:

• Docs (to replace MS Word etc)
• Spreadsheets (to replace Excel etc)   
• Presentations (to replace PowerPoint),
• Google-mail which looked and worked very much like Gmail in regular Google accounts - but was still different (to replace Outlook / Exchange) etc.
• Google Sites (for point-and-click website creation)

Today, many other software-as-a-service applications have been added to this list.

Google accounts vs Google Apps account

Initially, and until late 2010 / early 2011, a Google Apps account was NOT the same as a Google account, even though they appeared similar in many ways.  If an Apps user (even the domain Administration) wanted to use AdSense, Blogger, Picasa-web-albums, Google Maps, and some other applications from Google, then s/he needed to set up a separate Google account.

However since sometime in early 2011, Google Apps has been extended to include almost all the services that were previously available to Google accounts.   Effectively this means that now a Google Apps account is almost totally the same thing as a Google account.

To make this happen, Google had to resolve conflicting Google and Google Apps accounts.  This included asking owners of Google accounts with the same name as Google Apps accounts to choose a new name for their account.  They have also transitioned existing Google Apps accounts to Google, which has seen domain administrators get a flurry of warning emails.


Using Blogger with a Google Apps account

Today, if you have a Google Apps account, you can use it to log in to Blogger, Picasa, etc just like you did with a Google account, and you can do things like transfer blog ownership to Google Apps accounts.

The only exception is if your domain administrator has restricted your access to certain services.   For example, if your domain administrator has turned Blogger off for users in your domain, and you try to use Blogger with that account, you get a message like this:


It reads:

This service is not available
Blogger is not available for YOURDOMAIN.XXX. Learn more about Google products that you can use with YOUR-LOGIN@YOURDOMAIN.XXX.
If you are the Google Apps administrator, please read these articles to learn more about controling user access to Google Apps services and turning services on/off for certain users.
Did you use this product with a different Google Account? Sign out of your current Google Account and then sign in to the account that you want.

The only way around this is to ask your domain administrator to give access to Blogger (which they may be unwilling to do because it means giving access to all users in the domain, not just you) or to use another, different, Google account for Blogger.


Apps Security vs Blogger Security
Security restrictions that your domain administrator has set in Google Apps don't currently apply in Blogger.   For example, Google Docs may be set up so that only people in your domain (eg company) can see your documents.  But this if you create a blog in Blogger, this uses the Blogger security setting that you impose (under Settings > Permissions) - and by default it will be visible to the whole world.  This is why some domain administrators are not keen to enable Blogger for users in their domains.

(I haven't investigated, but it's likely that the same thing applies to other apps that were previously accessed via Google accounts not Google Apps accounts - eg Picasa.)

Other Google-account tools:
There are a few Google products that currently are not available using Google Apps accounts:

• Buzz
• Health
• Powermeter
• Google Profiles
  (NB  Blogger Profiles are available in the usual way via the Blogger Dashboard > Edit Profile link)

(ref:  http://www.google.com/support/accounts/bin/answer.py?answer=182213&hl=en&ctx=ch_b%2F0%2FServiceNotAllowed&p=blogger)

Again, if you want to use these applications, you need to use another, different, Google account.

Google Sites:
Some Bloggers use Google Sites, accessed with their Google account, to host files.

Currently, the Google Sites login screen that gives a choice between logging in with a Google Account, or with a Google Apps account, like this:


Despite this, if the Sites service is enabled for your domain, you can use your Google Appts account details to log in via the top, Google Account, part of the screen.  And if you choose the "Sign in with a Google Apps Account" link, the screen now asks for your email address (ie your account name), and simply puts it in the top part of the screen and asks for your password there.

---

Related Articles: 



Understanding Google accounts

Resolving conflicting Google and Google Apps accounts

Setting up your custom domain

Auto-renewing your blog's custom domain

AdSense and AdWords - understanding the difference

File hosting options

Using a "foreign" custom domain for your blog

Transferring blog ownership

What is renewing a custom domain about?

If you have purchased a custom domain (eg www.fred-fish.com), then you have the right to use that name for however long you purchased it for.   How long that is depends on the contract with the domain-registrar (ie the company that you purchased it from).

If you purchase a domain through Blogger (and thus through one of eNom or GoDaddy), the only option you have is to buy it for one year.

After the term of your contact is finished, you need to either buy it again or switch your blog to use another domain name (perhaps your old blogspot name).   And if you don't buy the domain again, someone else will be able to buy it.

If your custom domain name is important to you (and it will be if your blog is successful), then you will want to make sure that you have done the "paperwork" to re-purchase well before it's due to expire.   Your domain registrar should send you a reminder email about a month before the registration is due - but it's sometimes very easy to miss details like this.

Luckily, Google makes it easier by providing an option to automatically renew your domain each year.

Using the auto-renew option

When you first purchase a domain, one of the questions is whether to automatically renew the registration each year.   I usually answer "no" because I don't want my credit card charged with something I didn't specifically authorise.

But there are some domains that have become very important to me, and I want to be certain that they are renewed.  So I'm prepared to turn auto-renew on for them.

Follow these steps to turn domain auto-renew on:

1  Go to Google Apps   (www.google.com/apps)


2  Sign in by entering your domain name, and choosing Domain Management.


3  Log in with the administrator account that you set up when you first purchased the custom domain - remember that this may now be called bloggeradmin, if you purchased it more recently.

If you see an "Account Management" screen after logging in, then you may need to Go to Google Apps   (www.google.com/apps) again - sometimes it may take you to the wrong screen if you were logged into a regular Google account at the start.


4  Choose the Domains tab from the Admin Console.


5  Make sure that the the Automatic Renewal check-box is set to on, ie ticked (or off / unticked if you don't want to auto-renew).


6 Press Save Changes  (which only appears after you have made a change on the page)

What happens next

If the Auto-renew option is ticked, then about a month before the renewal is due Google sends you an email to remind that that it's going to occur.  

After that, at the appropriate time, Google charges the credit-card associated with your Google Apps account (ie the one you used to purchase the domain) for a one-year renewal.

The one thing that you need to do is make sure that the credit card that you have linked to the Google account is still valid.

You can find more information about Domain payments on this Google help page.

---

Related Articles

Checking the credit card that is linked to your account

Setting up an administrator for your custom domain

Transferring Blog Ownership.

Understanding Google accounts

This article is no longer current.   It was about setting up AdSense on a domain that you own, but are not using.

However this feature of AdSense was withdrawn in early 2012, so the feature is no longer available.

The information below was correct until then, but has not been update since.

What is AdSense for Domains

Sometimes, you may own a domain, but not actually want to use it for a blog-site as yet.  I'm currently working on one new blog for which I found a very appropriate, and available URL.   It won't be ready to be public for a month or more, but I've purchased the domain-name now so that someone else doesn't take it:  A lot of the design etc is based around the quirky name, and a lot of work would need to be re-done if I waited and tehn couldn't get the site-name that I want.

Or you may find you own a domain-name that doesn't actually work for what you wanted it to:  either your don't want to keep the site on-line, or people don't like the domain name.  But you still own it until the current paid period runs out.   (Don't forget to disable auto-renewal in this case.)   

An option that you have is to show paid advertisements on the domain in the meantime.   This may earn some advertising revenue - and (for domains-in-waiting) it gives an insight into the number of "natural" visitors that a domain gets without any promotion or links.  These visitors can some either through people guessing the URL, or following broken hyperlinks set up when the URL was used for something else.

If you're already signed up to be an AdSense publisher, then AdSense for Domain is an easy choice for putting advertising onto domain like this.

The Rules:

You need to check the terms and conditions:   here are the full T&C's for AdSense for Domains.

As always with AdSense, clicking your own ads isn't allowed.

But there are some extra conditions too:

You can't use it with domain URLS that are adult/sexual, promote hate, are overly rude, relate to weapons, alcohol, tobacco, illegal drugs, about other illegal things or sensitive current events, or which infringe trademarks (even if it's just with apparent typos).

Also, with AdSense for Domains, you're not allowed to promote the domain.   So when you're ready to start publicizing the URL on other websites, you need to take AdSense for Domains off it.   I'd assume that this is true even if the publicity clearly says "available next week" or similar.  

These are just some of the rules - make sure you read the full details before you get started.

Setting up AdSense for Domains:

(These instructions are based on the new - Nov 2010 - AdSense interface.  The process is very similar in the old menus, although the command names and positions may be slightly different.)

If necessary, release your custom domain from being used for a blog.

Log into AdSense with your main account.  
(For me, this is not always the one that purchased the domain, but it is always the one that paid for it via Google Checkout.   There may be some complications later on if your Google account that has AdSense wasn't the same one that paid for the domain.)

Go into the My Ads tab

Choose Domains from the left-hand menu.

Click the New Hosted Domain button, which is at the top of the list of domains.

Enter the name(s) of the domain(s) that you want to set up AdSense for Domains for  (or upload a comma-separated-values file listing them, if there are a lot).
Use the naked format, eg your-domain.com, not www.your-domain.com

Choose the language that most sense for people who might visit this domain.   (eg the domain I've parked at the moment is named with a word from the English language, so I've chosen English).



Click the Add Domains button

The system shows a pop-up box, either telling you that the domain was successfully added, or that there is a problem you need to resolve.

There will also be a message that "To begin serving ads, you must now point your domains to our servers. Follow the Domain Setup Guide to complete the setup process for each hosted domain that you have added."

If you bought your domain through Blogger (and probably through other Google products, eg Sites as well) can ignore this message to start with and close the window.

But if you purchased the domain another way (including directly from GoDaddy or eNom), you  need to read the Domain Setup Guide, and take whatever actions are recommended.

• Clicking the View the Domain Setup Guide opens it in an new window/tab (depending on your browser).   --- except that right now, it shows a message saying "We are sorry but the information that you have requested cannot be found. Please try searching or browsing the help centre".   If you get this, just search for the Domain Setup Guide using the search field on the screen.

Closing the pop-up takes you back to the My Ads > Domains listing.   There will be a new entry on the list, with status "DNS verification pending".

Under the domain-name, there are links for Details (which shows you what the DNS entries need to be), and Request verification.

After you have set up the correct DNS entries with your domain registrar  (or immediately, if you purchased via Blogger et al), click on the Request Verification link.   This sends a message to AdSense/Google, asking them to check that your domain setup is correct.

Wait:  there will be a delay (perhaps 2-3 days), while Google check that it is valid for you to display ads on this domain (remember those rules from the Terms and Conditions section - it seems that they do check), and that your DNS settings are correct.

If a problem is found, this screen will show a message about this, and tell you how to resolve it.

And once AdSense for Domains is enabled, the status changes to Active.

Testing and customizing AdSense for Domains:

Once the status is Active, test your domain by viewing it in your browser:  it should display AdSense ads.   (Remember not to click any!)

Back in the AdSense > AdSense Setup > AdSense for Domains tab, you can customise the look of the screen by selecting the domain (use the check-box to the left of the name), and choosing Actions > Edit from the menu items just above the domain list.   This lets you:

• Put the domain into a custom channel (for tracking performance)
• Edit the keywords that are used to help choose what advertisements to show
• Edit the colour-scheme of the displayed ads.

---

Related Articles:

Auto-renewing custom domains

Setting up an administrator account for your custom domain

Using a custom domain for something other than your blog

Setting up AdSense on your Blog

AdSense and AdWords - understanding the difference

Deleting Blogs and Blog-posts

Transferring Blog Ownership.