Skip to main content

Your Google Apps Account, And The New Google Login

In the not so distant past, explaining how to login to Google Apps was a painfully tedious process.

If I wanted to login to the Google Apps account for this domain, "", I would construct a URL in the browser address window (or use a bookmark)
The URL for your domain would be different - and explaining the difference was frequently a nuisance, in the login sequence instructions.

When explaining how to login to a recently created limited access Apps account, I would focus on the account reset process.
For this domain, "", I would access the account reset wizard as
or possibly
Again, your URLs would differ. Maintaining separate bookmarks, for each different domain, was a time sink.

With the new Google Apps integrated account login, all of that has changed.

If possible, use two browsers - 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.

To reset login to the limited access Google Apps account for this domain, you simply go to the standard Google login screen, using the second browser.
You then click on "Need help?". On the next screen, select "I don't know my password", and enter the limited access Google Apps account name, for your domain.

For my domain, if it had been purchased after November 2012, the default account name would be the limited access "". 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.

Enter the appropriate account name, click "Continue", and follow instructions.

Click on "Need help?".

Select "I don't know my password".

Enter your limited access Google Apps account name.
After you submit the password reset request, Google will send a password reset email message, to the backup email account associated with the domain. The email account, for a new Apps account, should be the email account used by the Blogger account, under which you purchased the domain.

The only problem which you can have is if the necessary email account can't be accessed.In either case, without access to the right email account, you won't be able to reset the Google Apps account password - and you won't be able to gain / regain access to your Google Apps domain administrator account, aka the "Admin Console", for the domain in question.

Other than that one possible problem, it should be a straightforward process.
  1. Access the new Google 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.
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.

If you're logging into Apps for a second time, and you remember the account name and password, it's simpler still. Access the new Google Login screen, enter the domain administrator account name and password, and login. Now, Google Apps is just one more Google application - but with its own unique account name.

If you remember the domain admin account name and password from last time, just login - and you're there.

Again, always open Google Apps in a second browser.

Other than the need to use a second browser, logging into Google Apps is now a series of bookmarks and simple scripts.

In some cases, you may not be able to use the limited option account reset sequence. Don't panic! Google also provides an expanded option administrative account reset process, for these situations! As an alternative, try Google Help: Domain Registration through Blogger.

>> Top


Biffybeans said…
Any clue on what to do if my bloggeradmin account has been deleted? I bought a domain a few years ago but I guess I never set it up and now I don't know how to access it....
Chuck Croll said…

If you bought the domain a few years ago, you'll need the Google Apps access token, found in the Google Apps email - or the Google Wallet transaction - from when you bought the domain.
La said…
So.. I also ignored (i.e., deleted/lost) the fateful email from google-apps the day I bought my domain and now my email address associated with my domain has been long deleted, i.e., same problem as biffy, above.

My domain is set to expire on December 26th.. am I SOL?

Chuck Croll said…

Check your Google Wallet for the domain purchase.

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: