Editorial standards

PeakBot, the company. Posts carry the “Peak Team” byline because that is accurate: they are written and edited in-house, with AI assistance in drafting. You should read anything here about PeakBot as coming from the people who make it, with the bias that implies.

We do not attach invented author names, fictional credentials, or made-up years of experience to posts. If a post ever carries a person’s name, it will be a real person who actually worked on it.

• Claims about PeakBot are checked against PeakBot. If a post says a setting exists, that setting exists in the dashboard, with the name and the default the post gives. A post promising a feature we have not shipped is treated as a bug, not a marketing choice.
• Competitor pricing is dated and hedged. Other bots change their plans without telling us. Where we quote a competitor’s price we say when it was checked, and you should verify it on their site before acting on it.
• Third-party tools have to be real. We only name a bot we can confirm exists, and we do not describe its features or pricing in detail unless we can check them. Where we cannot, we link the directory category so you can look for yourself.
• Internal links have to resolve. Links to other posts are checked against the actual set of published slugs.

• Reviews or testimonials we made up. No invented quotes from “a server owner with 18,000 members”, and no star ratings we awarded ourselves in structured data. We have found and removed both from this blog before; the checks below exist because of it.
• Statistics we did not measure. No “in our community of 500+ servers, 70% of admins…”. If we cite a number about our own users, it comes from something real, or it does not run.
• Bots that do not exist. Recommending invented tools wastes your time and, because search engines then quote us as the source, pollutes results for everyone.

Some of the above is enforced by a script rather than by memory. Our repository runs a set of content gates that fail the build-time check if any of these patterns reappear: self-awarded ratings, testimonials attributed to unnamed people, sentences citing first-party research we never conducted, references to review pages that do not exist, and pricing wording that implies one payment covers multiple servers.

They exist because the same problem came back three times in three different shapes, and each time a person had to notice it. A check that runs every time is better than a person who is paying attention most of the time.

If something here is wrong, tell us and we will fix it. The fastest route is our Discord server. Corrections to factual claims are made in place, and where a correction changes the substance of a post we say so in the post.

That applies to competitors too. If you work on MEE6, Dyno, Carl-bot, Arcane, ProBot, Sapphire or Wick and we have described your product inaccurately, we would rather hear it from you than leave it wrong.