Editorial Guidelines

These are the rules we hold ourselves to. We publish them so readers can judge whether a page is trustworthy and so editors know exactly what is expected before a page goes live.

Voice

Neutral, practical, direct, calm. We answer the question early. We do not pretend to be a vet, a farmer, or an expert beyond what our sources support. We do not use breathless or cutesy language.

Source standards

For health, safety, toxicity, and disease topics, we prefer:

• University extension services (e.g., poultry.extension.org)
• Veterinary schools and poultry-science departments
• Government agriculture and food-safety agencies
• Recognized poultry and veterinary organizations

We use forums, Facebook groups, Reddit threads, and personal blogs cautiously, and never as the main authority for a safety claim.

Page structure

• Every page leads with a direct answer.
• We use tables, checklists, and step lists where they help the reader.
• FAQs answer the questions a reader is most likely to type next.
• Long pages get a Table of Contents.
• Every page lists its sources and the date it was last reviewed.

Problem and health pages

Pages about sick or injured chickens use "possible causes include" language. We do not diagnose. Every health page includes a clear note that the page is general education, not a substitute for a poultry veterinarian.

Review cycle

Pages show a "Last reviewed" date in the byline. We review pages on a rolling basis and update the date when content changes meaningfully. Editorial corrections are made in place; significant corrections are noted.

What we don't do

• Mass-publish thin pages to chase keywords.
• Use AI-generated copy as the final article without human review and source-checking.
• Run health claims past affiliate or product opportunities — safety wins.
• Use HowTo, FAQPage, or other structured-data markup on content that isn't actually a how-to or FAQ.

Reporting a problem

If you find an error, a stale source, or a page that needs review, please tell us via the contact page. We take corrections seriously.