Link pages, run like infrastructure.
One console for every page your team ships, with routing, age gating and per page numbers. Built for the people who run dozens of them, not one.
Sign up to open your own workspace in a minute. Adding your team happens inside it, where an invite turns a seat into a sign in.
A console, not a page builder.
The building part takes a minute. The rest of the job is knowing which of forty pages is broken, who is allowed to fix it, and whether last week was better.
Every page in one place
Pages, their state and what each one took, in a list a person can actually read at forty rows. Search by path or name, filter by state, act on a selection.
Routing that survives an in app browser
A visitor arriving from an app browser gets sent on to wherever the page points. When the host will not hand off cleanly, the page says so and offers the address instead.
An age question that runs first
The gate is answered before anything behind it renders, and the answer is kept on that phone for thirty days so a returning visitor is not asked twice.
Numbers per page, not per account
Visits, taps, the share that tapped, countries, sources, devices and browsers. Counted once per visitor session, with the window stated on every card.
Tests that refuse to guess
Six platform experiments run on every page by themselves. Nothing is called a winner under twenty views, and inside a point is a dead heat rather than a result.
Seats scoped to what they own
An operator sees the pages assigned to them and nothing else. The boundary is stated on the screen as a fraction rather than left to be discovered.
Three steps, then it runs itself.
- 01
Make a page
A name, one link, publish. The address is yours from that moment, and renaming a live one warns you with the number of visits it took yesterday.
- 02
Put its address in a bio
Copy link sits on every row and every card. One address, however many destinations sit behind it, and you can change where it points without changing the link.
- 03
Watch it in Insights
Numbers appear within a minute of the first visitor. Until there are two full days to compare, the change figure stays blank rather than showing one that means nothing.
The parts that have to be right before anything else is.
These are not settings buried three screens deep. They are how every page behaves by default, and the console says which of them is running.
An 18 plus gate, answered once
It runs on the first request of a session, before the links exist in the response. A page that draws them and then covers them has already sent them. The answer is remembered on that phone for thirty days.
Crawlers receive a plain page
An automated request gets a static page with no creator content on it. One address always returns the same one, and the share card a messaging app shows matches that page rather than promising something else.
Nothing is indexed
Every page carries noindex and nofollow, so an address does not surface in a search result someone else runs.
Referrers are stripped
Pages are sent with a no referrer policy, so where a visitor came from is not readable by the destination they land on.
Three roles, and the screen says which one you are.
A locked control stays visible with the reason attached, because a control that vanishes teaches an operator the feature does not exist.