HighLevel makes it easy to build a website. But if we need that site to bring in traffic from Google, ease of use is not enough. Based on our experience with client sites, we would not choose HighLevel for a new site built mainly for SEO.
That does not mean WordPress is our first choice, either. We still have older client sites on WordPress, but we have moved away from it for new builds. The updates, upkeep, and security issues have become tiresome.
Our preferred path is lean HTML, with AI tools helping us build and publish sites. We have also been testing SiteSwarm for local business sites, directories, and content sites. The goal is simple: build sites that perform well without creating more work than they need to.
Why We Stopped Using HighLevel for SEO Sites
Our view of HighLevel comes from using it, not just comparing feature lists.
For a long time, HighLevel sites did not perform well in search for us. Then something changed. For roughly a year and a half to two years, properly structured sites began ranking well.
The results were good enough that we moved almost all our client sites to HighLevel. It was easier to build with, and it removed much of the update work we had with WordPress.
Then the results changed again. Sites that had done well began to perform poorly. We cannot say for sure whether Google changed, HighLevel changed, or both played a role. What we can say is that the results no longer supported using it as our main SEO site builder.
There is no clear number for how much worse HighLevel is than WordPress. Our choice comes from the pattern we saw across our own sites, not a fixed ranking penalty.
The Concern With Bloated Code
One suspected issue is the amount of code HighLevel creates.
Open the page source of a HighLevel site or funnel, and there is a lot going on behind what may look like a simple page. We suspect that code bloat is part of the problem, though we have not proved it caused the drop in rankings.
That distinction matters. Our results guide our choice, but they do not prove that every HighLevel site will fail in search.
Where HighLevel Still Makes Sense
We would separate a site built for organic search from a landing page built for a campaign.
HighLevel can still be a good fit for pages that receive traffic from:
- Paid ads
- Email campaigns
- Social media
In those cases, the page does not have to earn its traffic through Google rankings. We are sending people to it from another source.
So our advice is not to avoid HighLevel in every case. It is to match the builder to the job. For a landing page, it may work well. For a local business site that depends on organic search, we prefer another option.
Got SEO Questions? Get answers every week at 4pm ET at Hump Day Hangouts. Ask questions ahead of time, or live – just go to: https://semanticmastery.com/hdho (bookmark this!) 10+ years of insights given every week!
Get your checklist to help get better results with GBPs, faster.
Need DFY services for you Local SEO projects? Head over to Semantic Links.
Why We Are Not Going Back to WordPress
WordPress has a different set of problems for us. We still support older sites on it, but we are not using it for new builds.
The biggest frustration is upkeep. We log in and find plugin updates, theme updates, and core updates waiting. That work keeps coming back.
We have also dealt with hacked WordPress sites over the years. After enough of those problems, we wanted a simpler way to manage websites.
WordPress has changed a lot, too. For our workflow, learning those changes and handling the ongoing upkeep no longer feels like the best use of time.
This is not a claim that WordPress cannot rank. It is a business choice. We want good search performance and less time spent maintaining the platform.
What We Are Testing With SiteSwarm
SiteSwarm is the builder we have been beta testing for our newer approach. Our testing has included direct feedback to the developer and requests for added features.
The platform is designed to build several types of sites:
- Local business websites
- Directory websites
- Blogs and content sites
Our plans include moving the Tree Care HQ directory to it once the needed directory features are ready. We also plan to use its content platform for a content marketing service that agencies can resell to local businesses.
Another useful part is its API and MCP connections. These let connected tools work with the site builder to create sites, edit pages, remove pages, and change templates.
During this testing stage, a public launch and demos were still planned. For anyone without access, our practical advice is to start with clean HTML templates.
Why Lean HTML Is Our Preferred Starting Point
By lean HTML, we mean clean, well-coded pages without a large amount of extra builder code.
We do not need to write every page from scratch. A good HTML template can give us a starting point for the layout. Templates may be free or paid, and AI tools can help adapt them to the site we need.
Hosting does not have to be hard, either. HTML sites can use a normal web host or cloud hosting options, including Amazon S3.
The key shift is that we no longer need to figure out every setup step alone. We can describe the site, our budget, and the tools we use, then ask an AI coding tool to help plan the build and deployment.
Our AI Workflow: Brainstorm, Plan, Build
We use Cursor, though tools such as Claude Code and Codex can support similar work. The tool matters less than the process.
We also use Compound Engineering, which provides skills for brainstorming, planning, and carrying out the work.
1. Brainstorm When the Idea Is Still Rough
If we know there is a problem but are unsure of the best solution, we start with brainstorming.
We explain the idea, and the model asks questions. That helps us fill gaps and decide what we actually need. If the goal is already clear, we can skip this step and move straight to planning.
2. Explain Both What We Want and Why
This is one of the most useful habits we have learned. We give the model:
- The outcome we want
- The reason we want it
- The tools and accounts we already have
- Any limits, such as cost or ease of use
We also ask it to suggest other tools, APIs, or connections that could help.
The reason behind the goal can change the plan. Asking for a website is less helpful than explaining what the site must do and how we want to manage it.
3. Agree on the Plan Before Building
In planning mode, the model asks more detailed questions. We work through hosting, templates, setup, and the steps needed to publish the site.
Once we agree on the plan, the model uses that plan as its guide. This keeps the build tied to the goal instead of turning it into a string of unrelated edits.
4. Let the Model Handle the Setup Work
The model may ask us to create an account, get an API key, or provide access through environment variables. We handle those steps and approve changes as the work moves forward.
From there, it can help build the pages, set up hosting, and deploy the site through the connected tools.
Choose for Search Results and Ease of Management
Our choice is not simply HighLevel versus WordPress. We have moved toward lean HTML and an AI-assisted workflow because we want fewer platform headaches.
HighLevel still has a place for campaign landing pages. WordPress still serves our older sites. For new SEO-focused projects, we prefer clean code, a clear plan, and tools that make building and managing the site easier.

