Fixed a Broken Link in Elementor and It Came Back? Why

Elementor page where a broken link fix is undone after the page is saved again

You find a broken link, you fix it, the link checker turns green. A week later the old link is back on the page, as if nothing happened. If the page was built with Elementor, the fix probably never reached the page at all.

Last updated 18 November 2026. Tested on WordPress 7.0.2 with Elementor 4.4.1 (free, from WordPress.org), with wp-cli and curl on a local test site.

You’re not imagining it

This one keeps coming back in the Broken Link Checker support forum. In early November 2026 a user wrote: “All Links in Elementor are only fixed after opening a subpage and saving it again.” They added: “This makes the plugin useless on Elementor websites.”

The answer from plugin support was honest: “This situation remains the same. Elementor and other page builders are more complex to override the links.” They pointed the user to Elementor’s own search and replace instead.

And it isn’t new. An older thread from about seven years ago says much the same: “I have some issues with links in content made with page builders like elementor.” Support back then could reproduce it too.

So what’s going on?

A normal WordPress post keeps its text in one place, the post_content field of the wp_posts table. Elementor pages are different. Elementor stores the real page, every section and widget with its settings, as JSON (a structured text format) in a custom field called _elementor_data in the wp_postmeta table. It also writes a plain HTML copy into post_content, mostly so search, feeds and other plugins have something to read.

When a visitor opens the page, Elementor builds it from _elementor_data. Not from post_content.

So a tool that fixes links by editing post_content only changes the copy. Visitors keep seeing the old link. Then, the next time anyone saves the page in Elementor, Elementor rewrites post_content from its own data, and the “fixed” copy flips back to the old link. That’s the “it came back” moment.

We didn’t test Broken Link Checker itself, so we won’t claim exactly how it writes its fix. What we did test is the mechanism.

What we ran (and what visitors saw)

On a local WordPress 7.0.2 site we installed Elementor 4.4.1 and built a page through Elementor’s own save routine, with one Text Editor widget containing a link to a page that doesn’t exist (/old-pricing-page/, which returned a 404). Then:

  1. Fake “fix” in post_content. We changed the link in post_content to a real page (/pricing-el-test/) with a normal wp_update_post() call, the way a generic link tool would. post_content now showed the new link. _elementor_data still held the old one. We fetched the live page with curl: visitors got /old-pricing-page/, the broken link.
  2. Save in Elementor. We saved the page through Elementor’s document API, sending back the same data the editor loads, which is what clicking Update does. post_content went back to /old-pricing-page/. The fix was gone from both places.
  3. Plain search-replace on the meta table. A wp search-replace dry run for the normal URL on wp_postmeta found 0 matches. The same search with escaped slashes (more on that below) found 6: the page plus five saved revisions.
  4. Edit the data, forget the cache. We then changed the link inside _elementor_data directly in the database. The live page kept showing the previous link. Elementor’s Element Cache was still serving its pre-rendered copy. After wp elementor flush-css the live page showed the new link.
  5. Elementor’s Replace URL. wp elementor replace-urls changed the link that visitors see in one step (“1 database row affected”). But post_content still held the old link until the page was saved in Elementor again.

That last one matters if your link checker reads post_content: it may keep reporting a link that visitors no longer see, until the next Elementor save. Annoying, but at least it’s the harmless direction.

Afterwards we deleted the test pages and removed Elementor.

The escaped-slashes trap

Here’s why a normal search-replace misses Elementor links. Inside _elementor_data, the JSON escapes every forward slash. Our link was stored like this:

href=\"http:\/\/127.0.0.1:8090\/old-pricing-page\/\"

Search for https://example.com/old-page/ and you won’t match https:\/\/example.com\/old-page\/. The tool reports zero results, and it’s easy to read that as “the link isn’t there”. It is. It’s just wearing backslashes.

This is the boring answer and usually the right one.

  1. Open the page with Edit with Elementor.
  2. Find the widget that holds the link. Links hide in Text Editor widgets, buttons, icon boxes, image links and headings. The Navigator panel lists every element on the page, which helps on long pages.
  3. Change the link and click Update.

Elementor writes both _elementor_data and post_content on save, so the two copies agree again. Then check the live page in a private window, in case a page cache is still serving the old version.

If the same broken link sits in a header, footer or other template, edit the template, not each page.

2. A whole domain or protocol change: Elementor’s Replace URL

Elementor ships a tool for this under its Tools screen, on the Replace URL tab (also available as wp elementor replace-urls <old> <new>). Elementor describes it as being for “domain transfers or move to ‘HTTPS'”, and it asks you to back up the database first.

In the Elementor 4.4.1 code we read, it does a plain text replace of the slash-escaped form of your old URL, in _elementor_data only, then clears Elementor’s generated files and cache. A few things follow from that:

  • Both fields must be full, valid URLs. A relative link like /old-page/ isn’t accepted.
  • It will take a single page URL (it worked on our test page), but it’s a raw text replace across the whole site. https://example.com/old-page/ also matches the start of https://example.com/old-page/part-2/. Fine for a domain move, risky for one page.
  • It doesn’t touch post_content, so other tools may see the old link until each page is saved again.

3. Many pages, one dead URL: search-replace with escaped slashes

If you’re comfortable with wp-cli, you can do it yourself. Back up first, always:

wp db export before-link-fix.sql

Dry run on the meta table, with the slashes escaped. Single quotes keep the shell from eating the backslashes:

wp search-replace 'https:\/\/example.com\/old-page\/' 'https:\/\/example.com\/new-page\/' wp_postmeta --dry-run

If the count looks right, run it again without --dry-run. Your table prefix may not be wp_; wp db prefix tells you. Expect revisions in the count too. On our test page, 6 rows matched for one page because every Elementor revision keeps its own copy.

Then fix the plain copy as well, so link checkers agree:

wp search-replace 'https://example.com/old-page/' 'https://example.com/new-page/' wp_posts --include-columns=post_content --dry-run

Same prefix-match warning as above: make the old URL as specific as you can, ideally with the trailing slash.

If you use a plugin like Better Search Replace instead, the same rules apply: pick the postmeta table, search the escaped form, and dry-run first.

4. Clear Elementor’s cache afterwards

Skip this and you’ll think the fix failed. Elementor’s Element Cache (Elementor > Settings > Performance) stores pre-rendered copies of elements, and its default is 1 day. In our test, a database edit stayed invisible to visitors until we cleared it.

  • In wp-admin: Elementor’s Tools screen, Clear Files & Data.
  • In wp-cli: wp elementor flush-css (despite the name, it also clears the element cache; add --regenerate to rebuild the CSS right away).

Then purge any page cache or CDN you run on top.

For finding the broken links in the first place, our guide to finding and fixing broken links covers the general process, and this one on Broken Link Checker false positives helps sort real breaks from noise.

A tool that reads what visitors read

  • Free: a daily broken internal-link scan flags internal links that 404, checked from your own server. Linkweave reads Elementor pages from Elementor’s own data, so its suggestions, orphan list and link counts match what visitors actually see, not the plain copy.
  • Pro: one-click broken-link repair. Unlink or repoint dead internal links, one at a time or all at once. The Pro URL changer, broken-link repair and Competing pages change the link inside Elementor itself (undo included), instead of a copy visitors never see.

To be clear about the split: the Free version finds the broken links; repairing them from Linkweave is Pro. The Free plugin is a free download from our site. If you’re building out links on Elementor pages anyway, see how to add internal links in Elementor.

Frequently asked questions

Elementor builds the page from its own data in the _elementor_data field, not from the regular post content. A fix made only in the post content changes a copy visitors never see, and the next Elementor save rewrites that copy from Elementor’s data, so the old link returns.

Why does search and replace find nothing in my Elementor pages?

Elementor stores links in JSON with escaped slashes, like https:\/\/example.com\/page\/. A search for the normal URL misses them. Search the postmeta table for the escaped form, run a dry run first, and back up the database before the real run.

Elementor’s Element Cache serves pre-rendered copies of elements, for 1 day by default. Clear it with Clear Files and Data on Elementor’s Tools screen, or run wp elementor flush-css, then purge any page cache or CDN you use.