Esipher Guides · November 15, 2026

Why are my WordPress changes not showing? A practical Esipher guide

Esipher logo between an older website with a clock badge and an updated website with a green check

When WordPress changes are not showing, first check whether the new content reached WordPress at all. Then check the page visitors actually open, the active theme and any cached copies. If you use Esipher, a change in your design preview, a successful GitHub build and an applied WordPress update are three separate stages. Finding the stage that is missing is more useful than repeatedly clearing your cache.

Start here: is the new content missing or just hidden?

Open the exact page address in a private browser window while signed out of WordPress. Compare it with the page you edited, not just your design preview. A preview can show unpublished content or a completely different version of the website.

Next, look for the new page or article in WordPress. If it is absent, investigate the export and import. If it is present and published but the menu opens something else, investigate your links and homepage settings. If the correct published page exists at the correct address but still looks old, investigate caching.

  • Missing from WordPress: check the build and import
  • Present but not linked: check publication, menus and page addresses
  • Correct page still looks old: check the active theme and cache

1. Check that your finished export includes the changes

Esipher converts finished Vite and React builds, not an unbuilt source folder. Saving a new article in your design tool does not prove that the website files being imported contain it. If you upload a ZIP, make a fresh finished export after saving your changes.

For a website with multiple pages, inspect the exported files for the new page and its content. Also check that your articles listing links to it. A page visible through client routing in the original app is not automatically a separate HTML page in the export. Esipher does not convert client routing beyond what exists in the built HTML.

If the new page is missing from the exported website, fix the export first. WordPress cannot display content that never arrived in the uploaded files.

2. Check the GitHub repository and latest build

With Connected Projects, confirm that Esipher is connected to the repository containing your updated website. If your setup specifies a branch, check that your changes were saved to that branch. Updating a different repository or branch will not update the connected project.

Open the relevant workflow run in GitHub Actions. Check whether the latest change has a successful build, rather than relying on an older successful run. If it failed, read the reported error and resolve it before trying to apply the update.

A successful build is an important checkpoint, but it does not prove that every new page was included. Inspect the build output where available and check that it contains the article you expect.

3. Apply the ready update in Esipher

Open Esipher, then Connected Projects, in your WordPress dashboard. When the latest build is ready, an administrator must select Apply update. The official Esipher listing says nothing installs or activates without that approval.

Connecting GitHub or pushing a change is not the same as applying it. Review any status or error shown after applying the update. If you already applied it and the content is still missing, continue with the checks below instead of assuming another click will solve the problem.

Before changing an established site, keep a current backup of its files and database. Esipher is an early development release and does not yet provide a conversion history or rollback screen.

4. Check published pages, the homepage and menu links

Find the new content under Pages or Posts, depending on how it was imported. A converted article page may be a WordPress Page rather than a native blog Post. Confirm that it is published, then use its View link to open the address visitors can access.

If the direct page works but your Insights or Blog link shows an older listing, check the destination of that link. In a classic theme, review Appearance, then Menus. In a block theme, review the navigation in the Site Editor. Make sure it points to the intended published page.

In Settings, then Reading, check which page is assigned as the homepage. For converted static article listings, also check the imported listing page itself: creating an article does not automatically rewrite a static list of links.

If you see duplicate page names or addresses with number suffixes, compare them before changing anything. A newer copy may contain the content while your menu still points to an older one. Back up and check incoming links before removing duplicates. Do not delete pages simply because their names look similar.

5. Check the active theme and clear the relevant cache

If the content arrived but the design still looks old, check Appearance, then Themes, to see which theme is active. Review the converted theme on a test copy where possible before making a theme change on your live website.

WordPress documentation identifies browser cache, server cache, caching plugins and editing the wrong location as common reasons changes do not appear. Once you have confirmed the correct content and page, clear the cache through the controls provided by your caching plugin, host or CDN, if you use them.

Retest the exact public address in a private window and on another device. Do not disable unrelated plugins or delete website files at random. Clearing cache cannot create a missing article, repair a failed build or correct a menu pointing to the wrong page.

Common questions about WordPress and Esipher updates

Why does the preview show my article but the live website does not?

The preview may be using newer source content than your export or imported website. Check that the finished build contains the article, that the latest update was applied, and that the public listing links to the correct published page. Cache is only one possible cause.

Does Esipher publish every GitHub change automatically?

No. Connected Projects uses your own GitHub account and builds on pushes, but an administrator must click Apply update before the update installs or activates. A successful build alone is not a live update.

Why does the homepage work while a new article returns a missing page error?

Check whether the article exists as built HTML and whether it was imported as a published WordPress page. A route that only existed inside the original app is not automatically exported or converted. Also confirm that the link uses the imported page's actual address.

Will converting the design restore login, forms and live data?

Not automatically. Esipher does not convert backend authentication, database operations or live data. A screen can look correct while the service behind it is absent. Check these features separately and plan appropriate WordPress integrations.

What should I include when asking for help?

Share the affected public page address, what changed, whether you used a ZIP or Connected Projects, and the relevant build or apply error. Remove client secrets, tokens and other credentials from screenshots and logs before sharing them.

Is Esipher free to use?

The current Esipher release is free for now. Review its current features and limitations before starting.

Esipher

Convert finished Vite and React builds on your own WordPress server, with optional GitHub connections and administrator approved updates. Free for now.

Get Esipher free

Features and availability