You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oh! I missed this somehow. Thank you for the bug report!
It looks like:
It is not finding any schemas is knows about that Google consumes. Currently it supports about a dozen of the schemas Google uses, but currently they are mostly various different article types. It doesn't validate otherGoogle supported schemas yet, like Organization, but it should.
It doesn't reflect what was done meaningfully in the output - it should probably do something like output how many known and unknown Google schema types it found, so that it is more transparent about what was found / not found.
Does this explanation make sense?
Having it meet your expectations of the "expected behaviour" seems very reasonable.
Happy to take details of feature requests for the sort of behaviour you would like to see.
This should be resolved with the release of version 4.0.
I've added explicit support for the above schemas. It seems they both only have "optional" properties in Google, so I added support for checking optional properties in version 4.0.
The way any Schema.org properties are detected and the results displayed has also changed, so it should also work better for people using other schemas, even ones the tool does not know that Google explicitly supports.
Describe the bug
It seems that when using the Google preset option no google specific tests run
To Reproduce
sdtt --url https://www.techradar.com --presets "Google"
Expected behavior
Tests run under Google heading (as happens when using Facebook, Twitter )
Screenshots

The text was updated successfully, but these errors were encountered: