Where your announcement actually goes.
Not a number we cannot substantiate. A named list, a capped count, and a plain account of what each placement does and does not do for you.
“Distributed to 400+ outlets” is the oldest lie in this industry
You have seen the claim. Every wire service makes it. What it usually describes is an automated feed dump into a network of low-traffic syndication sites that no human reads, built to produce an impressive-looking report rather than an audience.
It stopped working as a search tactic over a decade ago, when search engines discounted syndicated release links and began expecting them to be marked as sponsored. It never worked as a readership tactic, because nobody was reading.
So we do not make the claim. Here is what actually happens instead.
Running a publication or a trade site? Every release here is available as a feed, as JSON and as a widget, with no account and no permission needed. Feeds, API and republishing terms →
The automatic layer
This runs on publication for every announcement we carry, at every tier, without anybody pressing anything. It is a build step, not a service we perform by hand.
Search engine push notification
On publication your URL is submitted through IndexNow to Bing — and, in the same request, to Yandex, Naver and Seznam — rather than waiting for a crawler.
Why it matters: ChatGPT's search layer runs on Bing. Reaching Bing quickly is one of the few levers that genuinely affects AI answer visibility. The other three engines come free in the same request and matter only if you sell into those markets.
Real-time feed notification
Our RSS feed declares a WebSub hub and pings it on publication, so subscribers are notified in seconds rather than whenever they next poll.
Why it matters: aggregators and readers that subscribe get your announcement in seconds, not hours.
Syndication feeds
RSS plus a JSON API — all releases, optimized only, featured, and one endpoint per category — that any publisher, aggregator or site can consume. Plus a free embeddable widget.
Why it matters: this is the actual substrate of syndication on the web, and it is how anything reaches anywhere.
Machine-readable site summary
Optimized and Network releases are described in the file AI crawlers look for to understand what a site contains.
Why it matters: being described is different from merely being crawlable.
/api/, and a build step that fires both on every publish. You
can verify each of these yourself rather than taking our word for it.
The placement layer, capped at three
At the Network tier your release is placed on named properties where the subject is genuinely relevant. Editorial pickup on Action Global News, plus up to two further properties matched by sector and geography.
How matching works
- By sector. A home services announcement goes to home services properties. A technology announcement does not.
- By geography. A Denver business reaches Colorado properties, not Hawaii ones.
- By format. Each placement is labeled as an announcement and canonically linked back to the original here, so there is never ambiguity about which version is authoritative.
One submission. Five places that matter.
Why Bing is the one that matters. ChatGPT’s search layer runs on Bing’s index, and DuckDuckGo, Yahoo and Ecosia source their web results from it too. Reaching Bing quickly is one of the few levers that genuinely moves AI visibility.
What to expect, honestly
Submitted immediately
Your URL is pushed to participating search engines the moment it publishes. The submission is deterministic infrastructure and it always happens. What each engine then does with it is their decision, not ours, and we will not pretend otherwise.
Subscribers accumulate
Feeds gather subscribers as a wire matures. Anyone claiming a new wire has a large subscriber base on day one is describing something else.
Pickup we do not control
We cannot promise a newspaper runs your story. Nobody can. Any service claiming guaranteed national pickup is selling a number, not an outcome.