---
title: "Scan a website with the GreenWashing scanner"
description: "How a scan runs, how to choose which sections of the site to include, and how to read the report's score, priority actions and proposed fixes."
type: "help"
url: "https://www.conphora.com/help/greenwashing/run-a-scan/"
markdown: "https://www.conphora.com/help/greenwashing/run-a-scan.md"
locale: "en"
language: "en"
updated: "2026-09-10"
author: "Conphora support"
publisher: "Conphora"
tags: ["help", "greenwashing", "member"]
license: "Free to quote with attribution and a link to the page"
---

# Scan a website with the GreenWashing scanner

> How a scan runs, how to choose which sections of the site to include, and how to read the report's score, priority actions and proposed fixes.

## In short

Open the scanner at platform.conphora.com/go/greenwashing, enter your website's address, tick the sections to scan, and the platform reads up to your plan's page limit and produces a report with a compliance score, problematic pages and a concrete fix per claim.

- Scan stages: queued · discovering · choose folders · running · done.
- Every finding names the page, the claim, the potential violation and a proposed solution.
- The report is indicative and must be reviewed before you act on it — it is not legal advice.

## What the scanner checks

The GreenWashing scanner reads pages on your own website and flags environmental claims that are vague, unsubstantiated or absolute — "eco-friendly", "climate neutral", "100 % sustainable" — against the rules on misleading environmental claims. It is a tool for the organisation's own site or webshop; it is part of the subscription. The background on the rules is public at [/tools/greenwashing](/tools/greenwashing).

## Starting a scan

Go to [platform.conphora.com/go/greenwashing](https://platform.conphora.com/go/greenwashing). Enter the website address (for example `example.com`) and choose **Run scan**. The hub shows your plan's page limit per scan and the scans left this month.

The scan first **discovers** the site: it reads the sitemap and top-level sections. It then pauses at **Choose folders** and lists the sections it found (homepage and top-level, /products, /about, /blog, …) with the page count for each. Tick the ones to scan — unticked folders are skipped and remembered, so future scans of the same domain skip them automatically. "Will scan" shows how many pages that adds up to, capped at the plan limit. Choose **Scan selected**.

## While it runs

The scan moves through Queued, Discovering, Running and Done. Pages are analysed in parallel; a busy period can leave a scan queued for a few minutes. You can leave the page — a "GreenWashing scan finished" notification (or "scan failed") is sent when it completes, and the hub lists every scan with its status.

## Reading the report

The report opens with a headline:

- **Compliance score** and **risk level** (low, low–medium, medium, high) for the scanned pages.
- **Legal risk** — how exposed the claims are as they stand.
- How many pages were scanned, and whether the scan was truncated by the plan limit.

Below it, **Priority actions** lists the findings that matter most. **Problematic pages** groups the rest by page. Each finding has:

- the **problem** — the claim as written,
- the **potential violation** — which rule it is likely to conflict with, with a severity of high, medium or low,
- the **solution** — one of four: replace the claim with a more specific one, add context, tone it down, or remove it because it is too vague to document.

**Compliant pages** lists the pages with no findings, so you know what was checked and passed. The issue distribution shows how the findings spread over the site.

## What to do with the findings

Work from the priority actions down. A good order: remove absolute claims you cannot document, then add the missing context (which product, which part of the life cycle, which standard) to the claims you keep. Re-run the scan after the changes; the earlier scan stays in the list for comparison.

The report is indicative. It reads text on public pages and cannot see the evidence behind a claim, so a flagged claim may be fine with the right substantiation, and a clean page may still make a claim in an image. Have someone with legal responsibility review the findings before publishing changes.

## Limits and deletion

Pages per scan and scans per month depend on the plan and are shown on the hub. Deleting a scan removes its report permanently.

If a scan has sat in Running for more than 30 minutes, [send a request](/help/request) with the domain and the start time.