Troubleshooting

Non-Elementor pages, blocked pages, missing fonts, CSS conflicts and failed pages.

“…was not built with Elementor”

Only pages rendered by Elementor can be rebuilt. Each page is checked before it is converted. Keep Show Elementor pages only on when you choose pages. Some caching or optimisation plugins change the markup Elementor outputs. If you’re sure the page uses Elementor, contact support with the URL.

The page is behind a login, a paywall or a firewall

Our service loads the page as a logged-out visitor. Pages that need a login, a password or a subscription can’t be imported, and the Terms don’t allow getting around that.

Some sites block automated requests with a firewall or bot protection, such as Cloudflare. The import then reports that the site “blocks automated requests”, and the credit comes back. Try again later, or ask the site owner to allow requests from SiteScrapper (for example in Wordfence or Cloudflare).

A page the site’s robots.txt keeps automated tools away from can’t be imported either: the import says so, and the credit comes back. Only the site owner can change that.

Fonts are missing or look wrong

• Check Elementor’s font settings on your site, for example whether Google Fonts are turned off.
• Fonts the reference site uploaded itself aren’t included. Upload the font (if you have a licence for it) and set it in Elementor.
• Caching or optimisation plugins on your site can delay or block font files. Clear their caches.

Styles clash with your theme or plugins

• Try the Elementor Canvas or Elementor Full Width page template, so your theme’s page styles get in the way less.
• Your theme’s or plugins’ CSS can override the carried CSS. Look for global rules on headings, buttons or containers.
• Your site’s Elementor global colours and fonts can differ from the reference. Adjust them in Elementor’s Site Settings.
• Anything you set in Elementor wins over the carried CSS, so you can fix a single element directly.
• Clear any caching plugin, and regenerate Elementor’s CSS under Elementor → Tools → Regenerate CSS & Data.

A page failed

If the conversion failed on our side, its credit is released automatically. You don’t need to ask.

1. Open the plugin’s History screen. For an unfinished import, choose Resume.
2. Or start a new import of that page from Import pages.

If a page downloaded but couldn’t be saved in WordPress (for example “Elementor did not save the page”), check that your user can edit pages with Elementor, then try again. That credit isn’t returned automatically: open a ticket and we’ll check it.

“This import needs … credit(s)”

You don’t have enough credits for the pages you chose. Choose fewer pages, or buy credits under Credits in the dashboard.

The page is too large

A page and its styles can be up to 15 MB in total. The plugin tells you when a page is over the limit.

Getting help

Turn on Debug log on the plugin’s Settings screen and repeat the problem. The log keeps requests and errors, without passwords, tokens or page contents. Then open a support ticket with the reference URL and what you saw.

Still stuck? Open a support ticket and tell us the reference URL and what you saw.