Corrections, missing detail, dead links and licensing requests all go through the form below. This page explains what to put in one so it can be acted on.
Last updated: September 2026
In This Article
The Form
This form is the only contact channel for the site. There is no phone line and no separate press address.
The rest of the page is about what to put in it, because a report with the URL and the exact sentence in it can be checked, and a report without them usually cannot.
What to Include, by Message Type
Different messages need different detail. The table gives the minimum that makes each one usable.
| Message type | What to include | What is done with it |
|---|---|---|
| Factual correction | The article URL, the exact sentence you are flagging, what is wrong, and the source you are working from | The claim is checked against the source, and the article is edited if the source holds up |
| Missing or unclear information | The article URL, the question you came with, and where in the page you expected the answer | Treated as a gap in the article and queued with the next revision of that page |
| Broken link or broken page | The URL you were on, the link text you clicked, and what you saw instead | The link is repointed or removed, and a broken page is repaired |
| Image problem | The article URL and what is wrong with the photograph, such as a cheese shown that is not the cheese named | Checked against the article and replaced or recaptioned |
| Licensing or reuse request | Which articles, where they would appear, in what language, and for how long | Assessed against the reuse rules in the terms of use |
| Privacy request | Enough detail to find the message you sent, such as the approximate date and subject | Handled under the privacy policy, which also says which requests go to Google instead |
| Unauthorised or broken ad | The page URL, what the ad showed, and a screenshot if you have one | Checked against the one publisher ID named in ads.txt and reported to Google if it does not match |
A screenshot helps for anything visual, and it settles ad reports faster than any description can.
Reporting an Error
Most reports fail for the same reason: they name the topic but not the sentence.
The full address, not the article title. Several cheeses share a name across countries, and the URL removes the guesswork.
Paste the words as they appear. A long article can carry the same claim in three places, and the quoted sentence points at the one you mean.
Name the part that is incorrect rather than the feeling that something is off. A wrong milk type, a wrong ageing minimum and a wrong region are three different repairs.
A protected designation of origin specification, a dairy board page, a producer's own documentation or a food authority page carries the most weight. Personal experience is still worth sending, and it changes how the claim is worded rather than whether it stands.
Reports that arrive in that shape can be verified without a second exchange, which is the whole point of the format.
What This Address Can and Cannot Help With
Being clear about the second list saves you writing a message that has no good answer.
Worth sending
- A factual error in an article, with the sentence and a source.
- A question an article raised and did not answer, which is useful even when we cannot reply to you directly.
- A dead outbound link, a broken page, or an image that does not match the cheese named.
- A licensing or translation request, with the detail listed in the table above.
- A privacy request about a message you previously sent.
- An ad that looks wrong, misleading, or sold by anyone other than the publisher named in ads.txt.
- A producer correcting the record about their own cheese, including production detail we have wrong.
Not something this site can do
- Medical, dietary or allergy advice. Nobody here is qualified to give it, and the terms of use set out why.
- Ruling on whether a specific cheese is safe in pregnancy. That depends on the label and the handling of that wheel, so it is a question for the label and your doctor or midwife.
- Judging whether a cheese in your fridge has spoiled. A description cannot replace your own nose and eyes, and the use-by date settles it.
- Valuing, authenticating or appraising a cheese, a wheel or a collection.
- Selling you cheese. This site runs no shop, takes no orders and processes no payments.
- Guest posts, link insertions, sponsored articles and paid placement. None of these are accepted, which the affiliate disclosure covers in full.
- Offers to trade links or place marketing copy. These are deleted unread.
How Corrections Work
A correction is a change to a claim that was wrong. A clarification is a change to a claim that was right but easy to misread.
Both are made in the article itself rather than in a note somewhere else, because the wrong sentence is what people find in search results and quote later.
A substantive change is dated on the article, so you can see that the page moved.
Typographical fixes, formatting repairs and dead-link swaps are made without a dated note, since nothing about the meaning changed.
Where a claim turns out to be contested rather than wrong, the article says so and names both positions instead of picking the tidier one.
The editorial policy sets out how sourcing and review work across the site.
Before You Write
Four questions have a faster answer somewhere else on the site.
- Is this cheese safe for me? The packet label and its allergen statement answer this, and no general guide can.
- Can I reuse your content? The reuse table in the terms of use answers this without an exchange for anything marked yes.
- What data does this site collect? The privacy policy lists every cookie, who sets it, and how to turn it off.
- Do you earn money from your recommendations? The affiliate disclosure covers every revenue source and the status of each.
What Happens to What You Send
The form runs on Contact Form 7, which passes your message to email and keeps no copy in the site database.
That means the message lives in an inbox, and the privacy policy covers how long it stays there and how to ask for it to be deleted.
Do not send medical records, payment details, passwords, or anything else sensitive through this form. It is a plain contact form on a website, and nothing about it is built to hold that kind of information.
Send only what a correction or a request actually needs, which is usually a URL, a sentence and a source.
Common Questions
You can send it, and a photograph settles far less than people expect. Rind colour, wedge shape and paste texture repeat across dozens of cheeses, so a label or a shop name identifies it much better than an image.
No. Every article on the site is written and edited in house, and unsolicited drafts are not read.
Coverage cannot be bought, and no pitch changes that. A producer correcting a factual error about their own cheese is a different matter and is genuinely worth sending.
Yes. Printing and saving pages for personal or classroom use is allowed, and republishing them anywhere is not.
Through this form for anything you sent us, and to Google for analytics and advertising data. The privacy policy splits the two.
Found something wrong in an article?
The URL, the exact sentence, and what is wrong with it. That is the whole report.