WordPress database search and replace is powerful—but dangerous if done wrong. One mistake can break your entire site.

This comprehensive safety guide teaches you how to search and replace in WordPress without fear—covering backups, testing, validation, and recovery strategies.

What you’ll learn:

• Complete safety protocols
• Backup and testing strategies
• How to avoid common mistakes
• Emergency recovery procedures
• Professional-grade workflows

Why Safety Matters

What Can Go Wrong

Serialized Data Corruption:

// Before (working):
a:2:{s:4:"name";s:4:"John";s:3:"age";i:30;}

// After wrong replace (broken):
a:2:{s:4:"name";s:5:"Susan";s:3:"age";i:30;}
         ^^^ Count is now wrong! Site breaks.

Real consequences:

• White screen of death
• Widgets disappear
• Settings reset
• Data loss
• Elementor pages break

Cost of Mistakes

Without proper backups:

• Hours/days of rebuilding
• Lost content
• Lost customer data
• Downtime costs
• Developer fees ($100-500+)

With proper protocol:

• Instant rollback (2 minutes)
• Zero data loss
• No downtime
• Peace of mind

The 3-Layer Safety System

Layer 1: Backup (Before)

Complete backup before any changes

Layer 2: Testing (During)

Validate changes before execution

Layer 3: Verification (After)

Confirm everything works

Result: 99.9% safety rate

Layer 1: Complete Backup Strategy

What to Backup

Database:

✓ All tables (not just wp_*)
✓ Structure + data
✓ SQL format preferred

Files:

✓ wp-content/ folder
✓ .htaccess file
✓ wp-config.php
✓ Root directory files

Backup Method 1: UpdraftPlus (Recommended)

Setup:

1. Install UpdraftPlus
2. Settings → UpdraftPlus Backups
3. Settings tab → Schedule:
   - Files: Manual (for this case)
   - Database: Manual
4. Remote storage: Google Drive/Dropbox

Create Backup:

1. Click "Backup Now"
2. Check:
   ☑ Include database
   ☑ Include files
   ☑ Include plugins
   ☑ Include themes
3. Click "Backup Now"
4. Wait for completion (5-15 minutes)
5. Download to computer

Why download?

• Cloud backup = relies on host
• Local copy = guaranteed restore
• Multiple copies = extra safety

Backup Method 2: cPanel

Database Backup:

1. cPanel → phpMyAdmin
2. Select database
3. Export tab
4. Quick method → SQL format
5. Download .sql file

Files Backup:

1. cPanel → File Manager
2. Select public_html/
3. Compress → Create .zip
4. Download archive

Backup Method 3: WP-CLI

Command:

# Export database
wp db export backup-$(date +%Y%m%d-%H%M%S).sql

# Create file archive
tar -czf files-backup-$(date +%Y%m%d).tar.gz wp-content/

# Download both files via FTP/SFTP

Validate Backup

Before proceeding, verify:

☐ Backup file exists
☐ File size reasonable (not 0 bytes)
☐ Downloaded to computer
☐ Can extract/open file
☐ Timestamp is current

Test restore (optional but recommended):

1. Create test database
2. Import backup
3. Check tables exist
4. Verify data present

Layer 2: Safe Testing Protocols

Testing Environment Options

Option 1: Staging Site (Best)

Pros:
✓ Exact copy of production
✓ Same server environment
✓ Safe experimentation
✓ No risk to live site

Setup:
1. Check if host provides staging
2. Or use WP Staging plugin
3. Or manually clone site

Option 2: Local Development (Good)

Tools:
- Local by Flywheel
- XAMPP
- MAMP
- Docker

Process:
1. Export live site
2. Import to local
3. Test changes
4. Apply to live

Option 3: Dry Run Mode (Minimum)

If no staging/local:
- Use dry run in Better Search Replace
- Review results carefully
- Understand exactly what changes

Dry Run Testing

Better Search Replace:

Tools → Better Search Replace

Search: old-text
Replace: new-text

Select tables:
☑ wp_posts
☑ wp_postmeta

☑ Run as dry run? ← CRITICAL

Click "Run Search/Replace"

Review results:

Table: wp_posts
Rows examined: 1,247
Changes found: 23
Cells updated: 23

Table: wp_postmeta
Rows examined: 8,932
Changes found: 156
Cells updated: 156

Total changes: 179

Questions to ask:

☐ Number of changes reasonable?
☐ Tables correct?
☐ No unexpected matches?
☐ Search term exact enough?
☐ Replace term looks correct?

Validation Checklist

Before executing:

☐ Backup completed and downloaded
☐ Dry run executed successfully
☐ Results reviewed and understood
☐ Number of changes expected
☐ Have recovery plan if issues
☐ Not during peak traffic hours
☐ Can dedicate time to test after

Safe Execution Process

Step-by-Step Protocol

Step 1: Final Preparations

☐ Backup confirmed (< 1 hour old)
☐ Dry run reviewed
☐ Maintenance mode enabled (optional)
☐ Team notified (if applicable)

Step 2: Execute Replacement

1. Tools → Better Search Replace
2. Enter search/replace terms
3. Select correct tables
4. UNCHECK "Run as dry run"
5. Take screenshot of settings
6. Click "Run Search/Replace"
7. Do not navigate away during process

Step 3: Note Results

Document:
- Exact number of changes
- Which tables affected
- Time completed
- Any error messages

Step 4: Immediate Verification

Within 5 minutes:
1. Visit homepage
2. Edit page in Elementor (if using)
3. Check database via phpMyAdmin
4. Look for any error messages

During Execution: What to Watch

Normal behavior:

✓ Progress indicator
✓ Completion message
✓ Results summary
✓ No error messages

Warning signs:

❌ Page timeout
❌ White screen
❌ PHP errors
❌ Incomplete results
❌ Database connection errors

If issues occur:

STOP IMMEDIATELY
Do not continue or refresh
Restore from backup
Investigate cause before retry

Layer 3: Post-Replacement Verification

Comprehensive Testing

Frontend Tests:

☐ Homepage loads
☐ Navigation menu works
☐ Images display
☐ Links click through
☐ Forms submit
☐ Search functions
☐ Mobile responsive
☐ No JavaScript errors

Backend Tests:

☐ Dashboard accessible
☐ Pages list loads
☐ Posts list loads
☐ Media library works
☐ Plugins active
☐ Settings intact

Elementor-Specific:

☐ Edit page with Elementor
☐ Widgets load correctly
☐ Preview mode works
☐ Changes saved successfully
☐ Navigator functions
☐ History/revisions intact

Database Integrity:

☐ phpMyAdmin accessible
☐ Tables intact
☐ Row counts unchanged
☐ No corrupted entries
☐ Character encoding correct

Browser Console Check

Check for errors:

1. Open site in Chrome
2. Press F12
3. Go to Console tab
4. Look for red errors
5. Reload page and watch

Common post-replacement errors:

❌ "Unexpected token" → JSON broken
❌ "Failed to fetch" → API issues
❌ "404 Not Found" → URL problems
❌ "SyntaxError" → Code corruption

Clear All Caches

Order matters:

1. Elementor cache:
   Elementor → Tools → Regenerate CSS & Data

2. Plugin cache:
   - WP Rocket: Clear cache
   - W3 Total Cache: Empty all caches
   - WP Super Cache: Delete cache

3. Server cache (if applicable):
   Contact host or clear via cPanel

4. CDN cache:
   Cloudflare → Caching → Purge Everything

5. Browser cache:
   Ctrl+Shift+R (hard reload)

Common Mistakes & How to Avoid

Mistake 1: No Backup

What happens:

• Irreversible damage
• Data loss
• Hours rebuilding

Prevention:

✓ ALWAYS backup before ANY database operation
✓ Download backup to computer
✓ Test backup restore process
✓ Keep backup for 30 days minimum

Mistake 2: Wrong Tables Selected

Example:

Wanted: Update Elementor content
Selected: Only wp_posts
Result: Missed wp_postmeta (Elementor data)
Outcome: Partial update, confusion

Prevention:

For Elementor: ALWAYS include wp_postmeta
For complete: Select all tables
For specific: Know which table contains data

Mistake 3: Overly Broad Search

Example:

Search: "press"
Result: WordPress → WordPold
        Express → Expold
        Impressive → Impoldive

Prevention:

✓ Be specific with search terms
✓ Include surrounding context
✓ Use case sensitivity when appropriate
✓ Test with dry run thoroughly

Mistake 4: Forgetting Serialization

Wrong tool:

Using phpMyAdmin REPLACE():
UPDATE wp_postmeta
SET meta_value = REPLACE(meta_value, 'old', 'new');

Result: Breaks serialized data

Correct tool:

Use plugins that handle serialization:
- Better Search Replace ✓
- WP Migrate DB ✓
- Search Replace DB script ✓

Mistake 5: Not Testing After

What happens:

- Run replacement
- Assume success
- Don't test
- Discover issues weeks later
- Backup expired
- Cannot recover

Prevention:

✓ Test immediately after replacement
✓ Thorough 30-minute verification
✓ Keep backup for 30+ days
✓ Document what was changed

Emergency Recovery Procedures

If Site Breaks Immediately

Scenario: White screen after replacement

Step 1: Don’t Panic

You have a backup
Recovery is straightforward
Deep breath

Step 2: Restore Database

Via UpdraftPlus:

1. Access WP Admin (if possible)
2. Settings → UpdraftPlus Backups
3. Click "Restore"
4. Select database backup
5. Click "Restore database"
6. Wait for completion

Via phpMyAdmin:

1. Access phpMyAdmin
2. Select database
3. Click "Import"
4. Choose backup .sql file
5. Click "Go"
6. Wait for import

Via WP-CLI:

wp db import backup-file.sql

Step 3: Verify Recovery

☐ Site loads
☐ Dashboard accessible
☐ Content intact
☐ Settings correct

Step 4: Investigate Cause

Before retrying:
- What went wrong?
- Was search term correct?
- Right tables selected?
- Tool used correctly?
- Test on staging next time

If Partial Corruption

Scenario: Some pages broken, some work

Diagnosis:

1. Check error logs:
   cPanel → Error Log
   Or: wp-content/debug.log

2. Identify affected posts:
   Note which pages/posts broken

3. Check database:
   Look for truncated data
   Check character encoding

Selective Restore:

Option 1: Restore specific post from revision
Option 2: Manually fix corrupted entries
Option 3: Full database restore (safest)

Professional Workflow Template

Pre-Execution Phase

Week Before (for major changes):
☐ Schedule maintenance window
☐ Notify users/team
☐ Create staging site
☐ Test replacement on staging

Day Before:
☐ Create fresh backup
☐ Download backup locally
☐ Verify backup integrity
☐ Clear schedule for testing time

1 Hour Before:
☐ Re-backup (most recent data)
☐ Enable maintenance mode
☐ Clear all caches
☐ Confirm team availability

Execution Phase

During Replacement:
☐ Document start time
☐ Screenshot settings
☐ Execute dry run
☐ Review results
☐ Execute real replacement
☐ Note completion time
☐ Save results summary

Post-Execution Phase

Immediately After:
☐ Disable maintenance mode
☐ Clear all caches
☐ Test critical pages (10 min)
☐ Check error logs
☐ Verify database intact

Within 1 Hour:
☐ Comprehensive frontend test
☐ Backend functionality test
☐ User acceptance test
☐ Monitor error logs
☐ Check analytics for issues

Within 24 Hours:
☐ Review all error logs
☐ Check user reports
☐ Monitor performance
☐ Verify search rankings
☐ Document any issues

Within 1 Week:
☐ Final verification
☐ Keep backup for 30 more days
☐ Document lessons learned
☐ Update procedures if needed

Safety Tools & Resources

Recommended Plugins

For Backups:

1. UpdraftPlus (free/premium)
   - Scheduled backups
   - Cloud storage
   - Easy restore

2. BackupBuddy (premium)
   - Complete site backup
   - Migration tools

3. Duplicator (free/pro)
   - Full site clones
   - Migration package

For Safe Search/Replace:

1. Better Search Replace (free)
   - Dry run mode
   - Serialization safe
   - Table selection

2. WP Migrate DB (free/pro)
   - Multi-site support
   - Advanced options

3. Search Regex (free)
   - Pattern matching
   - Precise control

For Testing:

1. WP Staging (free/pro)
   - One-click staging
   - Safe testing
   - Push to live

2. Local by Flywheel (free)
   - Local development
   - One-click WordPress

3. Query Monitor (free)
   - Debug tool
   - Database queries
   - Error tracking

Safety Checklist Summary

Essential Pre-Flight Checks

Before ANY search/replace:
☑ Complete backup created
☑ Backup downloaded locally
☑ Backup verified working
☑ Tested on staging (if available)
☑ Dry run completed
☑ Results reviewed
☑ Recovery plan ready
☑ Time allocated for testing
☑ Team notified (if applicable)
☑ Low-traffic time chosen

Post-Execution Validation

After replacement:
☑ Site loads normally
☑ Dashboard accessible
☑ Elementor editor works
☑ No console errors
☑ All caches cleared
☑ Critical pages tested
☑ Forms working
☑ No PHP errors in logs
☑ Backup retained for 30 days
☑ Changes documented

Conclusion

WordPress database search and replace is safe when you follow proper protocols. The three-layer safety system—backup, testing, verification—prevents 99% of issues.

Golden Rules:

1. ✅ ALWAYS create complete backup first
2. ✅ Download backup to your computer
3. ✅ Test on staging before production
4. ✅ Use dry run mode
5. ✅ Review results before executing
6. ✅ Clear all caches after changes
7. ✅ Test thoroughly post-replacement
8. ✅ Keep backup for 30+ days

Remember: 5 minutes of backup = hours saved in recovery

Recommended Safety Stack:

• Backup: UpdraftPlus
• Search/Replace: Better Search Replace
• Testing: WP Staging
• Monitoring: Query Monitor

With these protocols, you can confidently make database changes knowing you can always roll back if needed.

Frequently Asked Questions

Q: How long should I keep backups? A: Minimum 30 days. For major changes, keep backup until next major change.

Q: Is dry run 100% accurate? A: 99% accurate. It shows exactly what will change but can’t predict every edge case.

Q: Can I make multiple replacements at once? A: Better to do them one at a time, test each, then proceed to next.

Q: What if my backup is too old? A: Create a new backup before replacement. Never use backups older than 24 hours for major changes.

Q: Should I enable maintenance mode? A: For large replacements (thousands of changes), yes. For small changes, optional.

Q: How do I know if serialization broke? A: Widgets disappear, settings reset, white screen errors. Use proper tools to prevent this.

Stay safe! Have you ever had a search/replace go wrong? Share your story in the comments!

The post How to Safely Search & Replace in WordPress appeared first on Elementor Search & Replace.

Moving your Elementor site to a new domain? URLs don’t update automatically, which means broken links, missing images, and non-functional buttons across your entire site.

This comprehensive guide shows you exactly how to update all URLs in Elementor after a domain change—from simple plugin methods to manual database updates.

What you’ll fix:

• Internal page links
• Image URLs
• Button links
• Menu links
• CSS background images
• Popup trigger URLs
• And everything in between

Estimated time: 15-30 minutes depending on site size

Why URLs Break After Domain Migration

When you change domains (e.g., oldsite.com → newsite.com), WordPress and Elementor store old URLs in multiple places:

Where Old URLs Hide:

1. WordPress Settings
   • Site URL
   • Home URL
2. Database Content
   • Post/page content (wp_posts)
   • Post metadata (wp_postmeta) ← Elementor data lives here
   • Options table (wp_options)
   • Widget data
3. Elementor-Specific Areas
   • Widget settings (buttons, images)
   • Custom CSS with background images
   • Template library
   • Popup settings
   • Navigation menus

The Problem: Elementor stores data as serialized PHP arrays. Simple find/replace can break this data structure, corrupting your pages.

Pre-Migration Checklist

Before changing URLs, complete these critical steps:

1. Create Complete Backup

Using UpdraftPlus (Recommended):

1. Install UpdraftPlus plugin
2. Go to Settings → UpdraftPlus Backups
3. Click “Backup Now”
4. Check “Include database” and “Include files”
5. Download backup to your computer

Alternative Methods:

• Host backup (cPanel, Plesk)
• BackupBuddy
• Duplicator

2. Document Current Setup

Create a text file with:

Old Domain: https://oldsite.com
New Domain: https://newsite.com
Old URL patterns:
- http://oldsite.com
- https://oldsite.com
- //oldsite.com (protocol-relative)
- www.oldsite.com (if used)

3. Check for Hardcoded URLs

Places to check manually:

• Theme functions.php – Any hardcoded domains
• Custom CSS – Background image URLs
• Custom JavaScript – API endpoints or AJAX URLs
• .htaccess – Rewrite rules with old domain

Method 1: Using Better Search Replace Plugin (Recommended)

Best for: Most users, safest method, handles Elementor serialized data correctly.

Step-by-Step Process

Step 1: Install Better Search Replace

1. Go to Plugins → Add New
2. Search “Better Search Replace”
3. Install and activate
4. Navigate to Tools → Better Search Replace

Step 2: Update WordPress Core URLs

First, update general WordPress settings:

1. Go to Settings → General
2. Update:
   • WordPress Address (URL): https://newdomain.com
   • Site Address (URL): https://newdomain.com
3. Save changes

Step 3: Run URL Replacement

In Better Search Replace:

Search for: http://oldsite.com Replace with: https://newsite.com

Select Tables:

☑ wp_posts
☑ wp_postmeta (CRITICAL for Elementor)
☑ wp_options
☑ wp_comments
☑ wp_commentmeta
☑ wp_term_taxonomy
☑ wp_termmeta
☑ wp_usermeta

⚠️ IMPORTANT: Check “Run as dry run?” first!

Step 4: Review Dry Run Results

1. Click “Run Search/Replace”
2. Check results:wp_posts: 47 changes wp_postmeta: 312 changes (Elementor data) wp_options: 23 changes Total: 382 changes
3. If numbers look reasonable, proceed

Step 5: Execute Real Replacement

1. Uncheck “Run as dry run?”
2. Click “Run Search/Replace” again
3. Note the actual changes made

Step 6: Repeat for URL Variations

Run additional replacements for:

Replace #2: HTTPS to HTTPS (if old site was HTTP)

Search: http://oldsite.com
Replace: https://newsite.com

Replace #3: Protocol-relative URLs

Search: //oldsite.com
Replace: //newsite.com

Replace #4: WWW variation (if applicable)

Search: www.oldsite.com
Replace: www.newsite.com

Replace #5: URL-encoded versions

Search: http:\/\/oldsite.com
Replace: https:\/\/newsite.com

Method 2: Using WP Migrate DB Plugin

Best for: Migrations, handles serialized data perfectly, more powerful than Better Search Replace.

Installation and Setup

Step 1: Install WP Migrate DB

1. Go to Plugins → Add New
2. Search “WP Migrate DB”
3. Install and activate
4. Go to Tools → Migrate DB

Step 2: Configure Find & Replace

In the “Find & Replace” tab:

Find: https://oldsite.com Replace: https://newsite.com

Click “+ Add Row” for additional patterns:

• http://oldsite.com → https://newsite.com
• //oldsite.com → //newsite.com

Step 3: Select Tables

Choose “Migrate only selected data” or “All tables”

For Elementor, ensure these are selected:

• wp_posts
• wp_postmeta
• wp_options

Step 4: Choose Action

Select “Find & Replace” (not export)

Step 5: Execute

1. Click “Find & Replace”
2. Review report showing changes
3. Click “Close”

Method 3: WP-CLI (Command Line – Advanced)

Best for: Developers, very large sites, automated deployments.

Prerequisites

• SSH access to server
• WP-CLI installed
• Basic command line knowledge

Basic URL Replacement

Step 1: Connect via SSH

ssh username@yourserver.com
cd /path/to/wordpress

Step 2: Create Backup

wp db export backup-before-urls.sql

Step 3: Test with Dry Run

wp search-replace 'https://oldsite.com' 'https://newsite.com' --dry-run

Review output:

Success: 437 replacements to be made.

Step 4: Execute Replacement

wp search-replace 'https://oldsite.com' 'https://newsite.com' --skip-columns=guid

Step 5: Additional Variations

# HTTP version
wp search-replace 'http://oldsite.com' 'https://newsite.com' --skip-columns=guid

# Protocol-relative
wp search-replace '//oldsite.com' '//newsite.com' --skip-columns=guid

Advanced WP-CLI Options

Target specific tables:

wp search-replace 'oldsite.com' 'newsite.com' wp_postmeta wp_posts --skip-columns=guid

Export database after changes:

wp db export backup-after-urls.sql

Check for remaining old URLs:

wp db search 'oldsite.com' --all-tables

Method 4: Manual Database Update (Last Resort)

⚠️ WARNING: Only use if other methods fail. High risk of breaking serialized data.

Using phpMyAdmin

Step 1: Access phpMyAdmin

1. Login to cPanel or host control panel
2. Navigate to phpMyAdmin
3. Select your WordPress database

Step 2: Export Backup

1. Click “Export” tab
2. Select “Quick” export method
3. Format: SQL
4. Click “Go”
5. Save file to computer

Step 3: Run SQL Query

Go to “SQL” tab and run:

-- Update post content
UPDATE wp_posts
SET post_content = REPLACE(post_content, 'https://oldsite.com', 'https://newsite.com');

-- Update post metadata (Elementor data)
UPDATE wp_postmeta
SET meta_value = REPLACE(meta_value, 'https://oldsite.com', 'https://newsite.com');

-- Update options
UPDATE wp_options
SET option_value = REPLACE(option_value, 'https://oldsite.com', 'https://newsite.com')
WHERE option_name NOT IN ('siteurl', 'home');

-- Update GUIDs (optional, debatable)
UPDATE wp_posts
SET guid = REPLACE(guid, 'https://oldsite.com', 'https://newsite.com');

Step 4: Verify Changes

Run search query:

SELECT * FROM wp_posts WHERE post_content LIKE '%oldsite.com%' LIMIT 10;

Post-Migration Cleanup

After URL replacement, complete these essential steps:

1. Regenerate Elementor CSS

Why: Elementor caches CSS files with old URLs

How:

1. Go to Elementor → Tools
2. Click “Regenerate CSS & Data”
3. Wait for confirmation

2. Clear All Caches

Plugin Cache:

• WP Rocket: Settings → Clear cache
• W3 Total Cache: Performance → Dashboard → Empty all caches
• WP Super Cache: Settings → Delete cache

Server Cache:

• Check with hosting provider
• cPanel: Clear OPcache, Memcached, Redis

CDN Cache:

• Cloudflare: Purge everything
• StackPath: Clear cache
• Other: Check CDN documentation

3. Regenerate Thumbnails

Why: Image URLs may still reference old domain

How:

1. Install “Regenerate Thumbnails” plugin
2. Go to Tools → Regenerate Thumbnails
3. Click “Regenerate All Thumbnails”

4. Update Permalink Structure

1. Go to Settings → Permalinks
2. Don’t change anything
3. Just click “Save Changes” (flushes rewrite rules)

5. Test Navigation Menus

1. Go to Appearance → Menus
2. Check all menu items point to new domain
3. Update any hardcoded URLs

6. Check Elementor Templates

1. Go to Elementor → Templates
2. Edit each template
3. Check links and images
4. Update template

Verification Checklist

After migration, verify everything works:

Frontend Checks

☐ Homepage loads correctly
☐ All images display properly
☐ Internal links work (click 5-10 random links)
☐ Buttons navigate to correct pages
☐ Forms submit successfully
☐ Videos play (if embedded)
☐ Sliders/carousels function
☐ Mobile menu works
☐ Footer links correct
☐ Search functionality works

Elementor-Specific Checks

☐ Edit a page with Elementor (no errors)
☐ Check background images in sections
☐ Verify button links in widgets
☐ Test popups (if using Elementor Pro)
☐ Check mega menu links (if using Elementor Pro)
☐ Verify WooCommerce products (if applicable)
☐ Test contact forms
☐ Check social media links

Technical Checks

☐ No console errors (F12 → Console)
☐ No mixed content warnings (HTTP/HTTPS)
☐ SSL certificate installed and working
☐ Redirects working (old domain → new domain)
☐ Sitemap generated with new URLs
☐ Google Search Console verified for new domain

Troubleshooting Common Issues

Issue 1: Some Images Still Show Old URL

Symptoms: Random images broken, some pages fine

Causes:

1. Images in custom CSS
2. Background images in Elementor sections
3. CDN still serving old URLs

Solutions:

For Custom CSS:

1. Go to Appearance → Customize → Additional CSS
2. Find/replace old domain
3. Save

For Elementor Backgrounds:

1. Edit page with Elementor
2. Click section with background image
3. Re-upload or select image from media library
4. Update

For CDN:

1. Purge CDN cache completely
2. Wait 10-15 minutes for propagation
3. Test again

Issue 2: Elementor Editor Won’t Load

Symptoms: “Loading” spinner never stops, white screen

Causes:

1. Corrupted serialized data
2. Wrong site URL in settings
3. Cache not cleared

Solutions:

Check WordPress URLs:

SELECT option_value FROM wp_options WHERE option_name IN ('siteurl', 'home');

Should show new domain.

Fix if wrong:

UPDATE wp_options SET option_value = 'https://newdomain.com' WHERE option_name = 'siteurl';
UPDATE wp_options SET option_value = 'https://newdomain.com' WHERE option_name = 'home';

Clear Elementor Cache:

1. Deactivate Elementor
2. Activate Elementor
3. Go to Tools → Regenerate CSS

Issue 3: Links Work But Point to Old Domain

Symptoms: Clicking links redirects to old site

Cause: Didn’t update all URL variations

Solution:

Run additional replacements:

http://oldsite.com → https://newsite.com
https://www.oldsite.com → https://newsite.com
www.oldsite.com → newsite.com
oldsite.com (no protocol) → newsite.com

Issue 4: Mixed Content Warnings

Symptoms: Padlock icon missing, “Not secure” warning

Cause: Some resources loaded via HTTP instead of HTTPS

Solutions:

Find mixed content:

1. Open site in Chrome
2. Press F12 → Console
3. Look for “Mixed Content” warnings
4. Note the URLs

Fix with plugin: Install “Really Simple SSL” plugin (fixes most cases automatically)

Or run manual replace:

http://newsite.com → https://newsite.com

Advanced Scenarios

Scenario 1: Subdomain to Main Domain

Example: blog.oldsite.com → newsite.com

Replacements needed:

https://blog.oldsite.com → https://newsite.com
http://blog.oldsite.com → https://newsite.com
//blog.oldsite.com → //newsite.com

Scenario 2: Subfolder to Root

Example: oldsite.com/blog → newsite.com

Replacements needed:

https://oldsite.com/blog → https://newsite.com
https://oldsite.com/blog/ → https://newsite.com/
oldsite.com/blog → newsite.com

Additional step: Update .htaccess for redirects

Scenario 3: HTTP to HTTPS (Same Domain)

Example: http://mysite.com → https://mysite.com

Steps:

1. Install SSL certificate first
2. Run URL replacement: http://mysite.com → https://mysite.com
3. Add redirect in .htaccess:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Setting Up 301 Redirects

After migration, redirect old domain to new domain:

Method 1: .htaccess (Apache Servers)

Add to top of old site’s .htaccess:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_HOST} ^oldsite\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.oldsite\.com$
RewriteRule ^(.*)$ https://newsite.com/$1 [R=301,L]
</IfModule>

Method 2: Redirection Plugin

1. Install “Redirection” plugin on OLD site
2. Go to Tools → Redirection
3. Add redirect:
   • Source URL: .* (regex: all URLs)
   • Target URL: https://newsite.com/$1
   • Type: 301 Permanent

Method 3: Cloudflare Page Rules

1. Login to Cloudflare
2. Go to Rules → Page Rules
3. Add rule:
   • URL: oldsite.com/*
   • Setting: Forwarding URL (301)
   • Destination: https://newsite.com/$1

SEO Considerations

Update Google Search Console

1. Add new domain property in GSC
2. Submit new sitemap
3. Keep old property active for 6 months to monitor redirects

Update Google Analytics

1. Go to Admin → Property Settings
2. Update “Default URL” to new domain
3. Update tracking code if changed

Update Social Media Links

• Facebook page URL
• Twitter profile link
• LinkedIn company page
• Instagram bio link
• Pinterest verification

Inform Google of Domain Change

1. Verify both old and new domains in Search Console
2. Use the “Change of Address” tool
3. Google Help → Change of Address tool

Maintenance After Migration

Week 1: Daily Checks

• Monitor error logs
• Check Analytics for 404s
• Test critical pages daily
• Monitor uptime

Month 1: Weekly Checks

• Review Search Console for crawl errors
• Check backlink status
• Monitor rankings
• Verify redirects working

Month 3: Final Audit

• Remove 301 redirects from old domain (optional)
• Archive old site backups
• Update all third-party services
• Document migration for future reference

Conclusion

Updating URLs in Elementor after a domain change is straightforward when using the right tools. Better Search Replace and WP Migrate DB handle the complex serialized data safely, preventing corruption.

Key Takeaways:

1. ✅ Always backup before starting
2. ✅ Use Better Search Replace or WP Migrate DB
3. ✅ Test with dry run first
4. ✅ Update all URL variations (HTTP, HTTPS, www, protocol-relative)
5. ✅ Clear Elementor cache and all other caches
6. ✅ Set up 301 redirects from old to new domain
7. ✅ Update Search Console and Analytics

Recommended Plugin: Better Search Replace (free) handles 95% of cases perfectly.

Frequently Asked Questions

Q: Do I need to update URLs if I’m just moving to HTTPS on the same domain? A: Yes! Update http://yoursite.com to https://yoursite.com using the same process.

Q: Will URL changes affect my Elementor Pro license? A: No, your license is tied to your account, not the domain. Just reactivate with your license key.

Q: Can I use multiple find/replace plugins at once? A: No—choose one method and stick with it to avoid conflicts.

Q: What if I already changed URLs but pages are broken? A: Restore your backup and follow this guide step-by-step with dry run mode enabled.

Q: Should I update the GUID column in wp_posts? A: Debatable. WordPress documentation says don’t change GUIDs, but for domain changes, updating them is usually fine.

Q: How do I test if all URLs were updated? A: Use WP-CLI: wp db search 'oldsite.com' --all-tables to find any remaining references.

**Need help?** Drop your migration questions in the comments!

The post How to Update URLs in Elementor After Domain Change appeared first on Elementor Search & Replace.