Custom WordPress theme
Yootelco Website Rebuild
A rebuild of yootelco.com on WordPress with a rich SEO foundation, an editorial blog system managed in-house, and a more mature, consistent interface with the brand direction.
Overview
The Website
From the current Lovable build to a custom, SEO-ready WordPress theme that closes the gap between the brand promise and the live experience.
01
The Analysis
The current implementation is a Lovable build based on a Figma design, with technical and SEO limitations. The gap between the brand promise and the live experience is the single biggest growth blocker. The site is reachable, basically mobile-responsive, and tells the right story at a high level. But beyond that it carries the standard limitations of a no-code / AI-builder output.
+
What Is In Place
- An established visual direction.
- Comprehensive textual and media content is available.
- Domain and hosting are set up.
- An integrated blog with real content.
- Total blocking time around 140 ms (PageSpeed).
-
What Is Failing
- The blog lives on a separate subdomain, managed by a third-party provider.
- Adding a page or section means re-running the Lovable generator, not very reliable.
- Heavy initial JavaScript bundle, render-blocking assets, and limited caching-header control.
- A clean, SEO-friendly HTML skeleton is missing.
- No XML sitemap, canonical strategy, schema.org markup, robots controls, or per-page meta editing.
- og:image and twitter:site tags point at Lovable's preview infrastructure.
- Accessibility for AI agents (Claude, ChatGPT, Gemini, etc.) is poor.
- The brand identity is blurred; its signature isn't clearly represented.
- Some background/foreground colors don't meet a sufficient contrast ratio.
With no fancy words
Although there's a clearly established visual direction, the current interface looks outdated and doesn't provide a truly rich experience. Some illustrations look incomplete, and the layout isn't fully consistent. The website gives off too much of an AI vibe, which hurts the trust layer.
This doesn't mean the website is broken. But for a more SEO-rich and modern solution, several aspects of the site need to be revisited.
02
The Comparison
Several similar companies and direct competitors were analyzed during research. The good news: catching up with and even overshadowing them in the UI context is very achievable with quality approach. Most have more immersive interfaces (partly because of the market they target), but none use heavy animations or complex logic. At the same time, all of them run dozens of pages for SEO. Yootelco's content side is still amateur, but pages and content can (and arguably must) be expanded after launch.
Analyzed
03
The Rebuild
We'll build a custom WordPress theme based on the existing Figma design, with rich SEO and a slightly updated interface.
Core Features
More consistent colors, fonts & spacing
Minimalistic, mature interface
Built-in blogManaged from the admin dashboard, not a separate platform.
Contact form handlingStored in WordPress, listed on the dashboard, and emailed.
Integrated WhatsApp buttonSee Document 02 below.
Codeless management tools for admins
Rich SEO structure & tags
Properly configured skeleton
Sitemap setup
Schema.org markup setup
llms.txt configurationAn emerging standard that helps AI agents understand a site's key content.
Analytics tracking setup
No heavy animations · No Lovable reference
04
The Resources
Two clear approaches for how the website is developed: hardcoded vs. modular. Each trades flexibility against cost and maintenance independence.
Hardcoded
Custom
A fully custom website with virtually every page and section coded directly into the files, allowing a dramatically broader range of changes during and after development. It requires a developer for careful maintenance; admins can still manage dashboard-wired parts (e.g. contact submissions) with no code, but adding or modifying branded pages needs a technician.
Approx. deadline10 - 14 days
Approx. budget$800
Modular
No-code editor
Most pages can be edited directly from the admin dashboard via a drag-and-drop visual editor, and admins can assemble new branded pages from pre-built components. Several things must be agreed upon before development to define what's editable. Some maintenance needs no developer, but it's drastically pricier, since it means building a component library and a no-code editor.
Approx. deadline22 - 26 days
Approx. budgetfrom $2,200
* The fees of any third-party tools, platforms, and the like are not included.
05
The Maintenance
A post-development maintenance plan needs to be established either during or after the development phase. To build a concrete, reliable strategy, several aspects still need to be addressed and covered.
These open areas include defining response times for critical bugs, scheduling regular security updates, outlining content-management workflows, and establishing a clear hosting and backup infrastructure. Resolving these points ensures the platform stays stable, secure, and fully operational long after the initial launch.
Overview
WhatsApp Automation
Third-party tool integration to build a conversation flow and collect leads, capturing minimal data without disrupting the user journey.
01
The Problem
The current website lacks a robust chat-support feature, which directly results in lost leads. A basic chat widget might seem like a quick fix, but it isn't enough for the specific business needs here. Standard widgets fall short in two critical ways: they either fail to collect and store essential lead information at all, or they overcomplicate the experience with high-friction capture forms that drive prospects away. The right answer is an integrated solution that captures minimal lead data without disrupting the user journey.
02
The Solution
A simple solution: a fixed WhatsApp button in the bottom-right corner that takes visitors into a WhatsApp chat. The chat holds a pre-configured conversation path to guide interactions, and the lead data is preserved.
Fixed WhatsApp button
Bottom-right · pre-configured conversation path · lead data preserved.
Several tools can be adopted for this purpose. A few industry leaders are listed below to explore each one separately.
Choosing a tool depends on several factors: whether you plan to add more channels later, how you picture the conversation path, and whether the chats should be entirely pre-built or also allow a "call an agent" scenario. I'll be happy to walk through each option in more detail so we can find the best fit.