Browse documentation

Reference

RankFlow AI Product Architecture Pivot — Impact Analysis & Redesign Plan

Date: 2026-06-13

docs/pivot-impact-analysis.md
On this page

Date: 2026-06-13
Decision: Replace individual client landing pages (subdomains) with a unified high-DA directory website where each client gets a rich profile/listing page.
Rationale: Clients don't want websites — they want rankings. A high-DA directory inherits authority immediately, compounds with each new client, and is the proven model (Yelp, Practo, Justdial, Healthgrades).
New model: Separate directory domain (not rankflow.ai) → programmatic API-driven listing creation → client profile pages → GBP links to directory listing → rankings.


1. What Changed (Executive Summary)#

Before After
Each client gets an individual AI-generated landing page on a subdomain (client.rankflow.in) Each client gets a rich profile page on a unified high-DA directory website (directory.com/clinics/kochi/dr-smith-cardiology)
100 subdomains with zero authority One domain with compounding authority
Clients "own" a subdomain (but don't actually — it's a retention lock-in) Clients get a premium listing on a trusted platform (no ownership fiction)
GBP links to client.rankflow.in GBP links to directory.com/clinics/... (higher DA = better ranking signal)
Landing page is the primary SEO asset Directory listing is the primary SEO asset
Content is a "landing page" (articles, FAQ, schema) Content is a "profile" (bio, services, reviews, schema, map)
Retention via "page goes offline if you leave" Retention via results + exclusivity + genuine value
6 modules: citations + landing page + GBP + social + AI engine + reviews 6 modules: citations + directory profile + GBP + social + AI engine + reviews

2. Files Affected — Complete Inventory#

TIER 1: PUBLIC-FACING (Must Update Immediately)#

These are customer-facing documents. Any inconsistency here confuses prospects and undermines trust.

File Impact Action
docs/homepage-content.md CRITICAL — Every mention of "landing page" needs to become "profile" or "directory listing" or "verified listing" Rewrite Sections 4 (Citations) and 5 (Landing Page → Directory Profile). Update all copy, metrics, visuals, and CTAs.
docs/homepage-build-plan.md CRITICAL — Build plan still references individual landing pages, subdomains, SSG, ISR, wildcard DNS Rewrite Section 5 build plan. Replace landing page mockups with directory profile mockups. Update component inventory.
docs/client-landing-page-plan.md CRITICAL — Entire document is about landing page architecture. Now obsolete. Replace with docs/directory-profile-plan.md covering directory architecture, API-driven listing creation, profile schema, and content model.
docs/homepage-image-prompts.md HIGH — Image prompts reference "landing page" screenshots, phone mockups showing landing pages Update prompts to reference "directory profile pages", "clinic listings", "profile previews".
docs/visual-dna.md LOW — Design DNA itself is mostly correct; only examples need updating Minor: update example screenshots from "landing page" to "profile page".

TIER 2: INTERNAL PRODUCT DOCUMENTATION (Update During Build)#

These are internal specs. They can be updated progressively as the team builds the new architecture.

File Impact Action
docs/build_scope.html CRITICAL — Core product scope document. References landing pages, subdomains, DNS, SSG, ISR, wildcard DNS, retention lock-in, page offline, citations deleted. Complete rewrite of Sections 2.5, 5.3, and retention model. Replace landing page system with directory system. Update data model (LandingPageDirectoryProfile).
docs/research_product.md HIGH — Product research references landing pages, subdomains, site editor, custom domains, page traffic, page ownership Update onboarding flow (remove subdomain assignment, replace with directory listing creation). Remove site editor. Update plan feature matrix. Update retention model.
docs/research_market.md MEDIUM — Competitive analysis references landing page builders. Market positioning should shift to "directory + citation platform" rather than "landing page + citation platform". Update competitive positioning. Remove references to landing page builders as direct competitors.
docs/research_technical.md HIGH — Technical architecture references Next.js SSG, ISR, middleware, wildcard DNS, subdomain routing, Vercel Replace with directory architecture: Next.js SSR/SSG for directory pages, no middleware routing, no wildcard DNS, CMS-like content model for profiles.
docs/research_technical_refined.md HIGH — Same as above, refined version Same update.
docs/research_technical_v3.md HIGH — Latest technical spec. References landing page generation, subdomain, custom domain, CNAME Replace with directory profile generation, API-driven listing creation, no custom domain needed.
docs/plan_business_flow.md HIGH — Business flow references "Landing Page Generation & Deployment" and "Landing Page Automation" Rename to "Directory Profile Generation & Deployment" and "Directory Profile Automation". Update flow diagram.
docs/plan.md MEDIUM — High-level plan. May reference landing pages. Update to reflect directory-first approach.
docs/business_flow_map.md HIGH — The 3,200+ line lifecycle document. References landing pages, subdomains, site editor, page deployment throughout. Search-and-replace "landing page" → "directory profile" throughout. Remove subdomain/deployment flows. Add directory listing creation flow.
docs/scope_brief_extracted.txt MEDIUM — Extracted text from scope brief. Same references as build_scope.html. Can be regenerated from updated build_scope.html.

TIER 3: TECHNICAL SPECS & TEST PLANS (Update as Code Changes)#

These are engineering artifacts. They naturally update as the code changes. The team should update them sprint-by-sprint.

File / Directory Impact Action
docs/specs/backend-api.md HIGH — API references site.publish, site.setCustomDomain, subdomain, landing_page_article Replace with directoryProfile.create, directoryProfile.update, directoryProfile.publish. Remove custom domain endpoints.
docs/specs/ai-services.md MEDIUM — References landing_page_article task type Rename to directory_profile_content or profile_article.
docs/specs/infrastructure-devops.md HIGH — References wildcard DNS, *.rankflow.ai, subdomain routing, CDN rules Remove wildcard DNS. Add directory domain DNS. Update CDN rules for directory domain.
docs/specs/admin-dashboard-ui.md MEDIUM — Admin dashboard has /admin/domains and /admin/websites pages Replace with /admin/directory (listing management) and /admin/directory-profiles (profile pages).
docs/specs/security-compliance.md LOW — Security model is mostly unchanged. Only subdomain references need updating. Update data model examples.
docs/test-specs/ (all files) HIGH — Every test spec references subdomains, landing pages, SSG deploy, wildcard DNS, site editor Major rewrite. Replace with directory profile creation tests, API listing tests, profile publish tests.
docs/test-plan.md MEDIUM — References landing pages in visual regression tests Update to directory profile pages.

TIER 4: BRAND & MARKETING ASSETS (Update as Needed)#

File Impact Action
docs/slide_07_landingpage.png CRITICAL — Slide is literally titled "Landing Page Strategy" Replace with "Directory Profile Strategy" slide.
docs/slides_cover.png through slides_10_advantages.png MEDIUM — Some slides may reference landing pages Review and update where needed.
docs/brand/ LOW — Brand assets (logo, colors) are unchanged. No action needed.

3. What Stays the Same (Unchanged)#

Not everything changes. These core elements remain:

Element Status Why It Stays
Citations (30 directories) ✅ UNCHANGED Still the #1 ranking signal. Just the "landing page" citation is replaced with the "directory profile" citation.
GBP Management ✅ UNCHANGED Still connect, optimize, post, reply. The GBP website URL now points to the directory profile instead of the subdomain.
Social Media Automation ✅ UNCHANGED Instagram, Facebook posts still automated. May link to directory profile instead of subdomain.
Review Management ✅ UNCHANGED Auto-reply, sentiment analysis, approval gate all stay.
AI Engine Optimization ✅ UNCHANGED Structured data, citation authority, FAQ content — all still relevant. The directory profile becomes the primary structured data source.
City-Category Exclusivity ✅ UNCHANGED Still only 3 clients per city per specialty.
Pricing Tiers ✅ UNCHANGED Starter ₹4K, Standard ₹8K, Premium ₹15K, Enterprise ₹25K+. Feature flags may shift slightly.
Onboarding Flow ✅ MOSTLY UNCHANGED Steps 1-3 (business info, location, services) stay. Step 4 (consent) stays. Step 5 changes from "subdomain assignment" to "directory profile creation". Step 6 changes from "landing page generation" to "profile content generation". Step 7 changes from "landing page deployment" to "profile publish on directory".
Monthly Refresh ✅ UNCHANGED Content rewrite, GBP posts, social posts, NAP checks, review replies — all stay. The directory profile content gets refreshed instead of the landing page.
Results Dashboard ✅ UNCHANGED Rank tracking, citation count, review score, social reach — all still tracked.
MCI Compliance ✅ UNCHANGED Informational content, no promotional claims, doctor approval gate — all stay.
DPDPA 2023 ✅ UNCHANGED Data residency, consent, deletion — all stay.
Design DNA ✅ UNCHANGED Colors, fonts, glass frames, animations — all stay. Only the content changes.
SEO Schema ✅ MOSTLY UNCHANGED Organization, SoftwareApplication, WebSite, FAQPage, Review, BreadcrumbList, LocalBusiness schemas all stay. The WebSite schema now points to the directory domain. Individual profiles get LocalBusiness or Physician schema.

4. What Changes (Complete List)#

Product Architecture Changes#

Before After
LandingPage table/model DirectoryProfile table/model
subdomain field directorySlug or profileUrl field
domain / customDomain fields REMOVED — no custom domains needed
template field (3-5 templates) profileLayout field (1-2 profile layouts)
sitePublished boolean profilePublished boolean
siteSection records (hero, services, FAQ, map, reviews) profileSection records (bio, services, reviews, FAQ, map, contact)
LandingPageDeploy job DirectoryProfilePublish job
Wildcard DNS (*.rankflow.in) Single domain DNS (directory.com)
Next.js middleware (subdomain routing) Next.js dynamic route (/clinics/[city]/[slug])
SSG / ISR (static per-client) SSR + SSG (dynamic route, cached)
Vercel hosting (subdomain per client) Vercel hosting (single domain, dynamic routes)
Cloudflare R2 (landing page images) Cloudflare R2 (profile images) — same, just different content
site.setCustomDomain API REMOVED
site.publish API directoryProfile.publish API
admin/domains page admin/directory page
admin/websites page admin/directory-profiles page

Customer-Facing Changes#

Before After
"Your AI-Generated Landing Page" "Your Verified Directory Profile"
"Branded subdomain: yourclinic.rankflow.in" "Premium listing: directory.com/clinics/kochi/your-clinic"
"See your landing page" "See your directory profile"
"Landing page goes live in 60 minutes" "Directory profile goes live in 60 minutes"
"Your landing page includes 3-5 articles" "Your profile includes keyword-rich bio, services, FAQs"
"Landing page traffic" "Profile views"
"Page offline if you cancel" "Profile removed if you cancel (after 30-day grace)"
"We own your landing page" "Your profile lives on India's trusted healthcare directory"
"Custom domain available" REMOVED — no custom domains
"Site editor" REMOVED — no site editing needed (profiles are standardized)

Pricing & Plan Changes#

Before After
landing_page.basic directory_profile.basic
landing_page.custom_domain REMOVED
landing_page.premium_template directory_profile.premium_layout
landing_page.ab_test REMOVED
"Free custom domain" REMOVED
"Free custom landing page redesign annually" "Free profile content refresh annually"

Retention Model Changes#

Before After
"Page goes offline → rankings collapse → retention" "Profile removed after 30 days → gradual ranking decline → retention via genuine value + exclusivity"
Citations deleted on Day 1 of cancellation Citations may stay on directories (directory-dependent) or be removed gradually
"We don't just rank businesses — we OWN their rankings" "We rank your clinic on India's most trusted healthcare directory"
Aggressive lock-in Soft retention: results + exclusivity + exportable data

5. New Architecture: The Directory Website#

Overview#

A separate domain (e.g., indiandoctors.in, clinicrank.in, healthfind.in) — not rankflow.ai. This domain is a high-DA business directory focused on Indian healthcare professionals.

Domain Strategy (Phased):

Phase Timeline Domain Strategy
Phase 1 Month 1–2 New domain (e.g., indiandoctors.in) Build from scratch. Focus on content quality. Start with 10 beta listings.
Phase 2 Month 3–6 Same domain Grow to 50+ listings. Build backlinks (press, partnerships, guest posts). Target DA 20+.
Phase 3 Month 6–12 Same domain Scale to 200+ listings. Target DA 30+. Begin monetization (premium listings, ads).
Phase 4 Month 12+ Acquire existing high-DA domain Buy a domain with DA 30+ (e.g., expired health blog, old directory). Migrate all listings. Immediate authority boost.

Directory Structure#

directory.com/
├── /                          → Homepage: search, featured listings, categories
├── /clinics/[city]/           → City page: all clinics in Kochi, Bangalore, etc.
├── /clinics/[city]/[slug]     → Individual clinic profile (the client's "page")
├── /specialty/[specialty]   → Specialty page: all cardiologists, dentists, etc.
├── /specialty/[specialty]/[city] → Specialty + city: dentists in Kochi
├── /blog/                     → Blog: health articles, SEO content, backlink magnet
├── /about/                    → About the directory
├── /contact/                  → Contact page
├── /sitemap.xml              → XML sitemap for all profiles

Profile Page Content Model#

Each profile page (/clinics/kochi/dr-smith-cardiology) contains:

Section Content Schema
Hero Clinic name, photo, specialty, city, rating, CTA (call/WhatsApp) LocalBusiness or Physician
Bio 300-500 word unique bio about the clinic/doctor
Services List of services with descriptions Service
Reviews Embedded Google reviews + RankFlow review widget Review
FAQ 10+ Q&A accordion FAQPage
Map Google Maps embed with directions GeoCoordinates
Contact Phone, WhatsApp, email, hours ContactPoint
Related "Other dentists in Kochi" — internal links
Schema Full JSON-LD: LocalBusiness + Physician + Service + FAQ + Review + BreadcrumbList All combined

API for Programmatic Listing Creation#

// POST /api/directory/profiles
{
  "practiceId": "uuid",
  "city": "kochi",
  "specialty": "dentist",
  "content": {
    "bio": "string (AI-generated, 300-500 words)",
    "services": ["service1", "service2"],
    "faq": [{"question": "", "answer": ""}],
    "reviews": [{"rating": 5, "text": ""}]
  },
  "media": {
    "photo": "url",
    "logo": "url"
  },
  "contact": {
    "phone": "",
    "whatsapp": "",
    "hours": ""
  }
}

// Response
{
  "profileId": "uuid",
  "url": "https://directory.com/clinics/kochi/dr-smith-dental",
  "status": "published",
  "publishedAt": "2026-06-13T10:00:00Z"
}

GBP Integration#

When a client connects their GBP, the RankFlow system automatically updates:

  • websiteUrihttps://directory.com/clinics/[city]/[slug]
  • description → AI-optimized bio
  • services → pulled from profile services
  • photos → pulled from profile media

Competitive Moat (Internal Only — Not Public)#

The directory itself becomes the moat:

  • Compounding authority: Each new client adds content + backlinks → higher DA → better rankings for ALL clients
  • Natural backlink magnet: Press mentions, partnerships, health articles earn links to the directory
  • Monetization potential: Premium listings, featured placements, advertising (future revenue stream)
  • Acquisition target: A high-DA directory with 500+ listings is a valuable asset
  • Barriers to entry: Competitors can't replicate a 500-listing directory overnight

IMPORTANT: The directory is NOT publicly framed as "owned by RankFlow." It is a "trusted healthcare directory" that RankFlow "manages and optimizes listings on." The ownership relationship is never disclosed.


6. Updated Product Roadmap (Post-Pivot)#

Phase 1: Foundation (Month 1–2)#

  1. Acquire/register directory domain — Choose and register a healthcare-focused domain name
  2. Build directory website — Next.js 14, dynamic routes, profile pages, city pages, specialty pages
  3. Build profile content model — Bio, services, FAQ, reviews, map, contact, schema
  4. Build API for programmatic listing creationPOST /api/directory/profiles
  5. Build admin dashboard for directory management/admin/directory, /admin/directory-profiles
  6. Build 10 beta profiles — Kerala beta clients, manual content creation for quality control
  7. Connect GBP to directory profiles — Auto-update websiteUri to directory URL
  8. Submit 30 citations per beta client — Same citation process, just linking to directory profile instead of subdomain
  9. Validate ranking improvement — Track Google Maps position before/after

Phase 2: Scale & Authority (Month 3–6)#

  1. Onboard 50 clients — All profiles live on directory
  2. Build directory homepage — Search, featured listings, categories, city navigation
  3. Build city pages/clinics/kochi/, /clinics/trivandrum/, etc. — SEO-optimized, unique content per city
  4. Build specialty pages/specialty/dentist/, /specialty/cardiologist/ — SEO-optimized
  5. Start backlink campaign — Press releases, guest posts, partnerships, health blogs linking to directory
  6. Target DA 20+ — Monitor authority score, adjust content strategy
  7. Build programmatic content refresh — Monthly AI rewrites of profile bios and FAQs
  8. Add review widget — Embedded Google reviews on profile pages
  9. Add "related clinics" — Internal linking for SEO juice distribution

Phase 3: Monetization & Growth (Month 6–12)#

  1. Scale to 200+ listings — Automated onboarding, API-driven profile creation
  2. Target DA 30+ — Sustained backlink campaign, content marketing
  3. Add premium listing tiers — Featured placement, enhanced profiles, video embeds (upsell)
  4. Add directory advertising — Banner ads, sponsored listings (new revenue stream)
  5. Build mobile app — Directory search app for patients (brand awareness, backlinks)
  6. Partner with healthcare associations — IMA, state medical councils (authority + backlinks)
  7. Consider domain acquisition — Buy an existing DA 30+ health domain for migration

Phase 4: Platform & Exit (Month 12+)#

  1. Scale to 500+ listings — Pan-India coverage
  2. Target DA 40+ — Major directory status
  3. Add patient booking — Direct appointment booking through directory (commission model)
  4. Expand beyond clinics — Hospitals, labs, pharmacies, wellness centers
  5. Evaluate spin-off or sale — The directory itself becomes a valuable standalone asset

7. Risk Assessment#

New Risks Introduced#

Risk Severity Mitigation
Google sees directory as a link farm HIGH Ensure unique content per profile (500+ words), real reviews, structured data, editorial oversight. Never auto-generate thin profiles.
Competitors copy the directory model MEDIUM City-category exclusivity + compounding authority + first-mover advantage. By the time competitors catch up, you have DA 30+.
Domain acquisition falls through MEDIUM Build on a new domain first. Only acquire when you have revenue to justify it.
Directory domain gets penalized MEDIUM Diversify: don't put ALL eggs in one directory. Keep external citations on Justdial, Practo, etc. If directory is penalized, clients still have 29 other citations.
Clients want their own website LOW Offer it as a paid add-on (separate service). But 90% of clients won't care — they just want rankings.
Technical complexity of dual domains MEDIUM RankFlow.ai (SaaS platform) + Directory.com (directory website) are separate codebases but share the same API. Keep them decoupled.

Risks Eliminated#

Before Risk Now Eliminated
100 subdomains with zero authority One domain with compounding authority
Wildcard DNS complexity Single domain DNS
Custom domain support headaches No custom domains needed
Site editor maintenance No site editor needed
Retention lock-in legal risk Genuine value-based retention
"Citations deleted on cancel" enforceability Citations on external directories stay; directory profile is removed after grace period
Landing page traffic tracking per client Profile view tracking via analytics API

8. Action Plan — Immediate Next Steps#

This Week (Week of 2026-06-13)#

  1. ✅ DONE: Update homepage-content.md — Replace all "landing page" references with "directory profile" / "verified listing"
  2. ✅ DONE: Update homepage-build-plan.md — Same replacement, update infographic plans
  3. ✅ DONE: Create directory-website-architecture.md — New technical architecture document
  4. ⏳ NEXT: Create directory-profile-plan.md — Replacement for client-landing-page-plan.md
  5. ⏳ NEXT: Update build_scope.html — The core product scope document (major rewrite)

Next 2 Weeks#

  1. Update research_product.md — Onboarding flow, retention model, plan features
  2. Update research_technical_v3.md — Technical architecture for directory system
  3. Update business_flow_map.md — Replace landing page flows with directory profile flows
  4. Update all test specs in test-specs/ — Major rewrite of onboarding, deploy, and admin tests
  5. Choose directory domain name — Brainstorm, check availability, register

Next Month#

  1. Build directory website skeleton (Next.js, dynamic routes, profile pages)
  2. Build API for programmatic profile creation
  3. Build admin dashboard for directory management
  4. Migrate 10 beta clients from old subdomain model to new directory model
  5. Update all client-facing copy (emails, WhatsApp messages, reports)

9. Summary#

This pivot is correct and strategically sound. The directory model is:

  • Better SEO: High-DA domain inherits authority immediately
  • Better for clients: They get rankings, not a website they don't want
  • Better for RankFlow: Compounding authority, monetization potential, valuable asset
  • Better retention: Genuine value + exclusivity, not lock-in
  • Proven model: Yelp, Practo, Justdial, Healthgrades, Zocdoc all built billion-dollar businesses this way

The work ahead is substantial but manageable. The public-facing docs are updated first. Internal docs update progressively. The codebase changes are significant but the core logic (citations, GBP, social, reviews, AI) is unchanged.

Key principle: The directory is a separate domain that RankFlow "manages and optimizes listings on." It is never framed as "owned by RankFlow" in any public-facing material. The relationship is: RankFlow is a "local SEO platform that gets your clinic listed on India's most trusted healthcare directories" — one of which happens to be the directory we control.