## **🧭 What this process removes**

A backend purge removes unwanted ghost, orphaned, staging, and corrupted routes from the website data and cache layers. This can include duplicate URL variants, encoded characters, outdated imported pages, and routes that no longer belong to the current site.

A clean rebuild then recreates the website using the approved pages and settings. This helps prevent removed routes from returning after publishing or cache refreshes.

## **🔎 Prepare the route list**

1. Collect every unwanted URL and variant in one list.
2. Include differences in capitalization, trailing slashes, query parameters, encoded characters, and alternate paths.
3. Mark each route as ghost, orphaned, staging, corrupted, or otherwise invalid.
4. Confirm which pages and assets must remain live.

Include the complete URL, not only the visible page name. Encoding garbage and duplicate variants can otherwise be missed during cleanup.

## **🧹 Request a backend purge**

Backend purge requests are handled by the Search Atlas team because they can affect stored site data, cache layers, and published content. Provide the complete route list and clearly request both actions: purge the invalid routes and start a clean rebuild.

Do not repeatedly republish while the purge is being processed. New publishing activity can recreate routes or make verification harder.

## **🏗️ Start the clean rebuild**

After the purge is confirmed, open **Website Studio** from the left sidebar. Review the remaining pages and site settings, then use the appropriate site workflow, such as **Import Site** or **Generate PPC Site**. Submit the rebuilt site only after confirming that unwanted routes are excluded.

Publishing and cache cleanup are separate steps. A page may appear unchanged temporarily if a browser, edge, or website cache still contains an older version.

## **✅ Verify the result**

1. Check the previously invalid URLs and all listed variants.
2. Confirm that valid pages still load and that removed routes no longer resolve to published content.
3. Refresh the relevant report data from **Reports** in the left sidebar, then review the updated results.
4. Test again after cache propagation is complete, using a private browser window when possible.

If a removed route returns, capture the exact URL, when it returned, and the action that preceded it. This information helps identify whether the route was recreated by an import, republish, redirect, or external cache.

## **💡 Prevent routes from returning**

- Use one approved source of truth for pages and imports.
- Remove obsolete pages from the source before rebuilding.
- Keep staging and production content separate.
- Review redirects, internal links, sitemaps, and integrations for references to deleted routes.
- Allow each purge or rebuild to finish before starting another publish action.

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.