Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My WordPress content no longer shows correctly on my new front-end website

Short answer

A headless WordPress site is two systems: WordPress holds the content, and a separate website reads it through the REST API. Problems usually appear where they meet: private content needing authentication, changed fields, previews and plugins that affect only the old theme. Check what changed first, and do not update WordPress blindly.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I edit a page in WordPress and the public website does not change.
  • Drafts and previews do not show on the new site.
  • A plugin I installed does nothing on the live website.
  • Some fields or images are missing since an update.
  • Only my developer understands how the two parts fit, and they are gone.

Why does this happen?

  1. The website reads WordPress through its API

    WordPress documents a REST API that lets other applications send and receive JSON data to interact with the site. A separate front end reads your posts and pages from it, so WordPress itself no longer draws the public pages.

  2. Private content needs authentication

    The same documentation says the API applies the site's usual authentication restrictions. Public content is generally accessible, while private or password-protected content, internal users, custom post types and metadata require authentication or explicit configuration to be exposed. A missing draft or field often traces to this.

  3. Plugins that change the theme do not reach the new site

    A page builder, form or SEO plugin changes what the WordPress theme displays. A separate front end does not use that theme, so the effect has to be rebuilt there or read through the API.

  4. Updates change what the API returns

    A WordPress, plugin or field-plugin update can rename or restructure data, and the front end that expected the old shape shows gaps.

  5. The two parts are not refreshed together

    If the front end stores copies of pages, a change in WordPress shows only after those copies are refreshed. When that link is missing or broken, the site looks stale.

What can I do about it today?

  1. Find out what changed lastA WordPress or plugin update, a hosting change or a new field. The first symptom date narrows it.
  2. Hold off on further updatesDo not update plugins or WordPress to see if it helps. Take a backup first through your hosting panel if you can.
  3. Check both addressesNote the address where you log in to WordPress and the address visitors see. Ask your developer how they are connected.
  4. Note one exampleWrite down one page that is wrong, what it should show and what it shows, with a screenshot.
  5. Confirm who has accessYou need the WordPress admin login, the hosting account and the account where the front end is deployed.

When should I bring someone in?

  • Content you publish does not reach the live site at all.
  • The person who built the front end is unreachable.
  • Forms, search or checkout stopped working after the change.

How do I handle it?

  1. Map the two halvesI find where the front end is hosted, which WordPress address it reads, and how a publish in WordPress is supposed to reach it.
  2. Compare API output with the pageI look at what the API returns for the broken page and compare it with what the website expects.
  3. Fix the join, not the symptomThe repair goes at the point where data, access or refresh is wrong, not as a patch on one page.
  4. Test on a copyChanges are checked on a staging copy with a backup of WordPress first.
  5. Write down how it fits togetherYou receive a short note on how the two parts connect, who owns each account and what to do before the next update.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Should I go back to a normal WordPress site?

Only if the split gives you nothing. Decide after the cause is known; the problem may be one setting.

Is headless WordPress less secure?

I make no general claim. What matters is that WordPress stays updated and that private content is not exposed through the API.

Why can I see my draft in WordPress but not on the site?

Per WordPress documentation, private content requires authentication to be read through the API, so a front end needs explicit access to show previews.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.