What we're building. And why.

This page serves two audiences at once. For customers and evaluators, it's a commitment signal: the product is being built with intent, and the team is transparent about what's in-flight vs. speculative. For the dev team, it's a scoping compass: every item is tagged with the existing primitive it builds on, so nothing here asks for greenfield engineering when an adjacent service already exists.

The framing (tool + playbook + consulting) is shaped by the copy plan dated 2026-04-22. The plugin automates the repeatable work; the playbook tells clients when a human should step in; our consulting is one of the handoff destinations. Roadmap items are evaluated against that shape: does this strengthen one of the three lanes, or blur them?

Principles that govern what gets on this list

• Ship what Search Console actually supports. If a metric isn't available via the GSC Search Analytics API, we don't promise a product feature around it. “Impressions on AI Overviews” is a current research bet because Google surfaces it; “rank #1 on ChatGPT” is not on this roadmap because no primary-source data backs it.
• No feature we can't evidence. Every item names the primitive in Plugnrank-app it extends, or it's flagged as research. We would rather cut an item than add a checkbox that misrepresents scope.
• Consulting is a first-class lane, not a fallback. Items that only make sense with a human operator (auditing brand voice, interpreting ambiguous signals, rewriting YMYL-sensitive copy) stay in the Consulting lane and don't get re-scoped as plugin features just because it's easier to sell self-serve.
• Transparency over polish. Rejected and deferred items stay visible at the bottom of this page. Users deserve to see what we considered and didn't pursue, along with why.

In active development: next ~30 days

Items here have a branch, a ticket, or a working prototype. They are not promises of a shipping date, but of an allocation.

This quarter

Items here have design intent and a rough scope but aren't in-flight yet. Sequencing may shift based on Now-lane completion and customer signal.

Beyond this quarter: directional

These are active bets but don't yet have commitment-level detail. Exact scope depends on research outcomes and what Now/Next teaches us.

Out of scope (deliberate non-goals)

These are not on the roadmap, and this section exists so the decision is visible instead of silently dropped.

• “Rank guarantee” features of any form. No feature will promise a specific ranking, position, or visibility outcome. The legal and epistemic cost outweighs any conversion lift.
• Backlink exchange / PBN-adjacent tooling. Would clash with client sites' E-E-A-T exposure and Google's link-spam policy.
• One-click Google-Ads / paid-media orchestration. PlugnRank is organic-growth infrastructure. Paid-media tooling is a different product that different people operate; we would rather integrate with an existing ads platform than rebuild it.
• Self-serve “generate 1000 posts and auto-publish” mode. Would contradict the plugin's daily-limit posture (1/5/15 per plan) and the whole “automation inside guardrails” positioning.

How this roadmap is maintained

• Reviewed monthly by the product lead. The “Last updated” field above is the authoritative freshness signal.
• Items move Later → Next → Now based on two checks: (1) is there a named owner, and (2) is the primitive it builds on still stable? If a primitive is being rewritten, dependent roadmap items pause until the rewrite lands.
• Completed items graduate to the product changelog (not listed here; the roadmap is forward-looking by definition).
• Rejected items migrate to “Out of scope” above with a one-line reason.

Pointers