The Content Area Was Not Found in Your Page

This article explains what to do if you get the message:

"Sorry, the content area was not found in your page. You must call the_content function in the current template, in order for Elementor to work on this page."

What is the_content, and why does Elementor require it?

The the_content function is a WordPress function that gets the content from the database and prints it on the screen. Given that Elementor's content replaces the content of the page, if this function is not called for, then Elementor cannot work. Read more on the_content function on

The coding common reasons for the_content function not to be called

There are 3 common occurrences that may be the cause why the_content will not be called:
  1. Sometimes the theme has a front page template (homepage) that is already pre-built and does not include content from the page. When you select the "latest posts" as your homepage, you will also receive the the_contenterror. To edit this template, you have to edit the archive template via the Theme Builder of Elementor.
  2. Custom made page templates that do not include the_content
  3. WooCommerce product pages and WooCommerce shop pages that do not include the_content. Please note that the WooCommerce product page template can be edited via the WooCommerce builder of Elementor. If you edit it there and not into WooCommerce, you won't receive the the_contenterror and you will be able to assign the template to your WooCommerce product pages. 

Manual solution for the developers

Note: Switching to a different theme usually solves this issue. Try switching to a theme like Twenty Seventeen or GeneratePress and see if your problem is solved.

If you are developing a theme, add the_content function into the page template's code.

This is the line you need to add: <?php the_content(); ?>

If you are not familiar with where to place this code or how to add it to the page, please contact your website developer so it can be implemented properly as we cannot provide full support for that. Please note that adding this code won't enable the editing of Archive pages and Latest Post pages (these pages have to be edited via the  theme builder of Elementor) and it is really simple.

Important! You do not have to add this code if you are not the developer of a theme. The majority of the themes include this function in the regular pages and posts.

If switching to a different theme does not help or if you are not developing a theme, please read the following to troubleshoot.

Other occurrences of this error message

This is relevant if you keep on receiving this message whatever the theme you use:

  • Caching issues: (clear the cache of your browser and check if it helps). This is relevant especially if it happens from time to time.
  • Conflicts with browser add-ons: In this case, you can switch to another browser (it has to be Chrome, Safari, Firefox or Opera).
  • Back-end issues: (try to click on "Edit with Elementor" from the front-end and check if it works this way).
  • Plugin conflict (deactivate all your plugins besides Elementor and Elementor Pro to check if it removes the error message and if it is the case, reactivate them one by one to find the culprit). Make sure also that you publish your pages given that sometimes, conflicts or unusual server configurations can make the editing with Elementor impossible on draft pages.
  • Permissions on pages built with Elementor and Membership plugins. To rule out this possibility, deactivate temporarily your membership plugin.
  • The structure of your permalinks (in this case, save one more time your permalinks)
  • 404 pages (this can also be due to the structure of the permalinks) or the page does not exist anymore.
  • A WordPress install without the .htaccess file (in this case, you have to verify with your hosting company if you have this file on your WP install)
  • When you do not have the  Wordpress Default Loop in your layout (this has to be checked with the support of your theme)
  • A Server which erases the PHP $_GET variable (this can be solved by your hosting company)

Please note that this message occurs also whenever a page cannot be loaded (whatever the reason).