Preview before publishing
Bigger changes to a live page are made on a hidden copy first. You open a private preview link, and one approval puts the new version live on the same address. After every change, PressHelm also checks the live page really shows it.
Staged edits, step by step#
Your developer stages the page#
A hidden draft copy of the published page is made, with its page-builder layout. Visitors still see the old page.
Changes are made on the copy#
Text, blocks, Elementor or Beaver Builder widgets, SEO fields: all on the copy, so no approval is needed yet.
You preview it#
You get a private preview link (valid 48 hours, works without logging in, also while the store is in "Coming soon" mode, never indexed by search engines).
One approval publishes it#
The approval message names the page and links the preview. Publishing puts the new version on the same page and address, keeps a revision, and checks the live page. The copy goes to the trash.
If the live page was changed by someone else after it was staged, publishing stops and says so, so nothing gets overwritten by surprise.
Your Telegram botChecked on the live page#
After a change to a published page, PressHelm loads the page the way a visitor gets it and looks for the change: the new text or title, the page builder's CSS, your custom CSS. The receipt says "checked on the live page", or "saved, but not visible on the live page yet" when a page cache or CDN still shows the old version (clear it, or wait). A change is never undone just because a cache is slow; a change that breaks the page still is, automatically.
See any page like a visitor#
Ask "how does my pricing page look?" and your developer reads the live page: headings, text, links, images without alt text, forms, CSS and JavaScript files that fail to load, PHP errors printed on the page. With a screenshot, it also sees the page as Google's browser renders it on a phone or desktop.