If your MapifyPro map is not displaying on your website, there are two common causes. Follow the steps below in order.
Step 1 — Verify Your Licence
An unverified or expired licence will prevent maps from displaying entirely.
How to fix:
- Log in to your WordPress admin dashboard
- Navigate to MapifyPro → Activation in the left-hand menu
- Check the licence status
- If it shows as unverified, expired, or invalid — re-enter your licence key and click the button to save.
- Refresh your website and check if the map now displays
If the map is still not displaying after verifying your licence, continue to Step 2.
Step 2 — Allow Web Workers in Your Browser Security Policy (CSP)
MapifyPro uses Web Workers to render maps efficiently. Some web servers and security plugins block Web Workers by default using a Content Security Policy (CSP), which causes the map to appear blank or fail to load silently.
How to check if this is the issue
- Open your site in a browser
- Right-click anywhere on the page and select Inspect (or press
F12) - Click the Console tab
- Look for errors similar to:
Creating a worker from 'blob:https://yoursite.com/...' violates the
following Content Security Policy directive: "default-src https: ..."
Note that 'worker-src' was not explicitly set.
If you see this error, follow the fix for your hosting setup below.
Fix A — WordPress Plugin (Recommended for most users)
Install the Headers & CSP Manager plugin or use the Headers section in any security plugin you already have (e.g. Wordfence, iThemes Security, Really Simple SSL).
Add the following CSP header:
Content-Security-Policy: worker-src 'self' blob:;
Fix B — Apache (.htaccess)
Add the following to your .htaccess file in your WordPress root directory:
<IfModule mod_headers.c>
Header always set Content-Security-Policy "worker-src 'self' blob:;"
</IfModule>
⚠️ If you already have a
Content-Security-Policyline in your.htaccess, addworker-src 'self' blob:;to the existing line rather than adding a second one.
Fix C — Nginx
Add the following inside your server {} block in your Nginx config:
add_header Content-Security-Policy "worker-src 'self' blob:;";
Then reload Nginx:
sudo systemctl reload nginx
Fix D — Managed / Shared Hosting (cPanel, Plesk, WP Engine, Kinsta, etc.)
If you do not have access to your server config, contact your hosting provider and ask them to add the following HTTP response header:
Content-Security-Policy: worker-src 'self' blob:;
Let them know it is required for JavaScript Web Workers to function on your site.
Still having issues?
If your map is still not displaying after completing both steps above, please contact our support team and include:
- Your domain name
- A screenshot of any errors shown in your browser console (F12 → Console tab)
- Your WordPress version and active theme name
We're happy to help! 🗺️
Comments
0 comments
Please sign in to leave a comment.