Questions and answers

Links and Design edit a working copy of your page. Nothing a visitor sees changes until you press Publish, which is what lets you rearrange half your page without anyone watching you do it.

Everything else — Shop, Bookings, Newsletter, Download, Payments — saves live. There is no draft of an appointment book or a subscriber list to hold, so those sections have their own Save and a "No publishing needed" badge where the Publish button would be. If a section is drawn beside the phone preview, it publishes; if it is not, it is already live.

Publishing clears the cached copy of your page before it returns, so the next visitor is served the new one. There is no waiting period to sit through.

What usually survives is your own browser, or the in-app browser inside a social app, which keeps its own copy that we cannot reach. A hard reload or an incognito window shows you what a stranger gets, and is the check worth doing before assuming the publish failed.

Yes, on Pro — up to 10 profiles per account. A free account has one. Each profile has its own address, links, design, appointment book, subscriber list and analytics; nothing is shared between them except the login.

Billing is per account rather than per profile, so one subscription covers all 10. Switch between them from the profile menu at the top of the rail.

No. A username is fixed at creation, because it is the public address of the page and the key everything recorded against it is filed under. Changing it would break every link already printed, pasted and shared, and would split your analytics across two names.

If you need a different address, create a second profile with it. The old one keeps working, so anything already pointing at it still arrives.

It is life-size. The frame is a real phone width rather than a scaled thumbnail, so what you are looking at is the size a visitor actually holds — which is the only way to judge whether a headline fits or a button is reachable with a thumb.

It renders your unsaved working copy, not the live page. That is the point of it: it is the one place to see a change before Publish sends it.

A plain URL, an email address, a phone number or a WhatsApp chat — those four just send the visitor somewhere. A video link embeds the player in the page instead of sending anyone away.

The rest point at your own tools: a booking service, the newsletter signup, a gated download, or your shop. Those are the rows that turn the page from a list of exits into somewhere things happen, and they are set up in their own studio sections rather than in the row.

Yes. A link can carry a window — a start, an end, or both — and it is only on the page inside it. A launch that goes live at midnight and an offer that closes on Sunday both stop being something you have to be awake for.

The window is evaluated when the page is served, so it needs no publish of its own to take effect. Set it and the row will come and go without you.

More than anything else on the page. Attention falls off steeply down a link list, so the row you most want clicked belongs first, and the row you added most recently almost never does.

Drag rows to reorder them. Each row carries its own click count once it has been published for a while, which is the honest way to settle an argument about what should be at the top.

A booking and a gated download. Both are things you deliver, so both can carry a price and put the visitor through checkout before they get it — a paid consultation, or a file people buy rather than trade an email address for.

Charging is a Pro feature and needs a connected payment account. MyLink.is takes no cut of what you charge.

When the thumbnail is the thing being chosen — a product, an episode, a person. An image gives a row weight and pulls the eye to it, which is exactly what you want on one or two rows and exactly what you lose when every row has one.

A list where everything is emphasised reads as a list where nothing is. If you want all your rows to look alike, leave them all plain.

Because text has to survive the background it lands on. The contrast badge in the theme editor is measuring your text colour against your actual background, and it flags combinations that a good proportion of visitors would struggle to read — including you, outdoors, on a phone at half brightness.

It is a warning rather than a lock. But a page nobody can read converts at zero, so it is worth a second look before overriding it.

A photograph behind text is veiled deliberately. The page draws a scrim over it so the links and headings on top stay legible, and the strength of that scrim is the contrast guarantee, not a style preference — without it the page would be unreadable over the bright parts of your own image.

If the image matters more than the text, a header cover puts the photograph at the top at full strength and leaves the link list on a plain background below it.

They differ in how much of the screen is spent before the first link. An avatar layout is compact and gets a visitor to the links almost immediately; a cover layout spends the top of the page on an image and says something about you before anything is clickable.

Pick by what the page is for. A link hub that people arrive at knowing who you are wants the compact one; a page that has to introduce you first can afford the cover.

Into Design, under Header. It is the line under your name at the top of the page, so it belongs with the layout and the image it sits between rather than on a settings screen away from anything that shows it.

What is left in Settings is the part of a profile that never appears on the page at all — the address, and deleting it.

Less than the picker invites. Two typefaces is a design; four is a ransom note, and the display font is doing most of the work on a page this short anyway.

The safest change is the display font alone, left over a plain body font. Check it in the preview at phone width — a face that looks characterful at desktop size often turns to mud at fourteen pixels.

Products with a price, a picture and a destination — up to 24 of them per profile. A product can hand over a file, send the buyer to a link you control, or simply be something you fulfil yourself after the order lands.

The shop is a Pro feature and needs a connected payment account before anything can be bought.

A paid link is one thing at one price, sold from a row on your page — a consultation, a file. The shop is a catalogue with a cart, so a buyer can take three things in one checkout.

If you sell one item, the paid link is less to set up and less for the visitor to navigate. Once there is a second item that somebody might buy alongside the first, the cart starts paying for itself.

Publishing a product puts it in the shop; a shop row in your link list is what puts the shop on the page. The two are separate on purpose — a catalogue can be ready before you decide to feature it, and you can take the row off the page for a week without unpublishing everything in it.

So a product that seems to be missing is usually published into a shop that has no row pointing at it.

The buyer is taken through checkout, and the order is only marked paid when the payment provider confirms it — not when the buyer arrives back on the page. That ordering is deliberate: a returning browser is not proof of payment, and treating it as one is how a shop hands out goods it was never paid for.

Once the payment is confirmed, anything attached to the product is released, the sale appears in your analytics, and you are emailed: what sold, for how much, the address that paid and the reference the buyer holds. A shop order is the one thing here a person still has to fulfil, so the person fulfilling it is told rather than left to find out from your payment provider or from the buyer asking where their thing is.

Up to 5 bookable services per profile, and visitors can book up to 62 days ahead.

The ceiling on the calendar is a real constraint rather than a technical one: availability that runs further out than you can honestly commit to is availability you will end up cancelling, and a cancelled appointment costs more goodwill than a date that was never offered.

You set recurring weekly rules — the hours you are open on each day — and the calendar generates slots inside them. Blocks are the exception on top: a holiday, an afternoon out, a single hour you need back.

Anything already booked also removes its slot, so the calendar a visitor sees is your rules minus your blocks minus your existing appointments. You never have to take a slot down by hand after it is taken.

Yours when you set availability, and the visitor's when they pick a slot. The calendar converts, so somebody booking from another country sees their own clock and you see yours.

This is the single most common source of a missed appointment in any booking tool, so the confirmation emails both parties get name the time explicitly rather than leaving it to be inferred.

Yes — a booking link can carry a price, and the visitor goes through checkout as part of making the appointment rather than being invoiced afterwards. Charging for a booking is a Pro feature and needs a connected payment account.

MyLink.is takes no cut. What you charge, less your payment provider's own fee, is what arrives.

Yes. A booking row can point at an external scheduling page instead of the built-in calendar, which is the right choice if the tool you already use holds your real availability.

The trade is visibility: an external tool takes the visitor off your page and reports nothing back, so those bookings will not appear in your appointment list or your funnel.

A signup starts unconfirmed and becomes a subscriber when the person clicks the link we email them, which they have 72 hours to do. Signing up again inside that window simply resends it.

It costs you some signups and it is worth it. Confirmation is what stops a typo, a bot or somebody else's address from entering your list, and a list built without it degrades your sending reputation for every genuine subscriber on it.

No, and deliberately not. MyLink.is collects subscribers; it is not a mailer. Sending campaigns well means deliverability, templates, unsubscribe handling and reputation management, and doing a mediocre job of all four would serve you worse than handing the list to a tool that does them properly.

So the job here is capture and export. Take the list to whichever mailer you already use.

Yes, and without asking. The export is yours — addresses, names where given, and when each person confirmed — and there is no lock-in on it. The section can also hand new subscribers straight to your mailer as they arrive, if you would rather not move a file around.

The list stops being one list the moment you export: an unsubscribe here does not reach the copy in your mailer, so handle it in whichever tool is sending.

Every confirmation email carries a working unsubscribe link, and using it removes the person from your list here immediately. You do not have to action anything.

If you have already exported that address to a mailer, the removal here does not reach the copy over there — the two lists are separate the moment you export. Handle the unsubscribe in whichever tool is actually sending.

Up to 10MB. That covers a guide, a preset pack, a template, a sample — the things a link in bio is actually good at giving away.

For anything larger, host it where large files belong and use a plain URL link, or sell it through the shop with the destination pointing at your host. A lead magnet that takes a minute to download on mobile data is a lead magnet that gets abandoned.

The visitor gives an email address, and the file is released to that address rather than sitting on a public URL anybody can pass around. That is the trade the whole feature exists for: the file is the payment for the address.

The addresses collected this way are yours to export, and they are a separate list from your newsletter subscribers — somebody who wanted your checklist has not agreed to receive your emails.

Yes. A download link can carry a price, in which case the visitor pays at checkout and the file is released once the payment is confirmed. Selling a download is a Pro feature and needs a connected payment account.

The link is unguessable and issued per buyer, so it is not something that can be found by anyone who did not pay for it.

You can replace it at any time, and everyone who downloads from then on gets the new version. Nobody who already has the old one is re-sent anything — the file has left, and we have no way to pull it back.

So for a version-two of something you have been giving away for months, the honest route is to email your existing list yourself.

Nothing. Money goes from the buyer to your own connected payment account, and we are not in the middle of it — the only deduction is your payment provider's own processing fee, which they charge and which we do not see.

What Pro buys is the ability to charge at all, not a share of what you charge.

Because the money has to land somewhere, and it does not land here. Connecting is what tells the checkout which account to pay, and the provider's own identity and bank checks are what make payouts possible at all.

One connection covers the whole profile. However many links or products charge for something, they all pay into it.

No — one currency per profile, chosen in Payments and applied to everything you charge for.

A page listing some prices in dollars and others in euros makes a visitor do arithmetic in the middle of deciding to buy, and a cart that mixed two currencies could not be totalled at all. If you genuinely sell into two markets, a second profile is the way to do it.

In your payment provider's own dashboard. The charge was made to your account, so the refund is issued from it — we never held the money and cannot return it on your behalf.

The order stays on record here so your analytics still reflect what was sold, and it is worth telling the buyer directly rather than leaving them to notice the money reappear.

Your traffic and your button counts — pageviews, visitors, what was tapped and how often, over any of the ranges. That is the whole top of the Analytics tab and it is free on every account.

The two cards below it are Pro: the audience breakdown (device, browser, country) and the goal funnels, which show where visitors drop out between arriving and finishing. Those answer who came and why they left rather than how many, and they are the half that costs money.

The last 24 hours, 7 days, 30 days or 90 days. The last 30 days is what opens first, because it is long enough to survive one quiet week and short enough to still be about what you are doing now.

A range shorter than a week will show you your own posting schedule more than anything about your page. If you changed something on Tuesday, judge it on the following Tuesday, not on Wednesday morning.

Countries with very few visitors are folded into "Other" rather than named, and so is everything past the top few rows. A single visitor from a small country is close to being an identifiable person, and a breakdown that names them is a privacy problem wearing a chart.

The totals are unaffected — nothing is dropped, only grouped. As your traffic grows, more countries clear the floor and appear by name.

A rate calculated from a handful of visitors is noise with a decimal point on it, so rates below a minimum number of entries are withheld rather than printed. The raw counts behind them are always shown, because those are true at any volume.

It is not a bug and there is nothing to fix — it resolves itself as the traffic arrives.

A link's click count answers "is this row working" — one number per row, useful for deciding what goes at the top of the page.

The funnels answer "does this kind of thing work on my page" — visitors, then starts, then completions, for a whole goal like a paid booking. When a funnel drops off sharply between two stages, that is where to go and look; the link counts will not show you the stage that lost people.

Your visits to your own live page are ordinary pageviews and are counted like anyone else's. The preview inside the studio is not — it never leaves the editor and is not a visit to anything.

If you check your own page compulsively during a launch, expect a small self-inflicted bump in the 24h view. It washes out over 30 days.

What the page says and how it looks — the link list and the design. Version B is a copy of your page that you edit like any other, and visitors are split between the two.

Your tools are not part of it. There is one appointment book, one subscriber list, one file and one payment account per profile, so there is nothing for a second version to hold a different answer to. Set those up before starting a test, not inside one.

No — one experiment per page at a time. Two overlapping tests make every result ambiguous: a visitor who saw both changes cannot tell you which one moved them, and neither can the numbers.

Run them in sequence. A clean answer to one question beats two answers you cannot act on.

Until it has seen enough visitors to tell a real difference from a coin flip — the experiment screen estimates that for you from your current traffic, which is a far better guide than a number of days.

The temptation to call it on day two, when one version is ahead, is the mistake that makes testing worthless. Early leads swap constantly at low volume.

Because publishing would change the thing being measured half-way through, and the visitors counted before the change saw a different page from the ones counted after. The result would be an average of two experiments neither of which you ran.

Stop the experiment, make the change, and start again if you still want the answer.

You pick the version to keep and it becomes your page. The other one goes.

What it measured does not go: the comparison screen keeps both versions' numbers side by side, which is the only place those two figures mean anything. Keeping the loser's page around would just be a draft nobody will ever publish.

Three families of thing: selling, measuring, and scale. Selling is the shop and the ability to put a price on a booking or a download. Measuring is experiments, plus the detailed half of analytics — who your visitors are, and where they drop out. Scale is running up to 10 profiles instead of one.

Everything else is free and uncapped — links, design, bookings, the newsletter, gated downloads, and your page's traffic and button counts. Your first profile is free and nothing you have already built is ever taken away.

14 days, one per account, and it takes a card before it starts. It is the full Pro feature set rather than a limited version, because a trial you cannot actually sell through tells you nothing about whether selling works for you.

It is the first 14 days of a real subscription rather than a grant, so the first payment is taken on the day it ends unless you cancel before then. Cancelling is in the billing portal, from the same plan page you started on, and nothing you built is deleted either way.

They stop selling — they are not given away for free and they are not deleted. Paid links refuse the purchase and the shop comes off the page; the products, prices and settings all stay exactly as you left them and come back when the subscription does.

Your profiles are not touched. Every page you have built stays live, published and editable however many of them there are; what stops is adding another one. The audience and funnel cards stop as well, and your traffic and button counts carry on.

A failed payment does not do this immediately. There are 7 days of full access after the first failure, so an expired card is a thing you can fix rather than an outage.

No. The subscription is on the account, and covers every profile on it — all 10 if you use them all.

Extra profiles are what Pro buys, but it buys all of them at once: a second brand, a client page and a side project cost the same as the first extra page, which is nothing extra.

In the billing portal, reached from your plan page. Card details, invoices, switching between monthly and annual and cancelling all live there, with your payment provider, rather than here — which is also why we never hold your card number.

Cancelling takes effect at the end of the period you have already paid for. You keep Pro until then.

The parts of a profile that never appear on the page: its address, and deleting it.

Anything a visitor can see has moved to the section that shows it — your name, bio and picture are in Design under Header, because that is where you can see what changing them does.

The page goes offline and its links, design, appointments, subscribers and analytics go with it. It is not recoverable, and the username is not held for you afterwards.

The last profile on an account cannot be deleted — an account with no profile has nothing to sign in to. Export anything you want to keep, particularly subscriber and lead lists, before you do it.

Yes, by asking support. It is a deliberate conversation rather than a button, because it is irreversible across every profile at once and there is no undo to offer afterwards.

If you have an active subscription, cancel it first so the deletion is not racing a renewal.

Not as a transfer between accounts — a profile belongs to the account that made it.

If you are handing over a page you built for a client, the practical route is for the account itself to change hands: change the login email and password to theirs. Anything the page has collected goes with it, so make sure that is what both sides intend.

The changes that matter after the fact — publishes, settings changes, payment connection changes, deletions — with who did them and when.

It is not a keystroke history and it is not a version history: it tells you that your page was published on Tuesday, not what the page said on Monday. There is no way to roll a change back from it.

180 days. Older entries are removed rather than kept forever, because a security record that nobody has looked at in all that time is a liability rather than an asset.

If you need a copy for your own records, export it before it ages out.

Treat it as a possible compromise. Change your password first — that ends any session that is not yours — and then read back through the log for anything else from around the same time, particularly payment or email changes.

Then tell support what you found. The log holds what happened, which is exactly what is needed to work out how.