Carbon.txt
carbon.txt is a single, recognisable place on your website, at https://your-site.com/carbon.txt, where anyone can find out what your organisation publishes about its own environmental impact. This plugin builds that file for you. You describe your disclosures (the public documents where you report y
carbon.txt is a single, recognisable place on your website, at https://your-site.com/carbon.txt, where anyone can find out what your organisation publishes about its own environmental impact.
This plugin builds that file for you. You describe your disclosures (the public documents where you report your sustainability data) and the plugin turns them into a valid carbon.txt , served straight from your site.
What you can do with it:
- Add your disclosures. One or more links to the documents that back up your claims: your annual report, your sustainability page, a certificate, and so on. Each one gets a document type, so readers know what they are looking at.
- Point at any document. Paste a URL, pick one of your published pages, or choose a file from your media library.
- Record your certifications. If your organisation holds a certification (a B Corp, an ecolabel, an ISO standard), list it once and link your disclosures to it.
- Preview before you publish. The settings screen shows the exact file that will be served, so you always know what visitors will get.
- Start from what you already have. If a carbon.txt already exists on your server, the plugin can read it and offer to import what it finds.
- Keep a copy. Your disclosures stay saved when you deactivate the plugin, and you can copy or download them at any time.
How it works
Document types. The picker offers the document types the carbon.txt syntax defines. The Green Web Foundation has deprecated the “web page” type in favour of “sustainability page”, so it is no longer offered, and new disclosures start at “sustainability page”. Disclosures that already use “web page” keep working. They are labelled as deprecated in the editor, so you can move them on when you get the chance.
Required fields. A disclosure needs a URL, and a certification needs a title and a URL. Anything still missing one of those is skipped when you save. The editor marks every field as required or optional, and tells you what was left out.
Certifications. Each certification you list gets an id generated from its title, and your disclosures reference that id. Only complete certifications appear in the list you can choose from, so a half-finished one never shows up as a blank entry.
