These Good Practices describe what we expect from the press releases and RSS/Atom feeds carried on PPN World. They exist for one reason: journalists rely on the feed. Every feed submitted through our form is reviewed by a human against these guidelines before it is listed, and listed feeds are expected to keep meeting them — feeds that persistently don't may be throttled or removed, as set out in section 7 of the Terms of Service. Questions or corrections: info@ppnsource.com.
1. Accuracy and sourcing
A press release is a public statement of record. Facts, figures, quotations and claims must be accurate at publication and attributable: name the organization speaking, quote real, identified people with their title, and source any statistics or study results (who measured it, when, and where the full data lives). Do not publish speculation as fact, invent quotations, or announce products, deals or results that are not real. Material claims about health, finance or safety carry the highest bar — if a claim would need a citation in a newspaper, it needs one in your release.
2. Clear, honest headlines
The headline must say what happened, in plain language, in under about 120 characters where possible: who did what. Avoid clickbait, ALL-CAPS words, exclamation marks, unexplained superlatives ("revolutionary", "world-leading") and headlines that bury the news behind the company name. A journalist scanning 500 headlines a day should understand yours without opening it. The first paragraph should then answer who, what, when, where and why — not restate the boilerplate.
3. Dateline and dates
Open the body with a standard dateline — "MONTRÉAL, July 11, 2026 —" — naming the city the news originates from and the publication date. PPN World places releases on its live map from this dateline, so use the place of the news, not your PR agency's or distributor's head office. Write dates in full (day, month, year) somewhere in the release; "today" alone becomes meaningless in an archive. If the release is embargoed, do not publish it to your public feed before the embargo lifts — an RSS feed is publication.
4. Contact information
Every release must end with a working media contact: a named person or press office, a monitored email address, and ideally a phone number and the organization's website. Journalists on PPN World use these contacts to verify and follow up — a release nobody can call back on is a dead end. Keep the contact block current across releases, and remember that published press contacts may appear in PPN World's press-contact directory, as described in our Journalist & Press Contact Notice.
5. No spam or keyword stuffing
A feed must carry news, not noise. Do not: republish the same release repeatedly or in near-duplicate variants; stuff headlines or body text with SEO keywords, ticker symbols or link farms; pad the feed with content that is not a press release (job ads, product listings, blog roundups); or issue "releases" whose only purpose is backlinks. Volume is not the goal — a feed that publishes two real announcements a month is more valuable than one that publishes twenty rewrites. Feeds used primarily for search-engine manipulation are removed.
6. Disclosure of paid or sponsored content
Say who is speaking and who paid. A release issued on behalf of a client must identify that client; paid partnerships, sponsorships, paid endorsements and investor-relations promotion must be disclosed in the text, not hidden in a footer. Releases about securities must comply with the applicable securities regulations, including any required disclaimers and disclosure of compensation for coverage. Undisclosed advertorial dressed up as news is grounds for removal of the release and, if repeated, the feed.
7. Corrections
When a published release contains a material error, correct it visibly: publish a corrected version marked as such ("CORRECTION — …" in the headline is the wire standard) or a follow-up release identifying what changed, rather than silently editing or deleting the original. Keep the item's identity stable in your feed (see feed hygiene below) so the correction supersedes the error downstream. If a release we display needs correcting or removing, write to info@ppnsource.com with the release URL and we will act promptly.
8. Feed hygiene (technical requirements)
Your RSS or Atom feed is the contract between your newsroom and ours. Before submitting, check that it meets these requirements — they are what our reviewers test first: - Valid, standards-compliant RSS 2.0 or Atom XML that passes the W3C feed validator, served over HTTPS with a stable URL. - One item per release, with a stable, unique GUID (or Atom id) that never changes for a given release and is never reused — unstable GUIDs create duplicates for every reader downstream. - A full timestamp (pubDate / updated) with date, time and time zone on every item, matching the actual publication time. - A real headline in <title>, the release text (or a substantial, clean excerpt) in <description> or <content:encoded>, and a <link> pointing to the release's own public page — not to a homepage or a tracking redirect. - Correct character encoding (UTF-8), no raw HTML soup in titles, and reasonable item weight — the aggregator caps oversized responses. - Keep the feed reachable: allow standard aggregator user-agents, avoid aggressive bot-blocking on the feed URL, and keep at least the last 20–50 items in the document so short outages don't lose releases.
9. Review, fees and enforcement
Every submitted feed is reviewed by a human against these practices; we may decline a feed without stating a reason, and listing of commercial feeds may be subject to fees, always communicated before anything is charged. After listing, feeds are monitored automatically and editorially. Releases or feeds that breach these practices may be de-prioritized, reduced to snippet display, suspended or removed at our discretion, per section 7 of the Terms of Service. These practices evolve; the version published at this page is the one in force.
Contact
info@ppnsource.com