Search Atlas Help Center

🛠️ Migrate, Clone, and Clean Up Website Studio Pages

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🗺️ Overview

This article covers the full workflow for cleaning up a Website Studio project that has content published under incorrect URLs. Specifically, it walks you through migrating content to the correct /blog/ URL structure, updating author metadata, and permanently removing outdated URLs using a 410 (Gone) status so they are excluded from your sitemap and database.

Important: Some steps in this workflow are affected by known platform limitations currently being resolved by our engineering team. Where a limitation applies, we have noted the recommended workaround.

⚠️ Known Platform Limitations to Be Aware Of

Before you begin, review these active issues that may affect your workflow:

  • Page cloning is not yet available. Website Studio does not currently support cloning or duplicating an existing page within or between projects. This blocks a direct copy-and-migrate path. A fix is in progress.
  • Bulk import from Content Genius is not yet supported. You cannot pull your full blog library into Website Studio in bulk at this time.
  • Deleting a published page does not immediately revoke its public URL. There may be a short delay before the URL becomes inaccessible after deletion. This is a known issue and is being addressed.
  • Pillar page editing suggestions may point to incorrect pages. If Website Studio redirects you to the wrong page when you try to edit a pillar page, use the direct page management view instead (see steps below).

📋 Step 1 — Identify the Incorrect URLs

Start by making a list of every page that is published under the wrong URL. You will need this list to complete the migration and deletion steps.

  1. Open Website Studio from the left navigation menu.
  2. Select your project and go to Page Management.
  3. Review all published pages and note any that are not under your intended /blog/ URL path.
  4. Record the full URL of each incorrect page alongside the correct target URL it should move to.

✍️ Step 2 — Recreate Content Under the Correct /blog/ URLs

Because page cloning is not currently available, content must be manually recreated under the correct URL. Follow these steps for each page that needs to move:

  1. In Page Management, click Create New Page.
  2. Set the URL slug to the correct /blog/your-page-name path.
  3. Open the original incorrect page in a separate browser tab.
  4. Copy all content — headings, body text, images, meta title, and meta description — from the original page into the new page.
  5. Update the author name field. Change it from Marcus Eriksson to Nestor Vazquez (see Step 3 for full author metadata instructions).
  6. Save and publish the new page once all content and metadata are confirmed correct.

👤 Step 3 — Update Author Metadata

Author metadata is set at the individual page level inside Website Studio. To update the author name on each migrated page:

  1. Open the newly created page in the Website Studio editor.
  2. Navigate to the Page Settings or SEO Settings panel.
  3. Locate the Author field and replace Marcus Eriksson with Nestor Vazquez.
  4. Confirm the author name also appears correctly in any visible byline element on the page design itself. Update the design element manually if it does not pull from metadata automatically.
  5. Save your changes.

🗑️ Step 4 — Delete Incorrect URLs and Apply 410 Status

A 410 (Gone) status tells search engines that a page has been permanently removed and should not be re-crawled or re-indexed. This is different from a 301 redirect and is the correct choice when the old URL should leave no trace.

  1. Confirm the new /blog/ version of each page is live and correct before deleting the old URL.
  2. In Page Management, locate each incorrect URL.
  3. Open the page settings and look for the HTTP Status or Redirect / Status Code option. Set the status to 410 Gone — do not set a redirect destination.
  4. Save the setting, then delete or unpublish the page.
  5. Do not create a 301 redirect from the old URL to the new one. A 410 signals permanent removal; a redirect would pass authority to the new page but also signals the old URL once existed, which is not desired in this case.

Note: Due to the known issue with delayed URL revocation, check the old URLs again 24 hours after deletion to confirm they return a 410 response. You can use a free HTTP status checker tool to verify.

🗺️ Step 5 — Remove Old URLs from Sitemap and Database

After applying the 410 status and deleting the pages, ensure the incorrect URLs are fully removed from your sitemap:

  1. Go to your Website Studio project Settings.
  2. Open the Sitemap section and confirm the deleted URLs no longer appear. If they do, regenerate or republish the sitemap.
  3. Submit your updated sitemap to Google Search Console to prompt faster re-crawling and de-indexing of the removed URLs.
  4. In Google Search Console, use the URL Removal tool to request temporary suppression of the old URLs from search results while Google processes the 410 status.

✅ Checklist — Before You Finish

  • All content is live under the correct /blog/ URLs
  • Author name reads Nestor Vazquez on all migrated pages
  • All incorrect URLs return a 410 Gone status
  • No 301 redirects point from old URLs to new URLs
  • Sitemap has been regenerated and resubmitted
  • URL removal requests submitted in Google Search Console

💬 Need Help?

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.