wp cookie-consent scan
wp cookie-consent scan --format=csv
wp cookie-consent status
wp cookie-consent export > consent-record.csv

scan prints the services it found, then a second list, Not recognised: each other site's host, the page it was seen on, an example address and via, which is src for a tag's own address and snippet for one found inside a snippet pasted into the page, for the ones nobody has held back or left alone yet. With --format=json, csv or yaml it prints one list, so the output is one document: the services, then each of those other sites as a row of its own, with its host under service, Not recognised under kind, NO under held back and the page under found on. With --not-recognised it prints only the other sites, each with the page, an example address and via (wp cookie-consent scan --format=json --not-recognised). status has a row, Addresses not looked at, with how many are waiting, the ones the reading had no room to list included, or Not read yet when the last reading did not look for them. Its Last reading row says Up to date, Not read yet, or that the last reading, or some of its pages, was made by an earlier version that looked for less, and your site should be read again.

scan reads the site the same way as Read my site, so it also clears a note the monthly reading left on the Dashboard.

export writes the record a thousand rows at a time, the way the download on the Record screen does, so a full record never has to fit in memory. An empty record prints nothing and warns that there is nothing in it.

From the command line