Verify your Google + page to get more exposure in search results

I spotted an interesting post in the AdSense blog just now.

It's actually been deleted from the blog (probably because it was supposed to be posted on the Google+ blog, not the AdSense one), but the original feed content is still available, for now, at http://feedproxy.google.com/~r/blogspot/tuAm/~3/30qIWIcbTMk/social-fridays-gain-visibility-by.html

According to the feed, it's all about verifying Google + pages, ie making an official link between a page and a website.   They say

Verifying your +page confirms that the +page actually belongs to you. Once your +page is verified, it�ll appear with a checkmark designed to help our users find what they�re looking for.
and

Verified +pages that are popular and engaging may appear on the right side of relevant Google.com search results, for users who are logged in. .... Please keep in mind that to be eligible, the +page also needs to be active with regularly-updated content

To verify your page, you need to

1. Link your +page to your website: Fill out the �About� section of your Google+ page, being sure to enter your site�s top-level URL.
2. Link your website to your +page: Add a Google+ badge or code snippet to your site, ...
3. Complete ... [the]  verification request form.
4. ... continue posting regularly to your +page ....

The verification form, at http://support.google.com/plus/bin/request.py?hl=en&contact_type=page_verification&rd=1 states the conditions a little differently (boldness mine);

• Your Google+ page must be authorized by your commercial entity, organization, brand, or product.
• Your Google+ page�s profile must contain a link to your organization�s website.
• Your organization�s website must connect to your Google+ page, by adding the Google+ badge or by adding a snippet of code.
• A meaningful number of people must have added your Google+ page to their circles.

This will be simple enough for most of my sites - I own the website and the G+ page.   Though it should be a little more challenging for one or two community groups that I do things for, where the ownership is a little ore "vague".

My only decision is whether to start the verification process now, or to wait for this to be announced on the right blog!

Pinterest Twitter friend notification email messages

A while ago, Pinterest removed the need to request an invitation to sign up:  you can now go to www.Pinterest.com and register immediately.

It now looks like there are three options for signing up:

• Using your Facebook account
• Using your Twitter account
• Using an email address.

(However I can't confirm that the email address works or not - it didn't the last time I tried.)


Now, if you sign up via Twitter, there'a a question at the end of the registration process about whether you want your Twitter followers to be notified that you've joined Pinterest.  I'm pretty sure that this wasn't there the last time I signed up for a Pinterest account using a Twitter account.   But I ticked it - expecting that people might get some type of notification inside Pinterest.

However what actually happens is that an email message is sent to the email account of any Twitter followers who are already on Pinterest, telling them that you have just joined and inviting them to "make you welcome" - presumably by following you on Pinterest too.

The message reads

"Hi <<recipient's Twitter account name>>
Your Twitter friend <<your Twitter account name>> just joined Pinterest.   Help welcome <<your Pinterest account name>> to the community."

I'm fairly sure that the message is only sent to Twitter followers who are already registered in Pinterest themselves - not all your Twitter followers.

But I was a little surprised by this.

Sending an email is a little more invasive than I'd expected (and maybe shows that Pinterest is looking to do things with the linking data it collected when forcing us to sign up via our existing Twitter or Facebook accounts)####

Really I don't expect my Twitter followers to be following me on Pinterest.   I'm looking for a different target audience on Pinterest, not more of the same people who are following me already.  

And I'm a little worried that Twitter followers might think I've spammed them by telling them that I've joined Pinterest.

Google Blogger / Apps access to country-specific domains

Today, Google Apps announced that we can now purchase a wider range of global and country-specific domains through them - previously they only offered a more limited set of the global domains. And now they're cheaper, too: domains registration is $8/year instead if $10.

To do this, they've partnered with a new-to-them domain registrar http://www.domaindiscount24.com - instead of eNom and GoDaddy, who they used before

If you buy a domain via Google Apps, and DomainDiscount24.com is the registrar, then

• It comes pre-set up to work with Google's tools (mail, apps, sites, etc)
• You need to use DomainDiscount24.com's administration tools if you want to make any changes to the domain set-up
• You continue to use Google Apps domain management tools to manage the Google Services that are available to users in the domain (eg enabling/disabling Blogger)

Can we use one of these domains for Blogger?

I'd guess so: I'm pretty sure that Sites, like Blogger, requires that the domain-registrar provide DNS-hosting and the ability to edit CNAME and ANAME records.  You simply have to go through the same process that you need to use if you purchase a domain directly from any registrar.

(I'm going to test this very soon, there's a .co.nz domain that I've been thinking about for a while>

Will they work automatically with Blogger?

Not always: domain setup is a complex thing, and it's hard to predict if you will get the dreaded "Another blog is already hosted as this address" message:  I've purchased a domain via Google Apps before and and it work perfectly with Blogger - and I've had just the opposite experience, too.

If you get stuck, try either

• Use the information in this recent article from Chuck at Nitecruzr (he's one of the best for resolving custom domain issues)
• Going to the Blogger Product Forum: explain your problem and URL and ask the experts there to take a look.

Can we use this new registrar to buy country-specific domains inside Blogger?

Not at the moment, and - there's been no announcement from Blogger about it.

(Sideline:   I just tested it, and found that eNom is no longer offered as an option for domain-purchase under Blogger's switch-to-custom-domain track.   This means that GoDaddy, who not have a tool to make custom domain purchases easier, are now the only option inside Blogger - so I can see why Google might be looking to bring another registrar-partner on board.)

What domains are now available to purchase via Google Apps:

Global
.com    .info   .org    .net     .mobi     .biz     .name     .cc    .tv


Asia-Pacific
India: .in .co.in .org.in .net.in
New Zealand: .co.nz
Taiwan: .com.tw
Japan: .jp

Latin America
Colombia .co .com.co
Mexico:   .com.mx .mx

Europe
Belgium: .be
Switzerland: .ch
Czech Republic: .cz
Germany / Deutchland .de
Spain / Espana .es and .com.es
Republic of Montenegro: .me (though it has obvious wider appeal to English speakers!)
The Netherlands .nl
Poland .pl

Are domains for all countries available - why not?

There are still far more countries not on the list than on it.

I'm not surprised that there is no sign of Ireland (.ie) on the list -  these domains are hard to get.  I do manage one .ie site with Blogger:  the domain was obtained for a community group that doesn't have a company registration number, but which does have letterhead, a constitution and a well-connected chairman.   For it, I've found that LetsHost.ie provides the necessary domain management tools and their support people were helpful and didn't turn up their noses when I told them I was using it for a Blogger site.

Disappointing ommissions: Australia (.com.au) and England/Britain (.co.uk) - I'm not sure what the story is with these, or which registrars provide the tools needed to let you use a domain purchased from them with blogger.