---
title: Troubleshoot a store that does not publish
description: "Your Tapmy store won't publish or changes don't show up? Find out whether saving, validation, your custom domain or the cache is the problem."
lead:
  - "If your Tapmy store does not publish, work out which step fails: saving, validation, publishing, domain routing or a cached page. Open the public URL while signed out first, because that one check tells you whether the problem is in the editor or after it."
tags:
  - link-in-bio
source: docs/tapmy-wiki/pages/troubleshoot-a-store-that-does-not-publish--98ecd452.md
---

Use this page when a new store, or a recent edit, is not visible to visitors.

## Why is my Tapmy store not showing my changes? {#before-you-start}

Publishing is a chain: save, validate, publish, route, display. A break at any link looks the same from the outside, so find the link before you change anything.

Start with three quick moves. Copy your current public URL. Write down what you expected to change. Open a signed-out browser window (a private window works). Keep the old text and links somewhere so you can undo a change.

## Find the step that fails {#isolate-the-failing-stage}

1. Check that you are editing the right Site and that it saves with no validation message.
2. Look for required fields left empty, unsupported files, broken link destinations or components your plan does not include.
3. Publish once, then wait. Clicking again while the first request is still running only adds noise.
4. Open the Tapmy public URL while signed out. If it shows your change, the editor and publish steps worked. Look at your custom domain or the cache next.
5. Try the same URL on another browser or network. Compare what each one shows: the page, any error, the certificate warning, the redirect.
6. With a custom domain, compare the DNS record in your provider (host, type, value, proxy setting, duplicate records) with what Tapmy shows for your Site. Change nothing until you have compared them.
7. If you only see old content, note the time of your last publish and wait before editing again. Several unrelated edits make the cause harder to find.
8. If a clean save and publish still fails, contact support with the smallest example you can reproduce.

## What a working result looks like {#what-success-looks-like}

Visitors who are not signed in see the latest content at the right URL, on a phone and on a desktop. If you use a custom domain, it loads over HTTPS and lands on your store.

Always check the real public URL, not just the editor preview.

## Common symptoms and fixes {#troubleshooting-and-limits}

- **Save fails.** Check required fields, text length, file type and your connection. Read the validation message exactly as shown.
- **The Tapmy URL works, the custom domain does not.** Leave the Tapmy URL live and fix DNS, certificate and routing on their own.
- **Old content keeps showing.** Compare the preview with the public page, then test from a different network. Note when you last published.

Tapmy does not publish exact queue times, timeouts or DNS propagation promises, so do not rely on a fixed wait. Never change a DNS record to a value Tapmy has not shown for your Site.

Do not delete a working link, domain record, published offer or customer-facing page until its replacement is tested. Write down the time of each publish or DNS edit so you can tell cached pages from propagated ones.

## After it works {#next-steps}

Repeat the signed-out check and run a test purchase or signup. Update the links you have shared only once the final URL is stable.

Still stuck? [Contact Tapmy Support](/help/tapmy-support) with your Site URL, what you see, the time and time zone, your browser or device and screenshots with private details hidden. Never send passwords, verification codes, DNS-provider logins, tokens or customer data.