new_audit: structured data validation using shex #12324
Conversation
new structured data fork created due to significant differences and problems with history. Old fork: https://github.com/Gnomus042/lighthouse
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
This is a lot of work to get right, and we don't have the resources to pursue this now. In short, some non-starters are how big the dependencies are, and how long this takes to process. There is a possible future where this will be perfect as a Lighthouse plugin (which is a project somewhat on the backburner). We're thankful for the effort put towards this so far, it will surely be useful if this is ever picked up again. |
This PR introduces a structured data (seo) audit, which is based on ShEx validation language. Currently, the audit is based on ShEx shapes, which are close to Schema.org constraints and also include prototypes of service-specific shapes, close to oficial Bing, Google, Pinterest and Yandex requirements.
Background document, that is briefly describing core part of this audit.
Currently this PR is a draft PR and is not ready for checking in, but we would be grateful for any feedback