CSRD Digital Sustainability Reporting: What Your Website Emissions Mean

The Corporate Sustainability Reporting Directive (CSRD) is now in force, and for thousands of companies filing their first sustainability reports in 2026, the question is increasingly urgent: does our website count? The short answer is yes — and for high-traffic sites, it is a material Scope 3 emission source that must be quantified, documented, and tracked consistently across reporting periods.

Digital emissions — website traffic, software infrastructure, employee devices — sit within Scope 3 of the GHG Protocol and fall squarely inside the ESRS E1 standard that governs climate reporting under CSRD. The ICT sector as a whole currently accounts for 2–4% of global greenhouse gas emissions, comparable to commercial aviation, and enterprise technology alone generates an estimated 350–400 megatons of CO₂e annually. Regulators have taken notice. This guide explains exactly what CSRD requires for digital emissions, how to calculate your website's carbon footprint to satisfy an auditor, and which tools make the process defensible.

What CSRD Actually Requires for Digital Emissions

CSRD does not contain a specific chapter on websites. What it contains — through the European Sustainability Reporting Standards (ESRS) — is a requirement to disclose all material emissions sources across Scopes 1, 2, and 3, with consistent methodology and year-over-year comparability. Whether website emissions are material depends on your business, but for any company serving more than a few hundred thousand pageviews monthly, the numbers accumulate fast enough to matter.

The governing standard is ESRS E1, which requires:

• Gross emissions disclosure — Scopes 1, 2, and 3 must be reported separately. No netting against offset purchases. The gross figure is what enters the report.
• Consistent methodology — The quantification approach must be stated and applied the same way in each reporting period. Switching methodologies between years without explanation is a disclosure failure.
• Transition plan with interim targets — Companies must demonstrate a credible 1.5°C-aligned reduction plan. Digital optimisation — reducing page weight, switching to green hosting, retiring unused infrastructure — can and should feed into these targets as documented, quantified actions.
• Double materiality assessment — You must assess both the impact your operations have on the environment (inside-out) and the environmental risks that could affect your business (outside-in). For a high-traffic website, both directions are relevant.

Where does a website fit in the Scope 3 categories? The answer depends on context. For a company whose website is a distribution or sales channel, the energy consumed to serve users is typically Scope 3, Category 11 (Use of sold products) or Category 1 (Purchased goods and services, covering the hosting contract). The important thing is consistency: pick the right category, document it, and use it every year.

The CSRD Timeline: Who Reports When

The reporting wave structure has been revised by the Omnibus I regulation, approved by the EU Parliament in December 2025. The current picture for 2026:

The Omnibus revision raised the immediate threshold significantly — from the original 250-employee cutoff to 1,000 employees combined with a €450M turnover requirement. If your company sits below that combined threshold, you are likely looking at FY 2027 as your first reporting year under revised ESRS standards. That said, investors, procurement teams, and supply chain partners are already asking for this data regardless of your legal obligation. Getting ahead of the requirement costs little and creates durable competitive advantage in ESG-conscious procurement.

France also maintains its own REEN Act (Loi REEN, November 2021), which specifically targets digital sobriety for large French companies and public bodies. REEN requires organisations to establish digital environmental footprint reduction strategies and measure the energy consumption of their digital activities. It is narrower in scope than CSRD but was an early signal of where EU-wide regulation was heading — and it covers companies that might otherwise fall below the CSRD threshold.

How to Calculate Website Carbon Emissions for CSRD

The published methodology most suited to CSRD compliance for website emissions is the Sustainable Web Design Model v4 (SWDM v4), developed by Wholegrain Digital and cited by the majority of credible sustainability tools. It is fully documented, uses publicly sourced coefficients, and produces a figure in grams of CO₂ per pageview that can be multiplied by traffic data to produce an annual total.

The formula:

CO₂ (g) = page_weight_GB × 0.194 kWh/GB × 494 gCO₂/kWh × (1 − green_factor)

Breaking it down:

• 0.194 kWh/GB — the aggregate energy coefficient across three segments: data centres (0.055), network transmission (0.059), and end-user devices (0.080). The full methodology behind these coefficients is covered in the SWDM v4 deep-dive.
• 494 gCO₂/kWh — the world average grid carbon intensity, sourced from Ember Climate. This is the conversion factor between electricity consumed and CO₂ emitted.
• green_factor = 0.243 — applied if your hosting provider is verified as renewable by the Green Web Foundation. This 24.3% reduction reflects the lower carbon intensity of renewable-powered electricity relative to the global grid average. Zero if the host is not verified.

For a concrete example: a page weighing 2.5 MB (0.0025 GB) on a non-green host emits 0.240 gCO₂ per pageview. A site with 500,000 monthly pageviews — 6 million annually — produces approximately 1,440 kg CO₂ per year from that single page alone. For a site with multiple high-traffic pages at heavier weights, total annual emissions can reach several tonnes.

That figure — expressed in kg CO₂ per year — is what enters your Scope 3 inventory. The data source for annual pageview volume should be documented (GA4, Plausible, or server access logs are all acceptable) and applied consistently. On the full measurement guide, you will find a step-by-step breakdown of how to collect the data and apply the calculation across multiple URLs.

What a CSRD Auditor Actually Needs from You

Sustainability auditors are not primarily checking whether your emissions are low. They are checking whether your methodology is defensible and consistently applied. For website carbon data, that means providing:

1. Methodology statement — Name and version of the quantification standard used (SWDM v4, version 4), with a citation to the source document.
2. Per-URL measurements — Page weight (KB transferred), CO₂ per pageview (g), and hosting green status for each material URL. “Material” typically means your highest-traffic pages — the top 10–20 URLs usually account for 70–80% of total traffic.
3. Annual CO₂ total — Weighted average CO₂ per pageview × annual pageview volume from your analytics platform, expressed in kg CO₂.
4. Hosting verification — Green Web Foundation status for your primary hosting provider, with a screenshot or API query result dated to the reporting period.
5. Year-over-year comparability — The same methodology applied in the same way. If page weight changes (due to optimisation or added content), that is fine — what must not change without documentation is the formula or the coefficients.
6. Reduction actions documented — For your transition plan, a record of what was done: image format migration to WebP/AVIF, hosting provider change, JavaScript bundle reduction, script removal. Each action with an estimated CO₂ impact. The reduction playbook covers each lever with impact estimates.

This is precisely the data structure produced by a formal website sustainability audit. For companies in CSRD scope or approaching it, commissioning a professional audit once — to establish the methodology baseline and produce defensible documentation — followed by self-maintained quarterly monitoring is the practical approach most ESG teams adopt.

Integrating Website Carbon Into Your Broader Scope 3 Inventory

Website emissions are one component of a company's digital Scope 3 footprint. A complete digital emissions inventory for CSRD purposes would typically cover:

• Website traffic — Calculated via SWDM v4 as described above. Often the most tractable component because it is fully measurable with standard analytics.
• Employee devices — Laptop, mobile, and monitor energy consumption during work hours. Estimated using average wattage figures from IEA device databases and annual working hours.
• SaaS and cloud services — Energy consumption of the cloud infrastructure your applications run on. Major cloud providers (AWS, Google Cloud, Azure) publish carbon reporting APIs; smaller providers typically require estimation from billing data and average PUE figures.
• Business software and internal tools — Development, testing, CI/CD pipelines, internal communication platforms. Less directly measurable but increasingly expected as part of a complete digital inventory.

Website traffic is typically the starting point because the data is accessible, the methodology is published, and the number is directly actionable — every optimisation you make has an immediate and measurable impact on the figure. It is also the component most likely to be externally visible: the Carbon Badge embedded on your site signals your commitment to measurement transparency and gives you a publicly citable baseline. For the regulatory landscape specifically, the explainer on website carbon footprints and regulations provides full context on CSRD, REEN, and how they interact.

Practical Steps for CSRD-Ready Website Carbon Reporting

The process is straightforward once you know what is needed. Here is the sequence most compliance teams follow:

Step 1: Baseline Measurement

Run a full scan of your website’s key URLs using the Carbon Badge scanner. For each URL, record: page weight (KB transferred), CO₂ per pageview (g), letter grade (A–F), and hosting green status. Do this in the same month each year — ideally at the start of your fiscal year — so the baseline is comparable. Export the data to a spreadsheet; you will need it for the auditor.

Step 2: Annual Traffic Pull

Pull annual pageview data by URL from GA4 or your preferred analytics platform. For CSRD, full-year data (January to December, or your fiscal year equivalent) is what you need. Export URL-level data, not just a site total, so you can weight the CO₂ calculation by actual traffic distribution.

Step 3: Annual CO₂ Calculation

Multiply: CO₂ per pageview (g) × annual pageviews per URL. Sum across URLs. Divide by 1,000,000 for tonnes CO₂. That is your website’s annual Scope 3 contribution. Document the calculation in a tab of the same spreadsheet, with formula references visible — auditors want to follow the arithmetic.

Step 4: Reduction Actions

Before the next reporting cycle, implement and document at least one reduction action. The highest-impact single action for most sites is image optimisation — converting hero images and blog thumbnails to WebP or AVIF typically reduces image payload by 30–50%, directly cutting page weight and therefore CO₂. The tool comparison covers what each available scanner measures and how to choose the right one for ongoing monitoring. The green hosting guide covers how to verify and switch providers if hosting is your weak point.

Step 5: Continuous Monitoring

Carbon Badge’s Pro and Business plans offer scheduled scans with automatic alerts when a page’s CO₂ rises above a defined threshold — typically triggered by a CMS update adding a new video, a marketing team embedding a third-party widget, or a plugin update that ships heavier assets. Catching these regressions between annual baseline measurements is what keeps your reported figures accurate rather than aspirational. The Business plan is sized for the multi-domain monitoring that most CSRD-affected companies need across their full web estate.

Why CSRD Is an Opportunity, Not Just Compliance

The companies treating CSRD as purely a compliance burden are missing something. The process of measuring, documenting, and reducing digital emissions creates internal visibility into your website’s technical health that most organisations have never had. Page weight analysis surfaces the same inefficiencies that hurt Core Web Vitals scores and, by extension, search ranking. Hosting green status assessments open procurement conversations about energy contracts and data centre PUE. Third-party script audits routinely find 2–4 scripts per site with no identifiable business owner and no measurable value — scripts that are removed with zero business impact and immediate carbon benefit.

CSRD compliance for digital emissions, done properly, is a forcing function for technical quality. The Business and Enterprise plans are designed for exactly this use case: multi-domain monitoring, scheduled reporting, and the data export formats your ESG team needs to feed into your annual sustainability report without manual reconciliation.