As a first step, we'll add a JSON-LD script to all file pages on Commons with the [[ https://developers.google.com/search/docs/data-types/image-license-metadata | license data ]] that will soon be required by Google.
Sample script:
```
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "ImageObject",
"url": "https://example.com/photos/1x1/black-labrador-puppy.jpg",
"license": "https://example.com/license",
"acquireLicensePage": "https://example.com/how-to-use-my-images"
}
</script>
```
We should also inspect the page size (see [[ https://phabricator.wikimedia.org/T209309 | this task ]]; if the article script only added 0.5 - 1KB I don't expect this script will be a problem)
---
Acceptance criteria:
[ ] A JSON-LD script is present in the source code of file pages on Commons containing `license` and `acquireLicensePage` attributes
[ ] `license` links to the actual license, or to a page with information about the public domain, whichever applies to that image
[ ] `acquireLicensePage` should link to the file page on Commons
[ ] File pages on production Commons are valid when tested with the [[https://search.google.com/structured-data/testing-tool/u/0/ | structured data testing tool]]
---
### COVID-19 Deployment Criteria
[] Can you roll back this change without lasting impact?
# A recovery plan is required as this will help identify our capacity for recovering from the failure
# THIS IS A KEY QUESTION, if you can’t answer it, you shouldn’t deploy
[] Is specialized knowledge required to support this change in production? If so, are there multiple people with this knowledge?
[] Is there a way to increase confidence about the correctness of this change?
# Reviews (Design, Code, etc)
# Testing coverage (unit tests, integration tests)
# Manual testing (e.g. Beta, vagrant, docker)