GSC shows “Dataset Warning” for tables

@japsec please share the url of the page and a link to this tool when you test it against your URL.

https://www.nazmibaycin.com/wp-content/uploads/2019/12/Screen-Shot-2019-12-30-at-11.01.26.png

@japsec you can use this code snippet to add the license (or additional fields) directly to the front-end. You can change <your post id> to target a specific chart or remove that to target all charts.

add_filter( 'visualizer_schema', function( $schema, $id ) {
	if( ! empty( $schema ) && $id === <your post id> ) {
		$schema = str_replace( '}', ',"license": "GPL"}', $schema );
	}
	return $schema;
}, 10, 2 );

We haven’t heard from you in sometime so marking this as Resolved. If you continue to face an issue, please create a new ticket. We’d be happy to help.

If you are satisfied with our product and support, kindly spare a moment to leave us a review. It would really help us spread the word!

I tried everything, the trick with the code snippet doesn’t work.

But there’s a solution: you just need to leave the description field blank (settings of the chart > advanced > general settings > title > chart description).

Until the settings doesn’t provide a customable field “license”, the description can’t be used, otherwise Google will shoot down the whole page in their search machine.

• This reply was modified 4 years, 9 months ago by captainfi.

@captainfi License is a recommended field and not mandatory. Can you please share documentation that supports your below assertion?

otherwise Google will shoot down the whole page in their search machine

I don’t know about “google will shoot down the whole page”, but it does trigger a GSC warning when you use a description for a Visualizer.

The warning reads:
“Missing field “license”
First detected: 5/31/20
Status: Warning”

This can be fixed by simply removing the description. Of course, without a description, Visualizer doesn’t insert the other structured data and so it’s no longer part of Google’s dataset search tools.

It’d be great if we could add a license. It seems like a straightforward field to add:

“license” : “https://creativecommons.org/publicdomain/zero/1.0/”

//or//

“license” : {
“@type”: “CreativeWork”,
“name”: “Custom license”,
“url”: “https://example.com/custom_license”
}

@chrisrcooper I am getting a whole bunch of errors as well. Have you found any workarounds for this?

I didn’t dig any further; unless there’s been a plugin update to resolve this since my post, the only solution would be to remove the description–which is what I did. I’d prefer not to though so that Google will index the right structured data and come up as part of their data search tools.

Hey,
Thanks for your response.
Yeah nothing in the plugin so far.
I just removed all of my descriptions as well, as I think its better to have no structured data, than to show data that is missing fields. Will keep an eye out.