How does a website created by Odoo implement the Google schema mark-up in order to submit structured data to Google?

michel Guénard

I have not read something in this direction within the available documentation.

The issue here is to make sure that our websites will reach a satisfactory level when crawled by Google.

Below is a copy of what can be found to explain the issue.


Schema mark-up gives meaning behind simple words, numbers, ratings & dates to search engines.  Without it, search engines may not be able to draw any accurate conclusions from the web page code, apart from easily found fields such as telephone numbers or email addresses.

You can see schema mark-up in action within searches such as local restaurant reviewsmovie review scores or recipes to name a few.  Once indexed and approved, these can appear as rich snippets within search engine results:

Rich snippets from a restaurant review

Rich snippets from a restaurant review

To make it clearer I add an example of a page without mark-up, followed by the same page with mark-up

  1. <!-- A list of the issues for a single volume of a given periodical. -->
  2. <div>
  3.  <h1>The Lancet</h1>
  4.  <p>Volume 376, July 2010-December 2010</p>
  5.  <p>Published by Elsevier
  6.  <ul>
  7.    <li>ISSN: 0140-6736</li>
  8.  </ul>
  9.  <h3>Issues:</h3>
  10.  <ul>
  11.    <li>No. 9734 Jul 3, 2010 p 1-68</li>
  12.    <li>No. 9735 Jul 10, 2010 p 69-140</li>
  13.  </ul>
  14. </div>

Same page with Microdata mark-up

  1. <!-- A list of the issues for a single volume of a given periodical. -->
  2. <div itemscope itemtype="">
  3.   <h1 itemprop="name">The Lancet</h1>
  4.   <p>Volume 376, July 2010-December 2010</p>
  5.   <p>Published by <span itemprop="publisher">Elsevier</span>
  6.   <ul>
  7.     <li>ISSN: <span itemprop="issn">0140-6736</span></li>
  8.   </ul>
  9.   <h3>Issues:</h3>
  10.   <div itemprop="hasPart" itemscope itemtype="" itemid="#vol376">
  11.     <meta itemprop="volumeNumber" content="376">
  12.     <ul>
  13.       <li itemprop="hasPart" itemscope itemtype="" itemid="#iss9734">No.
  14.         <span itemprop="issueNumber">9734</span>
  15.         <time datetime="2010-07-03" itemprop="datePublished">Jul 3, 2010</time>
  16.         p <span itemprop="pageStart">1</span>-<span itemprop="pageEnd">68</span>
  17.       </li>
  18.       <li itemprop="hasPart" itemscope itemtype="" itemid="#iss9735">No.
  19.         <span itemprop="issueNumber">9735</span>
  20.         <time datetime="2010-07-03" itemprop="datePublished">Jul 10, 2010</time>
  21.         p <span itemprop="pageStart">69</span>-<span itemprop="pageEnd">140</span>
  22.       </li>
  23.     </ul>
  24.   </div>
  25. </div>

Same RDFa

  1. <!-- A list of the issues for a single volume of a given periodical. -->
  2. <div vocab="" typeof="Periodical">
  3.   <h1 property="name">The Lancet</h1>
  4.   <p>Volume 376, July 2010-December 2010</p>
  5.   <p>Published by <span property="publisher">Elsevier</span>
  6.   <ul>
  7.     <li>ISSN: <span property="issn">0140-6736</span></li>
  8.   </ul>
  9.   <h3>Issues:</h3>
  10.   <div property="hasPart" typeof="PublicationVolume" resource="#vol376">
  11.     <meta property="volumeNumber" content="376">
  12.     <ul>
  13.       <li property="hasPart" typeof="PublicationIssue" resource="#issue9734">No.
  14.         <span property="issueNumber">9734</span>
  15.         <time datetime="2010-07-03" property="datePublished">Jul 3, 2010</time>
  16.         p <span property="pageStart">1</span>-<span property="pageEnd">68</span>
  17.       </li>
  18.       <li property="hasPart" typeof="PublicationIssue" resource="#issue9735">No.
  19.         <span property="issueNumber">9735</span>
  20.         <time datetime="2010-07-03" property="datePublished">Jul 10, 2010</time>
  21.         p <span property="pageStart">69</span>-<span property="pageEnd">140</span>
  22.       </li>
  23.     </ul>
  24.   </div>
  25. </div>


And finally with the JSON-LD

  1. <script type="application/ld+json">
  2. {
  3.   "@context": "",
  4.   "@type": "Periodical",
  5.   "issn": "0140-6736",
  6.   "hasPart": {
  7.     "@id": "vol376",
  8.     "@type": "PublicationVolume",
  9.     "volumeNumber": "376",
  10.     "hasPart": [
  11.       {
  12.         "@id": "issue9735",
  13.         "@type": "PublicationIssue",
  14.         "datePublished": {
  15.           "@value": "2010-07-03",
  16.           "@type": ""
  17.         },
  18.         "pageEnd": "140",
  19.         "pageStart": "69",
  20.         "issueNumber": "9735"
  21.       },
  22.       {
  23.         "@id": "issue9734",
  24.         "@type": "PublicationIssue",
  25.         "datePublished": {
  26.           "@value": "2010-07-03",
  27.           "@type": ""
  28.         },
  29.         "pageEnd": "68",
  30.         "pageStart": "1",
  31.         "issueNumber": "9734"
  32.       }
  33.     ]
  34.   },
  35.   "name": "The Lancet",
  36.   "publisher": "Elsevier"
  37. }
  38. </script>
1 Comment

Interesting and good question. I'm curious about the answers!

1 Answer
michel Guénard
Best Answer

<text> I just checked one of the pages created on my own ODOO website:

The answer to my initial question is NO, the page does'nt contain any mark-up tag.

EDIT: Just made a test to add the required tags (using the Google tool

I was unable to edit the Odoo html code with what Google tool requires.

My observation is for ODOO V7 running on Saas</text>

Does V8 or V9 comply with these standards?

For what I understand with the SEO principles and rules etc...defined since 2 years by Google, this means my website has no chance to be present in the first search results pages (assuming the content of my site is of top quality; which is another story!)

Thus the issue is to hear Odoo community setting steps forward to effectively implement the new standards for the "out of the box" website building.

When done and adding the whole work on the styles (see the funding campain for new styles) then the tools will be available for a professional work.

Until then what are our options to publish good quality website?

1 Comment
michel Guénard

The cost for upgrading an existing website whith these new guidance from Goggle is rated at a starting 8000 usd! (just one example)