<?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: Workarounds for Google Places Verification	</title>
	<atom:link href="https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/feed" rel="self" type="application/rss+xml" />
	<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html?utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
	<description>Canada&#039;s Search and Social Media Authority</description>
	<lastBuildDate>Tue, 23 Jun 2020 00:07:29 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: michael		</title>
		<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-245888</link>

		<dc:creator><![CDATA[michael]]></dc:creator>
		<pubDate>Tue, 11 Dec 2012 12:10:57 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=19673#comment-245888</guid>

					<description><![CDATA[Using the second line for address hasnt worked for me?]]></description>
			<content:encoded><![CDATA[<p>Using the second line for address hasnt worked for me?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Nyagoslav		</title>
		<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-200542</link>

		<dc:creator><![CDATA[Nyagoslav]]></dc:creator>
		<pubDate>Thu, 14 Jun 2012 13:40:20 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=19673#comment-200542</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-200344&quot;&gt;Len&lt;/a&gt;.

Yep, MapMaker is now available in Canada, and will soon be available in Australia and New Zealand, too. However, it was not at the time this article was written, which is more than 9 months ago :)]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-200344" data-wpel-link="internal">Len</a>.</p>
<p>Yep, MapMaker is now available in Canada, and will soon be available in Australia and New Zealand, too. However, it was not at the time this article was written, which is more than 9 months ago 🙂</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Len		</title>
		<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-200344</link>

		<dc:creator><![CDATA[Len]]></dc:creator>
		<pubDate>Wed, 13 Jun 2012 16:29:55 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=19673#comment-200344</guid>

					<description><![CDATA[.. in fact Google Mapmaker is available in Canada and is very effective in correct map errors.  My recommendation is to correct you map error, and then get a group of Google account holders to review &#038; verify it.  Once that&#039;s done and it&#039;s approved the Mapmaker Map will be corrected, but that does not guarantee that Google Maps will adopt the change. I only have one experience, and in my case Google Maps was changed successfully.]]></description>
			<content:encoded><![CDATA[<p>.. in fact Google Mapmaker is available in Canada and is very effective in correct map errors.  My recommendation is to correct you map error, and then get a group of Google account holders to review &amp; verify it.  Once that&#8217;s done and it&#8217;s approved the Mapmaker Map will be corrected, but that does not guarantee that Google Maps will adopt the change. I only have one experience, and in my case Google Maps was changed successfully.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ron Kilbreath		</title>
		<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-192942</link>

		<dc:creator><![CDATA[Ron Kilbreath]]></dc:creator>
		<pubDate>Fri, 11 May 2012 15:53:19 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=19673#comment-192942</guid>

					<description><![CDATA[These work-a-rounds are exactly the info I&#039;ve been looking for...I live in Canada but want to do Places in the US. I&#039;m considering using an elite proxy with a US ip in or close to my chosen city(cities). 
What&#039;s your opinion on this?]]></description>
			<content:encoded><![CDATA[<p>These work-a-rounds are exactly the info I&#8217;ve been looking for&#8230;I live in Canada but want to do Places in the US. I&#8217;m considering using an elite proxy with a US ip in or close to my chosen city(cities).<br />
What&#8217;s your opinion on this?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Matt @ Compensation Lawyers		</title>
		<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-151895</link>

		<dc:creator><![CDATA[Matt @ Compensation Lawyers]]></dc:creator>
		<pubDate>Sat, 14 Jan 2012 20:22:36 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=19673#comment-151895</guid>

					<description><![CDATA[Thanks for sharing this. I know that with several clients I have had to set up Google places for them. Since Google has taken away the phone verification opt-in things have become more than a little pain in the butt. 

This definitely help.

Thanks again]]></description>
			<content:encoded><![CDATA[<p>Thanks for sharing this. I know that with several clients I have had to set up Google places for them. Since Google has taken away the phone verification opt-in things have become more than a little pain in the butt. </p>
<p>This definitely help.</p>
<p>Thanks again</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Nyagoslav		</title>
		<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-139224</link>

		<dc:creator><![CDATA[Nyagoslav]]></dc:creator>
		<pubDate>Tue, 13 Dec 2011 14:53:42 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=19673#comment-139224</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-135060&quot;&gt;Julian&lt;/a&gt;.

Julian, here is a rule from the Google Places Quality Guidelines:

&quot;Do not create listings at locations where the business does not physically exist. P.O. Boxes are not considered accurate physical locations. Listings submitted with P.O. Box addresses will be removed.&quot;

I&#039;d suggest you warn your client about that.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-135060" data-wpel-link="internal">Julian</a>.</p>
<p>Julian, here is a rule from the Google Places Quality Guidelines:</p>
<p>&#8220;Do not create listings at locations where the business does not physically exist. P.O. Boxes are not considered accurate physical locations. Listings submitted with P.O. Box addresses will be removed.&#8221;</p>
<p>I&#8217;d suggest you warn your client about that.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Julian		</title>
		<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-135060</link>

		<dc:creator><![CDATA[Julian]]></dc:creator>
		<pubDate>Fri, 02 Dec 2011 06:50:53 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=19673#comment-135060</guid>

					<description><![CDATA[Thanks for the PO box work around.  I have had a night mare trying to get a client who uses a virtual office verified.  Hoping I can just get it to work with the same method.]]></description>
			<content:encoded><![CDATA[<p>Thanks for the PO box work around.  I have had a night mare trying to get a client who uses a virtual office verified.  Hoping I can just get it to work with the same method.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Nyagoslav		</title>
		<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-134288</link>

		<dc:creator><![CDATA[Nyagoslav]]></dc:creator>
		<pubDate>Wed, 30 Nov 2011 14:14:12 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=19673#comment-134288</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-126382&quot;&gt;Susan Walsh&lt;/a&gt;.

Hi Susan,

In this case I&#039;d suggest that you get use of point 3 in the article :)]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-126382" data-wpel-link="internal">Susan Walsh</a>.</p>
<p>Hi Susan,</p>
<p>In this case I&#8217;d suggest that you get use of point 3 in the article 🙂</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Nyagoslav		</title>
		<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-134286</link>

		<dc:creator><![CDATA[Nyagoslav]]></dc:creator>
		<pubDate>Wed, 30 Nov 2011 14:13:11 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=19673#comment-134286</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-124269&quot;&gt;Jonathan&lt;/a&gt;.

Perfectly true! There are two ways to do that actually:

1) First create the listing and start waiting for the postcard. In the meantime create citations (this way hides a little risk of duplicates popping up).

2) First create a lot of citations, wait for Google to create a listing for you and then claim it by phone.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-124269" data-wpel-link="internal">Jonathan</a>.</p>
<p>Perfectly true! There are two ways to do that actually:</p>
<p>1) First create the listing and start waiting for the postcard. In the meantime create citations (this way hides a little risk of duplicates popping up).</p>
<p>2) First create a lot of citations, wait for Google to create a listing for you and then claim it by phone.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Nyagoslav		</title>
		<link>https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-134285</link>

		<dc:creator><![CDATA[Nyagoslav]]></dc:creator>
		<pubDate>Wed, 30 Nov 2011 14:09:09 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=19673#comment-134285</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-121287&quot;&gt;Lynn H&lt;/a&gt;.

It&#039;s amazing, isn&#039;t it! I believe I will have to make a note here that for some time now Map Maker is available in Canada too, so the opportunities expand :)]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.searchenginepeople.com/blog/workarounds-for-google-places-verification.html/comment-page-1#comment-121287" data-wpel-link="internal">Lynn H</a>.</p>
<p>It&#8217;s amazing, isn&#8217;t it! I believe I will have to make a note here that for some time now Map Maker is available in Canada too, so the opportunities expand 🙂</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
