Roadmap

These docs describe what AffRank does today. This page is where everything else lives, so nothing elsewhere in the documentation has to hedge.

It mirrors the roadmap in your dashboard.

No dates, no promises

Nothing unfinished here is committed or scheduled. AffRank is built by one person, and the order is driven by what customers actually ask for. Treat anything marked “not yet” as unavailable rather than imminent — please do not buy a plan on the strength of it.

Phase 1 — Core Foundation

Complete. The tracking and injection engine everything else builds on.

	Capability	What it does
✅	Session + source attribution	Know where every click comes from — Google, Reddit, direct
✅	Placement detection	Know where on the page clicks happen: inline, sidebar, comparison table
✅	Click context capture	See the surrounding text and anchor text that drives clicks
✅	Revenue dashboard with charts	Bar and donut charts, expandable click detail with full context
✅	Per-link SEO settings	Nofollow, sponsored, noindex, cloaking, new tab — per link
✅	Global link settings	Default cloaking prefix, SEO attributes, link categories
✅	Script injection engine	Auto-inject affiliate links, heading exclusion, keyword matching
✅	Domain & script management	Add and verify domains, generate your tracking script
✅	Revenue mapping by source & placement	Clicks broken down by source, page, keyword and placement
⬜	Redis performance layer	Faster redirects, caching and rate limiting

Phase 2 — Money Visibility

In progress. Turning clicks into an answer about what actually earns.

	Capability	What it does
✅	Postback / conversion tracking	Match affiliate commissions back to clicks via postback URLs
✅	Placement ROI	Compare intro vs. sidebar vs. comparison table
✅	Offer performance	Compare which offers convert best
✅	Source quality scoring	See which traffic sources bring buyers
⬜	Top money pages	See which pages make the most revenue
⬜	Link usage map	See every page each link appears on

Phase 3 — Actionable Insights

Planned. Plain-language suggestions, not dashboards to interpret yourself.

	Capability	What it does
✅	Rule-based recommendations	Plain-language suggestions, no jargon
✅	Dead offer detection	“High clicks but zero conversions”
⬜	Low click rate alerts	“This page gets traffic but no clicks”
⬜	Top placement insights	“Comparison tables convert 3x better”
⬜	Source intent scoring	“Google traffic has the highest buying intent”

Phase 4 — Link Health + Protection

Planned. A broken money link is the most expensive thing on your site.

	Capability	What it does
✅	Automated link checking	Detect 404s, redirect loops and broken destinations
✅	Health status flags	Healthy / Broken / Slow at a glance
⬜	Alert system	Get notified when a money link breaks
⬜	Scheduled monitoring	Background checks on a schedule

Phase 5 — Advanced

Future. Nothing here is started.

	Capability	What it does
⬜	A/B link routing	Split traffic between offers automatically
⬜	Geo routing	Route visitors to region-specific offers
⬜	Multi-offer optimization	Auto-promote the highest converting offer
⬜	Network normalization	Unified reporting across affiliate networks

Also not available

Common requests that are not on the roadmap above:

Public API. AffRank is script-based — you install one tag and everything happens automatically, so there is no API to call today. Programmatic link management and click-data access is the most frequent request.

Webhooks. No way to have AffRank notify your systems when a click or conversion is recorded. Export CSV from the Analytics Dashboard instead.

Multiple injections per page. Only the first occurrence of each keyword is linked, and that is not configurable.

Regex or fuzzy keyword matching. Keywords match as exact, case-insensitive phrases — VPN service does not match VPN services. Add both as separate links.

Scheduled or expiring links. The Active toggle is manual; links cannot activate or deactivate on a date.

Team accounts. One login per account. No way to invite a VA or a partner with their own credentials.

Status history. The status page checks live on each load and keeps no history, so there is no uptime percentage or incident timeline.

How to influence this list

The support form is read by the person who builds the product, not a queue:

Send feedback →

A request several people send in moves up; a request nobody sends in does not get built. If something is missing that you expected to find, that is worth saying even if you assume we already know.