Skip to main content

Site moves and new domains

Testimonial Widget After a Domain Change

A domain move changes more than the address. Sites get exported and imported, hosts change, themes are reinstalled, HTTPS gets switched on and security headers appear. Any of those can leave the testimonial widget blank on the new domain while it worked yesterday on the old one. Work through what changed, in the order it usually breaks.

  • Confirm the embed survived the move
  • Check new host headers and HTTPS
  • Fix links that still point at the old domain
Use the free toolStart free (opens in a new tab)
Domain move widget check
2 of 14 done14%
  • List every page that showed a widget on the old domain.
  • On the new domain, view source and search for data-storyproof-widget on each page.
  • Search the same source for embed.js and confirm it appears once.
  • Compare each widget id with the ids in your StoryProof account.
  • Open the browser console and look for Content Security Policy or mixed content errors naming app.storyproof.io.
Free tool, no sign-upTry it below

The problem, solved

What a domain move breaks

Situation 1 of 5

The widget area vanished after the move

Migration plugins, exports and theme reinstalls often leave behind blocks, widget areas or theme settings where the embed lived.

How StoryProof solves it

Copy a fresh snippet from StoryProof and paste it where the widget belongs on the new site: a div with the widget id and the async script.

Checklist

Get the widget back on the new domain

Work top to bottom. Each group rules out one layer before you move to the next.

1. Did the code arrive?
2. Did the script run?
3. Is the new site serving fresh pages?
4. Links and account

Ticks stay in your browser. Nothing is sent anywhere.

Symptom on the new domain

What you seeMost likely layerWhere to look
No gap where the widget wasCode did not arrivePage source for the div
A gap but no testimonialsScript missing or blockedSource for embed.js, then the console
Console names a policy directiveNew Content Security PolicyHost, security plugin or server config
Console mentions mixed contentHTTP script on an HTTPS pageThe script src
Fine in private window, old view for youSite cache or CDNCache plugin and CDN purge

In StoryProof

Recover in four passes

  1. 1

    Re-paste fresh code

    Copy each widget’s snippet from StoryProof and paste the div where it belongs on the new site.

  2. 2

    Load the script once, site wide

    Add embed.js to the footer or header code of the new site rather than per page.

  3. 3

    Clear headers and HTTPS issues

    Fix anything the console reports: add app.storyproof.io to script-src, and correct any http script address.

  4. 4

    Purge caches and confirm the selection

    Clear the site cache and CDN, then check each widget still shows the approved testimonials you picked for it.

What happens next: Keep the list of widget pages with your site documentation. The next move or rebuild starts from it.

Before you start

What this page does not assume

  • No domain rules claimed

    This page makes no claim that StoryProof limits widgets to particular domains, or that it does not. If everything on your site checks out, ask support rather than guessing.

  • No claim about caching

    Nothing here describes how StoryProof caches its script or testimonials. The cache steps refer only to your own site and CDN.

  • Search rankings are separate

    Redirects, Search Console and ranking recovery after a move are outside this page.

  • Host settings vary

    Where a host sets security headers differs by provider and plugin. Ask your host if you cannot find it.

FAQ

Questions people ask

Short answers to what usually comes up next.

Do I need a new widget after changing domains?

Start with the same widget and its existing snippet. Work through the checklist; only contact support if the code, headers and caches all check out.

Why does the widget work on the old domain but not the new one?

The two sites are usually not identical: a different host, a different theme setting for the script, new security headers or HTTPS. The checklist compares those one by one.

Will my collection links break when my domain changes?

Links you made yourself to pages on your old domain need redirects. For StoryProof links, open each one from your account and compare it with what your new site shows.

What should I send support?

The page address on the new domain, the widget id, a copy of any console errors and a note of what changed in the move.

Still have a question? Ask the StoryProof team or book a demo.

Bring your proof to the new address

Re-paste two lines, clear the headers and caches, and your testimonials are back.

Start free (opens in a new tab)

Sources

  1. Mixed content, MDN Web Docs. Checked 2026-11-14.
  2. CSP: script-src, MDN Web Docs. Checked 2026-11-14.

Last updated 2026-11-14.