How to Create a Blog with Elementor Pro

To create a blog with Elementor you need three templates, not one: an archive, a single post, and a query that feeds them. Most tutorials stop at “drag the Posts widget,” then readers publish a blog that shows ten articles and silently hides the rest. This walkthrough covers the archive template, the single template, dynamic tags, the pagination setting everyone misses, and the four things Elementor genuinely handles badly for blogs.

Before you open Elementor

Two of the most common Elementor blog problems are actually WordPress problems, and both are settled before you drag a single widget.

• A published, empty page called Blog, set as the posts page under Settings > Reading. Elementor’s own archive guide starts here for a reason: without it there is no archive URL for your template to attach to.
• A lightweight theme. Hello Elementor is the obvious pick, and its WordPress.org listing shows version 3.5.1 on over a million sites, requiring PHP 7.4. Astra and GeneratePress work too. If you would rather let the theme own the blog, our roundup of WordPress blog themes is the shorter road.
• Categories and tags that already exist, with a few real posts in them. Loop Grid queries filter by term, and you cannot filter against taxonomies you have not created.
• An SEO plugin. Elementor integrates with Yoast, Rank Math and AIOSEO rather than replacing them.

One more decision worth making now: write your posts in the WordPress editor, not in Elementor. The template supplies the design and the Post Content widget renders your writing inside it. Articles built widget-by-widget in Elementor are far harder to export, bulk-edit or migrate later.

What Elementor Pro actually costs for a blog

Theme Builder, Loop Grid, Archive Posts and every dynamic tag are Pro features. The free plugin, which the WordPress.org listing puts at over 10 million active installs on version 4.2.3, will not build you an archive template. So the first real question is which tier.

Disclosure: the Elementor link below is an affiliate link. If you buy through it we earn a commission at no extra cost to you. It does not change what we recommend.

Plan	Sites	First year	Renewal	What a blogger gets
Essential	1	$60	$60/yr	57 Pro widgets, Theme Builder, Loop Grid, Archive Posts, standard post dynamic tags. No custom-field tags, no popups, no custom CSS.
Advanced Solo	1	$84	$84/yr	85 Pro widgets plus custom fields and custom post types, Popup Builder, custom code and CSS.
Advanced	3	$108	$108/yr	Same features as Advanced Solo, three activations.
Expert	25	$204	$204/yr	Same features, 25 activations. Roughly $8 per site per year, the lowest per-site cost of these four.

Two things worth pulling out of that table. First, none of the four Pro plans renews at a higher price than year one, which is unusual and worth banking. Second, the tier line that matters for blogs is not widget count, it is dynamic content: Essential explicitly excludes custom fields and custom post types. A plain blog never touches those. An ACF-driven blog needs Advanced Solo, and that is also where Elementor popups and per-widget custom CSS start. Prices come from the Elementor pricing page.

The separate Elementor One bundle is the exception on renewals: it runs 180 USD for the first year and then 228 USD a year. Fine if you want the wider platform, irrelevant if you just want a blog.

Build the blog in seven steps

Step 1: Point WordPress at a posts page

1. Publish an empty page named Blog. Do not design it. Elementor will take it over.
2. Go to Settings > Reading and set Posts page to that page.
3. While you are there, confirm Discourage search engines from indexing this site is unchecked. Elementor’s own indexing troubleshooter lists this as the first thing to check, and it is left on after staging builds constantly.

Step 2: Create the archive template

Go to Elementor > Theme Builder and add an Archive template. Insert a library block or close the library and start empty. Use the gear icon in the lower left of the panel to choose which archive you are previewing, otherwise you are designing against whatever Elementor picked.

Then set your display conditions on publish. For a normal blog, one condition covering all archives is enough. Get more specific only when a category genuinely needs its own layout, and remember that per-category conditions multiply the templates you have to maintain.

One thing the Elementor archive documentation states plainly and most tutorials never mention: archive templates remove theme sidebars by default. If your design depends on a sidebar, you are rebuilding it inside the template.

Step 3: Choose Loop Grid or Archive Posts, then query it

These two widgets look interchangeable and are not. Elementor’s comparison of the Posts and Archive Posts widgets spells out the difference:

• Archive Posts has no query control at all. It shows whatever satisfies the archive template’s display conditions. On a category archive that is exactly right, and it is the correct widget for a true archive.
• Loop Grid and Posts have full query controls, and Loop Grid lets you design the card as a reusable template rather than picking from preset skins. This is what you want for a curated homepage feed or a “more from this category” block.
• Drop Archive Posts on a normal page and it renders only the current post. That is the source of the “my widget shows one post” complaint.

For the Loop Grid query, leave Source on Posts, keep the toggle on Include, then use Include by to filter on Term or Author. Term covers categories, tags and any custom taxonomy. Elementor’s loop grid query guide walks the same controls.

Step 4: Turn pagination on, because it is off by default

This is the single most common broken Elementor blog, and it fails silently. Loop Grid pagination defaults to None, and None means one page of items and no way to reach the rest. Nothing warns you. Your archive looks finished and quietly hides post eleven onward.

Select the Loop Grid, open the Content tab, expand Pagination and choose a style. Per Elementor’s pagination documentation your options are None, Numbers, Previous/Next, Numbers + Previous/Next, Load on click, and Infinite Scroll.

• Numbers or Numbers + Previous/Next for a blog. They produce real, crawlable, linkable pages. Turn Shorten on once you are past four pages and the list collapses to the current page, the next two, and the last.
• Load on click appends the next page under a button and leaves the previous one visible. Reasonable for a magazine-style homepage feed.
• Infinite Scroll is the one to be careful with. Elementor’s own documentation admits that users “will often be interrupted as new items need time to load,” and there are no page URLs for anything past the first screen.
• With Numbers or Previous/Next you also pick a page load method: Page Reload or AJAX. AJAX refreshes only the grid.

If you have two Loop Grids on one page, they paginate together by default. Switch Individual Pagination on to separate them, and note the constraint: every Loop Grid on that page must share the same Individual Pagination setting.

Step 5: Build the single post template

Back in Elementor > Theme Builder, click the plus beside Single Post. At minimum you need Post Title, Featured Image and Post Content. Author Box, Post Info, Post Comments, Post Navigation and Breadcrumbs are all in Essential, so add what your design calls for. Publish, add a condition covering all posts, then save and close.

The Post Content widget is the important one. It renders whatever you wrote in the WordPress editor, which is what keeps your articles portable. For the design decisions inside this template we have a longer piece on building a single post layout with Elementor.

Step 6: Wire up dynamic tags

Dynamic tags are what turn a static design into a template. Anywhere you see the database icon on a control, you can bind it to live post data instead of typing a value. Elementor’s list of available dynamic tags is the reference; the ones that carry a blog are Post Title, Post Excerpt, Post Terms, Post Time, Post URL, Featured Image Data, Author Name, Author Info and Comments Number.

Two practical notes. Featured Image Data will pull the image alt text, so a card that uses it inherits whatever alt you set in the media library, which is a good argument for writing real alt text. And Elementor flags that Post Time can be affected by caching, so if published dates go stale on your archive, look at your cache rules before you blame the template. Our guide to WordPress cache plugins covers where those exclusions live.

If you are binding to ACF fields, that is the Advanced Solo line again. Empty custom fields also leave gaps in a card design, which is a separate problem worth solving with conditional logic that hides a widget when its ACF field is empty or a dedicated dynamic visibility plugin.

Step 7: Verify it, properly

Do not trust the editor preview. Log out, or open a private window, and check the live site:

1. Visit /blog/. Your archive template should render, not the theme default.
2. Count the posts, then go to page 2. If there is no page 2 and you have more posts than the grid shows, Step 4 did not stick.
3. Open a single post. If it renders in the theme layout instead of your template, check that post’s Page Settings template value, not your conditions.
4. Open a category archive and an author archive. Both hit the same archive template unless you built separate ones.
5. Check a post with a manually written excerpt and one without. They will not match, and the next section explains why.
6. Run the live archive URL through PageSpeed Insights and note the numbers before you add anything else.

What breaks

Five failure modes account for most Elementor blog support threads, and three of them are silent.

• The single post template is ignored on some posts. Elementor only applies it to posts whose Page Settings use Default Template. Any post set to Canvas or Full Width skips it entirely, however perfect your display conditions are. This is documented in Elementor’s single post template guide and it catches almost everyone once.
• Excerpt Length does nothing on some cards. The control only trims auto-generated excerpts. Any post with a manually written excerpt ignores it, which is why archive cards end up ragged. Either write manual excerpts everywhere or nowhere.
• The sidebar vanished. Archive templates strip theme sidebars by default. Rebuild it in the template or accept the change.
• Two loops paginate as one. Default behaviour. Individual Pagination fixes it, and must be set identically on every Loop Grid on the page.
• Nothing is indexed. Usually the Reading setting from Step 1, a leftover staging robots.txt rule, or a security plugin injecting noindex. Elementor’s indexing troubleshooter walks the same checklist, and it is worth pairing with our notes on SEO-optimising blog posts in WordPress.

What most Elementor blog tutorials leave out

The genuine weak spots are not the ones people complain about. Elementor is very good at designing an archive. It is weaker in four specific places, and knowing them up front saves a rebuild.

Your layout lives in the database, not in files. Templates are WordPress posts. That means no version control, no diffing a template change, and no code review. For a solo blog that is fine. On a site two people edit, it is a real operational cost with no good workaround.

Archive Posts gives you no editorial control. There is no “pin this post to the top of the category” without dropping in a second, separately queried Loop Grid above the archive. Curation is a layout problem in Elementor, not a setting.

Card markup is a full template, repeated. Each Loop Grid item renders the whole loop template you designed. A card with a nested container stack costs that stack times the number of cards on the page, every page. Keep loop templates flat and shallow; this is the one design decision with a direct output cost.

Every extra capability becomes another plugin. Related posts, reading time, table of contents beyond the basic widget, post filtering: these arrive as third-party widgets. Our list of Elementor addons is genuinely useful here, but each one is another author, another update cycle, and another thing loading CSS on your archive.

The catch: what happens when you stop renewing

This is the part that should shape the decision, and it comes from Elementor rather than from us. Their documentation on not renewing Pro says that if you do not renew you can no longer update Elementor Pro or add Pro features, and “may only have limited access to existing Pro features.” Renewing is what keeps you eligible to update the plugin, add Pro widgets, duplicate them, and add new dynamic tags. The same page warns that updating free Elementor while Pro stays behind can cause compatibility problems.

Read that against what you just built. Your archive template, your single template and every card in your loop are Pro widgets. So the honest framing is that Elementor Pro on a blog is a recurring cost in the same bucket as hosting, not a one-off purchase. At 60 USD a year that is a defensible line item. It is still a line item, and it is the reason the free-plus-good-theme route deserves a serious look before you commit.

Performance is the part you have to measure yourself

Archives are the heaviest pages on most blogs: many images, many cards, and in Elementor’s case many repeated templates. The targets are not negotiable and they are public. Google’s Core Web Vitals guidance puts a good result at LCP within 2.5 seconds, INP at 200 milliseconds or less, and CLS at 0.1 or less, measured at the 75th percentile of page loads.

We are not going to hand you a benchmark number, because the number depends entirely on your loop template, your images and your host. Measure your own archive URL, then work the usual levers: set explicit image dimensions so cards do not shift, keep the loop template shallow, and cache aggressively. Our guide to speeding up a WordPress website covers the order to do these in.

One caution specific to blogs: cards above the fold should not be lazy-loaded, because the largest card image is frequently your LCP element. Lazy-loading it makes the number worse, not better.

Which path to take

• You want a designed archive and designed posts, one site. Essential, 60 USD a year. Follow all seven steps.
• You are using ACF, custom post types, popups or custom CSS. Advanced Solo, 84 USD. The extra 24 USD a year buys the dynamic content tier, not more widgets you care about.
• You build blogs for clients. Advanced at 108 USD for three sites, or Expert at 204 USD for 25 if you are past three. Budget the renewal into the retainer.
• You just want to publish. Skip Pro. Pick a theme that already handles archives well and spend the 60 USD on hosting instead.
• You want file-based templates and version control. Elementor is the wrong tool. Our comparison of visual page builders covers the alternatives honestly.

Frequently Asked Questions

The verdict

Buy Essential. For a blog on one site, 60 USD a year gets you Theme Builder, the Loop Grid and the post dynamic tags, and every step in this guide runs on it. The widget-count difference between Essential and the higher tiers is mostly WooCommerce, which a blog does not need. Upgrade to Advanced Solo the day you actually add a custom field, and not before.

The two settings that will save you the most grief are the least glamorous: set your posts page under Settings > Reading before you build anything, and change Loop Grid pagination away from None the moment you place the widget. Those two account for more broken Elementor blogs than every design decision combined.

And go in knowing the deal. Your blog layout will live inside a subscription plugin, in the database, and Elementor is explicit that letting it lapse limits what you can do with what you built. That is a fair trade for a designed archive you control. It is a bad trade if all you wanted was somewhere to publish.