1. Why this exists
By default FIRECRUX crawls your pages: it fetches HTML, parses meta and content,
builds a link graph. The WordPress plugin is the easiest alternative — instead of us crawling,
the plugin reads your content straight from WordPress and pushes it to the panel. No API to build,
no developer time: install, activate, pair, done.
Scope: the plugin replaces the content crawl of your pages. Data from Google Search Console / Analytics
and search volumes stay with our own integrations — the plugin doesn't touch them.
Prefer to expose your own endpoints instead of installing a plugin? Use the
API integration guide — the same data, exposed through your own endpoints.
2. Requirements
- WordPress 5.6+ with PHP 7.4+ and admin access.
- HTTPS on the site (outbound calls to the panel use TLS).
- Optional: WooCommerce — when present, products and product categories are detected automatically.
- Optional: a supported SEO plugin (Rank Math, Yoast or SEOPress) — the plugin picks up the SEO title and meta description managed by it; when missing it falls back to the post title and excerpt.
3. Download the plugin
Download the latest plugin package (.zip) — you upload this file in WordPress in the next step.
↓ Download FIRECRUX plugin (.zip)
Version: … · Build date: …
SHA-256: …
If the button doesn't start the download, copy the link and open it in a new browser tab.
4. Install & activate
- In WordPress: Plugins → Add New → Upload Plugin.
- Choose the
.zip you downloaded and click Install Now.
- Click Activate.
A top-level Firecrux entry appears in the WordPress admin menu (with
Projects / Data / Settings subpages).
5. Pair with the panel
Pairing links this WordPress site to your client in the panel — once per client.
Every crawl target of that client then uses this single connection (no per-target pairing).
- In the panel open the brand settings → Integrations tab → WordPress plugin section and click Generate token.
- In WordPress (wp-admin) open the Firecrux tab and choose "I have a pairing token".
- Paste the token from the panel (the Backend URL is usually pre-filled) and confirm the pairing.
- The panel section updates automatically to Paired when it succeeds.
The token only authorizes this site to send content for this client.
You can regenerate it from the panel at any time (Repair / regenerate token) — the old one stops working immediately.
The client can also Remove pairing from the panel or disconnect inside the plugin.
6. Content classification & crawl attachment
After pairing you decide in the panel what gets fetched and where the pages land.
Everything happens in the Integrations tab, in the Content classification section:
- Set the classification — assign each WordPress content type and taxonomy a
kind
(Post / Product / Post category / Product category / Other) and save your changes.
Unclassified rows are skipped.
- Each classified row shows a link icon:
orange = crawling not attached,
green = active. Click it to
attach fetching to a category — pick an existing category of the same kind
or create a new one (the name is proposed from the kind). One category can hold
at most one WP Plugin crawl config. The same dialog is where you
disable crawling for a row.
- Data arrives either manually — Integrations → Crawl targets → Synchronize —
or automatically with the nightly sync (the following evening).
- If the client previously had other sources configured (e.g. HTML crawling of the same pages),
deactivate or remove the old crawl data configs to avoid duplicating data.
Changing a classification detaches crawling: when you change the kind of a row that
already has an attached crawl, saving disables its fetching (the panel warns before saving) — re-attach
the row with the link icon afterwards.
7. What we fetch
After pairing the plugin reports which content types your site exposes and sends, per page:
| Content type | Mapped to kind | Source |
|---|
| Posts | POST | WordPress posts |
| Pages | OTHER | WordPress pages |
| Products | PRODUCT | WooCommerce (if installed) |
| Categories / taxonomies | POST_CATEGORY / PRODUCT_CATEGORY | classified in the panel (Integrations) |
For each page the plugin sends the same fields the contract expects: id, url, title,
h1, the main content as HTML, meta_description, canonical_url,
modified_at, status and kind. Navigation, header and footer are stripped — only the
substantive content is sent. Field-level details are in the API integration guide.
8. Incremental sync
The plugin doesn't resend everything every time. It tracks the last-modified date per page and only sends
what changed since the previous sync, plus it reports deletions so the panel can drop removed pages. Heavy content
(content_html) is only sent for pages that actually changed.
9. Security
- Outbound only: the plugin pushes to the panel over HTTPS; the panel doesn't need inbound access to your site.
- Scoped token: the pairing token authorizes content sync for this one client and nothing else.
- Rotation: regenerate the token from the panel whenever you want; re-paste it in the plugin.
- Published only: drafts, private and trashed content are never sent — only
published.
- Data sharing is opt-in (plugin 1.2.6+): cookie-consent statistics and the access log are off after installation. You switch them on in Firecrux → Settings → Data sharing; each switch says what is sent, where and why, and can be turned off at any time. The plugin also adds suggested wording for your own privacy policy under Settings → Privacy in WordPress.
- Legal: Plugin privacy notice · Plugin terms of use.
10. Troubleshooting
| Symptom | Fix |
|---|
| Status stays Waiting for plugin | Re-check the Backend URL and token in Firecrux → Settings, then click Pair now again. |
| Status shows Error | Regenerate the token in the panel (Repair / regenerate token) and paste the new one. |
| Products not listed | WooCommerce must be active. Reload taxonomies in the panel (Integrations) after activating it. |
| Categories missing | Classify the relevant taxonomies in the panel (Integrations → classification) — unclassified ones are skipped. |
11. Checklist
- WordPress 5.6+ on HTTPS with admin access
- Plugin
.zip downloaded (§3) and uploaded via Plugins → Add New → Upload Plugin
- Plugin activated
- Token generated in the panel (Integrations → WordPress plugin) and pasted into the plugin ("I have a pairing token")
- Pairing confirmed — panel shows Paired
- Classification set and saved in Integrations (§6)
- Crawling attached with the link icon on every type that should be fetched (icons green)
- Sync started manually (Crawl targets → Synchronize) or left for the nightly run
- Old crawl data configs deactivated if they duplicated the same pages