## **🔍 Overview**

Website Studio runtime errors and build crashes can interrupt your landing page workflow in several ways — including white screens on project load, the builder hanging at 98%, **"Something Went Wrong"** messages, or publish failures. This article explains the most common causes and the steps to resolve them.

## **⚠️ Common Error Types**

- **White screen on project load** — the project opens but displays a blank page with no editor controls.
- **Builder hangs at 98%** — the loading progress bar stalls and does not complete.
- **"Something Went Wrong" crash** — typically triggered when a prompt includes multiple URLs at once.
- **Publish failure** — an error referencing **"Failed to read pages.manifest.json"** appears when trying to publish.
- **Persistent runtime errors** — the page repeatedly malfunctions after reopening or editing.

## **🛠️ Step-by-Step Fixes**

1. **Refresh the page and clear your browser cache.** Many transient runtime errors resolve with a hard refresh. Press **Ctrl + Shift + R** (Windows) or **Cmd + Shift + R** (Mac) to force a full reload without cached data.
2. **Use a supported browser.** Website Studio performs best on the latest version of Google Chrome or Microsoft Edge. If you are using Firefox, Safari, or an older browser version, switch browsers and try again.
3. **Close and reopen the project.** If the builder is stuck at 98% or showing a white screen, close the tab, return to your Search Atlas dashboard, and reopen the project from the Website Studio project list. Do not click **Stop** when the builder is mid-load — this can leave the project in an empty state.
4. **Use one URL per prompt.** If you triggered the **"Something Went Wrong"** error while entering a prompt, ensure you are only including a single URL in each prompt submission. Remove any additional URLs and resubmit.
5. **Retry publishing after a short wait.** The **"Failed to read pages.manifest.json"** publish error is usually temporary. Wait 60 seconds, then attempt to publish again. If the error repeats, proceed to the next step.
6. **Duplicate the project and work from the copy.** If a specific landing page project consistently crashes on load, open Website Studio, locate the affected project, and use the duplicate option. Work from the duplicated version while the original is investigated.
7. **Check for unsaved changes before closing.** Always use the built-in save controls before closing a tab. Force-closing the browser during an active edit session can corrupt the project state and trigger errors on the next load.

## **🚫 What to Avoid**

- Do not click **Stop** while the builder is loading — this can leave your project in an unrecoverable empty state.
- Do not paste multiple URLs into a single AI prompt field.
- Do not publish immediately after making a large batch of edits — give the autosave a moment to complete first.

## **✅ When Everything Is Working Again**

Once the error is resolved, your landing page should load fully in Website Studio, the progress bar should complete past 98%, and publishing should succeed without manifest errors. If you previously duplicated a project as a workaround, you can delete the broken original once you confirm the copy is stable.

## **💬 Still Experiencing Issues?**

If the steps above do not resolve your runtime error or build crash, our team can investigate the specific project and error logs. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.