The CODEW — Press Release Intake Policy

 Last Updated: July 15, 2026

What we accept

1. Press releases from tech companies (AI, SaaS, cloud, enterprise software, Tech M&A) that are genuinely newsworthy to our audience of IT decision-makers, agency owners, and SMB founders.
2. Product launches, funding announcements, partnership/acquisition news, major feature releases — anything that fits our existing beats.
3. We do not accept a release "in exchange for" future favorable coverage — that conversation belongs in the Sponsorship Program track instead, not editorial.

Disclosure rules

1. Paid, sponsored, or affiliate-linked releases must carry a clear "Sponsored" or "Paid Content" label, visible before the reader reaches the body copy. This applies to anything tied to an active affiliate/sponsorship relationship (e.g. SignNow, Automattic).
2. Unpaid but company-sourced releases: label as "Press Release" or "Company Announcement" so readers know it originated from the company, even though no money changed hands.
3. Independent reporting: no label needed — this is our own original analysis/reporting, even if it references a press release as a source.

Rewrite checklist (before publishing any press release)

1. Never publish wire copy verbatim — always rewrite in house style (Arial, black/white, flat HTML, no external fonts/CSS blocks).
2. Add original framing: why does this matter to an IT decision-maker, agency owner, or SMB founder specifically?
3. Pull one quote with context (not just restating the company's boilerplate quote block).
4. Add a closing line of independent analysis or implication — this is what separates us from a syndicated wire feed and helps with on-page SEO (duplicate-content risk if left verbatim).
5. Confirm the correct label is applied per the Disclosure Rules above.
6. Follow standard Blogger conventions: slug, meta description, and labels set in the Post Settings block; retain the existing slug if this replaces or updates a prior draft.

Layout

• Standard sidebar layout applies to press-release-based posts unless the release includes a large table (e.g., pricing tiers, comparison data) that needs full-width space.