A stark ‘page doesn’t exist’ error traced to a third-party widget, not a rebuild.
A trades business had a homepage showing a stark “page doesn’t exist” error in the middle of the page. It looked like the site or server had failed, the kind of thing that can trigger an expensive rebuild or emergency server work.
We diagnosed it methodically before touching anything. The site, server and DNS all checked out healthy. We traced the fault to a third-party customer-reviews widget embedded on the homepage: the external provider had removed the business’s account on their side, so the provider’s own error page was loading inside the embedded frame. The fix was simply to remove or replace the broken embed.
The real cause was a third-party fault, not a hosting or WordPress problem, so the client avoided an unnecessary rebuild and paid for a fix rather than hours of server investigation.
Whether it is security, hosting, compliance or a site that is misbehaving, we will take a look and tell you straight.
Get in touch