Understanding Google My Business & Local Search
Google’s Rich Snippets For Local FAQ Update
Google provides no RSS feeds, no history of changes and no date that a given change was published. For a company that proclaims openness and transparency, intentional obscurity of changes to their help files is a curious thing. Clearly, it would seem to be in every one’s best interest if Google’s current policy and best practices were easily tracked. One has to assume that the decision to not include these standard features are an intentional act to obfuscate these changes.
That being said here are some interesting points in the now current Rich Snippets for Local FAQ
Does it matter whether I include multiple telephone types?
You should only provide the phone number for the location of the actual local business. Types of phone numbers that should not be included are: call tracking numbers and phone numbers that are not specific to a business location.
Should the <url> point to my home page or to the location specific page?
The <url> should point to the home page of the business. However, the attribution will link to the source of the crawled information.
Do I need to specify the <geo> lat long or is it okay to only use <adr>?
If you have precise coordinates, please include them. This will help Google display results accurately. If you do not have precise coordinates, then <adr> alone is okay.
What additional types of structured data does Google plan to recognize in the future?
The goal is to eventually be able to recognize all structured data that appears on the Place Page.
If I annotate my site with structured markup, where may results appear?
Results may appear in Web Search, the Place Page, and Video Search, as well as other Google services and services outside of Google. However, Google cannot guarantee by annotating your site that results will appear in any of the above services.
Should business owners be using structured markup instead of Google Places?
No. Currently, Google Places is the only way to verify ownership of a business, update its Place Page instantly, and see the analytics dashboard. Annotating your site with structured markup is still a good idea, and a great way to make sure your website is reliably associated with the places it mentions.
How will Google treat businesses posting testimonials with review mark up on their own site? Will these be treated as a review by the Place Page?
Google’s goal is to provide a comprehensive, unbiased, and credible view of businesses. Reviews should come from an independent source to remain trustworthy. Posting testimonials or using review markup on a business site will generally not improve how its listing appears on Google. As with any form of unuseful content, reviews markup intended to game search results will only undermine the listing’s credibility and may negatively affect its ranking. See our Webmaster Guidelines.
Will Rich Snippets for Local Search be as trusted as Google Places data?
It doesn’t replace verification via Google Places. We’re using this information to allow site owners to tell us about a specific location. Like other information, it will be ranked and displayed algorithmically, depending on its relevance.
If I annotate my site with structured markup, how fast may results appear on the Place Page?
It typically has the potential of appearing within a couple of weeks of your page being indexed by Google. Currently we will only be able to recognize basic business listing information (name, address, phone number) and surface reviews and photos.
What is the optimal way of using structured markup. Should you have a separate “Reviews” page or should you incorporate them within the body of the site?
For “discoverability” purposes, it does not matter much. But from an attribution/link back point of view, having a reviews page might make more sense since Google can point users directly to that page. Having a page for each review might be even better. In the end, you should really design the page in a way that makes sense for your site and your end users’ experience.