There is a persistent assumption that a WordPress site which looks properly designed requires paid plugins. It does not, but it does require knowing exactly where the free versions stop — because the usual failure is to start building in the wrong tool and hit the wall halfway through.
This is the map, based on building a full site on the free tiers of Blocksy and Elementor.
The rule that makes it work
The theme does the chrome. The page builder does the content.
That one division of labour is what makes the free stack viable, and ignoring it is what makes people conclude they need to upgrade.
Elementor Free has no Theme Builder. It cannot build your header, your footer, your blog archive, your single-post template or your 404 page. If you try, you will either build a header on every page by hand or pay for Pro.
Blocksy Free, meanwhile, has a full header and footer builder — including a sticky header, a transparent header and a mega menu, all of which are typically paid features elsewhere. It also styles the blog archive and the single post template without any builder at all.
So: header, footer, navigation, blog templates and global colours go in Blocksy. The inside of each page goes in Elementor. Nothing overlaps and neither tool is asked to do the thing it cannot.
What Elementor Free genuinely gives you
More than its reputation suggests. Containers — the flexbox layout model — are free, which means proper responsive layout without the old section-and-column scaffolding. The widgets that matter for a content site are free: heading, text editor, button, image, divider, accordion, icon list, shortcode.
The most under-used free feature is the CSS Classes field on every element. Per-widget Custom CSS is a Pro feature, but the class field is not. So you write your styles once in the theme’s global CSS, and apply them by class name from inside the builder. In practice this is better than per-widget CSS anyway — the styling lives in one file you can read, rather than scattered across post meta where nobody will ever find it.
What you will actually hit
No form widget
Elementor’s form widget is Pro. Use a dedicated form plugin and drop it in with the shortcode widget. Forminator’s free tier is unusually complete — conditional logic, multiple recipients, entry storage, spam protection. One thing to do first: set the form’s design style to “None” in its appearance settings, or it fights whatever you style on top of it.
No post loop
You cannot list blog posts inside an Elementor page on the free tier. You do not need to: point WordPress at a Posts page and let Blocksy render the archive, which it does well and which you can style in the Customiser.
No sticky elements
Sticky is Pro in Elementor. It is free in Blocksy’s header builder, which is where you actually wanted it.
Duplicate H1s
This one costs people hours. If you build a page hero in Elementor with an H1 in it, and the theme is also printing a page title, the page ships with two H1s — which is an SEO problem and an accessibility one. In Blocksy the fix is the per-page hero setting: any hero type other than the two that render a title outputs nothing at all. Set it per page, or globally for pages, and your Elementor H1 is the only one on the page.
SEO on the free tier
Rank Math Free covers what matters: per-page titles and meta descriptions, canonical URLs, Open Graph tags, XML sitemaps, schema and robots control. There is nothing in the paid version that a brochure site needs.
What it will not do for you is the part that actually moves rankings. A green light on a checklist is not content. Pages rank because they answer a question completely, link sensibly to the other pages that support them, and load fast — not because a plugin approved the keyword density.
Performance
The free stack’s real risk is weight, and it compounds quietly: a builder, a theme framework, a form plugin, a cache plugin and an icon library all loading on every page.
Three things do most of the work. Turn off the Font Awesome and animation libraries in Elementor’s advanced settings if you are not using them. Self-host your fonts rather than calling Google’s CDN, which removes a third-party connection and a privacy question at the same time. And let the cache plugin combine and defer, but check the site afterwards rather than assuming — aggressive JS deferral is the most common cause of a builder site that looks broken only for visitors.
When you would actually pay
Be honest about the line. Buy Elementor Pro when you need custom templates for a content type — a properly designed single-product layout, a custom archive, a dynamic loop pulling from custom fields. Buy Blocksy Pro for advanced conditional headers or its content blocks.
A studio site, a service business site, a portfolio, a brochure site with a blog and a contact form: none of those need either. The constraint is mostly useful anyway. Building inside a smaller set of tools tends to produce a more consistent site than building with everything available.
This is the stack I build client sites on. If you want the approach applied to yours, the website design and development page covers how a build runs.