Newsroom & Press Releases

The newsroom is a full press room for your site: press releases with their own URL space, a public index and feed, media kits journalists can download, reusable boilerplates and press contacts, and a double–opt-in journalist subscriber list. Releases live under /press on your site, alongside your blog and docs.

It is a first-class content type — not a collection and not a component — so it comes with everything a modern newsroom needs: scheduled and embargoed publishing, correct NewsArticle structured data, RSS/Atom/JSON feeds, and a machine-readable .md mirror for AI crawlers.

New to the newsroom? Publish your first press release walks the whole flow once, end to end. This page is the reference for everything in it.

Writing a release

Go to Content → Press → New release. A release has:

a title, subheadline, and a URL slug,
a rich-text body (headings, lists, links, images, quotes),
a dateline (city + date) — rendered on the release and emitted in structured data,
a release type: press release, statement, media alert, or newsbyte,
an optional boilerplate (a reusable "About us"), media kit, and press contacts,
a hero image, and full SEO fields (title, description, social cards).

There is no "FOR IMMEDIATE RELEASE" ceremony in the default template — just a clean dateline, boilerplate, and contact block. That is what modern corporate newsrooms actually ship.

Publishing, scheduling, and embargoes

A release is draft, scheduled, embargoed, published, or archived.

Publish now puts the release live under /press and in your press feed.
Schedule sets a future go-live time; the release flips to published automatically at that moment — no one has to be at a keyboard.
Embargo holds a release back until a lift time, while letting you share a private preview link with named journalists. Each journalist gets their own expiring token, so a leak is attributable, and the preview page is marked noindex so it never reaches search engines. At the embargo lift time the release publishes automatically.

Media kits

A media kit is a downloadable bundle — logos (PNG, SVG, EPS), executive headshots, product photos, fact sheets — packaged as a single ZIP your visitors can download in one click. You build the kit; nothing is pre-filled.

Downloads are ungated by default. Journalists on deadline should never hit a form wall to get your logo — so they don't have to. (You can opt into gating if you need it.)
Downloads are counted, and file sizes render human-readable so people know what they're getting.
Size ceiling: real kits run comfortably from a few MB up to ~80 MB. Very large bundles (over ~100 MB) can be rejected at the network edge before they reach us — keep a kit under 100 MB, and split unusually large asset sets into more than one kit.

Press contacts and boilerplates

Press contacts are named people with a title, email, region, and beat — so a release can list the right regional or topic contact instead of a generic inbox.
Boilerplates are reusable, versioned "About X" blocks. Write one once, mark a default, and attach it to any release.

Journalist subscribers

Reporters can subscribe to your newsroom to be emailed when you publish.

Double opt-in: they sign up, confirm by email, and only then start receiving releases — the standard that keeps your sender reputation clean.
One-click unsubscribe is on every message (required for good deliverability and GDPR posture).
Publishing a release notifies confirmed subscribers automatically.

Discoverability — search engines and AI

The newsroom is built to be found, by both search engines and AI systems:

NewsArticle structured data with a dateline on every release page — the correct schema.org type for news (there is no PressRelease type), and one most newsrooms get wrong. See Search Engines.
Feeds: /press/feed.xml (RSS), plus Atom and JSON variants, including per–release-type feeds.
A .md mirror: append .md to any release URL (/press/your-release.md) to get clean Markdown — the format AI crawlers and LLMs ingest best. Combined with llms.txt, this makes your newsroom machine-readable for the tools that increasingly surface news. See AI Crawlers (llms.txt).

Structured data must be enabled for your site for the NewsArticle markup to emit — see Search Engines. llms.txt full-content mode is opt-in per site.

Start from a template

You do not have to lay the page out yourself. Six one-click newsroom templates are published in the marketplace. Apply one and you get a working press room built from the same blocks you would have assembled by hand.

Every template adopts your own site's palette, typography and navigation — none of them carry baked-in colours, so a template designed on a dark background still looks right on a light site. What differs between them is the composition: which blocks appear, in what order, and how the releases list is laid out.

Template	Best for	What you get
Newsroom	Most sites	The original one-page press room — releases list, coverage marquee, media kit, press contact and an about/fact-sheet section
Newsroom — Minimal	Solo founders, quiet brands	A single column. Releases as a flat reverse-chron list, one media kit, one contact, a boilerplate. No hero, no clutter
Newsroom — Startup (dark)	Bold, high-contrast brands	A full-width announcement hero, coverage marquee ranked high as social proof, and a changelog-rhythm release list with type badges
Newsroom — Startup (light)	Clean, light brands	The same launch-led composition, tuned so the media kit stays legible on a light palette
Newsroom — Agency	Studios and creative shops	An editorial cover, releases as a picture-led card grid, and the media kit front-and-centre as a thumbnail grid. Two contacts — press and new business
Newsroom — Corporate	Enterprises with a filing cadence	Your built-in `/press` route renders the register: a featured latest release, real type-filter links, and a year-grouped list. Applying the template adds the media-resources companion page — regional press offices, boilerplate, fact sheet and a coverage wall

To apply one, open Design → Marketplace, pick the newsroom template you want, and apply it. An agent can do the same thing with apply-site-template. See Marketplace.

Corporate is worth one extra note: it is the only template that is two halves. Your /press route already renders the filterable, year-grouped register — that part is built in and a template cannot improve on it. So the Corporate template deliberately leaves the register alone and gives you the media-resources page that sits beside it.

Your media kit starts empty — that is expected

A freshly applied template shows an empty media kit. That is deliberate, and it is not a bug.

Earlier versions of these templates shipped with placeholder assets — a sample headshot, a fake "download all" — which looked convincing enough that a live page could advertise files that did not exist. We removed them. A template will never publish an asset you did not upload.

So after you apply a template, populate the kit yourself:

Go to Content → Press → Media kits and create a kit.
Upload your logos (PNG, SVG, EPS), executive headshots, product photos and fact sheets.
The block on your newsroom page picks them up and renders them.

Until you do, the kit block shows a short "no media assets published yet" line instead of a fake one.

With the CLI or an agent

The whole newsroom is agent-native — an AI agent can run it end to end, which no traditional newsroom vendor offers.

CLI — manage releases, contacts, boilerplates, and kits under the spideriq content press command group.
MCP / agents — 27 press_* tools let an agent draft, schedule, embargo, publish, and attach media entirely on its own. For example: "Draft a launch announcement dated in San Francisco, attach the product media kit, schedule it for 9am Tuesday, and send me the preview link."

See Overview and The CLI to get set up.