<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Google&#8217;s Local Business Center Should Allow Shared Users</title>
	<atom:link href="http://www.geolocalseo.com/blog/google-maps-lbc-should-allow-shared-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.geolocalseo.com/blog/google-maps-lbc-should-allow-shared-users/</link>
	<description>In the trenches of local search</description>
	<lastBuildDate>Mon, 23 Jan 2012 22:18:58 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Keeping Control of your Local SEO Assets &#124; Search Engine People &#124; Toronto</title>
		<link>http://www.geolocalseo.com/blog/google-maps-lbc-should-allow-shared-users/comment-page-1/#comment-774</link>
		<dc:creator>Keeping Control of your Local SEO Assets &#124; Search Engine People &#124; Toronto</dc:creator>
		<pubDate>Wed, 13 Apr 2011 11:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.geolocalseo.com/blog/?p=32#comment-774</guid>
		<description>[...] create a shared user access system like that of some of its other products. I recommended that this should be a priority for Google, at the beginning of last year, but still nothing is in [...]</description>
		<content:encoded><![CDATA[<p>[...] create a shared user access system like that of some of its other products. I recommended that this should be a priority for Google, at the beginning of last year, but still nothing is in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stever</title>
		<link>http://www.geolocalseo.com/blog/google-maps-lbc-should-allow-shared-users/comment-page-1/#comment-726</link>
		<dc:creator>Stever</dc:creator>
		<pubDate>Sat, 02 Apr 2011 21:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.geolocalseo.com/blog/?p=32#comment-726</guid>
		<description>If the previous agency logs back in and happens to edit anything, then their version now takes over again. I&#039;ve also seen cases where the new account that has re-verified again ends up getting suspended while the old account the biz can&#039;t get its hands on stays active.

At the moment I don&#039;t really know what the solution is. I mean Google does not yet have a satisfactory solution to address this and that&#039;s a shame.</description>
		<content:encoded><![CDATA[<p>If the previous agency logs back in and happens to edit anything, then their version now takes over again. I&#8217;ve also seen cases where the new account that has re-verified again ends up getting suspended while the old account the biz can&#8217;t get its hands on stays active.</p>
<p>At the moment I don&#8217;t really know what the solution is. I mean Google does not yet have a satisfactory solution to address this and that&#8217;s a shame.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Portland Marketing Company</title>
		<link>http://www.geolocalseo.com/blog/google-maps-lbc-should-allow-shared-users/comment-page-1/#comment-712</link>
		<dc:creator>Portland Marketing Company</dc:creator>
		<pubDate>Fri, 01 Apr 2011 22:28:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.geolocalseo.com/blog/?p=32#comment-712</guid>
		<description>GREAT CALL HERE.  We searched for &quot;claim map listing lock out previous account&quot; because we want to claim a customer&#039;s account into a new Gmail account for them - as a responsible agency (just like Steve above us in the comments). Our concern is that the previous agency won&#039;t be locked out of that listing - and can undo any changes we implement... DOH!  What do you recommend there?</description>
		<content:encoded><![CDATA[<p>GREAT CALL HERE.  We searched for &#8220;claim map listing lock out previous account&#8221; because we want to claim a customer&#8217;s account into a new Gmail account for them &#8211; as a responsible agency (just like Steve above us in the comments). Our concern is that the previous agency won&#8217;t be locked out of that listing &#8211; and can undo any changes we implement&#8230; DOH!  What do you recommend there?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Transfering Ownership of Local Listings in Google Maps &#124; GEO Local SEO</title>
		<link>http://www.geolocalseo.com/blog/google-maps-lbc-should-allow-shared-users/comment-page-1/#comment-10</link>
		<dc:creator>Transfering Ownership of Local Listings in Google Maps &#124; GEO Local SEO</dc:creator>
		<pubDate>Thu, 07 Jan 2010 02:43:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.geolocalseo.com/blog/?p=32#comment-10</guid>
		<description>[...] I recommended that Google should be allowing shared user access in the LBC [...]</description>
		<content:encoded><![CDATA[<p>[...] I recommended that Google should be allowing shared user access in the LBC [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SearchCap: The Day In Search, January 5, 2010</title>
		<link>http://www.geolocalseo.com/blog/google-maps-lbc-should-allow-shared-users/comment-page-1/#comment-8</link>
		<dc:creator>SearchCap: The Day In Search, January 5, 2010</dc:creator>
		<pubDate>Tue, 05 Jan 2010 21:54:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.geolocalseo.com/blog/?p=32#comment-8</guid>
		<description>[...] Google LBC Accounts Should Allow Shared Users, GEO Local SEO [...]</description>
		<content:encoded><![CDATA[<p>[...] Google LBC Accounts Should Allow Shared Users, GEO Local SEO [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Shotland</title>
		<link>http://www.geolocalseo.com/blog/google-maps-lbc-should-allow-shared-users/comment-page-1/#comment-6</link>
		<dc:creator>Andrew Shotland</dc:creator>
		<pubDate>Tue, 05 Jan 2010 04:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.geolocalseo.com/blog/?p=32#comment-6</guid>
		<description>Welcome back to the jungle Stever!</description>
		<content:encoded><![CDATA[<p>Welcome back to the jungle Stever!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Scott</title>
		<link>http://www.geolocalseo.com/blog/google-maps-lbc-should-allow-shared-users/comment-page-1/#comment-5</link>
		<dc:creator>Will Scott</dc:creator>
		<pubDate>Tue, 05 Jan 2010 03:07:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.geolocalseo.com/blog/?p=32#comment-5</guid>
		<description>Steve,

Great post!

The way we deal with this is to create a new Google account and claim the listing with that. We then share the login information with our clients.

This way our clients have control. We can be kicked out if they change the password and it means that to some extent we&#039;re carrying the risk. And, we have more of a challenge in maintaining multiple IDs on behalf of our clients.

And, of course, we don&#039;t have ownership of those accounts as a switching cost.

That said, it&#039;s totally worth it. We are much more interested in a relationship based on trust than one built on manufactured control.

I&#039;m expecting great things from your new site!

Looks good,
Will</description>
		<content:encoded><![CDATA[<p>Steve,</p>
<p>Great post!</p>
<p>The way we deal with this is to create a new Google account and claim the listing with that. We then share the login information with our clients.</p>
<p>This way our clients have control. We can be kicked out if they change the password and it means that to some extent we&#8217;re carrying the risk. And, we have more of a challenge in maintaining multiple IDs on behalf of our clients.</p>
<p>And, of course, we don&#8217;t have ownership of those accounts as a switching cost.</p>
<p>That said, it&#8217;s totally worth it. We are much more interested in a relationship based on trust than one built on manufactured control.</p>
<p>I&#8217;m expecting great things from your new site!</p>
<p>Looks good,<br />
Will</p>
]]></content:encoded>
	</item>
</channel>
</rss>

