Publishing issues
When a change doesn't appear on the live site.
When a change does not show up on the live site, checking approval, then the publish itself, then caching isolates most causes.
An article cannot be published
- Confirm the version was approved, not just saved as a draft. The Publish button stays disabled until the article is approved.
- Check whether it was edited after approval. Editing returns it to pending review, so it needs approving again.
- Check that an author is set and that no technical errors remain.
- If critical SEO issues are blocking it, fix them or use Publish anyway.
- Check your role. Approving needs reviewer or higher, and publishing needs publisher or higher.
Scheduled publishing did not happen
- The publish cadence only publishes approved articles. Check that the article is still approved.
- Check that auto-publishing has not been switched off for the site.
- If there is no free slot in the next 30 days, the article cannot be scheduled. Add auto-publish times or publish manually.
- If a scheduled publish fails, the schedule is cleared. Publish it again manually.
WordPress or social publishing failed
- Read the error message returned by WordPress, fix the cause, then publish again or run Update WP. There is no automatic retry.
- For Facebook, check that a Page is selected.
- Failed automation jobs can be retried from the automation queue.
Published, but the page has not changed
- The public API is cached; allow revalidation to complete.
- For landing pages, check that you saved the draft before publishing. Unsaved changes are not published.
- Check the market and locale. A locale with no value falls back to the market's default locale, then en.
- Check that the page has not been switched off for that market.
To tell a front-end problem from a CMS one, call the public API directly and check whether it returns the value you expect.