You can still see the block in the editor, yet it vanishes on the live page. That is frustrating, but it also gives you a useful clue: the content may be saved correctly while the shortcode, embed, template or front-end script fails to display it.
Start by naming the exact thing that is missing and checking the same URL while logged out. A blank video, a printed shortcode and a mobile menu that will not open come from different parts of WordPress, so they should not all be treated as cache problems.
Use the symptom table to find the relevant section. If the entire page returns 404 or a critical error, follow the linked page-loading guide instead.
Guide reviewed: October 8, 2026. Menu labels use English WordPress; provider-specific controls may differ.
Find the missing layer before changing settings
| Missing or broken element | Check first | Test to make |
|---|---|---|
| Shortcode printed as text | Handler plugin and exact shortcode | Use the simplest documented tag in a Shortcode block |
| Video stays a link | Provider URL and embedding availability | Compare another public video from that provider |
| Sidebar is absent | Template and widget area | Compare a page using the expected sidebar layout |
| Mobile toggle does nothing | Menu script and optimization settings | Compare the same visitor page on a test copy |
| Comments, search or feed | That output’s own settings and response | Test the specific form or feed URL |
What is missing, and where does it still appear?
- Open the affected post in the editor and confirm the element is saved.
- Open its public URL while logged out.
- Compare a second page using the same feature.
- Record whether the failure depends on the page, device or login state.
Before changing anything, compare the editor with the public page. Is the original text, block or widget still present in the editor? Does the same element work on another page? Does it disappear only on a phone, or only when you are logged out? A few observations can narrow the problem considerably.
Suppose a contact form appears correctly on one page while another shows its shortcode as text. The plugin may be working, but the second page may contain a misspelled tag or place it in a block that does not process shortcodes. If the form is missing everywhere after a plugin was disabled, the plugin itself becomes the more useful place to look.
Keep a note of the affected URL, what you expected to see and the last change made before the problem appeared. That gives you a way to judge whether a later adjustment has helped, and provides useful context if you need assistance from the theme or plugin developer.
When a shortcode appears as text
- Copy the shortcode from the provider’s documentation.
- Confirm its supplying plugin or theme is available.
- On a draft, insert a Shortcode block and paste the simplest valid tag.
- Preview it before adding optional attributes or replacing the live content.
A shortcode is a small tag that asks WordPress to generate something, such as a form or gallery. The tag needs a registered handler, usually supplied by a plugin, theme or custom code. Without that handler, WordPress cannot produce the intended output.
If you see something like [example] on the public page, compare its spelling and attributes with the provider’s documentation. Then look at whether the relevant plugin is active. A recent theme change can also matter when the old theme supplied the shortcode.
For a shortcode in a post or page, the dedicated Shortcode block is a sensible place to test it. A Custom HTML block serves a different purpose, so moving the same text between blocks does not always produce the same result. It is helpful to try the provider’s simplest documented example before adding optional settings.
When an embedded video stays blank or becomes a link
WordPress can turn supported links into embedded content through oEmbed. That depends on the provider, the URL and a successful request for the embed information. A link that opens normally in your browser is not necessarily a URL that the provider allows WordPress to embed.
Try the original video’s share URL in an appropriate Embed block and compare it with another public video from the same service. If one works and the other does not, availability or embedding restrictions on that particular video are worth checking. If neither works, the provider or a request from your site may be involved.
There is also a difference between an embed that never appears in the editor and one that looks correct there but disappears on the public page. The second situation can involve privacy controls, blocked resources or scripts on the public page. Browser Console and Network messages can help distinguish a failed request from a display problem.
WordPress may retain cached embed information. Refreshing that information can help after the original problem is resolved, but repeated cache clearing cannot make an unsupported or unavailable video embeddable.
A sidebar can disappear after a theme or template change
Widgets appear in the areas provided by the active theme. A new theme may use different areas, and a page template may omit the sidebar even when the widget settings still exist. This is why a missing sidebar does not automatically mean your widgets have been deleted.
Compare the affected page with a page that still has the expected layout. In a classic theme, the widget areas and template selection are useful places to look. In a block theme, the Site Editor and the relevant template or template part may control that area instead. The available menus depend on the theme.
If the area exists but only one widget is missing, its own visibility settings become more relevant. Some plugins limit an element to particular pages, devices or logged-in visitors. Understanding that rule is more useful than recreating the widget and leaving the same rule in place.
A mobile menu that will not open needs a different check
Menu content and menu behavior are separate. If the expected links are absent, look at the menu assignment or Navigation block. If the links exist but the toggle does nothing, the menu may be waiting for a script that failed to load or encountered an error.
This can become noticeable after a performance plugin changes script loading or CSS. A controlled comparison with that particular optimization disabled on a test copy can show whether it is involved. Changing several optimization settings together makes the result harder to interpret.
Testing while logged out is useful because visitors may receive a different cached page from the one you see as an administrator. Once the underlying setting or script issue is corrected, refreshing the affected cache helps visitors receive the corrected version.
Comments, search and feeds have their own clues
A useful search test: select one published post, copy a distinctive word from its title, and search for it as a visitor. If it is found but products are not, inspect which content types the search includes. If neither is found, check the search request itself.
A missing comment form may come from the individual post’s discussion settings, a rule that closes comments on older posts, or a template that does not display the comment area. Moderation is different: a submitted comment waiting for approval does not by itself explain why the form is absent.
For search, begin with a known public post and a distinctive word from its title. If that post appears but a custom content type does not, a theme or search plugin may be limiting what the query includes. If every search fails, the search form’s destination and the wider search configuration deserve attention.
An RSS feed is another separate output. Opening its feed URL directly helps you see whether it returns feed data or an error page. Some browsers do not present XML attractively, so an unfamiliar display alone is not proof of a broken feed. A login page, server error or unwanted content in the response is a more specific clue.
How to tell whether the fix has worked
After one change, revisit the original URL in the same conditions that revealed the problem. A restored sidebar on a desktop is not enough if the reported issue was a mobile menu. A working editor preview is not enough if logged-out visitors still see an old page.
When the element returns, try another page that uses the same feature. This helps you catch a fix that solves one example but disrupts another. If the problem remains, your notes should now identify the missing element, the provider or template involved and the result of your test. That is a much clearer support request than simply saying that WordPress content is not showing.
Official references and related guides
- WordPress Shortcode API
- WordPress oEmbed documentation
- Managing WordPress widgets
- WordPress feed documentation
If an entire URL returns a missing-page response, the WordPress 404 guide is a more useful next step. If the site cannot load normally at all, see the critical error guide.
Keep the comparison specific
Write down “the mobile toggle on this URL does not open while logged out” instead of “content missing.” Include the theme or supplying plugin, last change, and result on a second page. That gives support a reproducible problem and prevents unrelated changes to media or server routing.
Frequently Asked Questions
Why is WordPress content visible in the editor but not on the live page?
The public page may still be serving a cached version, a different template, or content controlled by a shortcode, plugin, or display condition. Open the exact public URL in a signed-out window first, then clear the relevant page, plugin, server, and CDN caches. If the content is still missing, check the page template and any conditional visibility settings before disabling plugins.
Why does WordPress content disappear only on mobile?
Mobile-only problems usually come from responsive CSS, breakpoint-specific widget or menu settings, or a separate cached mobile version. Compare the page in a narrow browser viewport and on a real phone, then inspect the missing element’s visibility rules. Do not remove the theme or multiple plugins at once; change one controlled setting at a time and retest the public URL.
Should I clear cache before changing the theme or plugins?
Yes. Save a backup or staging copy, record what is missing, and clear the browser, WordPress, host, and CDN caches that apply to the page. If the problem remains, test one theme or plugin change at a time so you can identify the cause and restore the previous state without losing unrelated settings.