A single, unindexable page that sells unbuilt features, hides price, and shows no proof is leaking qualified operators before a demo is ever booked. Three ways to rebuild it, and the one we recommend.
Ten structural issues, ranked by priority. The first three are P0: they touch credibility and discoverability, and two of them are free.
| # | Issue | Priority | Action |
|---|---|---|---|
| 1 | Unbuilt features sold as live | P0 | Remove present-tense claims for retention, occupancy, and AI modules sitewide. Reframe as en desarrollo. Rewrite hero and feature copy to shipped capability only. |
| 2 | Single-page site cannot be found or indexed | P0 | Rebuild as a multi-page, server-rendered or pre-rendered site with one indexable URL per intent. |
| 3 | No transparent pricing or self-qualification | P0 | Add a precios page with the three COP tiers and a pre-demo qualification form. Show Operación now; mark Cobros tiers disponible próximamente until rails ship. |
| 4 | Hero sells features, not the operator job | P1 | Replace the hero with the dues-and-DIAN outcome plus Bogotá-operator credibility and one demo CTA. |
| 5 | Zero on-site proof in a peer-proof category | P1 | Add a casos proof section (named Colombian cases led by Alpha Fit Club) and surface review signals once seeded. |
| 6 | No compliance content where buyers search | P1 | Add evergreen DIAN, Bre-B, and Ley 1581 pages that own the long-tail the category leader ignores. |
| 7 | No guided-migration or onboarding page | P1 | Add a migración page describing free, WhatsApp-supported white-glove migration off spreadsheets. |
| 8 | Member-app identity bleeds into operator pitch | P1 | Lead with the operator narrative; present the member app as an operator benefit on a separate page. |
| 9 | Demo CTA is the only path and high-friction | P2 | Add transitional CTAs (pricing, dues-leakage calculator, DIAN checklist) alongside the demo CTA. |
| 10 | No URL taxonomy, breadcrumbs, or linking | P2 | Define a lowercase, hyphenated Spanish-slug scheme, breadcrumbs, and hub-and-spoke internal linking in the rebuild. |
Vigoo App's public site is effectively a single, unindexable page that sells features the product does not yet ship, hides price, and shows no proof, so qualified Colombian operators leak out of the funnel before a demo is ever booked.
Epirco recommends a multi-page rebuild that leads with the operator's real job, collecting dues off cash, invoicing for DIAN, and seeing month-end numbers, publishes transparent COP pricing, and builds a Spanish compliance-content layer that captures the search intent the category leader ignores.
The single most urgent action is free and immediate: stop presenting unbuilt retention and AI features as live, because that gap ruptures trust in a trust-led category and endangers the referral base that produced near-zero churn.
Of the three architectures presented, Epirco recommends the Authority-and-Compliance Hub, which optimizes conversion and organic discovery together and addresses every P0 issue.
The problem is not a weak product. It is invisibility and a trust exposure. Fix the honesty, publish the price, rebuild for indexing, and own the compliance long-tail.
The distribution is front-loaded on credibility, because the central commercial problem is invisibility and a trust exposure, not a weak product.
The product retains operators at top-decile rates once they are inside, so the structural work is almost entirely about being found, being believed, and being understood before the demo. Two of the three P0 issues, the honesty of claims and price transparency, are fast and cheap. The third, the multi-page rebuild, is the setup-phase build the engagement already scopes. Fixing the P0 set unlocks the conversion the plan depends on.
Ten findings, ordered P0, then P1, then P2. Each ends with an action and a before-to-after. Current-site assessment is partial: the site is a client-side-rendered SPA that blocks automated crawl, so structure was read from Spanish search snippets and app-store listings.
Feature grid lists retention and AI modules as current features.
Feature grid lists only shipped capability; a separated En desarrollo section names what is coming without present-tensing it.
vigooapp.com: one route, all content, no sitemap.
Home plus producto, precios, casos, and a compliance layer, each separately indexable and listed in sitemap.xml.
No pricing page; demo is the only CTA.
A precios page shows transparent monthly COP pricing and a self-qualification form precedes the booked demo.
Hero leads with an abstract limitless-growth promise.
Hero leads with the operator outcome, cobra sin efectivo, factura para la DIAN, cierra el mes en minutos, and the Bogotá-operator proof line.
No proof anywhere on the site.
A casos section plus proof modules embedded on the home, product, and pricing pages.
No compliance content; zero coverage of the buyer's highest-intent questions.
A recursos compliance cluster answering the searched questions, internally linked to product and pricing.
No migration content; the switch reads risky and undefined.
A migración page makes the switch concrete, supported, and low-risk, linked from product and pricing.
Home copy interleaves member class-booking language with operator administration language.
Operator-first home and product pages; a separate app-miembros page covers the member experience as an operator selling point.
One CTA everywhere, agenda tu demo.
A primary demo CTA plus transitional self-education CTAs on every key page.
No taxonomy, no breadcrumbs, no internal links.
A documented URL scheme, breadcrumbs on every page below home, and a defined internal-linking map.
Three materially different architectural postures, named for this vertical. Each gives a genuinely different commercial decision, not three speeds of the same plan.
Treats the website as a single job: turn a qualified, WhatsApp-reachable operator into a booked, attended demo with the least possible friction. It attacks the documented top-of-funnel leak at the cheapest point, transparent pricing, a self-qualification step, and one dominant demo CTA.
It serves the beachhead Owner-Coach Operator and the ready-to-buy New-Gym Opener. The tradeoff is deliberate: it wins operators who already know they need a tool, and it gives up the slower organic and authority capture that compounds over a year. Fastest to launch, simplest to maintain.
Home (/) [NEW] Producto (/producto) [NEW] Precios (/precios) [NEW] Casos (/casos) [NEW] Alpha Fit Club (/casos/alpha-fit-club) [NEW] Como migras (/migracion) [NEW] App para miembros (/app-miembros) [NEW] Demo (/demo) [NEW] Acceso (/acceso) [MIGRATES] Footer: Sobre, Contacto, Terminos, Privacidad
Total: 13 pages, depth 2. The privacidad page carries Ley 1581 member-data language.
Keeps the full conversion funnel of Option 1 and adds the one thing Option 1 leaves on the table: a Spanish compliance-and-operations content layer that captures the operator's highest-intent searches and makes the site citable by AI answer engines.
It closes the top-of-funnel leak immediately through the funnel pages, and it compounds over the year by owning the long-tail local-rails and compliance intent the category leader does not target, rather than fighting that leader for the broad term head-on. It serves the beachhead and the new-gym opener at once.
The tradeoff is a heavier content build and an ongoing editorial cadence, which the engagement already scopes as ongoing support, so the cost lands inside existing scope. What it gives up relative to Option 3 is the deeper tool-and-expansion infrastructure, correctly deferred until Colombia proof exists.
Home (/) [NEW] Producto (/producto) [NEW] Operacion diaria (/producto/operacion) [NEW] Cobros y DIAN (/producto/cobros-dian) [gated on rails] Reporteria (/producto/reporteria) [NEW] Precios (/precios) [NEW] Casos (/casos) + Alpha Fit Club + [rolling slots] [NEW] Recursos (/recursos) [content hub] Facturacion DIAN para gimnasios Cobrar mensualidad sin efectivo Bre-B para gimnasios [rails-gated] Abrir un gimnasio en Colombia Retencion de socios y enero Proteccion de datos (Ley 1581) Herramientas (/herramientas) [Phase 2] Calculadora de fuga de ingresos / Checklist DIAN Como migras (/migracion) [NEW] App para miembros (/app-miembros) [NEW] Sobre Vigoo App (/sobre-vigoo-app) [NEW] Demo (/demo) Acceso (/acceso) [MIGRATES]
Total: ~28 pages, depth 3. The Cobros y DIAN page and the Bre-B and DIAN resources reflect shipped status only; until the rails ship they describe the problem and planned approach without claiming a live capability or a date.
Keeps the full funnel and content layer of Option 2 and adds a deep resource library, an interactive-tool suite, and pre-built localized expansion shells for the secondary markets. The largest long-run organic and authority capture of the three, and the readiest expansion posture.
The tradeoff is significant and, for this stage, mostly against the plan: it commits build capacity to expansion infrastructure and a large content surface before Colombia proof exists, which the strategy gates against. The local-rails moat does not travel, Mexico runs different tax rails, so expansion shells must compete on operator credibility and local price.
It is the genuine third posture and the eventual destination once the beachhead is won, not the right first move.
Home (/) + full Option 2 funnel and content layer Producto: + Retencion [en desarrollo] + Multisede Recursos (/recursos) [full library] Guias (/recursos/guias/{slug}) + Blog (/recursos/blog/{slug}) Herramientas: Calculadora / Checklist / Comparador Comparativas (/comparativas/{slug}) [evaluator-stage] Programatico (/co/{ciudad}/{tipo}) [Phase 3, narrow] Expansion [gated on Colombia proof]: Mexico (/mx) [CFDI/SAT, not Bre-B] Peru (/pe)
Total: 60+ pages, depth 3-4. The Mexico shell must reflect CFDI and SAT and must not claim Bre-B or DIAN. Faceted and expansion sets carry thin-content and locale risk if built before there is unique substance per page.
| Dimension | Option 1: Conversion-Funnel | Option 2: Authority-and-Compliance Hub | Option 3: Operator-Platform Ecosystem |
|---|---|---|---|
| Vertical archetype | Product-led conversion funnel | Content-and-SEO-led hub | Deep resource-and-tools ecosystem |
| Total page count | ~13 | ~28 | 60+ |
| Phase 1 pages (launch) | 13 | ~18 | ~16 |
| Build complexity (1-5) | 2 | 3 | 5 |
| Estimated launch timeline | Fastest | Moderate | Slowest |
| SEO potential (1-5) | 2 | 4 | 5 |
| Conversion optimization (1-5) | 4 | 5 | 4 |
| Content maintenance burden | Low | Moderate (within scope) | High |
| Scalability (1-5) | 2 | 4 | 5 |
| Best persona served | Owner-Coach (ready buyers) | Owner-Coach + New-Gym Opener | Full sequence incl. multi-site + secondary |
| Priority metric optimized | Conversion | Conversion + operational clarity | Lifetime value + average order value |
| Compliance risk level | Low | Low | Moderate (faceted + expansion) |
| P0 issues addressed | 3 of 3 | 3 of 3 | 3 of 3 |
| P1 issues addressed | 4 of 5 | 5 of 5 | 5 of 5 |
The highlighted column is the recommended option.
Epirco recommends Option 2, the Authority-and-Compliance Hub.
It closes the same top-of-funnel leak Option 1 closes, and it does so while also capturing the compliance long-tail the category leader ignores, which is the documented, low-cost organic opportunity for this market. Option 1 is faster but forfeits the compounding organic capture. Option 3 commits build capacity to expansion and a large content surface before Colombia proof exists, which the strategy gates against and which the single-SDR throughput and bootstrapped position make premature now.
Option 2 fits the recommended Balanced direction: Colombia-first, rails-gated, ARPU on the loyal base, paced to existing capacity. It serves the beachhead and the new-gym opener together, keeps the ongoing content cadence inside existing scope, and leaves Option 3 as the natural evolution once the beachhead is won.
This option addresses 10 of the 10 priority issues, all three P0 and all five P1, plus both P2 items in the rebuild.
Research support: the competitor owns broad category search but carries near-zero proof, so the win is the compliance long-tail plus seeded proof; the buyer's highest-intent searches are compliance-driven; and AI-citation for compliance questions is an explicit channel goal.
Regardless of which option you select, these items should be addressed immediately.
Once you select your preferred direction, Epirco will develop it into a complete sitemap specification with page-by-page content requirements, redirect maps, and build priority timelines.
When you are ready, reach out and Epirco will turn your choice into a complete, build-ready sitemap specification, with page-by-page content requirements, redirect maps, and build priority timelines.