About this site
Editorial policy
Official pages first, our test log second, community reports third. Every number is dated. Corrections are logged in public, with old and new values.
We rank sources in a fixed order: the vendor’s official page first, our own test log second, community reports third. Every number on the site carries a date. This page sets out the rules as of 2026-10-21, including how we log corrections.
Where our facts come from
As of 2026-10-21 we use three source types, in this order.
- Official vendor pages. Pricing, help center and terms of use, saved with the crawl date. Plan prices and limits come only from here, for example the plan prices from higgsfield.ai/pricing, crawled 2026-10-20.
- Our own test log. Model names, credits charged, tries and failures from runs on our own account. What a run actually charged comes from here, not from the price list. The method is on the How we test page.
- Community reports. Posts by users, always attributed and linked, always worded as a report: “users on r/X report …”. We never present a community number as a vendor fact.
Where no source confirms a claim, we write "not verified as of <date>“. Where we did not run a test, we write ”not tested". We never fill a gap with a plausible number.
The "checked <date>" convention
Since 2026-10-21, every price, credit amount, limit or duration shows the day we last confirmed it, in ISO format, next to the number. Example: “Starter costs $19 per month billed annually (higgsfield.ai/pricing, checked 2026-10-20).” The same figure, with its check date, sits on our page of Higgsfield plan prices.
We do not write “today”, “currently” or “this year”. A reader who opens the page months later sees the date and can judge the age of the number.
Promotions rotate, so we re-verify prices and free limits at least every 30 days. A price table whose date is older than that is stale, and we flag it for review.
The fact-check pass before anything is published
Before a page goes live, an editorial review pass checks four things against the saved source or the log.
- Every number matches the archived page or the log line it came from.
- Every test claim has a log entry: model, date, credits, tries.
- Every vendor claim is attributed to the vendor.
- Every gap uses the fixed wording above.
The check covers the title, the meta description, the structured data and the image captions, not only the body. Pages with tables show the line "Checked <date> by editorial review“. Pages carry the byline ”Editorial team".
How we treat community reports
A community report is a lead, not a fact. We use it to decide what to test and what to look up on the vendor’s page. Each citation names the forum and links the thread with its date. The claim itself is labeled as reported.
If a report contradicts an official page, we show both versions and say which one we could test. We do not average them. If we cannot test it, the line reads "not verified as of <date>".
How AI assists our writing and how it is checked
As of 2026-10-21 our pages are machine-assisted. A language model drafts and edits the text, and an automated workflow submits our test jobs to the vendor on our account. Prices come from vendor pages and test results from the vendor’s job records. The model supplies no number of its own.
Every number and test claim is checked against its source in an editorial review pass before publication. Drafting and review are machine-assisted, as described above. We invent no reviews, testimonials or expert names. The fictional test character is never presented as a person.
Do commissions change what we write?
No. Some links to vendors are commission links, which would pay us if you subscribe through them. As of 2026-10-21 no commission program is active for us; the status and the exact wording are on the affiliate disclosure page.
A commission never decides a verdict. We test vendors the same way whether or not they run a partner program. Free routes come before paid ones on our pages. Where a competitor is cheaper or better, the page says so. We do not publish a discount percentage or a code we have not verified.
Corrections and change log
Since 2026-10-21, we fix a confirmed factual error on the page and log it here with its old value. We do not edit past values silently. To report an error, email info@copythetrend.com with “Correction” in the subject, plus the page, the line and a source. The contact page explains what else to include.
Each row has five parts: date, page, what changed, old value to new value, source.
Date | Page | What changed | Old to new | Source |
|---|---|---|---|---|
2026-10-20 | Higgsfield pricing | Plan prices recorded for the first time | none to $19 Starter (270 credits), $47 Plus (1,200 credits) and $99 Ultra, all per month billed annually | higgsfield.ai/pricing, crawled 2026-10-20 |
2026-10-21 | Test log | First test session logged, 16 charged runs | none to 24.98 credits charged | Our test log, 2026-10-21 |
Dates in this table are the day the change was made. No factual corrections have been needed yet, as of 2026-10-21.
Checked 2026-10-21 by editorial review.