Skip to content
FeedFast
Get started

WordPress

Your changelog, your board and your status — inside wp-admin.

Paste an API key once. After that the feedback people left, the release notes you publish and whether your site is actually up all live in the dashboard you already have open — and the widgets go on your site with a block, not a theme edit.
Start freeRead the docs
FeedFast for WordPressA free plugin, on the WordPress plugin directory

Three steps, about five minutes

  1. 01Install the plugin from your WordPress dashboard.
  2. 02In FeedFast, create an API key under Settings → API keys.
  3. 03Paste it, pick your project, and drop a block where you want a widget.

Requires WordPress 6.4+ and PHP 8.0+. GPLv2 or later.

In the dashboard

Four screens, and none of them make you open another tab

The reason a WordPress site owner ignores their feedback board is that it lives somewhere else. This puts it where the rest of the work already happens.

Overview

Current uptime, open incidents, the top feedback by votes and the latest changelog entry — one screen that answers whether anything is on fire and whether anything is new.

Feedback

The board as an ordinary WordPress list table, with the status, category and sort filters you would expect. Change a status, reply in public, or resolve a request and publish the release note in the same step.

Changelog

Every entry, and a Markdown editor for new ones — as a draft, or published straight to your hub page, RSS feed and every embedded widget at once.

Uptime

Monitors with their uptime windows, latency and last check. Open incidents, the history behind them, and scheduled maintenance with the next window called out.

An outage finds you, rather than the other way round

A dashboard widget, a coloured dot in the admin bar whose menu names the next maintenance window, and an admin notice when a monitor goes down. There is also a Site Health entry reporting the connection, the key’s scope and the last successful sync — so “is this still working” has an answer you can point at.

On your site

Place a widget without editing a theme

The embed script is only loaded on pages that actually use one of these — and never in wp-admin.
  • A site-wide “What’s new” badge, with its corner, theme and accent colour set from the settings screen.
  • Blocks for the changelog, the uptime bars, a feedback button and a public roadmap.
  • Shortcodes for the same four, if you would rather stay in the classic editor or a page builder.
  • Three sizes of uptime widget — full, compact bars, or a one-line badge sized for a footer — and you tick which monitors appear.
  • Any navigation menu item can become a feedback trigger or a “What’s new” opener.
  • Publish a WordPress post to your changelog from a box on the post editor — the content is converted to Markdown for you.

How it behaves

A plugin should be boring about your site

Three decisions that matter more than any feature on this page.

  1. Your API key never reaches a browser

    It is stored server side with autoloading off and used only by PHP. Everything your public pages need comes from the public widget payload, which needs nothing but the project slug. Load a page with every widget enabled and search the source — the key is not in it.

  2. No front-end page waits on the network

    FeedFast is never called during a page load. Responses are cached in transients — uptime for a minute, feedback and changelog for five — and refreshed in the background on an interval you set, or not at all if you would rather it did not run.

  3. It fails quietly

    When FeedFast is unreachable, admin screens fall back to the last known data and say so. A read-only key hides every write control instead of offering a button that fails. Uninstalling removes its options, transients and cron events.

Questions

Questions people ask first

Do I still need a FeedFast account?

Yes. The plugin is a client for FeedFast, not a copy of it — it reads and writes one FeedFast project through the API. Without an account and a project there is nothing for it to show. The free plan covers one project.

Where does my API key live?

In your WordPress database with autoloading off, used only by PHP. It never appears in page source, in an enqueued script, in a block attribute or in a REST response. Your public pages only ever carry the project slug.

Does it slow my site down?

Nothing is fetched from FeedFast during a front-end page load. Everything public comes either from the embed script your visitor's browser loads, or from data cached in WordPress ahead of time by a background refresh you control. The embed script is only enqueued on pages that use a widget, and never in wp-admin.

What happens if FeedFast is unreachable?

Admin screens fall back to the last known data and say so. Nothing white-screens and no front-end page waits on the network.

Can I give it a read-only key?

Yes, and it behaves properly: full read access with every write control hidden, rather than a button that fails when you press it.

Does it work with WP-CLI?

Yes — wp feedfast status, feedback list, changelog publish and refresh.

Is anything sent about my visitors?

No. Your visitors' browsers load the widget payload from FeedFast directly, which needs only the project slug. There is one optional setting, off by default, that passes a signed-in WordPress user's name and email to the feedback form so it can pre-fill — it never applies to logged-out visitors.

WordPress is one of several ways in — see all integrations.

Five minutes from a fresh install to a live hub

Create a project, generate a key, paste it into WordPress. The free plan covers one project, one monitor and fifteen changelog entries — no card.

Start freeSee the widgets