How to handle 404 pages in Bubble

Bubble does not have automatic 404 handling for broken dynamic URLs. You must create your own 404 page and send users to it using conditional redirects. The usual setup is: make a regular page called 404, then on every page that loads dynamic data (for example: a page with a type of content), add a Page is loaded workflow that checks whether the data exists. If the data is empty, redirect the user to your 404 page.

Create a custom 404 page

Create a new page in Bubble named 404. It can contain any UI that explains the page wasn’t found.

• Keep it simple: a text saying “Page not found” and a button to go home.

Handle 404s for dynamic pages

Most 404 situations happen when a user types or clicks a broken URL like /product/some-wrong-id. Bubble loads the page, but the object is empty. You must detect this and redirect.

• Open the dynamic page (example: Product page).
• Make sure the page has a Type of content set (example: Product).
• Add a workflow: When Page is loaded.
• Add an action: Navigate → Go to page → choose 404.
• Set the condition on the event: When Current Page Product is empty.

// Condition for the workflow
Current Page Product is empty  // means Bubble couldn't find the thing from the URL

Handling 404s for URL parameters

If you’re loading data using Get data from URL instead of a page’s Type of content, do the same check on page load. If the data fetch returns empty, send the user to 404.

• Event: When Page is loaded.
• Only when: Do a search for X:first item is empty.
• Action: go to page 404.

Optional: set a 404 for missing static pages

Bubble does allow setting a default 404 page in Settings → SEO → 404 page. This only catches nonexistent static URLs, not broken dynamic data. You should still use the workflow method above.