How to Tell If Your Web Designer Is Using a Template and Charging You for Custom Work

You hired a web designer for a "custom" website, paid a custom price, and the result feels oddly familiar: a generic navigation, a footer with sections you never asked for, and a layout you are sure you have seen on other sites. You may be paying custom rates for template work, and you would not be the first. This is not always malicious, since some designers genuinely use templates as starting points and customize them heavily, which is a legitimate service when it is disclosed and priced accordingly. The problem is charging premium custom rates while delivering a cheap marketplace theme with your logo swapped in. That is not custom design. It is a markup.

Using a commercial theme is not wrong by itself. According to W3Techs, WordPress powers over 43% of all websites, and a large share of those run on commercial themes that serve their owners perfectly well. The issue is misrepresentation: being told and charged for fully custom work and quietly receiving a lightly customized template instead. Here is how to tell the difference, even if you are not technical.

How can you quickly check if your site uses a template?

The fastest check takes two minutes. Right-click your homepage and choose "View Page Source," then press Ctrl+F and search for "theme" or the names of popular page builders. If your site runs on WordPress, open the dashboard and look under Appearance then Themes, where the active theme name is shown directly. Google that theme name. If it is for sale on ThemeForest or any theme marketplace, you are running a commercial template.

That alone is not a problem. But if you were told and charged for fully custom work, finding a purchasable theme name in your source code is a serious conversation to have with your designer. Free online tools can also detect which theme and plugins a WordPress site uses; enter your URL and they report what is running underneath.

What site features suggest a template was used?

Generic sections you never asked for are the clearest non-technical sign a template was left mostly intact. Open your site and look critically. A "Meet the Team" block when you are a solo operation, a portfolio gallery when you have no portfolio, a blog you never wanted, or tabs and accordions filled with filler all point to a template, because templates ship with a full set of sections designed to suit any business, and removing the unused ones takes customization work a corner-cutting designer skips.

Two more tells. Check the footer: links to features you do not use, such as "Shop" or "Events" or "Members Area," or a credit to a theme company, are template territory. And check your plugins list if you have admin access, under Plugins in the WordPress dashboard. A pile of plugins you do not recognize, especially a page builder like Elementor, Divi, WPBakery, or Beaver Builder, plus bundled slider plugins, usually means the site was assembled from a template that came packaged with all of them. Custom builds tend to have far fewer plugins because the functionality is written into the code.

What technical signs point to a template-based build?

The technical tells live in your page source and your speed score, and both are easy to check. Right-click and choose "View Page Source," then search for theme or page-builder names such as elementor, wpbakery, divi, or beaver-builder. Those builders are tools, not crimes, but they add significant code bloat and are the opposite of hand-coded custom work. Count the stylesheet and script files too: a lean custom site might load a handful of each, while a template-heavy site can load 15 to 30, many for features your site never uses.

Then run a speed test at Google's PageSpeed Insights. According to industry benchmarks from Envisage Digital, the average site loads in around 2.5 seconds on desktop, but template-heavy sites loaded with unused features often exceed 4 to 5 seconds. A mobile score below 50 usually means code bloat is a contributing factor, and that bloat directly affects your revenue. Custom sites on modern frameworks routinely score 90 or higher because every line of code is intentional.

Can you tell from how hard the site is to manage?

A site you cannot update without calling your designer is a strong sign of a template-heavy build, sometimes by design. Custom sites built by competent developers ship with a content management interface that matches your site's structure, so updating text, swapping an image, or adding a post is straightforward. Template sites often do the opposite, burying simple edits under layers of theme-option panels and builder modules until changing a single paragraph means opening a visual builder, hunting for the right module, editing it in a popup, and saving repeatedly.

If that is your experience, the site was built for your designer to manage, not for you, which conveniently guarantees them ongoing revenue. A proper website handover should include training on common updates. If that step was skipped, or the process you were shown was needlessly complex, the underlying architecture is likely the reason.

Does the price and timeline reveal a template?

A genuinely custom 5 to 10 page business website, with original design, hand-coded development, responsive work, and proper testing, takes 40 to 100 or more hours of skilled labor, which is why custom builds are not cheap. In the Philippines a real custom marketing site typically lands in the ₱150,000 to ₱350,000 range, and a professional build in the ₱50,000 to ₱150,000 range. If you paid the low end of those for something described as "fully custom" and it arrived in a week or two, the math does not add up: that is template customization, a legitimate but very different and much cheaper service.

Template customization in the Philippines reasonably runs around ₱15,000 to ₱50,000, so an affordable site is not automatically a scam. A transparent designer who uses a template as a starting point and prices it in that range is offering an honest service. The problem is only ever misrepresentation, charging custom prices for template work. The timeline is a useful cross-check: a custom site usually takes 6 to 12 weeks from kickoff to launch, so a "custom" site delivered in 1 to 2 weeks was almost certainly customized, not built. Understanding the hidden costs of cheap websites explains why the initial price rarely tells the whole story.

What if your designer dodges technical questions?

A designer who built custom work answers technical questions confidently; one who dressed up a template deflects. Ask directly what theme or framework your site is built on, whether the code is custom-written or based on a pre-built theme, how many third-party plugins it uses, and whether another developer could take over the codebase. Clear, specific answers are a good sign. Vague ones, or phrases like "it is proprietary," "you do not need the technical details," or "it is a custom version of our internal framework," often translate to a template they have reused before.

The cleanest prevention is in writing. Before hiring your next designer, make sure your web design contract states whether the work is template-based or custom-built. One clause removes all ambiguity.

What should you do if you paid for custom and got a template?

Start with a direct conversation, not an accusation, because genuine miscommunication about what "custom" means does happen. Then review your contract to see whether it specifies custom design or development or names a theme, since that language determines your standing. If you are unsure whether the customization justified the price, get an independent developer to do a short audit that tells you exactly what is custom, what is template, and whether the price was fair. Finally, weigh whether it matters functionally: if the site loads fast, ranks, and generates business, the template itself is not the problem, only the misrepresentation is, and you might negotiate a partial refund rather than rebuild.

Custom or template: when does each make sense?

Not every business needs a custom build, and the honest answer is that the right choice depends on what the site has to do for you.

If your business has outgrown its current website, custom development is usually the right next step. What matters is making an informed decision based on transparent information, not a sales pitch.

Frequently asked questions

Is using a WordPress theme the same as using a template? Technically every WordPress site uses a theme; it is how WordPress works. The distinction is between commercial themes, which are pre-built, purchased, and used by thousands of sites, and custom themes built from scratch for your project. A custom theme uses the WordPress framework but with original design and code.

Can a template-based website rank well on Google? Yes, but it is harder. Templates often carry code bloat that slows load times, generic structures not optimized for your keywords, and limited control over technical SEO. A well-optimized template can rank, but a well-built custom site usually has a clear performance advantage.

How can I check if my designer used a page builder? Log into the WordPress dashboard; if you see Elementor, Divi, WPBakery, Beaver Builder, or similar in the page editor, your site uses a builder. Page builders also leave distinctive signatures in the source code.

Should I confront my designer if I find a template? Approach it as a conversation. Ask what theme or framework they used, how much of the code is custom, and why. Their answer reveals whether it was deliberate misrepresentation or a terminology mix-up.

Can a template site be converted to custom later? Usually it is more practical to start fresh than to convert, since template code is structured around the template's framework and unwinding it often costs more than building new. Your content migrates fine; the code typically needs rewriting. If you make the switch, plan it so you do not lose SEO, using our guide to switching web designers.

The web design industry has a transparency problem, and too many designers blur the line between template customization and custom development. Now you know the questions and the signs, which protects you from overpaying whether you are auditing your current site or shopping for the next one. If you want to talk to a studio that builds on a headless WordPress and Next.js architecture with no commercial themes, no page builders, and no code bloat, book a call and we will show you exactly what you are getting.