Why don't my changes show on my live site?

TeleportHQ doesn't update your live site by itself: design and page changes reach visitors only after you click Publish to Production in the Publish window. Content is different: blog posts, help center articles and records in the TeleportHQ database go live without a publish, usually within seconds. A page that fills a state from a data source, such as a Google Sheet or a REST API, reads that data again on every visit, so changes in that source show without a publish too. A list with caching on can take up to its cache time (5 minutes by default). If you did publish and still see the old version, work through the checks below, from the most common cause to the least.

1. You haven't published since the change#

How to tell: in the TeleportHQ Publish window, on Production, you see Unpublished changes under your site's address. Point at it to read "You have edited this project since it was last published to production."

Fix: at the top right of the editor, click Publish, then Publish to Production. See How to publish your site.

These changes also need a new publish:

• page design, text and images, pages you add, rename or delete;
• Project settings, such as the favicon, custom code, fonts and the SEO settings, Show this site in search engines included;
• restoring a backup;
• the design and settings of the Blog and Help Center pages, and their categories.

2. You published to Staging, not Production#

How to tell: on Production, you see Staging is ahead of your live site with a Make it live button.

Fix: click Make it live to put the build you tested on your live site, without rebuilding it. Or publish to Production. See How to test changes on a staging site before going live.

3. The build is still running or failed#

How to tell: you saw "Your project is still building on Vercel. It will go live on its own — check the Deployments tab in a few minutes.", or the status at the right of your address says Publish failed.

Fix:

1. In the Publish window, click Deployments on the left.
2. Look at the status of the newest row: Building or Queued means it's still running; Ready means it finished building; Error means it failed.

3. If it's still running, wait a few minutes, then reload your site.
4. If it failed, click ⋮ on that row and choose Build Logs. See How to read build logs when publishing fails and Publishing failed: what should I do?.

A failed or unfinished build leaves your previous version live.

4. Blog posts, help center articles and data#

TeleportHQ reads content from your data while visitors open the page, so content changes don't wait for a publish:

• Blog posts and Help Center articles go live as soon as you save them with the Published status, usually within seconds, once the Blog or Help Center pages have been published at least once. A Draft, an Archived post or a post Scheduled for later stays hidden. In rare cases the live list can take up to 5 minutes to refresh. See Why isn't my blog post showing on my site?.
• Records in the TeleportHQ database, for example products or a table you show in a list, reach the lists on your live site on the next page load. A details page (one page per record) can take about a minute. When you change records in the editor, lists with caching on are refreshed within seconds too.
• A page with a state filled from a data source (a state whose Source is Data source or SQL query) is built with fresh data each time a visitor opens it. A change in that source, for example a new row in your Google Sheet or the TeleportHQ database, shows on the next page load. A REST API source with Cache API responses on can still answer from its cache. See How to store and use values with States.
• A list with caching on (in the list's settings, Caching → Cache results) shows its stored copy until Cache for runs out. The default is 5 minutes. Data from sources other than the TeleportHQ database, such as Google Sheets, Airtable or a REST API, isn't refreshed early: wait for the cache time to pass. A REST API data source can also cache its answers with Cache API responses.
• A headless CMS connected to your site refreshes its pages on its own schedule. To refresh them when your content changes, set up the CMS webhook. See How to update your site's content without republishing (CMS webhook).

If your data looks different in the editor and on your live site, see Why does my data look different in the editor and on my live site?.

5. Only your custom domain shows the old version#

How to tell: your teleporthq.app or teleporthq.site address shows the changes, but your own domain doesn't.

Fix:

1. Open your domain in a private browser window. If it shows the changes there, your browser kept an old copy (see check 7).
2. In the Publish window, check the status of your domain in the Custom domain section. If the domain isn't verified, see Why is my custom domain not working?.
3. Publish to Production again, with Publish to custom domain ticked at the bottom of the window. It's ticked each time you open the window. A publish to Production with that box unticked goes live on your TeleportHQ address only: your domain keeps the previous version.

6. Some pages were left out#

How to tell: after publishing you saw "1 page that failed to generate was excluded from the published site." (or "… pages that failed to generate were excluded …").

Cause: TeleportHQ leaves out pages that AI started to build but never finished, so your site doesn't show empty pages. In the editor, such a page is marked Generation failed (or Generation didn't finish) in the pages list and on the canvas.

Fix: open the page and click Try again (or Retry) to generate it again, or build it yourself, then publish again. Pages you excluded on purpose are left out too. See How to keep a page out of your published site.

7. Your browser shows a saved copy#

How to tell: the site looks old on your computer, but correct on your phone or in a private window.

Fix: reload the page while holding Shift, or open the site in a private window.

8. A link leads to an old or missing page#

How to tell: the page itself is up to date, but a button or menu link opens the wrong page or a "page not found" page.

Fix: at the top left of the editor, click the yellow issues chip. The Issues window lists every link that leads nowhere, under Broken links on pages, before and after publishing. Fix the links, then publish again. See How to find and fix broken links on your site.

9. You're editing a different project#

How to tell: the project name at the top of the editor doesn't match the site you're checking, for example you're in a copy.

Fix: on your dashboard, each project card shows its address. Open the project whose address matches your live site, and publish that one.