301.st Documentation
Production guides for running redirects, conditional routing, and conversion attribution on your own Cloudflare account — without rebuilding your stack inside another vendor.
What 301.st Replaces in Your Day
If you manage redirects through Cloudflare Page Rules and a spreadsheet, change tracking via Slack, and attribution by exporting CSVs from each affiliate network — 301.st collapses that work into one panel that talks to your existing Cloudflare zones over the API.
The platform runs on top of infrastructure you already own. Nothing moves; we read and write through your Cloudflare token. The rollout order below is the fastest way to evaluate whether the trade is worth it for your team.
Best First Reading Order
- Getting started — sign-up to first live redirect in under 10 minutes.
- Cloudflare integration — the 5-minute API-token step that unlocks zone sync and bulk apply.
- Domain management — one inventory view replaces tab-switching across registrar dashboards.
- Projects and sites — containers that match how your business is organized (brand, market, team).
- Redirects — form-driven rules across all your Cloudflare zones, with T1–T7 templates covering the common shapes.
- TDS and postbacks — geo/device/UA routing plus drop-in attribution from affiliate networks.
Built For
- SEO webmasters and affiliate site owners running portfolios of multiple domains with regular redirect operations.
- Affiliate media buyers and arbitrage teams placing landing pages and routing paid traffic across geos.
- Agencies and infrastructure leads evaluating 301.st for client work or internal traffic management.
The Core Pieces, in the Order You Adopt Them
Integrations: connect what you already own
One Cloudflare API token gives 301.st read/write access to your zones — no DNS migration, no provider lock-in. Registrar integrations (Namecheap, NameSilo) layer in expiry tracking and renewal visibility so a missed payment stops being how you find out a domain is offline.
You can revoke access at any time from the integration drawer or from the provider side. Everything 301.st ever sees flows through the credentials you grant.
Domains: your portfolio in one dashboard
Synced domains land in a single filterable table — by status, health, provider, role, and expiry — with a per-domain inspector that surfaces DNS state and Cloudflare configuration. Bulk actions cover the painful parts: block, unblock, delete, and pointing site-less domains at a target.
That inventory is what everything else reads — projects, sites, redirects, TDS rules, postback sources. Configure once, reference everywhere.
Projects and sites: structure that matches your campaigns
Projects group related work — usually one per client, brand, or vertical. Sites declare a primary domain and bind redirects to it. Together they keep dropdowns short and filters meaningful once you pass a handful of domains.
Small setups can stay shallow — the "Default Workspace" project and its site come with the account, so the floor is one of each and you are already on it. The structure scales without forcing premature decisions.
Redirects: edge-speed rules across your portfolio
Define a rule from a template (domain-level, path-level, exact URL, maintenance page), pick the site, hit Save. Pending changes show a diff against what Cloudflare currently has; one Sync applies everything in batch. T1–T7 templates cover the shapes most teams need.
Bulk sync writes to all your Cloudflare zones from one place. Local edits stay versioned until you apply, so nothing reaches production by accident.
TDS: site-scoped split testing and routing
Smart Shield filters traffic by geo, device, OS, or bot signals; SmartLink routes by URL parameters (utm_source, fbclid, gclid). Rules bind to a site and deploy to a Cloudflare Worker on your acceptor domain — without you writing or operating the Worker code.
A/B splits, geo-splits, and conditional landing logic all live here — running on a Cloudflare Worker on your primary domain, your account.
Postbacks: conversion attribution from your affiliate networks
Each network you work with gets one postback source in 301.st — paste-ready URLs per event (Registration, FTD, Deposit, etc.) and a field map that translates the network's parameter names into a normalised conversions feed.
Conversions land in a live dashboard with attribution back to the originating click. It covers both traditional affiliate networks and 1Win-class operators that route each event to its own URL.
Integrations
Integrations: connect what you already own
One Cloudflare API token gives 301.st read/write access to your zones — no DNS migration, no provider lock-in. Registrar integrations (Namecheap, NameSilo) layer in expiry tracking and renewal visibility so a missed payment stops being how you find out a domain is offline.
You can revoke access at any time from the integration drawer or from the provider side. Everything 301.st ever sees flows through the credentials you grant.
Domains
Domains: your portfolio in one dashboard
Synced domains land in a single filterable table — by status, health, provider, role, and expiry — with a per-domain inspector that surfaces DNS state and Cloudflare configuration. Bulk actions cover the painful parts: block, unblock, delete, and pointing site-less domains at a target.
That inventory is what everything else reads — projects, sites, redirects, TDS rules, postback sources. Configure once, reference everywhere.
Projects & Sites
Projects and sites: structure that matches your campaigns
Projects group related work — usually one per client, brand, or vertical. Sites declare a primary domain and bind redirects to it. Together they keep dropdowns short and filters meaningful once you pass a handful of domains.
Small setups can stay shallow — the "Default Workspace" project and its site come with the account, so the floor is one of each and you are already on it. The structure scales without forcing premature decisions.
Redirects
Redirects: edge-speed rules across your portfolio
Define a rule from a template (domain-level, path-level, exact URL, maintenance page), pick the site, hit Save. Pending changes show a diff against what Cloudflare currently has; one Sync applies everything in batch. T1–T7 templates cover the shapes most teams need.
Bulk sync writes to all your Cloudflare zones from one place. Local edits stay versioned until you apply, so nothing reaches production by accident.
TDS
TDS: site-scoped split testing and routing
Smart Shield filters traffic by geo, device, OS, or bot signals; SmartLink routes by URL parameters (utm_source, fbclid, gclid). Rules bind to a site and deploy to a Cloudflare Worker on your acceptor domain — without you writing or operating the Worker code.
A/B splits, geo-splits, and conditional landing logic all live here — running on a Cloudflare Worker on your primary domain, your account.
Postbacks
Postbacks: conversion attribution from your affiliate networks
Each network you work with gets one postback source in 301.st — paste-ready URLs per event (Registration, FTD, Deposit, etc.) and a field map that translates the network's parameter names into a normalised conversions feed.
Conversions land in a live dashboard with attribution back to the originating click. It covers both traditional affiliate networks and 1Win-class operators that route each event to its own URL.
Guides by Topic
- Getting started — sign-up to first live redirect, with what each step actually unlocks.
- Cloudflare integration — token scopes, what we read, and how to revoke.
- Postbacks and attribution — receive S2S conversions from affiliate networks and see them in the live dashboard.
- Domain management — filters, inspector, bulk actions, subdomain handling, expiry tracking.
- Projects and sites — when to layer structure on, when to stay flat.
- Redirects — T1–T7 templates, version-aware sync, bulk apply across all zones.
- TDS rules — Smart Shield filtering, SmartLink parameter routing, MAB experiments, sandbox preview.
- Smart Shield vs SmartLink — a short decision guide for choosing the right TDS rule type: filtering vs routing.
- Bot filtering — bot categories, why bot rules run first, and presets for whitepages, AI crawlers and datacenter traffic.
What These Pages Will Not Do
- Promise features that aren't built. If it's listed here, it's live today.
- Document API contracts or implementation internals — those live in the engineering repo.
- Hide rough edges or known limits — we call them out explicitly.
What These Pages Cover
Written for SEO webmasters, affiliate teams, agencies, founders, and partners deciding whether to put production traffic behind 301.st. The framing is operational, not aspirational.
- Included: setup, Cloudflare access, domain ops, structure, redirects, TDS routing, postback attribution, and billing.
- Not included: API contracts, source-level details, or features that are not yet generally available.
- Intent: give a prospect or new operator enough context to make a real evaluation decision in one sitting.
FAQ
How does this compare to Cloudflare Page Rules or Bulk Redirects?
301.st sits on top of your Cloudflare zones, so the same edge engine still serves the redirect. What you trade is the Cloudflare UI for a form-driven panel that spans every zone in your account, versions changes before they sync, applies in bulk, and adds the surrounding workflow (domain inventory, projects, attribution) Cloudflare does not.
Do I need to migrate DNS or change nameservers?
No. Domains stay on Cloudflare with your current nameserver setup. 301.st only needs an API token to read zones and write redirects/Worker rules. Revoke the token to stop access — nothing is mirrored elsewhere.
What is the smallest sensible evaluation?
Sign up, connect one Cloudflare account, sync the zones, create one redirect through the panel, and verify it lives on Cloudflare exactly as expected. Most teams reach that point in under 10 minutes.
Is there a free tier?
Yes. The free plan covers the core features — Cloudflare integration, domain sync, redirects, projects, and TDS rules — within usage limits suitable for a one-brand operator or evaluation account. Paid plans raise the limits and add postback attribution capacity.
Run the 10-Minute Evaluation
Sign up, paste your Cloudflare API token, sync zones, ship one redirect. If the platform does not save you a meaningful amount of operating time on day one, it will not save you any later — and you will have spent ten minutes to find out.