Does Google actually care which one you use?
No. This is the first myth to clear, because plenty of agencies sell one platform by claiming Google prefers it. Google has said outright that it does not rank sites by the software that built them. It reads the finished page: how fast it loads, how cleanly it is structured, whether the content answers the search, and whether the site is easy to crawl. A page served by WordPress and a page served as a hand-coded file are the same thing to Googlebot once they arrive. The engine underneath is invisible to it.
So the platform is not a ranking factor. What the platform decides is how easy or hard it is for you to hit the things that ARE ranking factors. That is the honest frame for this whole comparison. Nobody is choosing between a fast platform and a slow one, or a Google-friendly one and a Google-hostile one. You are choosing between a tool that gives you speed and clean structure by default, and a tool that can give you the same result but makes you work for it and keep working for it.
Think of it like a truck. A base work truck and a loaded one both haul the same gravel. The difference shows up in what it takes to keep each one running a route every day. WordPress is the loaded truck with a lot of moving parts, some of which you did not ask for and all of which need service. Hand-coded static is the stripped work truck: fewer parts, less to fail, less to maintain.
For a contractor, that maintenance question is the one that matters. You are not a full-time webmaster. You do roofs or drains or panels. The platform that keeps ranking while you ignore it for six months is the one that fits your life. That is where the platforms genuinely diverge, and the rest of this guide walks through exactly where.
Speed is the real ranking gap between the two
Page speed is a confirmed Google ranking signal, and it is where WordPress and hand-coded genuinely part ways. Not because WordPress cannot be fast, but because it does not start fast. A stock WordPress page assembles itself on every visit: the server runs code, queries a database, loads a theme and however many plugins, and builds the HTML fresh each time. That is real work happening before a single word reaches the homeowner's phone. On a typical contractor WordPress site with a page builder and a dozen plugins, that lands the visitor at four to six seconds on mobile.
A hand-coded static site skips all of it. The page is already built. It is a finished file sitting on a server, and when a homeowner taps your listing, the file ships as-is. No database, no theme assembly, no plugins waking up. That is why a hand-coded contractor site loads in under 2 seconds without any tuning: there is simply nothing between the tap and the page.
Speed matters twice over, and this is the part contractors miss. First, it is a ranking signal, so the faster page has an edge in the results. Second, it decides whether the visitor who found you actually waits. A homeowner with a burst pipe or a dead AC is not patient. Every second of load time bleeds off people who tap away before the page paints, and those are leads you paid for in ranking effort and never got to talk to.
| What happens on a page load | WordPress (typical contractor setup) | Hand-coded static |
|---|---|---|
| Database query on each visit | Yes, unless cached | None |
| Theme and plugin code runs | Yes, every request | None |
| Mobile load, out of the box | 4 to 6 seconds common | Under 2 seconds |
| Caching plugin needed to fix speed | Yes, and maintained | Not applicable |
You can make WordPress fast. It takes a caching plugin, an image optimizer, sometimes a lighter theme, and someone who keeps all of that working after the next update. The trouble is that speed you have to maintain is speed you can lose. A theme update, a new plugin, or an oversized image dropped in by whoever edits the site can quietly undo the tuning, and you find out weeks later when the rankings slip. Hand-coded is fast because there is nothing to make fast and nothing to accidentally un-fast. If speed is the ranking gap you care about most, and for contractors it usually is, this is the section that decides it.
Crawlability and clean code: what Google actually reads
Beyond speed, Google has to be able to read and crawl your pages, and this is the quiet advantage of hand-coded that never shows up in a sales pitch. When a page is built by hand, the code is exactly what it needs to be: your headings, your content, your service list, your schema, and nothing else. Googlebot lands on a clean, shallow file and reads it in one pass. There is no wrapper of builder markup burying your actual words.
WordPress page builders are the usual culprit here. Tools that let you drag boxes around a page produce a lot of nested code to make that flexibility work: layers of divs, inline styles, and generated classes that pad the file and push your real content deeper. Google can still read it, but you have made it work harder, and on a big site that friction adds up. It also bloats the page, which drags speed right back down, so the two problems compound.
Crawlability also covers whether Google can find every page you want ranked. On a hand-coded contractor site, the URL structure is deliberate and flat: your trade pages, your service-area pages, your guides, each at a clean address you chose. On WordPress, URLs and archive pages get generated automatically, and you can end up with tag pages, author pages, and date archives that Google crawls but that add nothing and dilute the site. Someone has to notice those and shut them down.
None of this makes WordPress unrankable. Plenty of contractor sites rank fine on it. The point is narrower: hand-coded gives you a site where every byte Google reads is content you meant to publish, and every URL it crawls is a page you meant to rank. That control is the difference between guessing what Google sees and knowing it.
It shows up most on the sites where it matters most: the ones with a real spread of pages. A contractor chasing rankings across a full set of trade pages and service-area pages, ninety-plus cluster pages is typical for a competitive market, is asking Google to crawl and understand a lot of the site. Every unnecessary tag page, every archive Google wastes a crawl on, every slow builder page is friction spread across all of them. On a small brochure site you might never notice. On the kind of site that actually ranks a contractor across a metro, less code between Google and your content is a straight advantage, page after page.
AI search reads the same clean pages, harder
The comparison sharpens when you factor in AI search, because the answer engines are less forgiving than Google ever was. When ChatGPT, Google's AI answers, or Perplexity pull a contractor into a response, they are reading your page and extracting facts: what you do, where you work, how to reach you. A page that states those plainly in real text gets quoted. A page that buries them in builder markup, images, or slow-loading scripts gets skipped, because the engine grabs what it can read fast and moves on.
This rewards exactly what hand-coded does well. Clean HTML, real trade nouns in the headings, service and service-area pages that name the work in plain words, and schema that hands the engine your facts in a structured form. There is nothing to dig through. The same qualities that make the page fast and crawlable for Google make it quotable for an AI answer. You are not doing anything extra, you are just not fighting the tool.
WordPress can be made AI-readable too, and clean-built WordPress often is. But the common contractor setup, a heavy theme and a page builder, works against it in the same way it works against speed and crawlability: more markup, slower load, facts wrapped in layout code. The engine that has a hundred pages to scan and a token budget to spend is not going to wait for yours to render. It reads the fast, clean page first.
AI-answer optimization is its own discipline, and we treat it as one, but the foundation is the same site quality this guide is about. A fast, cleanly structured, hand-coded page is already most of the way there. That is why we build for it from the first line of HTML rather than bolting it on later. If you want the deeper version of how AI search changes what a contractor site needs to be, that is a separate guide, and this one just flags where it overlaps: clean pages win in both places.
The maintenance and security tax nobody quotes you
Here is the cost that never makes it into the platform pitch. WordPress is not a thing you build once. It is a thing you maintain forever. The core software updates, the theme updates, and every plugin updates, on their own schedules, and those updates regularly break each other. A plugin that ran your quote form for two years stops working after a core update, and now your leads are quietly failing while you have no idea. That is not a rare horror story, it is Tuesday for a neglected WordPress site.
Security is the sharper edge. WordPress runs a large share of the web, which makes it the biggest target for automated attacks. Every plugin is another door, and an out-of-date one is a door left open. Contractor sites get hijacked this way constantly: not because anyone targeted the business, but because a bot found a stale plugin and walked in. It is nothing personal, which is exactly why it is so common. A hacked site can get de-indexed by Google, flagged with a warning, or filled with spam links, and cleaning it up is a bad week and a hit to the rankings you spent months earning.
A hand-coded static site removes this entire category of problem. There is no CMS to update, no plugins to patch, no database to breach, no login for a bot to brute-force. It is finished files served from a fast host. There is nothing to hack in the way WordPress gets hacked, and nothing that breaks itself while you are not looking. The site you launch is the site that is running six months later, unless you deliberately change it.
For a contractor, this is the honest sticker price of WordPress that rarely gets quoted: either you pay someone monthly to maintain and secure it, or you skip that and accept the risk that it breaks or gets breached at the worst time. Hand-coded trades that recurring tax for a site that mostly takes care of itself. When ranking is compounding equity you are trying to protect, not resetting, the platform that does not quietly break underneath you is worth a lot.
So when does WordPress still make sense?
We say no to bad fits, so here is the honest other side. WordPress is not wrong for everyone, and there are real cases where it earns its keep for a contractor. The clearest one is when you genuinely need to publish often and edit pages yourself, weekly, hands-on, without calling anyone. WordPress gives you a dashboard to do that. If you are running a real content operation in-house and someone on your team lives in that editor, the CMS is doing a job you actually need.
The other honest case is if you already have a WordPress site that ranks, takes leads, and works. You do not have to rip out a site that is performing just to change platforms. If it is fast enough, secure, maintained, and bringing calls, leave it alone. Migrating an already-winning site is a real project with real risk, and it only pays off when the current site is actively holding you back on speed, structure, or maintenance headaches.
Where WordPress stops making sense is the most common contractor situation: you want to rank, you want the site to keep ranking while you run your business, and you do not want to be a part-time webmaster or pay one every month. In that case the CMS is solving a problem you do not have (constant self-editing) while creating ones you do (speed, security, maintenance). You are carrying a heavy tool to do a job a lighter one does better.
The way to decide is to be honest about how you will actually use the site. If it is a page you set up to rank and then mostly leave running, updating a service or a phone number a few times a year, hand-coded static fits that reality and rewards it with speed and quiet. If it is a living publication you touch every week, WordPress may be worth its tax. Most contractors we talk to are the first kind and think they are the second. Figuring out which you really are is the actual decision here, and it is worth an honest conversation before anyone builds anything.