@en-us not compatible with range

  • Resolved photoburt

    (@photoburt)


    2 years, 10 months ago

    There are errors in the structured data made by yoast SEO premium.

    Per https://pagespeed.web.dev/ a webpage needs to pass the Structured Data Linter at http://linter.structured-data.org/ This test finds a few errors in Yoast’s structured data. On my page it is saying:

    property og:url: Object "https://tools4families.com/family-support-for-depression-how-you-can-help/"@en-us not compatible with range (ogc:url)

property og:image: Object "https://tools4families.com/wp-content/uploads/2021/09/Untitled-design-23.jpg"@en-us not compatible with range (ogc:url)

    The lines that generate this error are:

    <meta property="og:url" content="https://tools4families.com/family-support-for-depression-how-you-can-help/" class="yoast-seo-meta-tag" />

    and

    <meta property="og:image" content="https://tools4families.com/wp-content/uploads/2021/09/Untitled-design-23.jpg" class="yoast-seo-meta-tag" />

    Researching this error, you find an answer on: https://github.com/structured-data/linter/issues/49 Basically, meta “content” is defined as text but Yoast is giving a URL. This causes an error. It should be a link defined like:

    <link property="og:url" href="https://tools4families.com/family-support-for-depression-how-you-can-help/" class="yoast-seo-meta-tag" />
    <link property="og:image:secure_url" href="https://tools4families.com/wp-content/uploads/2021/09/Untitled-design-23.jpg" class="yoast-seo-meta-tag" />

    Similar errors are showing

    property schema:width: Object "2000"^^<http://www.w3.org/2001/XMLSchema#integer> not compatible with rangeIncludes (schema:Distance,schema:QuantitativeValue)

property schema:width: Object "512"^^<http://www.w3.org/2001/XMLSchema#integer> not compatible with rangeIncludes (schema:Distance,schema:QuantitativeValue)

property schema:height: Object "1428"^^<http://www.w3.org/2001/XMLSchema#integer> not compatible with rangeIncludes (schema:Distance,schema:QuantitativeValue)

property schema:height: Object "512"^^<http://www.w3.org/2001/XMLSchema#integer> not compatible with rangeIncludes (schema:Distance,schema:QuantitativeValue)

    This is due to a similar reason. It is expecting text but receiving an integer

    <meta property="og:image:width" content="2000" class="yoast-seo-meta-tag" />

<meta property="og:image:height" content="1428" class="yoast-seo-meta-tag" />

    The error with 512 is because schema:height and schema:width are expecting a Distance or QuantitativeValue not an integer. This is probably why https://search.google.com/test/rich-results wasn’t finding the Logo structure on the page until I made a separate schema structure in the header for it.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    2 years, 10 months ago

    Hello @photoburt

    Thanks for reaching out about your site’s structured data. I understand the Structured Data Linter is reporting some errors. But these are not specific to Yoast SEO but Open Graph protocols.

    For instance, the recommendation to use the link element <link property="og:image:secure_url" instead of <meta property="og:image:secure_url" doesn’t follow the protocol. You can learn more here.

    I’d recommend using https://validator.schema.org/ to check that there are no syntax errors, https://classyschema.org/Visualisation to check that the schema graph is cohesive and complete and https://search.google.com/test/rich-results to check any Google-specific requirements/errors.

    For instance, RRT reports Missing field “url” (optional). You may resolve that by adding a profile URL for the author, Noosha

    Thread Starter photoburt

    (@photoburt)

    2 years, 10 months ago

    Thanks for the detailed response. So, it’s the Open Graph protocols that don’t meet the html specs. Interesting. I thought that this was the error causing the RRT not to list the logo object when using the base Yoast structured data. So, if that isn’t the case, do you have any insight into why the Yoast logo object within the Organization structure is not being seen by RRT? If you run the RRT on a page now it shows the extra logo element I put in the header manually. Before that, it didn’t show.

    Plugin Support Maybellyne

    (@maybellyne)

    2 years, 10 months ago

    Hello @photoburt

    Indeed, the logo rich result does not show as part of a known schema. And the same situation applies on our homepage. We had to create it separately for the logo to output for Yoast too.

    Google doesn’t properly support logos in graphs where the organization isn’t on the leading edge. You could also add a DIY fix like ours.

    Thread Starter photoburt

    (@photoburt)

    2 years, 10 months ago

    Yes, I did add a diy fix like yours. Have you considered adding that feature Yoast plugin?

    Plugin Support Maybellyne

    (@maybellyne)

    2 years, 10 months ago

    Yes, this has been considered in-house in the past but decided it’s for Google to fix.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘@en-us not compatible with range’ is closed to new replies.