A well-written crypto press release can still fail at the final step if it doesn’t pass editorial review. Editors and distribution services reject releases for predictable and avoidable reasons: unverifiable data, unconfirmed partners, promotional language, incorrect images, or missing basic disclaimers.
This checklist covers the points that most often cause rejections in 2026. Use it as a final review before submitting any release. If you’re still in the drafting phase, you may also find this practical guide to AI tools for writing press releases useful, which explains how to generate quality drafts without falling into the generic tone that many editors discard immediately.
1. Verifiable Facts and On-Chain Data
Everything you claim must be verifiable within minutes. Editors do not accept “according to our estimates” without a source.
- Confirm the exact project name, token name, and ticker (they must match across the website, explorers, and social channels).
- Include contract addresses or links to explorers (Etherscan, Solscan, etc.) when discussing launches, upgrades, or metrics.
- Any number (TVL, users, volume, funding, supply) must include a measurement period and source (Dune, DefiLlama, audit report, official announcement).
- Clear dates: when the event happens, when a round closes, or when a listing goes live.
- If you mention an audit, link the full report and specify its scope.
A release that says “TVL of over $50M” without a link or date is often returned or heavily edited.
2. Confirmed Partners and Approvals
Mentioning an exchange, investor, auditor, or protocol without written permission is one of the most common causes of rejection or later corrections.
- Obtain written confirmation (email or message) from every named entity.
- Ensure the partnership or listing wording matches what was approved (scope, dates, pairs, etc.).
- Quotes must include full name, title, and organization, and be pre-approved.
- Silence is not approval. If there is no response, remove the mention.
This is especially important for exchange listings and funding rounds with well-known investors.
3. Disclaimers and Compliance
Crypto is a YMYL (Your Money or Your Life) sector. Language that sounds like investment advice or a promise of returns leads to immediate rejection at most serious outlets.
- Completely avoid: “guaranteed,” “risk-free,” “100x,” price predictions, “safe investment,” or calls to buy.
- Use neutral language: “announces,” “launches,” “integrates,” “according to data from…”.
- Add a standard disclaimer at the end:
“This release is for informational purposes only and does not constitute financial, investment, or trading advice. Cryptocurrencies involve risk of capital loss.” - For mining, staking, or token sales, include additional risk warnings and jurisdictional restrictions where applicable.
- Verify regulatory claims (“regulated,” “MiCA-compliant,” etc.) against official sources.
4. Technical Format (Word Count, Images, Links)
These are automatic or first-pass filters on most platforms.
- Length: Maximum 700 words on most wires (including headline and “About” section). Ideal: 400–600 words.
- Images: 1200 × 628 px is the most commonly cited size for social previews (some services request 1200 × 720 or a 16:9 ratio). High-resolution PNG or JPG with clear rights. Avoid using only a generic logo; prefer a graphic related to the announcement.
- Links: Maximum 3–5 depending on the service, all HTTPS and relevant (official website, docs, explorer, audit). One link every ~150 words is a good rule.
- Submit as plain text or .doc (avoid complex PDFs).
- Third person, no “we,” no exclamation marks, and no all-caps for emphasis.
5. Style, Language, and Structure
- Clear, factual headline (ideally 10–15 words) that states what happened, not just the project name.
- Lead paragraph that answers who, what, when, where, and why in the first 50–75 words.
- Zero hype: remove “revolutionary,” “game-changing,” “the world’s first” without proof.
- Real media contact (name + email that someone actually monitors).
- Short boilerplate consistent with the official website.
Quick Pre-Submission Checklist
- ☐ All numbers and claims have a verifiable source or link
- ☐ Partners, investors, and exchanges have approved the text
- ☐ Quotes are correctly attributed and approved
- ☐ Risk disclaimer is included
- ☐ No investment language or return promises
- ☐ Length ≤ 700 words
- ☐ High-quality, relevant 1200×628 (or 16:9) image
- ☐ Maximum 3–5 functional HTTPS links
- ☐ Active media contact
- ☐ Spelling, name consistency, and ticker review completed
Conclusion
Most rejections in crypto press release distribution do not happen because the announcement is bad, but because the release is not ready for editorial review. Validating on-chain data, partner confirmations, disclaimers, and technical specifications (especially the 1200×628 image and word-count limit) dramatically reduces back-and-forth and improves the chances of clean, fast publication.
In addition, a release that passes this filter has a better chance of being properly indexed and cited by AI models—an increasingly relevant factor. If you want to go deeper into how press release distribution contributes to authority and citations in the AI era, we recommend this article: How to Be Cited by AI (And Where Press Release Distribution Fits In).
Treat this checklist as the final mandatory step before any distribution. A release that passes this review arrives cleaner to editors and creates less friction with the distribution service.
