Editorial Policy

MorseCoder publishes a free International Morse translator and learning pages. This policy explains how we source claims, what we will not invent, and how to request a correction.

1. Who writes

Site copy is published under the MorseCoder organization name. We do not attach a personal amateur-radio callsign, Extra Class credential, or university degree to the byline. If a page used those claims in the past, they were unverifiable and have been removed. See About.

2. Morse accuracy

Character maps and dit/dah ratios are checked against ITU-R M.1677-1 (International Morse). American Morse is documented only as a historical contrast on the comparison page. Audio WPM is a practice approximation in the browser — not a calibrated laboratory instrument.

3. What we will not publish

• Fabricated testimonials, star ratings, or Review / AggregateRating schema.
• Unverifiable traffic stats (“millions of operators,” “#1 translator”).
• Borrowed FCC callsigns or academic identities.

4. AI assistance

Drafting tools may help with outlines or copy editing. Published pages are reviewed for ITU accuracy and for identity honesty. AI is not used to invent sources, callsigns, or user reviews.

5. Corrections

If a timing table, history date, or identity statement is wrong, write via the contact page. Material corrections get an updated “Last verified” date on the page and a note on the changelog.

6. External standards we cite

When we describe timing, spacing, or the international character set, we point to ITU-R M.1677-1. Licensing and on-air etiquette references defer to national regulators and the ARRL learning hub for U.S. readers. Historical claims link to Wikipedia or museum sources rather than unattributed anecdotes.

7. Advertising and thin pages

Google AdSense may appear on long-form guides and tools with substantial original explanation. Legal pages, contact forms, and embed iframes stay ad-free because they lack publisher content. We do not use noindex to hide thin drafts — we expand pages or consolidate them with honest redirects instead. A page that shows ads is expected to teach something a visitor can use: a pattern, a timing rule, a practice step, or a limit of the tool. Contact, privacy, terms, and the embed widget stay outside that rule. If a new tool page is too short to explain itself, it is expanded before ads are left on. The build checks that an ad page still has a few hundred words of visible explanation, so a stub cannot ship with an ad script by accident.

8. Tools vs. claims

Microphone decoders, image flash scanners, and quizzes run client-side. Their accuracy depends on microphone quality, lighting, and operator skill. We describe limits plainly (for example WAV download instead of mislabeled MP3 files) so users are not misled about file formats or performance.

9. Updates

Substantive rewrites receive a new “Last verified” month on the page and, when user-facing, a bullet on the changelog. Automated build checks enforce minimum article length on ad-enabled URLs so we do not rely on noindex to hide thin drafts. A correction that changes a timing table or an identity statement is recorded on the changelog in the same month.