XF 2.1 data-vocabulary.org schema deprecated error from google today?

[TUG]

got this notification today from google referencing the forum domain?

Search Console has identified that your site is affected by 1 Breadcrumbs issues:

Top Warnings

Warnings are suggestions for improvement. Some warnings can affect your appearance on Search; some might be reclassified as errors in the future. The following warnings were found on your site:

data-vocabulary.org schema deprecated

ive made no changes to this since upgrading?

any ideas?

 

[cayne]

It seems like it's possible. There are about 5 templates that use data-vocabulary, so changing them would fix the issue...

So there is a way to fix this on 1.5?

 

[rickhz]

So there is a way to fix this on 1.5?

I'm also looking for a solution for V1.5x.

 

[cayne]

I'm also looking for a solution for V1.5x.

Please let me know ASAP - if you find something. I'm a bit afraid of upgrading to v2

 

[Ozzy47]

I'd be more afraid of staying on old unsupported software.

 

[leebo]

I too got this warning at the same time as the OP. I’ve never been on XenForo 1. We migrated from vB 4 to XenForo 2 last year. The warning was saying one thread only had the issue and upon advice from this forum I simply clicked “Validate Fix” to see what happens.

Got the email today saying the Breadcrumbs issues were fixed and all is good.

 

[Ozzy47]

Yeah, there are going to be false positives for some unexplained reason.

 

[valdet]

By checking this resource, it doesn't look too difficult to change the references in the templates.

Sunsetting support for data-vocabulary

Official news on crawling and indexing sites for the Google index

webmasters.googleblog.com

The only issue I am having is how to generate the appropriate content="#" value

There is a loop cycle in the breadcrumb template

            <xen:if is="{$navigation}">
                <xen:foreach loop="$navigation" value="$breadcrumb" i="$i" count="$count">
                    <span class="crust"{xen:if $microdata, ' itemscope="itemscope" itemtype="https://data-vocabulary.org/Breadcrumb"'}>
                        <a href="{xen:raw $breadcrumb.href}" class="crumb"{xen:if $microdata, ' rel="up" itemprop="url"'}><span{xen:if $microdata, ' itemprop="title"'}>{xen:raw $breadcrumb.value}</span></a>
                        <span class="arrow"><span></span></span>
                    </span>
                </xen:foreach>
            </xen:if>

and here is the example of a breadcrumb from schema.org

<ol itemscope itemtype="http://schema.org/BreadcrumbList">
  <li itemprop="itemListElement" itemscope
      itemtype="http://schema.org/ListItem">
    <a itemprop="item" href="https://example.com/dresses">
    <span itemprop="name">Dresses</span></a>
    <meta itemprop="position" content="1" />
  </li>
  <li itemprop="itemListElement" itemscope
      itemtype="http://schema.org/ListItem">
    <a itemprop="item" href="https://example.com/dresses/real">
    <span itemprop="name">Real Dresses</span></a>
    <meta itemprop="position" content="2" />
  </li>
</ol>

I just cannot figure out how you can insert the ordering number inside this block
<meta itemprop="position" content="1">

Any tips ?

 

[GPA-R]

Running the latest version of XF and still getting these.

 

[Chris D]

You’ll have to be more specific or please open a new thread with the details including the specific error and any relevant URLs where they’re occurring etc.

 

[ProCom]

I keep getting these emails as well (on XF v2.1.11 converted from 1.5 about 10 months ago) and every time I get nervous. It may not make any difference in SERPs, but I don't know anybody that relies on Google for traffic that also wouldn't be nervous about even a hint of warnings from Google search.

"Search Console has identified that your site is affected by 1 Breadcrumbs issues:

Top Warnings

Warnings are suggestions for improvement. Some warnings can affect your appearance on Search; some might be reclassified as errors in the future. The following warnings were found on your site:

data-vocabulary.org schema deprecated

We recommend that you fix these issues when possible to enable the best experience and coverage in Google Search."

 

[djbaxter]

As I've said before, my practice when I get those emails is to simply go into Search Console, click on the supposed errors, mark them as fixed (without actually changing anything at all), and click on verify. Then a couple of days later, I get another email from Search Console saying they have verified the fix and everything is now okay.

And again I emphasize that I don';t actually fix or change anything. I'm basically telling Google to check again. I've been doing this for well over a year now and it has always worked. Not permanently... I'' get another email a few months later and I just rinse and repeat.

Clearly the page scanners at Google Search Console are flawed and imperfect. Even visual inspection of the page they're complaioning about can tell you that.