---
title: Sitemap Recommendations - Vigoo App - Prepared by Epirco
description: Sitemap Recommendations for Vigoo App. A diagnostic and decision document prepared by Epirco.
---

[Sitemap *· Vigoo App*](https://epir.co/vigoo-app/sitemap-recommendations#top)Prepared by Epirco

SearchCtrl K

Overview

[00Top 10 Priority Fixes](https://epir.co/vigoo-app/sitemap-recommendations#top10)[01Executive Summary](https://epir.co/vigoo-app/sitemap-recommendations#exec)[02Priority Map](https://epir.co/vigoo-app/sitemap-recommendations#priomap)

Diagnostic

[03Current State Diagnostic](https://epir.co/vigoo-app/sitemap-recommendations#diagnostic)

The Options

[04Three Sitemap Options](https://epir.co/vigoo-app/sitemap-recommendations#options)[4AOption 1 · Conversion-Funnel Site](https://epir.co/vigoo-app/sitemap-recommendations#opt1)[4BOption 2 · Authority-and-Compliance Hub](https://epir.co/vigoo-app/sitemap-recommendations#opt2)[4COption 3 · Operator-Platform Ecosystem](https://epir.co/vigoo-app/sitemap-recommendations#opt3)

Decision

[05Comparison Matrix](https://epir.co/vigoo-app/sitemap-recommendations#matrix)[06Recommendation](https://epir.co/vigoo-app/sitemap-recommendations#recommendation)

Execution

[077 to 14 Day Action Plan](https://epir.co/vigoo-app/sitemap-recommendations#plan)[08Next Steps](https://epir.co/vigoo-app/sitemap-recommendations#next)

ESC

enter to openesc to closeCtrl K anywhere

Driving Your Business Forward

Diagnostic and decision document

# Sitemap *Recommendations*

Vigoo App

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*.

**Engagement**Setup + ongoing**Market**Colombia · es-CO**Date**June 2026**Prepared by**Epirco

Scroll

Overview · 00

## The ten fixes that *matter most*

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. |

Overview · 01

## Executive *Summary*

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 one-line takeaway

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.

Overview · 02

## Priority *Map*

The distribution is front-loaded on credibility, because the central commercial problem is invisibility and a trust exposure, not a weak product.

3

P0 · Compliance and Credibility · act within 7 days

5

P1 · Conversion Impact · act within 30 days

2

P2 · Brand Polish · act within 90 days

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.

Diagnostic · 03

## Current State *Diagnostic*

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.

1

### Unbuilt features presented as live capability

P0

Current

The homepage and store listings present retention, revenue-engineering, and AI-adjacent capability in present tense, alongside genuinely shipped admin features.

Problem

Several of these modules are in development, not shipped, so the page claims capability the product cannot demonstrate.

Impact

In a trust-led category where the buyer probes claims during the demo, a marketed-but-unbuilt feature ruptures trust at the decisive moment and endangers the referral base. Hits brand trust and conversion.

Action

Remove present-tense claims for unshipped modules sitewide, label them *en desarrollo* with no implied date, and rewrite hero and feature copy to claim only shipped capability.

Before

Feature grid lists retention and AI modules as current features.

After

Feature grid lists only shipped capability; a separated *En desarrollo* section names what is coming without present-tensing it.

2

### Single-page architecture is unindexable and unnavigable

P0

Current

All marketing content lives on one client-side-rendered route; there is no per-intent URL, no XML sitemap detected, and sub-paths resolve to the same shell.

Problem

Search engines and AI answer engines cannot parse distinct pages, and visitors cannot navigate to a specific answer, so the site is invisible at the evaluation stage.

Impact

The category leader owns Spanish category search while Vigoo App is absent, so the top-of-funnel leak happens before any demo is booked. Hits conversion and the SEO and AEO scope.

Action

Rebuild as a multi-page site with one indexable, server-rendered or pre-rendered URL per intent, an XML sitemap, and clean meta patterns.

Before

vigooapp.com: one route, all content, no sitemap.

After

Home plus producto, precios, casos, and a compliance layer, each separately indexable and listed in sitemap.xml.

3

### No transparent pricing and no self-qualification step

P0

Current

The motion is demo-gated with no public price; the only path is book a demo, and the free second month is the first concrete commercial signal.

Problem

Asking a price-sensitive, non-technical operator to book a demo with no price and no proof raises the activation energy of the first step to where most never take it.

Impact

This is functionally a price objection in disguise and the primary top-of-funnel leak. Hits conversion and suppresses average-order-value signaling.

Action

Publish a precios page with the three COP tiers and add a pre-demo self-qualification form. Until rails ship, publish Operación and mark the Cobros and Multisede tiers *disponible próximamente*.

Before

No pricing page; demo is the only CTA.

After

A precios page shows transparent monthly COP pricing and a self-qualification form precedes the booked demo.

4

### Hero sells feature confidence, not the operator job

P1

Current

The hero leads with the technological-engine line and consumer-tech energy.

Problem

The copy sells volume and feature confidence, not the operator job or the one differentiator no competitor can copy, and it leans on hype the brand guardrails prohibit.

Impact

A scanning operator does not see their own problem reflected back, so the value proposition fails the five-second test. Hits conversion and premium perception.

Action

Replace the hero with the dues-and-DIAN outcome plus operator credibility, built and run by a Bogotá box, with one demo CTA and one transitional CTA.

Before

Hero leads with an abstract limitless-growth promise.

After

Hero leads with the operator outcome, cobra sin efectivo, factura para la DIAN, cierra el mes en minutos, and the Bogotá-operator proof line.

5

### Zero on-site proof in a peer-proof category

P1

Current

No named cases, no review or rating signals, and no operator testimonials on the site.

Problem

The buyer leans on peer proof before booking a demo, and the site offers none, so it cannot clear the evaluation-stage check.

Impact

Evaluation-stage invisibility loses a peer-proof buyer to a competitor who shows reviews. Hits conversion and premium perception.

Action

Add a casos proof section with named Colombian cases led by Alpha Fit Club, and surface review signals on home, product, and pricing once the review base is seeded.

Before

No proof anywhere on the site.

After

A casos section plus proof modules embedded on the home, product, and pricing pages.

6

### No compliance content where buyers actually search

P1

Current

No evergreen content on DIAN e-invoicing, Bre-B dues collection, or member-data obligations.

Problem

The operator's highest-intent searches are compliance-driven, and the site answers none of them, so it captures none of that intent.

Impact

The long-tail local-rails and compliance intent the category leader ignores is left on the table, and the site is uncitable by AI answer engines for those questions. Hits conversion, operational clarity, and the AEO scope.

Action

Build evergreen compliance pages, DIAN for gyms, Bre-B dues, Ley 1581, with FAQ and HowTo schema, each routing to the demo and the relevant tier.

Before

No compliance content; zero coverage of the buyer's highest-intent questions.

After

A recursos compliance cluster answering the searched questions, internally linked to product and pricing.

7

### No guided-migration or onboarding page

P1

Current

Nothing on the site addresses the switch off spreadsheets and WhatsApp, the buyer's largest perceived risk.

Problem

Migration is the highest-risk lifecycle interaction, and an unaddressed migration fear suppresses close confidence at the decision point.

Impact

Onboarding and migration friction drives avoidable drop-off at the close. Hits conversion and downstream retention.

Action

Add a migración page describing free, WhatsApp-supported white-glove migration, import members, set plans, first invoice, with the steps and the time commitment stated plainly.

Before

No migration content; the switch reads risky and undefined.

After

A migración page makes the switch concrete, supported, and low-risk, linked from product and pricing.

8

### Consumer member-app identity bleeds into the operator pitch

P1

Current

Public listings and copy mix the end-member class-reservation experience with the operator administrative pitch in the same breath.

Problem

The B2B operator buyer and the B2B2C member user have different jobs, and merging them muddies who the site is for.

Impact

Message ambiguity forces the operator to work out whether the product is for them, which depresses conversion at the value-proposition stage.

Action

Lead with the operator narrative across the marketing site; present the member app as an operator benefit on a dedicated page, not as the headline identity.

Before

Home copy interleaves member class-booking language with operator administration language.

After

Operator-first home and product pages; a separate app-miembros page covers the member experience as an operator selling point.

9

### Demo CTA is the only path and it is high-friction

P2

Current

The single conversion action is book a demo, with no lower-commitment alternative.

Problem

A price-sensitive operator who is not ready to talk to sales has nowhere to go, so the only options are commit or leave.

Impact

The funnel loses operators who would convert later if given a way to self-educate now. Hits conversion at the margin.

Action

Add transitional CTAs, see pricing, dues-leakage calculator, DIAN checklist, alongside the demo CTA so the not-yet-ready operator stays in the funnel.

Before

One CTA everywhere, agenda tu demo.

After

A primary demo CTA plus transitional self-education CTAs on every key page.

10

### No URL taxonomy, breadcrumbs, or internal linking

P2

Current

With a single route there is no slug convention, no breadcrumb trail, and no internal linking structure.

Problem

There is no orientation system and no link equity flowing between pages, which weakens usability and SEO in the rebuild if not defined up front.

Impact

Users cannot tell where they are, and search engines cannot understand page relationships. Hits operational clarity and SEO.

Action

Define a lowercase, hyphenated Spanish-slug taxonomy with a consistent trailing-slash policy, breadcrumbs mirroring the path, and hub-and-spoke internal linking from compliance content to product and pricing.

Before

No taxonomy, no breadcrumbs, no internal links.

After

A documented URL scheme, breadcrumbs on every page below home, and a defined internal-linking map.

The Options · 04

## Three Sitemap *Options*

Three materially different architectural postures, named for this vertical. Each gives a genuinely different commercial decision, not three speeds of the same plan.

- **Option 1, Conversion-Funnel Site.** Product-led, lean, demo-optimized. About 13 pages.
- **Option 2, Authority-and-Compliance Hub.** Content-and-SEO-led, mid-depth. About 28 pages. The recommended option.
- **Option 3, Operator-Platform Ecosystem.** A deep resource library with tools and localized expansion shells. 60+ pages.

Option 1

### Conversion-Funnel *Site*

Pages~13

Build complexity2*/5*

OptimizesConversion

Issues addressed7*/10*

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.

Recommended Option 2

### Authority-and-Compliance *Hub*

Pages~28

Build complexity3*/5*

OptimizesConversion + clarity

Issues addressed10*/10*

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.

Option 3

### Operator-Platform *Ecosystem*

Pages60+

Build complexity5*/5*

OptimizesLTV + AOV

Issues addressed10*/10*

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.

Decision · 05

## Comparison *Matrix*

| 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.

Decision · 06

## The *Recommendation*

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.

Coverage

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.

Execution · 07

## 7 to 14 Day *Action Plan*

Regardless of which option you select, these items should be addressed immediately.

Days 1 to 3: P0 fixes, act now

- Remove every present-tense claim for unbuilt modules, retention, occupancy, AI, from the current site and the demo deck, and relabel them *en desarrollo*.Owner: Web developer + PM
- Draft the honest hero and product copy that claims only shipped capability.Owner: Epirco content
- Confirm the Bre-B and DIAN rails build-versus-extension status and the named DIAN-authorized provider, so compliance pages and the Cobros tier can be scoped honestly.Owner: PM + client CFO

Days 4 to 7: quick P1 wins

- Publish a transparent Operación-tier price and a pre-demo self-qualification form; mark Cobros and Multisede *disponible próximamente*.Owner: Web developer
- Stand up the Alpha Fit Club named case as the first proof asset.Owner: Epirco content + client
- Add a privacy page with Ley 1581 consent language for WhatsApp outreach.Owner: Web developer

Days 8 to 14: P1 items

- Draft the three priority compliance resource pages, DIAN invoicing, cobros sin efectivo, abrir gimnasio Colombia, with FAQ and HowTo schema.Owner: Epirco content
- Define the URL taxonomy, breadcrumb rules, and internal-linking map for the rebuild.Owner: Epirco IA specialist
- Separate the member-app story from the operator pitch in all current copy.Owner: Epirco content

After option selection

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.

Next steps

## Review the three options and select the direction that fits how you want to *grow*.

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.

Email Cintia Calegari to discuss and select[projects@epirco.com](mailto:projects@epirco.com)

Driving Your Business Forward

**Prepared by Epirco** for Vigoo AppSitemap Recommendations · Pass 1 · June 2026