Pro Tips & Features

Moving to a custom domain without losing the search traffic you have

Your storefront and product pages are statically rendered and indexable, so a domain change is a real move. What to do before, during and for the month after.

The store.fan teamSeptember 11, 20269 min read
Moving to a custom domain without losing the search traffic you have

The reason you have not done this yet is not the DNS. It is the small cold feeling that something is currently working, you do not entirely know why, and moving it might stop it. A few of your product pages get found in search. Someone links to your storefront from a forum you have never read. If you change the address and that quietly evaporates, you will not get a notification about it. So the move gets postponed, which is a reasonable instinct and a fixable one.

What is genuinely at stake, and what is not

First, the good news about how your pages are built. Every storefront and product page on store.fan is statically rendered, carries its own title and description, and appears in the sitemap. That is why product pages can be found at all, and it is why a domain move is worth doing properly instead of casually. You are moving real indexed pages, not a JavaScript shell that search engines were mostly ignoring anyway.

Now the honest part. For most creators reading this, the search traffic at stake is smaller than the fear attached to it. If nearly all of your visitors arrive from a link in your bio, from a video description or from an email you sent, then a domain change is a link-updating job with a small search footnote, and you can move this week. If, on the other hand, you have a handful of product pages that have quietly been bringing strangers in for months, the sequencing below matters much more.

The thing genuinely outside your control is other people's links. Anyone who has linked to your store.fan address from their own site, newsletter archive or forum post is not going to update it because you asked nicely. That is the part of the move you plan around rather than solve. Everything else, from your own bios to your invoices, you can fix in an afternoon.

The scramble and the ordered move

The difference between a domain change that costs you a month and one that costs you nothing is almost entirely sequencing. Here is the same migration done two ways. If you are also arriving from another platform at the same time, do that move first and separately; the migration guide covers the content side of it.

The usual scrambleThe ordered move
Buy domain and connect it the same evening, then announce itBuy the domain, connect it, confirm it resolves, then announce it days later
Redesign the storefront at the same time, because you are in there anywayChange nothing about the content for two weeks, so any wobble has one cause
Discover broken links in bios weeks later, one at a timeWork a written list of every place your link appears, in one sitting
Do it the night before a launch, when the traffic matters mostDo it on your quietest weekday, with nothing scheduled for a fortnight
Judge it by refreshing analytics the next morningJudge it at week five against the numbers you wrote down in week zero
No record of what ranked before, so no way to tell what changedA one-page baseline saved before the move, with your top pages listed

Before, during, after

Print this or paste it into a note. The whole sequence takes about two hours of actual work spread over five weeks, and most of it is in the first bracket.

The migration checklist

0/10

A worked example: a ceramics teacher with four ranked pages

Picture someone selling four things: a glaze guide, a beginners course, a monthly membership and a set of studio dates. Before the move she writes down that three quarters of her views arrive from her own social bio, and that the glaze guide page is the only one bringing in strangers from search, at a modest but steady trickle. That single sentence is her baseline, and it takes four minutes to produce from the per-product view in analytics.

She moves on a Tuesday, updates her bios the same evening, and by Thursday the bio-driven traffic looks exactly as it did before, because that traffic never depended on search at all. The glaze guide dips and then recovers over the following weeks. Had she not written the baseline down, she would have spent that fortnight reading the dip as a disaster, and would probably have started changing things at the worst possible moment. The numbers here are illustrative rather than a promise, but the shape of the story is the ordinary one: the traffic you control moves with you immediately, and the traffic you do not control takes a few weeks to settle.

If you have not built the storefront yet, start it on the free plan and move it to your own domain later, in that order.

Start for free

The mistake most people make

They change three things at once. New domain, new theme, new product names, all in the same week because it felt like a fresh start. Then traffic moves and there is no way to tell which change did it, so the next fortnight is spent guessing and undoing. Move the address on its own. Keep the titles, the descriptions, the product names and the layout exactly as they were until you are through the settling period, then redesign to your heart's content with the store designer. One variable at a time is not a rule for scientists. It is a rule for anyone who wants to know what happened.

Plan for two to three weeks of noise and judge the move at week five. Search engines rediscover pages at their own pace, and the honest answer is that nobody can give you a date.

No. Do it after. A launch is the one week where you want every variable held still, and a domain change is the largest variable you can voluntarily introduce.

Your product pages are statically rendered with their own titles and descriptions, and that is a property of the page rather than the address. The content you wrote stays the content you wrote.

You cannot edit those, so treat them as fixed background. If a particular partner sends you real traffic, it is worth one polite email asking them to update. For everything else, let it be.

A domain move is one of the rare jobs where the calm version and the fast version are the same version. Baseline, move, update your own links, wait, then look. Five weeks from now the address will feel like it was always yours, and you will have a written record proving nothing fell over.

Get the storefront live and indexable first, so that when you do move a domain there is something worth moving.

Open your store
#custom-domain#seo#migration#static-rendering#pro-plan

Turn your knowledge into income

Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.