Editorial Standards

Editorial Standards and Brand Safety

These standards describe how review content is produced, approved and corrected in our publisher partnerships and client engagements. They are operating procedures that we apply and document, not a legal guarantee. Where a publisher holds approval rights under its agreement with us, those rights take precedence.

Standards

ES-01

Authorship and accountability

Every article names the people responsible for it: the writer, the editor who approved it and, where relevant, the specialist who verified market-specific facts. Authors are real people with relevant experience; we do not publish under invented names or attribute work to people who did not do it.

Within a publisher partnership, the section states that it is operated by Tallwood Media in partnership with the publisher, so readers know who is accountable for the content.

ES-02

Review methodology

Each review type has a written methodology: the criteria, how they are weighted, what evidence is required and how the verdict is reached. The methodology is published in summary on the section and applied consistently across reviews of the same type.

We state how an assessment was done. If a review is desk-based, it says so. We do not claim hands-on testing, registration or purchase unless that test took place and is recorded.

ES-03

Sources and verification

Factual claims are checked against primary sources: regulators' registers, the provider's own published terms, official documentation and our own recorded tests. Secondary sources are used for context and are cited. Where a claim cannot be verified, it is removed or clearly qualified.

ES-04

Dates and updates

Every article shows when it was published and when it was last reviewed. Reviews are re-verified on a schedule agreed for the section and whenever a material change is reported, such as a change of licence, terms or availability. Material updates are recorded in a change log.

ES-05

Editorial approvals

Nothing is published without an editor's approval. In publisher partnerships, the approval workflow is agreed in writing before launch and specifies who reviews, approves and updates each type of content. The publisher retains the approval rights set out in the agreement, including the right to reject a piece or require changes.

ES-06

Commercial disclosures

Readers are told, in plain language and in a consistent position on the page, when content includes commercial placements or affiliate relationships and how the section is funded. Disclosure wording is agreed with the publisher. Commercial relationships never determine a verdict, and the methodology applies equally to partners and non-partners.

Paid or sponsored links carry rel="sponsored" (or rel="nofollow" where required). Sponsored content is labelled as such.

ES-07

Corrections

Anyone can report an error to [email protected]. We acknowledge reports within two working days, investigate against the sources and correct confirmed errors promptly. Material corrections are noted on the page; minor typographical fixes are not. Within partnerships, corrections follow the procedure and timelines set out in the agreement, and the publisher is informed of material corrections.

ES-08

Complaints

Complaints about accuracy, fairness, disclosure or the suitability of content are handled by a named editor who was not involved in producing the piece. Complainants receive a written response. Where a complaint is upheld, the content is corrected, amended or removed, and the outcome is recorded.

ES-09

Access and brand-safety controls

Access to a publisher's systems is limited to named accounts with the minimum permissions needed for the agreed scope, reviewed regularly and removed when roles change or a partnership ends. Either party can pause a piece under dispute while it is resolved. We do not describe any of this as “100% safe” or as approved by a search engine; brand safety means documented controls, applied consistently and open to audit.

Regulated topics

Additional Controls for iGaming and Betting Content

Gambling content is regulated differently in every market. Before any iGaming or betting review section launches, we agree the following with the publisher and record the outcome in the partnership documentation.

This is our operating process. It is not a statement that the activity is lawful in every country: country-specific requirements are assessed and defined in the agreement and in the specification of the relevant vertical.

Admissible markets

Which markets the section may address, based on the regulatory position, the publisher's audience and the disclosures each market requires. Markets outside the agreed list are not targeted.

Operator approval

Which operators and products may be reviewed or placed commercially, with licensing status checked against the relevant registers before publication and re-checked on a schedule.

Age-appropriate targeting

Content, placement and promotion are designed for adult audiences only. Age restrictions are stated where required, and no content is aimed at or styled for minors.

Mandatory disclosures and responsible-play messaging

Regulatory notices, responsible-play resources and commercial disclosures required by the market are included in the agreed wording and position, and reviewed when regulations change.

Escalation and stop procedure

Named contacts on both sides, a route for urgent regulatory or reputational concerns, and the ability to pause or remove content immediately while a question is resolved.

Scheduled review

The market list, operator list and disclosure wording are reviewed on a fixed schedule and whenever the regulatory position changes, with changes recorded.

Contact

Report an Error or Raise a Concern

Corrections and complaints: [email protected]. Please include the page URL, the statement you believe is wrong and, where possible, a source. We acknowledge every report within two working days.

If you are considering a review section for your publication, these standards and your own approval rights are written into the partnership documentation before launch.