Templates.

There's a version of this story you've heard before: someone pays a freelancer $800 for a "custom website," gets a ThemeForest theme with their logo dropped in, and six months later wonders why the site doesn't show up anywhere in Google. The template gets the blame. Usually fairly.

But templates aren't uniformly bad. They're a tool with a specific appropriate use — and the problem is almost always applying that tool to situations it can't handle. This guide walks through what templates actually are, what the major categories do well and do poorly, and where the genuine ceiling sits when you're trying to grow a Tucson service business online.

01What templates are and how they actually work.

1.1What is a website template, technically?

A website template is a pre-designed set of page layouts — homepage, about, services, contact — sold or distributed to multiple buyers. In WordPress, a "theme" is the template layer: the PHP files that control layout, the CSS that controls visual style, the JavaScript that controls interactions. A ThemeForest theme is a WordPress template. The same files — same layout, same CSS — are installed on thousands of sites. You're not buying a custom layout; you're buying a copy of a layout that was designed once for the broadest possible audience.

1.2How do agencies use templates in builds they sell as "custom"?

This is where the line blurs. A common pattern: an agency purchases a ThemeForest theme for $59, installs it for the client, changes the colors, swaps the logo, fills in the copy, and charges $2,500–$4,000 as a "custom build." The client gets a template; the agency captures the production savings. The tell is the timeline: a ThemeForest install can be configured in 10–15 hours. A real custom build for the same scope takes 60–100 hours. A 10-hour "custom website" is a template build.

1.3What are the most common template sources?

ThemeForest (part of the Envato marketplace) is the dominant WordPress theme marketplace — over 11,000 themes, most bundled with a page builder. Elegant Themes sells Divi as both a builder and a template library. StudioPress (Genesis framework) sells child themes. Outside WordPress: Wix, Squarespace, and Webflow all have their own template systems. Shopify has its own theme ecosystem. The common thread is that the design was produced once and sold to many — a fundamentally different product from a design produced once for you.

1.4What does a "demo import" mean?

Most premium ThemeForest themes include a "demo import" — a one-click install that replicates the theme's demo site on your WordPress install, complete with sample pages, images, menus, and widgets. The idea is to get you started with a fully designed site that you then replace with your real content. In practice, many "builds" never get much further than swapping the demo images and text for client images and text. The demo import is the product; the rest is configuration.

1.5Is a "premium" ThemeForest theme better than a "free" WordPress theme?

Not necessarily in quality — some free themes are built better than premium ones. Premium themes typically include a bundled page builder, a demo importer, more layout options, and support. But premium doesn't mean performant. Many of the most popular ThemeForest themes (Avada, The7, Salient) are notoriously heavy — shipping megabytes of JavaScript and CSS that produce Lighthouse scores in the 20–40 range on mobile. Premium buys you more features. It doesn't buy you speed or SEO fitness.

02The ThemeForest ecosystem — what you're actually buying.

2.1What's Avada and why does it come up constantly?

Avada is the best-selling ThemeForest theme of all time — over 900,000 sales. It's a multi-purpose theme bundled with its own page builder (Fusion Builder) and an enormous library of pre-built sites. Its ubiquity is partly why "Avada site" has become shorthand for generic design — when you've seen 900,000 variations of the same template structure, the aesthetic becomes recognizable. Avada sites also consistently underperform in performance benchmarks; the theme ships a substantial JavaScript and CSS payload that most sites using it never fully address.

2.2What about themes that claim to be "ultra-fast" or "performance-first"?

Astra, GeneratePress, and Kadence are the most commonly cited "lightweight" themes — they're genuine improvements over Avada or The7 in base load. Astra in particular has invested in performance and has competitive Lighthouse scores when used with minimal plugins. The important distinction: a lightweight theme used with Elementor is not the same as a lightweight theme used with core Gutenberg blocks. Many "fast Astra builds" are Astra + Elementor, which cancels out the theme's performance advantage. Ask what builder, if any, is running under the theme.

2.3What happens when a ThemeForest theme stops being maintained?

Theme abandonment is a real risk. When a theme author stops updating their theme, it stops receiving compatibility updates for new WordPress versions, PHP versions, and plugin updates. A site running an abandoned theme accumulates security vulnerabilities over time. ThemeForest themes also often bundle plugins (Revolution Slider, WPBakery, Visual Composer) that may have their own maintenance dependencies. We've migrated sites where the theme hadn't been updated in three years and was running PHP 7.0 because a newer PHP version broke it. The migration cost was substantial.

2.4Can I identify if my site is running a ThemeForest theme?

Yes. Wappalyzer (browser extension) identifies the theme. The WordPress admin also shows the active theme name under Appearance > Themes. You can also view page source and search for the theme name or "Envato" — many ThemeForest themes include attribution comments in the HTML output. If you see a theme you recognize from ThemeForest on your own site, you're on a template, regardless of what you were told when you purchased the build.

2.5How many sites are running the same theme as mine?

For popular ThemeForest themes: hundreds of thousands. Avada's 900,000+ installs. The7 has 250,000+. Salient has 200,000+. Your direct local competitors may be running the same theme with different colors. This matters for brand differentiation — if your HVAC company site and your main competitor's site are both running The7 with the same section order and widget patterns, there's no visual reason for a prospective customer to perceive one as more professional than the other. Templates make brand differentiation structurally difficult.

03Wix and Squarespace templates — the hosted trap.

3.1Are Wix and Squarespace templates the same as WordPress templates?

Similar concept, different infrastructure. Wix and Squarespace are closed platforms — you don't install software, you subscribe to a service. The templates are layouts within those platforms' editors. The difference that matters for business owners: you can't move a Wix or Squarespace site to another platform. If you decide to migrate to WordPress, you're rebuilding from scratch. You don't own the infrastructure, only a subscription to use it. WordPress — even with a ThemeForest theme — is self-hosted. You own the database. The distinction is significant at migration time.

3.2Does Wix actually affect SEO?

Wix has improved meaningfully since 2020 — it now supports structured URLs, allows meta customization, and generates XML sitemaps. The SEO gap between a well-configured Wix site and a basic WordPress installation has narrowed. What hasn't closed: server-side rendering limitations that affect crawl efficiency, limited schema markup control, and the platform's inherent constraint on technical SEO depth. For a business competing on local service keywords in Tucson, a well-configured WordPress site has more SEO ceiling than Wix — not because Wix is broken, but because WordPress's technical flexibility allows more precise optimization.

3.3What's the honest case for Squarespace?

Squarespace produces genuinely good-looking sites with minimal effort. The template quality is above average — thoughtful typography, consistent spacing, mobile responsiveness built in. For photographers, creative professionals, and small retailers who need a portfolio or e-commerce presence without developer involvement, it's a legitimate choice. The limitations emerge at the edges: custom integrations, complex content structures, technical SEO depth, and migration. For a Tucson service business competing aggressively in local search, those edges matter.

3.4What does migrating off Wix or Squarespace actually involve?

More work than people expect. Wix and Squarespace have limited export options — some content can be exported via XML or CSV, but page layouts, custom sections, and design elements don't transfer. Images export cleanly. Blog posts sometimes export via RSS. Service pages, portfolio items, and custom content often require manual reconstruction. A 20-page Squarespace site migrating to WordPress realistically requires 20–40 hours of work to rebuild — comparable to building the WordPress site from scratch with the Squarespace site as a content blueprint.

04Why templates limit growth over time.

4.1Why does a template site struggle to scale to 50+ pages?

Templates are designed around a fixed number of page types — homepage, about, services, contact, maybe blog. Adding a complex content architecture (industry sub-pages, city-specific landing pages, programmatic content) requires manipulating the template in ways it wasn't designed for. You end up with pages that are clearly the same template with different text — no unique visual language, no page-type-specific layout, no structured data variation by page type. Custom themes are built with a content architecture in mind; templates are built for a snapshot site.

4.2How does template design affect conversion rate?

Templates optimize for generic visual appeal, not for your specific conversion goal. The "hero" layout in a ThemeForest theme was designed to look good in a demo. It wasn't designed around the question "when a Tucson homeowner lands here after searching 'HVAC repair near me,' what's the fastest path to a booked appointment?" Conversion rate optimization requires page layouts built around a specific user journey. Templates force your user journey into a pre-designed flow. Custom builds reverse the process: the journey comes first, the layout follows.

4.3What about brand differentiation — does it really matter in Tucson?

It matters in any competitive category. If your Tucson dental practice and the dental practice two miles away are both running the Salient theme with different photos and logos, there's no visual reason for a prospective patient to perceive one as more professional, more trustworthy, or more aligned with their needs. Visual differentiation doesn't close sales on its own — but it creates the first impression that either earns the scroll or doesn't. Templates guarantee you're building on the same visual foundation as your competitors who use the same theme.

4.4Does the template's visual structure ever actually hurt conversion?

Frequently. ThemeForest templates are built to showcase as many features as possible in the demo — sliders, counters, multiple hero variants, portfolio grids, team sections. Businesses install these themes and activate most of the sections because they're there and they look impressive. The result is a homepage with 15 sections competing for attention, no clear primary CTA, and a user who doesn't know what to do. A custom layout is edited down to what's necessary. Templates are built to impress on ThemeForest; custom layouts are built to convert on your site.

4.5What happens when you need something the template doesn't support?

You either build a workaround, hire a developer to hack the template, or discover the limitation is structural and can't be addressed without rebuilding. Template hacks accumulate: child theme overrides, custom CSS injections, plugin additions that partially compensate for missing functionality. After 2–3 years of this, the site is a patchwork — custom CSS fighting the theme's CSS, plugins adding JavaScript that conflicts with the builder, functionality that breaks unpredictably when either the theme or a plugin updates. This is the most common state of a 4-year-old template site.

05When a template is the honest right answer.

5.1What business situations genuinely warrant a template site?

A pre-revenue business that needs a web address this week. A business testing a new service offering that may not exist in 90 days. An event or campaign with a clear end date. A side project with no SEO ambitions. A business whose entire customer acquisition happens offline — through referrals, in-person networking, or existing relationships — and who only needs a digital business card. In these cases, a template site at an honest price ($500–$1,500) is exactly the right tool. The problem is charging custom prices for it, or scaling a template into a growth channel it can't support.

5.2Are there industries where templates work better than others?

Yes. Industries with low online competition — niche B2B services, highly specialized trades, businesses in markets with few digital competitors — have more room for a template site to perform adequately. If you're the only English-speaking dentist within 30 miles, a template site with accurate NAP and some basic SEO can rank without much effort. The competitive pressure that makes custom work necessary is what determines whether a template can hold. In competitive Tucson service categories (dental, legal, HVAC, med-spa), that pressure is high enough that templates consistently leave ranking potential on the table.

5.3What's a reasonable budget expectation for a template-based build?

A ThemeForest theme costs $59–$69. A developer configuring it honestly — installing, customizing colors and fonts, populating content, configuring SEO basics, setting up contact forms — should charge $800–$1,500 for a 5–10 page site. A well-configured Wix site can be set up for $500–$800. These are appropriate prices for template work. If you're being quoted $3,000–$6,000 for a 10-page site and you're not getting a scope document that explicitly mentions custom theme development — ask what's in the build before you sign.

5.4Can a template site rank in Google?

Yes — for low-competition queries, local searches with limited competitors, and long-tail keywords with specific intent. A well-configured Astra site with quality content can rank. A carefully managed Wix site can compete for local terms. Template sites fail to rank primarily in two situations: competitive queries where performance matters at the margin, and queries that require a depth of content and technical SEO that template sites can't cleanly support. "Will it rank at all" is a different question from "will it rank as well as it could."

5.5If I start with a template, when should I plan to rebuild?

When the business is generating enough revenue that the opportunity cost of ranking better is real. For most Tucson service businesses, that's around the $300K–$500K annual revenue mark, or when you're clearly leaving leads on the table because of ranking position. Plan 12–18 months from launch as a reasonable horizon to reassess. The mistake is assuming the template site will scale indefinitely — it won't, and the rebuild cost only goes up as the template accumulates plugins, hacks, and content that needs to be migrated. Earlier rebuilds are cleaner rebuilds.

06Escaping a template — what a rebuild involves.

6.1What can be preserved from a template site in a rebuild?

Content is almost entirely portable: page copy, images, blog posts, team bios, service descriptions. WordPress's database stores this content independently of the theme — swapping the theme preserves the content. What doesn't transfer is any styling applied via the page builder, builder-specific shortcodes embedded in page content, and any layout configurations stored in the builder's custom tables. You're building a new theme and importing content, not migrating a site.

6.2How disruptive is a rebuild to an existing live site?

With a proper staging workflow, not very. The new site is built on a staging URL — separate from the live site — and is fully tested before anything goes near the production URL. When the new site is approved, the staging site replaces the live site, typically during a low-traffic window. The existing site stays live and unchanged throughout development. There's no downtime during development, and a clean cutover typically involves only a few minutes of DNS propagation. A firm that plans to build on the live site without staging is a firm you shouldn't hire.

6.3Will a rebuild hurt my existing SEO?

A rebuild done correctly should not hurt SEO — and often improves it. The critical pieces: preserve all existing URL structure (or set up 301 redirects for any URLs that change), preserve and improve on-page meta tags and structured data, and submit an updated sitemap to Google Search Console after launch. A well-executed rebuild typically shows ranking improvement within 60–90 days as Google indexes the improved performance scores and schema. SEO Preservation is its own field guide if you want to go deeper on protecting rankings during a migration.

6.4What's the timeline for a proper rebuild?

For a 10–20 page service business site, plan 6–10 weeks from kick-off to launch. That includes discovery and strategy (1–2 weeks), design and approval (2–3 weeks), development and content population (2–3 weeks), QA testing and pre-launch checks (1 week). Rushed timelines are where quality gets cut. A rebuild from a template is also an opportunity to get the information architecture right — to add the service sub-pages, the FAQ sections, the location pages that should have been there from the beginning. Build it right the second time.