Integrate Prezly into your website
Learn how you can integrate your Prezly site and display your news feeds on your website
Integrating your Prezly sites and stories with your own external website makes the transition between your pressroom and your company site seamless. By default, your sites are on the prezly.com domain. e.g. yourbrand.prezly.com. You can easily replace this with a custom link on a domain that you own. e.g. press.yourbrand.com. For example, Toyota can set their site URL to press.toyota.com.
Having your site on your own domain looks more professional and passes on SEO value to your website. See how to set up a custom domain.
You can create a Prezly integration with your company's website in a few ways, as outlined below.
You will need some IT technical experience or help from your IT department to implement this.
1. RSS
It is a standard RSS feed that contains the title, link, and description of a story. You can access it by adding /feed.rss to your site URL. e.g. https://press.prezly.com/feed.rss
If you have a multilingual site, you can filter by language by adding the two-letter language code to the URL, e.g. https://press.prezly.com/feed.rss/en will retrieve the English story feed.
2. JSON (Recommended)
A JSON feed is similar to an RSS feed with the addition of a lot more details, such as the title, subtitle, preview image URL, intro, link, contact details, and so on. For a better, more solid integration, we definitely recommend using the JSON feed.
You can access it simply by adding /feed.json to your site URL. e.g. https://press.prezly.com/feed.json.
If you have a multilingual site, you can filter by language by adding the two-letter language code to the URL, e.g. https://press.prezly.com/feed.json/en will retrieve the English story feed.
Here's an example of how a Prezly client, dnata, uses JSON feeds to feature their Prezly stories at the bottom of their homepage.
Optional parameters for the feeds
parameter | value | description |
|---|---|---|
culture | en_US, fr_FR | 4 letter short code for language and country of that language. |
year | 2018, 2019 | 4 character number year notation. Only display stories from this specific year. |
tag | financial, lifestyle | Filter on specific tags you’ve added to your stories. You can use a comma separated list to filter on multiple tags at the same time. |
limit | 0–100 | An integer between 0 and 100 (the max amount of stories displayed). |
date_format | d-m-Y | Displays the date in day-month-year format. The PHP documentation shows all different available date formats. |
See the list of language codes and the PHP documentation.
Example 1: Returns a JSON with 5 English stories from 2015: https://press.prezly.com/feed.json?lang=EN&year=2015&limit=5
Example 2: Returns a JSON with the most recent Dutch story on 'Duurzaamheid': https://ikea.prezly.com/feed.json?lang=NL&category=Duurzaamheid&limit=1
If you'd want to get the feed in javascript (client side), you'll need to add an extra parameter named callback to the url: https://ikea.prezly.com/feed.json?callback=?&lang=NL&category=Duurzaamheid&limit=1
Story details
You can get the full details of a story in JSON as well. Just add .json to the permalink of your story. E.g. https://press.prezly.com/30-pr-pros-combine-forces-for-how-to-guide-on-tools.json
3. Use the Prezly API
Achieve almost anything in the app.
Some example use cases:
- Import your content into Prezly
- Segment your contact list
- Subscribe contacts to your CRM
- Feed coverage into your account
- Create a newsroom
Learn more here >>> Prezly API documentation
4. Build a custom theme
We allow you (or our internal service team) to build a custom theme, which is based out on our open-source Bea theme , making all customization and potential integrations possible.
5. Headless CMS pattern (API + webhooks)
Increasingly, customers run their own website as the public face of their brand and use Prezly as a headless CMS behind it — editors keep writing stories, sending pitches, and mailing from Prezly, while the stories themselves render on the customer's site.
How it works
- Author in Prezly. Your team continues to write, translate, and publish stories in Prezly as normal, and keeps using Prezly for distribution (email campaigns, contact management, pitches).
- Sync to your site. Your site picks up new and updated stories in one of two ways:
- Webhooks (recommended). Subscribe to story events and receive a push whenever something changes. See Newsroom webhooks.
- Polling the API. Periodically fetch the newsroom's stories endpoint if webhooks aren't an option.
- Render on your site. Your CMS stores and renders the story under your own URL structure.
- Tell Prezly the canonical URL. Send the public URL back to Prezly as the story's canonical link. This keeps SEO consolidated on your domain and lets Prezly route traffic correctly.
Why the canonical link matters
Every Prezly campaign, pitch, social post, and embed links to the story on its Prezly newsroom URL. Once a canonical is set:
- The Prezly story page can automatically redirect to the canonical URL on your site (newsroom setting — ⚠️ available soon, contact for early access). This means every link already sent out in past emails continues to work, landing readers on your CMS instead of the Prezly-hosted page.
- Search engines consolidate ranking signals on your domain.
What this requires from your side
- You must actually publish the corresponding story on your site before — or very shortly after — it's published in Prezly. If the canonical URL 404s, readers coming from past mailings will hit a dead page.
- Rebuild the story layout in your own CMS. Prezly's rich content (images, embeds, galleries, contacts) is available via the API, but rendering it is your team's responsibility.