Competitive

Competitive is the tab (under the Research surface) where you track competitor positioning. Add a competitor URL, audit it on demand, keep history per competitor, and link competitors to projects so their audits show up in the project’s Competitive tab and feed comparisons. Its sibling tab, Market, is the market-landscape view — see Market Research.

It’s intentionally separate from your Landing Pages list. Landing Pages are yours — audited as the system-of-record for your own positioning. Competitors are someone else’s URLs you’re benchmarking against — audited because you want a foreign baseline, not because you’re shipping copy.

How competitors work

A competitor is an org-level record — one row per (organization, url). Multiple projects in the same org can reference the same competitor without duplicating audits or quota. That’s the whole point of org-scoping: when your team adds “Acme Cloud” once, every project that benchmarks against Acme uses the same competitor row and the same audit history.

A competitor record carries:

The URL and an optional label (e.g., “Acme Cloud” rather than the raw URL)
A pointer to the most recent successful audit run (latest_audit_run_id)
All historical audit runs (kept indefinitely, like Landing Page history on paid plans)

Older runs aren’t deleted when you re-audit — they stack up so you can watch a competitor’s own positioning drift over time, the same way Monitors show your drift on your pages.

Audit on demand

Competitor audits are manual by default — there’s no scheduled monitoring on competitors the way there is for your own Landing Pages. Click Run audit on a competitor record and PlumPMM scrapes + audits the URL using the same 13-dimension pipeline as a Landing Page audit. Same scoring, same ~30s wall time, same audit-unit cost (1 per run).

You can re-audit whenever — to refresh after a competitor relaunches, to compare new copy against your own latest, or just to keep the trail current.

Linking competitors to projects

A project_competitor link is the join between a competitor and a project. Same competitor, multiple projects. Two reasons to link rather than just track org-wide:

Per-project label override — “Acme Cloud” might be your Direct competitor in one project and your Adjacent competitor in another. The link row carries an optional label_override to capture that framing.
Project-scoped views — the project workspace’s Competitive tab only shows linked competitors. Keeps the per-project context tight; the org-wide list lives on the Research surface itself.

Unlinking a project_competitor doesn’t delete the underlying competitor or its audit history — those persist at org level for any other project to use.

Quota — distinct from Landing Pages

Competitors are not counted against your max_landing_pages cap. There’s no separate “max competitors” limit either — the throttle is the audit-unit budget. A competitor audit costs 1 audit-unit, same as any other audit, and rolls up to your monthly quota.

Action	Audit-units
Add a competitor	0 (no audit until you click Run)
Run a competitor audit	1
Re-audit a competitor	1
Compare competitor to your URL	1 (the Audit Compare narrative call)

Practically: a Solo Founder org with 100 audits/month can comfortably maintain 5–10 active competitor benchmarks alongside its own Landing Page work without straining quota.

Plan availability

Every paid plan supports Competitive research. Free users can see the Research nav but most actions there require paid-plan audit budget.

Competitors and Audit Compare

Once a competitor has an audit, you can vs.-Competitor compare any of your URLs (or draft preview audits) against it. The compare shows up in the same Orchestrations → Audit Compare list as your other compares, tagged as the cross-page kind. → Audit Compare