The manual
Everything the machine does with your order.
One page, start to finish. What is printed before you pay, what runs in the hour after, how we prove the redirect is really serving, and what to do when you want those links pointing somewhere else.
Start to finish
How buying works.
Five moves. Four of them are yours and take about a minute each, and the long one belongs to the machine.
01Open the catalogue
The shelf lives in the app and browsing costs nothing. Each listing prints the publisher carrying the head link, that publisher's authority score, how many editorial links come with the domain, how old the evidence is, and the price for the year.
02Pick your package
One buyer per package. Nothing on the shelf is a slot in a rotation, and a listing comes off the shelf at checkout and stays off.
03Pay by card
Stripe takes one payment in dollars for twelve months of the redirect. The domain name never shows up on the Stripe page, because at that point it is still not yours.
04Give us the landing URL
Any URL on your site: the home page, a product page, the article you are trying to rank. You can hand it over at checkout or from the dashboard while the machine is still working.
05The machine delivers
The name moves into your account, the edge configuration comes up, DNS publishes, the permanent redirect is written and a check is made from outside our own network. Nobody here schedules any of it and you have nothing to chase. About an hour, most of the time.
The dossier opens on your account the moment the package is yours, and the delivery log fills in as each state lands.
The one thing we hold back
Why the name stays sealed.
The name is the part that makes a package identifiable. Printed in the open it is copied into somebody else's index inside a week, and every buyer here ends up competing with mirrors of their own package. So the name goes to the account that owns it and nowhere else, and every fact you need to judge the link is printed before you pay.
Printed before you pay
- The publisher carrying the head link, with its authority score
- Up to three more publishers by name, and a count for the rest
- How many editorial links the package carries
- The year of the oldest dated page still holding one
- The price for twelve months
- That the package sells once and then leaves the shelf
Held back until it is yours
- The domain name
- Every source URL
- Every anchor text
- Verification timestamps
- The full delivery log
The head link gets read live again in the seconds before your card is charged. A link that died in the meantime pulls the listing and leaves your money alone.
The delivery machine
Ten states, in the order they run.
Every order walks the same list. Each state is written down as it happens, so the delivery log in your account is the machine's own record of the work, with a timestamp on every line.
01The order is booked
Payment cleared and the order is in the queue.
02The name moves to your account
The name is being put under your account. This is the one step where an outside system sets the pace, and it is usually over in a couple of minutes.
03The edge is standing by
An edge configuration is ready to answer for the domain the moment it is delegated, so nothing is ever parked on a placeholder page in between.
04Nameservers pointed
Every lookup for the name now goes to that edge configuration.
05The edge has taken it
The edge network has seen the delegation and answers for the domain. Registries can be slow here, so this state carries the longest clock.
06Records published
The domain resolves, and every request for it is served at the edge rather than by an origin server. That is what makes the redirect instant from anywhere in the world, and what leaves nothing for anyone to knock over.
07Waiting on your URL
The only state that waits for a human, and only if you have not given us a landing URL yet. Everything else is already built and the order sits here until you do.
08The permanent redirect is written
Every path on the domain now answers with a 301, including the exact URLs those old editorial links point at. Permanent, never temporary: a 302 is the most common way a redirect ends up passing nothing at all.
09Proved from outside
We fetch the domain over the public internet, from outside our own network, and read the response ourselves. Our own systems reporting success and your redirect actually serving are two separate facts, and this state is the second one.
10Yours and running
The package is delivered. The dossier is open in your account and the redirect keeps working for the twelve months you paid for.
Anyone can point a redirect. That is the easy part.
Pulling a list of domains and aiming a redirect at your site takes an afternoon. Whether the result carries any weight at all is decided by everything around it, and almost none of that is visible from a browser. We do not publish the whole method. These are the parts we are happy to describe.
The certificate, from the first minute
The domain answers on HTTPS from the moment it goes live, with the certificate issued and renewed at the edge. A package that only answers on plain HTTP is a package half the web treats as broken, and it is the most common way a hand-rolled setup quietly loses everything it was carrying.
Permanent, never temporary
A 302 tells a search engine the move is provisional and to keep the old address. Every package is written as a 301, and the check reads the status code back rather than trusting the configuration that wrote it.
Both schemes, every path
http and https are fetched separately and both have to answer permanently. Every path answers, not only the root, because the old editorial links point at deep URLs and a root-only redirect strands every one of them.
No chain hiding behind the first response
We refuse to follow the hop on purpose. Following it would prove that something further down a chain answers, which is not the claim. The claim is that the domain itself redirects, and that is a property of the first response.
Checked against the URL that is live now
The target verified is the one in your account at that moment, not the one recorded when the order was placed. Change your landing page mid-delivery and the check follows you.
The verdict comes from outside
Our own systems reporting success proves our systems agree with themselves. The check is made from a public address over the open internet, the same way a search engine would see it.
Most orders reach live in about an hour.
Every state has a clock
A state that overruns its clock stops the order instead of leaving it stuck. That is the same path any step that cannot finish takes, and it ends in a refund you did not have to ask for.
The reveal
What opens the moment you pay.
The seal comes off the whole file at once, on the account that paid. Everything below is sitting in your dashboard before you have finished reading the payment confirmation.
The domain name
Yours, printed at last, with its renewal date.
Every source URL
One click each, straight to the page carrying the link. Open a few and read them yourself.
Every anchor text
The words the editor wrapped around the link, exactly as they sit on the page.
Verification timestamps
When each link was last read live, including the read that happened seconds before your card was charged.
The delivery log
Every state above with the time it landed, from the first step to the check made from outside.
The dossier opens on the account that paid and nowhere else.
If delivery fails
The refund fires before anyone here hears about it.
The order stops on the first state that cannot finish. A step that will not complete, an edge configuration that never goes active, a redirect that will not verify, a head link that died between the listing going up and your payment landing: any of it ends the same way.
- The full price of that package goes back to your card automatically
- You hear about the failure from us, without opening a ticket first
- The listing goes back for investigation instead of straight onto the shelf
- You are never billed for a redirect that is not serving
After it goes live
Move the redirect whenever you like.
The 301 points wherever you tell it. Change the target from your dashboard as often as you want during the year: a new landing page, a seasonal campaign, another site of yours. The new redirect is written the same way the first one was and checked from outside the same way.
The links do not care
Those editorial links point at the domain you own. What the domain does with a visitor is your call, and you can change it every week if you have a reason to.
Search engines take their time
Crawlers re-read a redirect on their own schedule. Give a change a few days before you look for it in anyone's index.
The dossier stays put
Source URLs, anchors and timestamps are facts about the links, so they do not move when the target does.
Billing
One payment, twelve months.
1 of 1- Priced per package
- Each package carries its own yearly price, set by the publishers doing the linking. There is no plan on top and no monthly fee.
- Paid by card
- Stripe handles the payment and the invoice lands in your account. Prices are in US dollars.
- A warning before the date
- We write to you before the twelve months are up, so the renewal never arrives as a surprise.
- Renew or let it go
- Renew and the redirect keeps running for another year. Let it lapse and the redirect stops and the domain goes back to the open market.
Support
When you want a person.
Anything about an order in flight goes to the support address and jumps the queue. Everything else can go through the contact form, and most messages get an answer the same working day.