Google Announces Schema.org Support for Phone Numbers, Hours & Menus

In response to the growing number of user queries for more specific business contact information (ie. Cox Cable billing, Sears customer service, etc.), Google announced today that it now includes support for structured data markup for four types of phone numbers: customer service, technical support, billing support, and bill payment. This markup allows you to specify multiple business phone numbers along with their contact type, if they’re toll-free or suitable for the hearing-impaired, and whether the number is global or country-specific, even if they’re not visible on your website.

sears-phone-google

Here’s an example of the Schema.org markup based on Google’s suggestions (directly from the CM website):

<script type="application/ld+json">
{ "@context" : "http://schema.org",
   "@type" : "Organization",
   "url" : "https://www.customermagnetism.com/",
   "contactPoint" : [
   { "@type" : "ContactPoint",
      "telephone" : "+1-800-610-7265",
      "contactType" : "customer service",
      "contactOption" : "TollFree"
   } , { "@type" : "ContactPoint",
      "telephone" : "+1-800-610-7265",
      "contactType" : "billing support",
      "contactOption" : "TollFree"
   } , { "@type" : "ContactPoint",
      "telephone" : "+1-800-610-7265",
      "contactType" : "bill payment",
      "contactOption" : "TollFree"
   } , { "@type" : "ContactPoint",
      "telephone" : "+1-800-610-7265",
      "contactType" : "technical support",
      "contactOption" : "TollFree"
   } , {
      "@type" : "ContactPoint",
      "telephone" : "+1-757-689-2875",
      "contactType" : "customer service"
   } , {
      "@type" : "ContactPoint",
      "telephone" : "+1-757-689-2875",
      "contactType" : "billing support"
   } , {
      "@type" : "ContactPoint",
      "telephone" : "+1-757-689-2875",
      "contactType" : "bill payment"
   } , {
      "@type" : "ContactPoint",
      "telephone" : "+1-757-689-2875",
      "contactType" : "billing support"
   } ] }
</script>

Based on the above markup, we’re telling Google how we can be reached in the contactPoint property, which indicates our local and toll-free phone numbers. Since we service all inquiries from our local and toll-free phone numbers, customer support, technical support, billing support, and bill payment contactType values each need to be specified by separate contactPoint properties and values. Also because these are the numbers used for all of the areas we serve, we’ve left out the optional areaServed property, which indicates these are the numbers we’d like to use globally.

Once you’ve added the markup to your website, you can check it in Google’s Corporate Contacts Markup Tester, which extracts structured data and identifies any possible issues.

Here’s a peek at our results:
webmasters_markup-tester_corporatecontacts

Location Pages Markup Guidelines

In addition to their announcement of multiple contact type support, Google introduced recommendations for location page markup. Here are some examples of Google’s structured markup guidelines, including information on specifying multiple departments, location addresses, operating hours, contact phone, and more. This is where we finally find out how to specify menus to appear in the coveted (and new) Google Menus results.

Get into Google Menus

Of course Google still advises the use of Google Places for Business to ensure your business’ contact information is front and center for users, and we’re betting smart businesses will use their place listing in conjunction with structured data to guarantee maximum impact.

  • Divyanshu

    Is this needs to be implemented only on contact page. Or HOme page/Contact page or in a file that will be called on all pages and code is visible on all page. I guess code on only contact us page will work just fine. Any comments ?

    • Hi Divyanshu! I think the way it’s implemented is going to vary for each website and how it’s set up. For us, we include a lot of common contact information on every page (think footer, etc.), so we have contact schema implemented site-wide. If you only have contact information on your contact page, it would make sense to add the markup there. I hope that helps!