### Author:  [@neil](https://meta.discourse.org/u/neil)
#### Post date: [September 25, 2017, 3:22pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/22 "2017-09-25T15:22:26Z")
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [March 27, 2018, 7:30pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/23 "2018-03-27T19:30:04Z")
---
### Author:  [@jlepine](https://meta.discourse.org/u/jlepine)
#### Post date: [March 27, 2018, 3:03pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/24 "2018-03-27T15:03:13Z")
Hi Discourse team,
First of all, I am new here, so I hope I am doing well posting here for a bug.
I tried to find an existing topic before to post a new one but I did not find anything, so I am sorry in advance if such topic already exists. Do not hesitate to link it or do whatever is necessary. Thank you.
* * *
So here is the issue I would like to report. As mentionned in the title, microdata on discourse do not fulfil with Google tool’s expectations.
**On topic lists, Google tools reports more than 60 errors :**
_example of the main topic list_
for more details, see [this test](https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fmeta.discourse.org%2Flatest)
**There is also errors on posts :**
for more details, see [this other test](https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fmeta.discourse.org%2Ft%2Ftopic-stopwatch-theme-component%2F83939)
* * *
My company is using discourse as forum for 3 of our websites. We greatly consider the SEO aspect and would be thankful for you to correct all possible errors in microdata.
So is it possible for you to fix microdata ?
---
### Author:  [@jlepine](https://meta.discourse.org/u/jlepine)
#### Post date: [April 13, 2018, 1:55pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/25 "2018-04-13T13:55:13Z")
Hi Discourse team,
I posted my question about two weeks ago. I assume fixing microdata will take a certain amount of time but since I got no answer yet I allow myself to ask you if the fix is on track and when it could be released ?
Thank you in advance for your work and your reply.
---
### Author:  [@neil](https://meta.discourse.org/u/neil)
#### Post date: [April 13, 2018, 2:50pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/26 "2018-04-13T14:50:47Z")
Are all 61 errors saying the same thing? `` needs to have a “position” attribute?
---
### Author:  [@jlepine](https://meta.discourse.org/u/jlepine)
#### Post date: [April 13, 2018, 3:00pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/27 "2018-04-13T15:00:28Z")
The 61 errors count 3 different kind of error :
- ItemList → itemListElement → url and/or ItemList → itemListElement → item → url (30 times): All values provided for _url_ must point to the same page.
- ItemList → itemListElement → position (30 times): A value for the _position_ field is required.
- global to ItemList (1 time): ListItem with _url_ and ListItem with _item_ are incompatible.
As I mentioned it in my first post, you can follow the links I gave to see all details.
---
### Author:  [@noisegratte](https://meta.discourse.org/u/noisegratte)
#### Post date: [May 2, 2018, 8:30am UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/28 "2018-05-02T08:30:18Z")
Hi @t\_d ,
Any news about this subject ?
When do you think a fix will be released ?
Thx
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [May 31, 2018, 8:03pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/30 "2018-05-31T20:03:41Z")
I can take it during june.
---
### Author:  [@hustler](https://meta.discourse.org/u/hustler)
#### Post date: [June 3, 2018, 9:53pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/31 "2018-06-03T21:53:04Z")
Invision Boards handle structured data well to see how it could/should be done.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [June 13, 2018, 10:21pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/32 "2018-06-13T22:21:18Z")
I just pushed a commit to improve this:
[https://github.com/discourse/discourse/commit/276526e30ea6e791f97e1a14d1d6bc7a2fc06be2](https://github.com/discourse/discourse/commit/276526e30ea6e791f97e1a14d1d6bc7a2fc06be2)
I will keep digging but I think the remaining errors are due to google validation tool:
> **[Schema Markup Testing Tool | Google Search Central | Google for Developers](https://developers.google.com/search/docs/appearance/structured-data)**
>
> Use the Rich Result Test to see what Google results can be generated for your pages and the schema markup validator for generic schema validation.
> **[Schema Markup Testing Tool | Google Search Central | Google for Developers](https://developers.google.com/search/docs/appearance/structured-data)**
>
> Use the Rich Result Test to see what Google results can be generated for your pages and the schema markup validator for generic schema validation.
> **[Schema Markup Testing Tool | Google Search Central | Google for Developers](https://developers.google.com/search/docs/appearance/structured-data)**
>
> Use the Rich Result Test to see what Google results can be generated for your pages and the schema markup validator for generic schema validation.
> **[Schema Markup Testing Tool | Google Search Central | Google for Developers](https://developers.google.com/search/docs/appearance/structured-data)**
>
> Use the Rich Result Test to see what Google results can be generated for your pages and the schema markup validator for generic schema validation.
I still have this page to improve, will do it tomorrow:
> **[Schema Markup Testing Tool | Google Search Central | Google for Developers](https://developers.google.com/search/docs/appearance/structured-data)**
>
> Use the Rich Result Test to see what Google results can be generated for your pages and the schema markup validator for generic schema validation.
Particularly this page has a warning with “DiscussionForumPosting” which is asking us to provide an image if possible. I think we could just add `itemprop=“image” when we cook the post to images. I will investigate this.
---
### Author:  [@noisegratte](https://meta.discourse.org/u/noisegratte)
#### Post date: [June 18, 2018, 10:04am UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/33 "2018-06-18T10:04:55Z")
Hi @j.jaffeux ,
You fixed the issues regarding the “position” attribute.
> [@jlepine](#):
>
> The 61 errors count 3 different kind of error :
>
> - ItemList -\> itemListElement -\> url and/or ItemList -\> itemListElement -\> item -\> url (30 times): All values provided for _url_ must point to the same page.
> - ItemList -\> itemListElement -\> position (30 times): A value for the _position_ field is required.
> - global to ItemList (1 time): ListItem with _url_ and ListItem with _item_ are incompatible.
>
> As I mentioned it in my first post, you can follow the links I gave to see all details.
But it still remains to resolve the uncompatibility between ListItem with “url” and ListItem with “item” Also, url attribute of each ListItem should point to the same page.
There is progress but still some work to do.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [June 18, 2018, 10:06am UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/34 "2018-06-18T10:06:30Z")
Yes I’m continuing work on this today or tomorrow. Thanks for recap/update.
> [@noisegratte](#):
>
> Also, url attribute of each ListItem should point to the same page.
I will investigate more, but I do think there’s a bug in google tool here. Can you share me a test where it’s showing this for you please?
---
### Author:  [@noisegratte](https://meta.discourse.org/u/noisegratte)
#### Post date: [June 18, 2018, 10:33am UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/35 "2018-06-18T10:33:34Z")
For example : [https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fmeta.discourse.org%2Flatest](https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fmeta.discourse.org%2Flatest)
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [June 18, 2018, 10:35am UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/36 "2018-06-18T10:35:57Z")
I see:
```plaintext
```
It seems weird to me that’s it’s not validated because the two elements with item prop have the same URL:
```plaintext
Color Scheme Contest (with Prizes!)
```
I will look if it’s caused by the page-links or category link at the end of the block.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [July 24, 2018, 4:37pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/38 "2018-07-24T16:37:17Z")
More than any error in google validation tool, I’m interested by errors you would see in the google search console.
`Search console -> Search appearance -> Structured data` If you have **ERRORS** in this section which you think are caused by Discourse, I’m very interested to fix these.
---
### Author:  [@jlepine](https://meta.discourse.org/u/jlepine)
#### Post date: [July 30, 2018, 12:08pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/39 "2018-07-30T12:08:28Z")
As you asked for, I checked the `Search console -> Search appearance -> Structured data` panel for both our websites using Discourse as forum (i.e. [https://www.gamekult.com](https://www.gamekult.com) as GK and [https://www.focus-numerique.com](https://www.focus-numerique.com) as FN). We have absolutly **no errors caused by Discourse** on GK and no errors at all on FN.
However, I do not see how it could be different since Discourse is not embeded in the source code of our website. As you should know (I guess), our Discourse instances are completely separated applications that are hosted separately (servers/network of your own). We just provide access to them from links in our websites.
Since the issue relates only to errors that appear on Discourse’s pages ([https://meta.discourse.org](https://meta.discourse.org) or [Discourse Meta](https://meta.discourse.org/latest) for example), we provided you the link to the analysis of one of these urls : [https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fmeta.discourse.org%2Flatest](https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fmeta.discourse.org%2Flatest)
I think you should focus on this link and on the corresponding Discourse source code cause the issue really seems to concerns Discourse only.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [July 30, 2018, 12:32pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/40 "2018-07-30T12:32:48Z")
[Forum Jeux vidéo - Gamekult](http://www.gamekult.com/forum) is a subfolder, you can totally configure search console on this subfolder and google recommends it: [Add a website property to Search Console - Search Console Help](https://support.google.com/webmasters/answer/34592?hl=en)
> We recommend creating a separate Search Console property for each domain or folder that you want to track separately, as well as the lowest level domain that you own. For example, if you have a travel site with specific subfolders covering Ireland, France, and Spain, you could add the following sites to your Search Console account:
>
> - [http://www.example.com/](http://www.example.com/)
> - [http://www.example.com/france/](http://www.example.com/france/)
> - [http://www.example.com/ireland/](http://www.example.com/ireland/)
> - [http://www.example.com/spain/](http://www.example.com/spain/)
The fact that it’s not in your “main” application code doesn’t change anything here, google doesn’t inspect your source code. He tries to get an URL an sees what he gets that’s all.
And yes I’m focusing on this link too, but I get very confusing results in my tests and would like to cross check this with " REAL" data.
---
### Author:  [@jlepine](https://meta.discourse.org/u/jlepine)
#### Post date: [July 30, 2018, 2:21pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/41 "2018-07-30T14:21:24Z")
I understand what you are saying.
I do not master Google Search Console so thank you for your explainations. I did not know about the subfolders.
I will try to give you as much information as possible.
**Google search console** :
_As you can see for Gamekult, there is only few errors on VideoGame and Review data types._
**Google structured data testing tool** ( **_GK_** - [Schema Markup Testing Tool | Google Search Central | Google for Developers](https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fwww.gamekult.com%2Fforum)) :
_Here a first occurence of a unique error message on the right panel and the responsible source code line highlighted in grey on left panel_
_Here the second occurence of this unique error message on the right panel and the responsible source code line highlighted in grey on left panel. You can see that it is not the same line than for the first occurence (maybe it is relevant ?)_
**Google structured data testing tool** ( **_Discourse_** - [https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fmeta.discourse.org](https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fmeta.discourse.org)) :
_Here you can see only one error instead of 2 on GK’s forum. But it seems to be the exact same one than one of GK_
**Remark** :
- both urls in the `
` tag and the `
` tag are absolute on Discourse whereas the `` tag’s url is relative on GK. I do not know why or if it is relevant but I think it could explain why urls are considered different.
First of all, I thought this issue would be an easy one for you. But after reading your last answer (which was lightning for me), I understand better how strange is this issue from your side.
So I hope this long answer will be helpful, even if I may not have been precise enough regarding what answer you expected. I tried to answer your question and to provide you in the same time as much information as possible . If I missed something, do not hesitate to ask.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [July 30, 2018, 2:23pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/42 "2018-07-30T14:23:01Z")
Awesome! Thanks! I just pushed a commit for this btw, we will get there 😉
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [July 30, 2018, 4:54pm UTC](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037/43 "2018-07-30T16:54:53Z")
seems my last fix improved this page: [https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fmeta.discourse.org%2Flatest](https://search.google.com/structured-data/testing-tool/u/0/?hl=en#url=https%3A%2F%2Fmeta.discourse.org%2Flatest)
[Previous page](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037.md?page=1)
[Next page](https://meta.discourse.org/t/google-structured-data-invalid-article-schema/57037.md?page=3)