Fixing Broken Links After Cloning an Elementor Site

Introduction

Cloning an Elementor site — for a staging copy, a client demo, or a fresh dev environment — is fast with tools like Duplicator or All-in-One WP Migration. But clones bring their own flavor of broken links that's different from a straightforward domain change: leftover absolute URLs pointing back at the original site, table-prefix mismatches, and duplicate-content risks if the clone gets indexed by accident.

This guide covers the broken-link issues specific to cloned Elementor sites and how to fix them safely.

What you'll learn:

• Why cloned sites link back to the original by default
• How to update every internal link to the new URL
• Keeping the clone out of search results while you work
• A pre-launch checklist before the clone goes live

Why Clones Break Links

Cloning tools copy your database as-is, including every absolute URL Elementor stored — internal links, image sources, button targets, popup triggers. Unless the tool specifically rewrites URLs during the clone (some do, many don't by default), every one of those still points at the original domain.

The Problem: Because Elementor stores this data as serialized PHP inside wp_postmeta, a simple text editor find/replace on exported files will corrupt the structure. You need a tool that understands PHP serialization.

Method 1: Update URLs During the Clone

When to Use This Method

• Your cloning plugin supports a URL find/replace step (most migration plugins do)
• You know the new URL before you start

Step-by-Step Process

1. During export/import, look for a "find and replace" or "search and replace URLs" option
2. Enter the original domain and the new clone's domain
3. Complete the import, then spot-check a few pages for broken links or images

✅ Pros: Handled automatically as part of the migration, no extra step.

❌ Cons: Not every plugin offers this, and it's easy to skip by accident during a quick clone.

Method 2: Fix It After the Fact

When to Use This Method

• The clone is already done and links are still pointing at the original
• Your cloning tool didn't offer a URL rewrite step

Step-by-Step Process

1. Back up the clone's database (yes, even the clone)
2. Install Better Search Replace on the clone
3. Search for the original domain, replace with the clone's domain, across wp_posts, wp_postmeta, and wp_options
4. Dry run first, then run for real
5. Clear the Elementor cache

✅ Pros: Works no matter how the clone was made, catches every table at once.

❌ Cons: Requires comfort running a database tool on a copy of production data.

Method 3: Search & Replace Inside the Elementor Editor

Search & Replace for Elementor can run the same domain swap from inside the editor, with a preview of exactly which links, images, and buttons will change before anything is saved — useful if you'd rather not run a raw database tool on a client's cloned site.

✅ Pros: Visual preview, no direct database access needed.

❌ Cons: Paid, and covers Elementor content specifically rather than every database table.

Pre-Launch Checklist

• Add a noindex tag or password-protect the clone while it's a work in progress
• Check internal links, images, popups, and forms all resolve to the clone's own domain
• Verify the sitemap and canonical tags reference the correct domain before going live

Frequently Asked Questions

Q: Why do images still load from the original site after cloning? A: Some migration plugins only copy the database, not the uploads folder, so image URLs point back to the original media library unless you also migrate files or update the URLs.

Q: Will search/replace on the clone affect my live site? A: No, as long as you're running the tool on the clone's own database, not the original.

Q: How do I stop Google from indexing my clone? A: Use Settings → Reading → "Discourage search engines" and consider password protection for anything publicly accessible.

Q: Does this apply to local development clones too? A: Yes — local URLs (like mysite.local) have the exact same issue and the exact same fix.

Q: What if I'm cloning back and forth between staging and production regularly? A: Consider a tool built for that workflow, like WP Migrate DB, which supports repeatable environment-to-environment pushes and pulls.

For the general link-fixing workflow, see how to search and replace links/URLs in Elementor.

Not cloning, just changing domains? See how to update URLs in Elementor after a domain change for the general workflow.

Just cloned a site? Share which migration tool you used in the comments!