Publishing pages

The publish flow

Publishing turns the version you reviewed into the page visitors see. The live page stays unchanged until you choose Publish. On the Free plan the same button puts your website online at a Mirin address: see Put your website online free. If you have no homepage yet, begin with Start your website.

1. 1
   Preview your page. Check the page at desktop and mobile widths. Previewing does not change what visitors see.
2. 2
   Save your latest edits. Mirin saves the version you are editing. If anything is still unsaved, the Publish popover offers to save it first.
3. 3
   Open the blue Publish button. The anchored popover explains whether this is a first publish, a change to an existing page, or a republish.
4. 4
   Choose Publish. Your approved version becomes visible to visitors. A scheduled page can be published now from the same popover.
5. 5
   Copy or view the live page. After a successful publish, the popover confirms that the page is live and gives you Copy live link and View live actions.

The popover keeps the decision beside the page controls and confirms the live address when it succeeds. That address is your own domain once it is connected and verified, and your Mirin address until then.

Draft and published

Pages exist in one of two states. You can freely edit drafts without affecting what visitors see.

Preview links

Share draft pages with stakeholders before publishing. Preview links let others see exactly what will go live. Copy one from the Share menu in the page editor, described in Share and invite.

• Signed for one page. Each preview link carries a signed token for that one page, so it cannot be edited into a link for another page.
• Time limited. A link copied from the Share menu works for 7 days, then you copy a fresh one.
• Always current. Preview always shows the current draft state, so reviewers see your latest changes.

Common uses. Get stakeholder approval before launch, share with copywriters for review, test on mobile devices, or demo to clients without affecting the live site.

Where your page is served from

Your published pages are distributed across a global network of edge locations, not a single server. When someone visits your site, they connect to the nearest edge node, which assembles and delivers your page in milliseconds.

Pre built

No server processing delay. Your pages are pre built and ready to serve instantly.

Close by

Visitors connect to the closest location, typically under 20 ms away.

Light to load

Interactive components load efficiently without blocking your page content.

Protected

The edge network automatically mitigates DDoS attacks and bad traffic.

Custom domains

Connect a domain you already own to your published Mirin site. Mirin hosts your website, but Mirin does not register, transfer, renew, or host the DNS for your domain. Your domain stays with the company that manages it today.

Provider instructions

Wix

Domains, Domain Actions, Manage DNS Records

1. Choose the domain and open Manage DNS Records.
2. Add or edit each record shown in Mirin. Wix uses a blank host name for the root domain instead of @.
3. Select Save, then confirm with Save Changes.

If Wix does not show the DNS editor, your nameservers may point to another provider.

Read Wix’s official DNS guide

Squarespace

Domains dashboard, your domain, DNS

1. Open the Domains dashboard, select the domain, and select DNS in the side panel.
2. Add or edit a custom record. Complete the Type, Host or Name, and Data fields using the values from Mirin.
3. Save each record. Use @ for the root domain when Squarespace requests a host.

Domains migrated from Google Domains are now managed in Squarespace. If the nameservers point elsewhere, edit DNS there instead.

Read Squarespace’s official DNS guide

GoDaddy

Domain Portfolio, your domain, DNS

1. Open Domain Portfolio, select the domain, and open DNS.
2. Select Add New Record or Edit beside an existing website record.
3. Use @ for the root domain and www for the www record. Save and complete identity verification if GoDaddy requests it.

Only replace records for the website host you are connecting. Keep mail and verification records in place.

Read GoDaddy’s official DNS guide

Namecheap

Domain List, Manage, Advanced DNS

1. Choose the domain, select Manage, and open Advanced DNS.
2. Under Host Records, select Add New Record or edit an existing website record.
3. Use @ for the root domain, www for the www record, and Automatic for TTL. Save with the checkmark.

If Host Records is unavailable, the domain uses another DNS provider. Check the Nameservers section to find it.

Read Namecheap’s official DNS guide

Cloudflare

Your domain, DNS, Records

1. Choose the domain, open DNS, and select Records.
2. Select Add record or edit the existing record for the same host. Copy the type, name, and target from Mirin.
3. Set Proxy status to DNS only for the Mirin A and CNAME records, then save.

The gray cloud DNS only setting lets Mirin confirm that the records point to the required destination.

Read Cloudflare’s official DNS guide

After you save the records

Where should I edit my DNS records?

Edit records at the provider listed in your domain’s nameservers. That provider may be different from the company where you bought the domain or built the old website. If a DNS editor is missing, check the nameservers or ask your domain provider where the DNS zone is managed.

Should I change the TTL?

Keep the TTL at its default or automatic setting unless your provider tells you otherwise.

Verification is still pending. What should I look for?

Look for an old A, AAAA, or CNAME record using the same @ or www host.

Can I use my Mirin address while the domain connects?

Yes. Your MyMirin address remains available while the custom domain is connecting.

Open Domains in Mirin.

Keep old domains and links working

Choose one primary domain for the address customers should remember. In Settings, connect additional domains and set any connected domain as primary when needed. The former primary automatically redirects to the new address. In Content, use URL redirects for pages whose addresses changed.

Connect another domain

Add a redirect

Redirects applies to your entire website, including old or removed pages. Open Redirects under Website and choose Add redirect. The empty view illustrates an old address leading to its new address. Enter the source, destination, and redirect type, then save. If a connection fails, your entered values stay in place so you can retry.

Use the right redirect type

Exact paths and one trailing wildcard

Exact rules win when both an exact path and a wildcard could match. A wildcard can appear once at the end after a slash. Query details are preserved automatically.

• Internal. A destination on your own website begins with a slash.
• External. A destination on another website must use HTTPS.
• Checked before saving. Mirin rejects duplicate sources, loops, and redirect chains.

Protect a published page when its URL changes

When you change the URL of a published page, Mirin checks Create a permanent redirect from the old URL by default. Keep it checked so saved links and search results continue to work. The generated 301 appears in Website, then Redirects, where you can edit or remove it like any other redirect. You can clear the checkbox to opt out.

• Created on a successful save. Mirin creates the redirect only after the page save succeeds. Draft page URL changes do not create redirects.
• A path already in use. If another redirect already uses the old or new path, Mirin pauses the save and asks whether to replace that redirect. If another page owns the new path, choose a different URL so the existing page is never overwritten.

Retired products and collections keep their links

When you archive a product or remove a collection, links to it still land somewhere useful, with a permanent redirect and nothing to set up. Mirin decides where at the moment someone opens the old address, from what your store has live then. A sold out product keeps its own page.

• The same product, in its new vintage or size. When the product is live again under another year or size, the old address leads to it.
• Its collection. Otherwise it leads to a collection it was in, or one named in its title or details, such as Bourbon for a Kentucky straight bourbon.
• A search for its name. When no collection fits, the visitor lands on your store search for the product name.
• Its own page, the moment it returns. Nothing is stored for a retired product. Make it active again and its page answers at once.

A removed collection leads to the collection its address extends, such as Beer and Cider for Belgian beers, or the one sharing most of its products, otherwise to your home page. An address your store never had still shows your page not found. Moving from another platform? Mirin can keep your old site's product and collection addresses too, so their links land the same way. Ask the Mirin team when you move.

HTTPS, without setup

There is nothing to set up. Mirin looks after the certificate for every site it hosts.

• HTTPS on every site. Every Mirin site is secured with HTTPS automatically, so browsers trust it at all times.
• Renewed for you. Certificates are provisioned and renewed without any configuration on your part.
• Industry standard TLS. Your site is protected with industry standard TLS encryption, managed entirely by Mirin.

What publishing refreshes

When you publish changes, only the affected pages are invalidated across all edge locations globally. The rest of your site continues serving from cache for maximum performance, ensuring visitors always get fast responses.

Only the page you changed

Only the specific page you publish gets invalidated from all edge locations.

Seconds, not minutes

Changes propagate to every edge location in seconds, not minutes.

No waiting on expiry

Active purging means you never wait for a cache to naturally expire.