Custom Licensing Policy generating error in License Field

  • d.

    (@pxlar8)


    3 years ago

    When using the Custom option, the output is including rogue "https://custom" in the page code that is prompting a Google Search Console error (Invalid URL in field “license”). It’s happening for each image on the page.

    A valid page is selected as the licensing policy page, and that page’s URL is being inserted into the “acquireLicensePage” field, but the “license” field is being output as "https://custom".

    An example below (I’ve replaced the domain name):

    "license": "https://custom","acquireLicensePage": "https://exampledomain.com/license-policy/?license-policy=1&id=14016&src=https%3A%2F%2Fexampledomain.com%2Fwp-content%2Fuploads%2F2019%2F04%2F13-2-678x452.jpg"},{"@context": "https://schema.org/","@type": "ImageObject","contentUrl":

    • This topic was modified 3 years ago by d..
Viewing 4 replies - 1 through 4 (of 4 total)

  • I just discovered the same issue. 400+ errors in console for our photography website. Did you find a solution?

    My guess is there isn’t anything we can do about it, because the plugin doesn’t allow us any way to *define* the custom license, or point it to a separate page. So therefore Google has no idea what we are trying to tell it.

    Thread Starter d.

    (@pxlar8)

    No, I didn’t. And with no response from the developer, I had to ditch the plugin, unfortunately. The idea is good, but this one currently isn’t working for me.

    I assume the License Policy Page setting is supposed to address this, but something about that isn’t working, even when an internal page was selected (and external URL would be even better).

    However, I did reach out to the developers of my preferred SEO plugin, since this seems like something that should be incorporated there. They said that it’s already on their to-do list but isn’t currently available (and currently no public release timeline for this feature).

    What’s your preferred SEO plugin?

    We use RankMath, and after reading your comment I’m so hoping they are the developers you are talking about.

    Thread Starter d.

    (@pxlar8)

    Unfortunately not.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Custom Licensing Policy generating error in License Field’ is closed to new replies.