{"slug": "relicensing-to-cc-by-sa-and-making-it-visible-in-schema-metadata", "title": "Relicensing to CC BY-SA and making it visible in Schema metadata", "summary": "Terence Eden relicensed his blog to CC BY-SA and published a minimum viable Schema.org markup pattern for declaring per-post copyright licences to machines. The example uses a BlogPosting itemtype with itemprop=license linking to the licence URL and itemprop=copyrightNotice on an image whose alt text reads \"🄯 CC BY-SA\", alongside an author who is also the copyrightHolder, and Eden notes the structure allows different copyright and copyleft licences to be assigned to different parts of the same page. The post also covers the HTML link rel=\"license\" attribute as a less specific alternative that requires a visitor to interpret the linked page.", "body_md": "How do you make it clear what copyright licence a blog post uses? I know in our wonderful AI-powered future that copyright and copyleft are but a distant memory. But some of us still believe it's worth making these things clear to both men and machines.\n\nThe first port of call is the page's metadata. Using the [`rel` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/rel#license). Placing something like this in your page's `<head>` indicates that the copyright information can be found at a specific URl.\n\n```\n<link rel=\"license\" href=\"https://example.com/copyright\">\n```\n\nBut that's not overly specific. Someone (or some*thing*) has to visit that website and then interpret what it says. How about we use some fancy [Schema.org](https://schema.org) metadata to make things slightly clearer?\n\nHere's a minimum viable example you can [paste into the validator](https://validator.schema.org/):\n\n```\n<body itemscope itemtype=https://schema.org/Blog>\n    <main itemprop=blogPost itemscope itemtype=https://schema.org/BlogPosting>\n        <article>\n            <span itemprop=\"author copyrightHolder\"\n                  itemscope \n                  itemtype=https://schema.org/Person>\n                <span itemprop=name>Terence Eden</span>\n            </span>\n            <a href=https://shkspr.mobi/blog/copyright-and-copyleft/ itemprop=license>\n                <img alt=\"🄯 CC BY-SA\" \n                     content=\"Creative Commons Attribution ShareAlike\" \n                     itemprop=copyrightNotice \n                     src=\"https://example.com/cc-by-sa.svg\">\n            </a>\n```\n\nThat says this website is a blog. The `<main>` element is a blog post. The article has an author who is also the copyright holder (they may be two different entities). The link is to the licence URl. The image shows the copyright notice with human readable text also available.\n\nIt looks like this to a machine:\n\nThis sort of structure will allow you to assign different copyright and copyleft licences to different parts of the same page.\n\nIn other news, this blog is now CC BY-SA!", "url": "https://wpnews.pro/news/relicensing-to-cc-by-sa-and-making-it-visible-in-schema-metadata", "canonical_source": "https://shkspr.mobi/blog/2026/11/relicensing-to-cc-by-sa-and-making-it-visible-in-schema-metadata/", "published_at": "2026-11-21 12:34:40+00:00", "updated_at": "2026-11-21 12:42:23.602599+00:00", "lang": "en", "topics": ["structured-data", "ai-crawlers"], "entities": ["Terence Eden", "Schema.org", "Creative Commons", "CC BY-SA"], "also_reported_by": [], "takeaway": "Mark up each post as a schema.org BlogPosting with itemprop=license pointing at the licence URL and itemprop=copyrightNotice on the licence image, so machines read the licence without visiting a separate copyright page.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/relicensing-to-cc-by-sa-and-making-it-visible-in-schema-metadata", "markdown": "https://wpnews.pro/news/relicensing-to-cc-by-sa-and-making-it-visible-in-schema-metadata.md", "text": "https://wpnews.pro/news/relicensing-to-cc-by-sa-and-making-it-visible-in-schema-metadata.txt", "jsonld": "https://wpnews.pro/news/relicensing-to-cc-by-sa-and-making-it-visible-in-schema-metadata.jsonld"}}