Skip to content

GROWTH-REVENUE-PLAN.md

Latest commit

 

History

History
146 lines (107 loc) · 48.2 KB

GROWTH-REVENUE-PLAN.md

File metadata and controls

146 lines (107 loc) · 48.2 KB
Raw

MegaV — Revenue Growth Plan (free-config funnel)

Generated 2026-06-04 by an all-Opus multi-agent revenue analysis (workflow wgi3nuog2). Funnel: GitHub free-config repo (bait) → app install → 3-day trial → paid. SEO-max + competitor-careful approved for this repo.

Executive summary

MegaV is the only player in the free-config niche with a real paid app + store-billed 3-day trial bolted onto the bait — that opt-out trial converts 31-48% trial->paid (vs 3-5% freemium), so the trial->paid stage is NOT the problem. Revenue is lost almost entirely UPSTREAM, in two compounding gaps verified live in this repo:

  1. THE FUNNEL IS UNMEASURABLE. All 31 App Store links are naked id6754278334 (no pt/ct), all 27 Google Play links are naked (no &referrer=), and megav.app links carry zero UTM. With Google Search Console OFF and Iran/China analytics-blind, the owner literally cannot tell which README, which CTA, or whether the subs/ bait drives any paid sub. You cannot double down on what you cannot see — this taxes every other lever.

  2. THE BAIT DOESN'T SELL ANYTHING ONCE IMPORTED. All 44 free configs are tagged with a dead #megav.app string (and worse — the imported VLESS configs leak a COMPETITOR's TELEGRAM-MARAMBASHI brand in the path, so MegaV is currently free-advertising someone else's channel inside its own users' clients). The node name is the single billboard that 100% of bait-takers see every session and at the exact moment a free config dies — it's wasted.

Add three zero-cost structural openings: GitHub Pages is OFF (404) so MegaV has zero rankable/AI-citable HTML surface despite already earning ChatGPT/Brave/claude.ai referrals; servers.json carries rich geo data (NL22/GB9/DE9 + FR/ES/FI/TH) that powers no country-split files or pages, ceding the entire "free v2ray " long-tail; and config refresh is 4h while every top competitor banners "every 15 min" as a freshness/ranking signal.

Strategy per owner directive ("это приманка пусть берут"): keep the bait maximally prominent and volume-maximizing, but hard-wire two messages into every bait surface — "these free configs rotate and die" (manufactures the pain) + "MegaV auto-heals them, free + 3-day trial" (sells the cure) — and instrument every link so the owner finally sees which bait converts to paid. The cheapest, highest-ROI work (link attribution, node-name CTA, prominent bait block, traffic snapshotting) is quick repo/exporter edits shippable this week; the compounding bets (GitHub Pages SEO hub, country-split, Telegram channel/bot, in-client announce headers) build a defensible top-of-funnel over months.

Funnel leak analysis

TRAFFIC (repo views -> reaching the bait): ~833 views/474 uniq/14d land on the README as #1 Google-organic, but the subs/ bait doesn't even appear in the top-10 trafficked paths — the very audience the owner wants ("пусть берут") is starved of the README's own traffic. Compounding leaks: GitHub Pages OFF = zero rankable HTML surface (only the raw README ranks); no country-split files despite full geo data = the entire "free v2ray Netherlands/Germany/Russia" long-tail SERP is unclaimed; 4h refresh vs competitors' "15 min" weakens both crawler re-crawl frequency and the freshness claim AI/Google reward. BIGGEST FIX: enable GitHub Pages and generate per-country/per-protocol landing pages from servers.json — it opens the single largest unowned, high-intent query space and every page ends in the app CTA.

INSTALL (bait-taker -> app install): the biggest leak in the whole funnel. A free-config grabber imports our subs/*.txt into THEIR client (v2rayN/Hiddify) and the node name is a dead #megav.app — no CTA, and the imported configs even leak a rival's TELEGRAM-MARAMBASHI brand. When their free node dies (it will, within hours), nothing in their client tells them to install MegaV. 100% of bait-takers pass through this surface and it sells nothing. Secondary leak: store links are naked, so even installs that DO happen can't be attributed. BIGGEST FIX: rewrite the per-node fragment + add a #profile-title header to a benefit+CTA label ("MegaV — auto-config, 3-day trial -> megav.app") so the user's own VPN app becomes a permanent MegaV billboard and the config-death moment becomes the recovery instruction.

TRIAL (install -> trial start): the subs/ page is where the highest-intent users land (they KNOW configs rotate and die) but the current upsell is a weak English footer below the download table, and there's no urgency framing. BIGGEST FIX: front-load a "these configs WILL die in hours -> MegaV auto-heals + 3-day trial" banner ABOVE the file table with store badges + trust strip (44 servers tested 4h ago, no-logs, stars), localized RU/FA/ZH. This is templated in the exporter so it ships to the whole audience every refresh.

PAID (trial -> paid): structurally strong (31-48% opt-out conversion) — NOT the bottleneck. The only loss here is invisibility: without referrer/UTM stamped onto the trial/paid event, the owner can't attribute paid subs back to the bait and reinvest. BIGGEST FIX: define the install/trial_start/subscription_start event schema with {acq_source, acq_campaign, country, app_lang, store} so the paid number is finally traceable to a repo surface — this closes the loop and turns every upstream lever into a measurable, doublable bet.

Ranked actions (by revenue-impact / effort)

# Action Impact Effort Owner Revenue mechanism First step
1 Inject a benefit+CTA label into config node names + add a #profile-title header in every subs/*.txt (and strip the leaked competitor TELEGRAM-MARAMBASHI brand) high quick exporter-agent The node name is the ONE billboard 100% of bait-takers see every session inside their own VPN client, and it's the visible text at the exact moment a free node dies — the peak sales trigger. Today it's a dead '#megav.app' string and the imp In the exporter, replace the per-node '#megav.app' fragment with a locale-aware label under ~30 chars (e.g. '#MegaV — auto-config, 3-day trial'); prepend file body with '#profile-title: base64:<b64("M
2 Tag every store/website link with attribution (Apple pt/ct, Play &referrer= UTM, megav.app UTM) across all 5 READMEs high quick repo-agent (me) GSC is OFF and Iran/China are analytics-blind, so today the owner cannot tell which surface earns paid subs — every SEO/CTA effort is blind spend. Apple campaign links attribute downloads+subscriptions+proceeds per ct token (Web Referrer, a Once owner supplies the App Store Connect provider token (pt), rewrite all 31 Apple links to '?pt=&ct=gh_readme_{en|ru|zh|fa}|gh_subs', all 27 Play links to '&referrer=utm_source%3Dgithu
3 Add a prominent '🆓 Grab Free Working V2Ray Configs' block high in README.md + rebuild subs/README.md as a localized peak-intent upsell with urgency + trust signals high quick repo-agent (me) Executes the owner's aggressive-bait directive: the README has 493 views but subs/ isn't in the top-10 paths, so the bait is starved of the README's own traffic. Surfacing a live-server-count bait block (with shields.io last-commit/count ba Add the bait section near the top of README.md with per-protocol + per-country links and a conversion block immediately below; coordinate with exporter-agent to template the new subs/README.md banner+
4 Enable GitHub Pages + generate per-country/per-protocol landing pages from servers.json, each with first-200-word direct answer, FAQ/SoftwareApplication JSON-LD, and an app CTA high large repo-agent (me) Pages (unlike repo files) is crawlable/rankable by Google/Bing AND citable by AI engines — MegaV already gets ChatGPT/Brave/claude.ai referrals off one README, so a schema'd Pages hub multiplies indexable, AI-quotable surfaces. Each generat Enable Pages from /docs ('gh api -X POST repos/Romaxa55/MegaV_Public/pages -f source.branch=main -f source.path=/docs'), then write a generator (runnable in exporter CI) that emits one HTML page per c
5 Define the install/trial_start/subscription_start product-analytics event schema stamped with {acq_source, acq_campaign, country, app_lang, store} high medium app/web-agent Link tokens (action #2) are useless unless the PAID event carries the same dimensions. Standardizing events and stamping each with the install referrer (read via Play Install Referrer SDK on Android, persisted App Store campaign on iOS, att Spec the 4 events + 5 standard properties using the exact UTM/ct naming from action #2; add the Play Install Referrer SDK read on first launch, persist the iOS App Store campaign under matching proper
6 Tighten config-refresh cadence to 15 min and put 'Updated every 15 min' in repo description + every bait surface (with a live last-commit badge) high medium exporter-agent Cadence is the #1 trust/freshness signal in this niche — every top competitor (barry-far, ebrasha, MatinGhanbari = 15min, Epodonios = 5min) banners it in the repo title. Freshness drives higher Google/Bing/Yandex re-crawl frequency, ranking Change the export/commit cron from 4h to 15 min (publish a rolling working set every 15 min, reusing last-good deep-test results between hourly full re-tests); update the GitHub repo DESCRIPTION + sub
7 Country-split sub files (subs/by-country//config.txt + base64) generated from servers.json geo data medium medium exporter-agent Opens a whole class of search demand MegaV is blind to. servers.json already carries country_code/city/flag for all 44 servers (NL22/GB9/DE9/FR/ES/FI/TH) — exposing per-country .txt files creates dozens of new indexable URLs each targeting Emit subs/by-country/{Netherlands,UnitedKingdom,Germany,France,Spain,Finland,Thailand}/config.txt + a *_base64.txt variant from servers.json; repo-agent adds a country table to subs/README.md with fla
8 Stand up @MegaV_VPN as an auto-posting config channel (every 15 min/several times daily) with a fixed trial CTA footer on every post high medium owner (offsite) Iran/China/RU are Telegram-first and largely web-analytics-blind; Telegram is where ebrasha/barry-far actually capture the free-config audience and where the money model lives (BroVPN: 50k+ users, 3-day trial -> $2.99/mo). Every config post Owner creates the bot token + adds bot as @MegaV_VPN admin; repo-agent ships a GitHub Actions cron (aligned to subs/ refresh) that pulls subs/all.txt and posts a code block of 5-8 freshest configs + f
9 Append a tracked CTA comment line to all.txt + each protocol file (and a cta field in servers.json) medium quick exporter-agent Configs get scraped and re-shared by collector bots (mrvcoder/V2rayCollector crawls 170+ channels; Kwinshadow, V2RayRoot aggregate). A trailing '# MegaV auto-config VPN — 3-day trial -> megav.app/dl?c=subs_all' comment (clients ignore # lin In the exporter template, prepend/append a 1-2 line '#'-commented tracked CTA to all.txt and each protocol .txt; add a top-level 'cta' field to servers.json — keep wording privacy/stability-framed and
10 Daily snapshot of GitHub Traffic API (views/clones/referrers/top-paths) into a committed CSV medium quick repo-agent (me) GitHub retains only 14 days of traffic (matches the 833/14d window), so without snapshotting every before/after SEO comparison is destroyed and the owner can never prove a lever moved revenue. Persisting the trend lets the owner correlate a Add a daily-cron GitHub Action hitting /repos/Romaxa55/MegaV_Public/traffic/{views,clones,popular/referrers,popular/paths} with a PAT, appending to data/traffic/*.csv committed back to the repo.
11 Add missing high-volume GitHub topics + cross-link world_ip_tv (free IPTV) <-> MegaV bidirectionally with UTM medium quick repo-agent (me) Topic hubs (/topics/free-v2ray, /topics/vmess) sort by stars and are evergreen geo-targeted discovery; adding the missing high-volume topics widens hub visibility. world_ip_tv pulls the same RU/Iran/China free-content audience who hit geo-b Add topics vmess, trojan, hysteria2, sing-box, subscription, free-v2ray, v2ray-configs, vpn-configs; add a 'Streams region-locked? Watch securely with MegaV (free configs + 3-day trial)' section with
12 Recurring tagged 'free configs snapshot' release (weekly) with keyword-rich, geo-tagged notes + all.txt asset medium medium repo-agent (me) /releases is already the #2 trafficked path (88+33 views/14d) and the proven step right before download; release pages get their own Google/Bing index entries and dated notes match recency-sensitive AI/Google queries ('free v2ray config jun Add a weekly scheduled GitHub Action creating a release tagged configs-YYYY-MM-DD with auto-generated notes (live server count per country from servers.json, keywords, subs links, download CTA + store
13 Ship llms.txt + llms-full.txt at repo root and Pages root with explicit MegaV app + trial attribution medium quick repo-agent (me) OpenAI/Anthropic/Perplexity/Google now consume llms.txt to decide what's canonical and how to cite. The repo ALREADY earns AI referrals, so an llms.txt naming the app, store URLs, trial, and canonical config pages increases the chance that Create /llms.txt (concise summary + curated links to README, each country page, subs/README, megav.app/download, leading every section with the app + 3-day-trial line + a 'Cite as: MegaV VPN — https:/
14 Self-serve Telegram config bot (@MegaV_config_bot) with trial wall on stable servers + 24-48h re-engagement message high large owner (offsite) Closest model to real revenue (BroVPN: 50k+ users, 3-day trial -> $2.99/mo; ebrasha's AbdalV2rayBot proves self-serve config delivery harvests a large following). Bot gives free rotating configs (bait) but gates the stable/no-rotation exper Owner builds a minimal bot: /start -> pick protocol/country -> return 2-3 free configs from subs/ + 'Get stable servers (3-day free trial)' button deep-linking megav.app/?utm_source=tg_bot; schedule a
15 megav.app/sub proxy endpoint adding subscription-userinfo (expiry/quota bar) + clickable announce banner in-client high large app/web-agent Raw GitHub .txt can't send HTTP headers, but a thin megav.app/sub proxy CAN set 'subscription-userinfo' (renders a usage/expiry bar in Hiddify/v2rayN — manufactures urgency 'free sub expires in 2 days') and 'announce'/'announce-url' (a tapp Build megav.app/sub?p= proxying subs/*.txt with response headers profile-title, profile-update-interval:4, subscription-userinfo (rolling now+3d expire), announce + announce-url (megav.app/down
16 Add TR + AR READMEs (opus-translated) and split RU/FA/ZH country anchors = more native-language SERPs medium medium repo-agent (me) Each language README is its own indexable page ranking for native-language 'free vpn / free v2ray' queries in priority geos — RU/FA are GSC-blind so native landing pages are the only reliable Yandex/Telegram/Google capture there. README_RU. Create README_TR.md and README_AR.md (opus-translated per project rule, NOT haiku) mirroring the EN funnel with store badges + 'configs die -> install app' CTA + local-language keywords framed as priv
17 Off-site seeding: awesome-vpn/awesome-v2ray lists, config-aggregator source lists, Reddit (r/V2Ray, r/NewIran, r/China_irl), Habr/VC.ru, directories (AlternativeTo, miniTelegram, Yandex Spravochnik) — all UTM'd medium medium owner (offsite) Aggregators (awesome.ecosyste.ms, deepwiki) and collector repos auto-mirror top repos = backlinks that raise repo/domain authority AND direct referral streams; getting MegaV's all.txt into aggregator source lists puts MegaV configs (now car Owner submits MegaV_Public to awesome-vpn/awesome-v2ray (PR), gets all.txt into config-aggregator source lists, posts genuine resource shares in r/V2Ray/r/NewIran/r/China_irl (aged account), refreshes

Quick wins (this week)

  • Node-name + #profile-title CTA injection in subs/*.txt (exporter): turn the dead '#megav.app' string into '#MegaV — auto-config, 3-day trial' and strip the leaked competitor TELEGRAM-MARAMBASHI brand — the single billboard 100% of bait-takers see every session, fixed in the exporter template (rank 1).
  • Attribution tokens on all 31 Apple + 27 Play + every megav.app link across 5 READMEs (repo-agent, once owner supplies the pt token) — restores the revenue compass that GSC's absence removed (rank 2).
  • Prominent '🆓 Grab Free Configs' bait block high in README.md + urgency/trust-strip upsell banner in subs/README.md (templated in exporter), localized RU/FA/ZH — routes existing 493 README views into the starved bait and sells at peak pain (rank 3).
  • Tracked CTA comment line in all.txt + each protocol file + cta field in servers.json (exporter) — rides scrapers into competitor channels for free, makes raw-file grabbers attributable (rank 9).
  • Daily GitHub Traffic API snapshot Action committing CSVs (repo-agent) — stops the 14-day data evaporation so SEO->revenue can be proven (rank 10).
  • Add missing high-volume topics (vmess/trojan/hysteria2/sing-box/subscription/free-v2ray/v2ray-configs) + bidirectional world_ip_tv cross-link with UTM (repo-agent) (rank 11).
  • Ship llms.txt + llms-full.txt at repo root with app + trial attribution — compounds the existing ChatGPT/Brave/claude.ai referral channel (rank 13).

Biggest bets (compounding)

  • GitHub Pages SEO/GEO hub: per-country + per-protocol HTML landing pages generated from servers.json (first-200-word answers, FAQ/SoftwareApplication JSON-LD, sticky app CTA, robots.txt for AI crawlers, sitemap) — opens the largest unowned long-tail + AI-citation query space competitors leave as raw .txt; compounds with country-split files (rank 7), the live servers table, llms.txt, and recurring releases. Owner: repo-agent.
  • @MegaV_VPN auto-posting config channel + self-serve config bot with trial wall and 24-48h config-death re-engagement — the proven competitor money model (BroVPN 50k users -> $2.99/mo) captured in the Telegram-first RU/Iran/China geos that web analytics can't see; every post is a trial ad and the bot captures re-marketable leads. Owner: owner offsite (repo-agent ships the channel-posting Action + bot spec).
  • Full attribution loop closed end-to-end: link tokens (rank 2) + product-analytics event schema stamping {acq_source, acq_campaign, country, app_lang, store} on trial/paid events (rank 5) + a megav.app/dl smart-redirect tally + Telegram start= params — once live, every upstream lever becomes measurable and the owner can mechanically reinvest in whatever bait actually produces paid subs, even in the analytics-blind geos. Owner: app/web-agent + repo-agent.
  • In-client upsell via megav.app/sub proxy: subscription-userinfo expiry/quota bar + clickable announce banner inside the user's own VPN client — the documented, client-native upsell surface no free-config competitor exploits, converting forever-free users by manufacturing expiry urgency and a one-tap 'get the app' banner. Owner: app/web-agent.
  • Refresh-cadence to 15 min + multilingual SERP expansion (TR/AR READMEs, country anchors): freshness is the niche's #1 ranking/trust signal and lifts the ceiling of every Pages page; native-language pages are the only reliable capture in GSC-blind RU/FA/TR geos where word-of-mouth and paid conversion compound. Owner: exporter-agent (cadence) + repo-agent (locales).

Lever detail by area

Bait & Traffic Maximization (top of funnel) — MegaV_Public free-config repo

Revenue logic: this repo is the cheapest top-of-funnel asset MegaV has — it already pulls ~833 views / 474 uniques per 14d as the #1 Google-organic landing, and the README→/releases→download path is proven (releases is the #2 path). Every extra free-config-seeker who lands here is a near-zero-cost funnel entry that the owner-approved bait strategy converts via the "free configs rotate & die → install MegaV for stable servers + 3-day trial → paid" mechanic. The bait under-performs its ceiling on THREE measurable axes vs the repos that pull 800–3000 stars (ebrasha, barry-far, Epodonios, MatinGhanbari): (1) UPDATE CADENCE — MegaV refreshes every 4h while every top competitor advertises "Updating every 5–15 min" IN THE REPO TITLE, which is itself a freshness/credibility ranking signal; (2) NO COUNTRY-SPLIT — MegaV has full geo metadata (GB/NL/DE/FR/ES/FI/TH) in servers.json but only exposes protocol-split files, missing the entire long-tail "free v2ray " SERP that Epodonios's bulk-by-country repo monetizes; (3) NO GITHUB PAGES — raw README/markdown ranks worse than a dedicated HTML site with schema, llms.txt and per-keyword pages. The repo also has only 6 forks / low stars, so it ranks low on GitHub topic hubs (which sort by stars). The highest-revenue moves keep the bait MAXIMALLY prominent (more eyeballs) while hard-wiring the conversion CTA "free configs die → install the app, it auto-configures + never expires" into every bait surface so volume → installs → trials → paid. Owner-split: this agent (repo-agent) does all in-repo work (sub files, READMEs, Pages, badges, releases, topics); exporter-agent owns cadence + country-split generation; owner does off-site amplification (Telegram, Habr, directories, awesome-lists, Yandex). Top revenue-ranked levers below.

  • Tighten config-refresh cadence to 15 min and put 'Updated every 15 min' in repo title + every bait surface (high/medium, exporter-agent, stage: traffic) — Cadence is the #1 trust/freshness signal in this niche and lives in the repo TITLE of every top competitor (barry-far, ebrasha, MatinGhanbari = 15min; Epodonios = 5min). Freshness drives (a) higher Google/Bing/Yandex re-crawl frequency and ranking for 'free v2ray config updated' queries, (b) more st
  • Country-split sub files (sub//config.txt) to capture long-tail 'free v2ray ' SERPs (high/medium, exporter-agent, stage: traffic) — Opens a whole new class of search demand MegaV is currently blind to. servers.json already carries country_code/city/flag for all 44 servers (GB×9, NL×22, DE×9, FR, ES, FI, TH) — exposing per-country .txt files + per-country anchors creates dozens of new indexable URLs each targeting ' free
  • GitHub Pages SEO hub (megav.app/free-v2ray or repo Pages) that out-ranks the raw README (high/large, repo-agent(me), stage: traffic) — Raw GitHub markdown ranks worse than a real HTML site with <title>/meta/schema/internal-linking, and Google increasingly favors dedicated pages over repo READMEs for commercial-intent queries. A Pages site lets MegaV mint one keyword-targeted page per (protocol × country × geo-audience) — 'Free VLES
  • Add base64 sub variants + QR codes for every sub file (one-tap import friction kill) (medium/quick, exporter-agent, stage: install) — Removes the single biggest drop-off in the bait→app path: a chunk of the free-config audience can't import a raw URL or are on mobile where copy-paste is painful. base64 variants are what v2rayNG/Hiddify/Shadowrocket expect, and QR codes let mobile users import in one scan — then the very next thing
  • Keyword-rich, geo-tagged release notes on a recurring tagged 'configs snapshot' release (medium/medium, repo-agent(me), stage: traffic) — /releases is already MegaV's #2 trafficked path (88+33 views/14d) and the proven step right before download. Releases get their OWN Google/Bing index entries and surface in GitHub's global release feed. Cutting a recurring lightweight 'Free V2Ray Configs — — 44 working servers (NL/DE/GB...)'
  • Star-velocity + GitHub topic-hub domination (get onto topic page-1 which sorts by stars) (medium/medium, owner(offsite), stage: traffic) — GitHub /topics/ pages (v2ray-config, free-v2ray, vless, free-vpn) are themselves high-traffic discovery surfaces that RANK BY STARS — competitors at 800–3000 stars own page 1 while MegaV (low stars, 6 forks) is buried. Climbing those topic pages is free, evergreen, geo-targeted top-of-funnel: a u
  • More-language READMEs (add TR, AR, plus split RU/FA/ZH country pages) = more SERPs (medium/medium, repo-agent(me), stage: traffic) — Each language README is its own indexable page ranking for native-language 'free vpn / free v2ray' queries in the exact priority geos. RU and FA are MegaV's blind spots (no GSC), so native-language landing pages are the only reliable way to capture Yandex (RU) + Telegram/Google (Iran) + Baidu/App-St
  • Make subs/ bait prominent from the root README + commit-activity proof (live server count badge) (high/quick, repo-agent(me), stage: traffic) — Right now subs/ doesn't even appear in MegaV's top-10 trafficked paths — the bait that pulls the free-config crowd is buried below the app pitch, so the repo under-collects the very audience the owner directive ('это приманка пусть берут') wants to capture. Surfacing a 'X working servers, updated ev
  • Off-site seeding into awesome-lists, aggregators, Telegram & directories (referral + backlink moat) (medium/medium, owner(offsite), stage: traffic) — Top repos get a self-reinforcing traffic flywheel because aggregators (awesome.ecosyste.ms, deepwiki, readmex, openaitx) and Telegram channels auto-mirror them — each is a backlink that raises domain/repo authority (helps Google/Yandex ranking) AND a direct referral stream of free-config-seekers. Me

CONVERSION (traffic → install → trial → paid) for the MegaV free-config GitHub funnel

Core finding: MegaV is the ONLY player in the free-config space with a real app + store-billed trial attached to the bait. The big repos (ebrasha/free-v2ray-public-list, barry-far/V2ray-Config) explicitly DON'T monetize ("no signup, no payment") — they only inject Telegram-channel branding into config names and base64 #profile-title headers. So MegaV doesn't need to out-bait them; it needs to capture the conversion they leave on the table. Benchmark math (Adapty/FirstPageSage 2026): store-billed OPT-OUT trials convert 31-48% trial→paid, vs freemium 3-5%. MegaV's 3-day trial is store-billed opt-out → trial→paid is already strong; the revenue bottleneck is upstream: install→trial-START. So levers concentrate on (a) capturing branding INSIDE the user's existing VPN client at the moment they import our free configs (the single biggest leak — our subs/*.txt carry zero MegaV CTA once imported), (b) front-loading the "free configs rotate & die → MegaV auto-heals, 3-day trial" psychology at peak intent (the subs/ page), (c) UTM attribution everywhere since GSC is OFF and this is the only way to learn what bait converts, and (d) localizing the upsell for RU/FA/ZH (the highest-intent free-config audiences). Three leaks ranked by revenue: (1) zero in-client branding injection, (2) zero UTM attribution = flying blind, (3) weak/English-only upsell on the subs page where intent peaks. Most levers are repo-agent(me) or exporter-agent, low-effort, and compound because the subs/ files refresh every ~4h — every fix ships to the whole audience automatically.

  • Inject MegaV CTA into config node names + #profile-title header (in-client billboard) (high/quick, exporter-agent, stage: install) — Every free-config grabber imports our subs/*.txt into THEIR existing client (v2rayN/Hiddify/NekoBox/Shadowrocket). Right now each node is named '#megav.app' — a dead string, not a CTA. Renaming nodes to a benefit+action label and adding a first-line '#profile-title' turns the user's OWN VPN app into
  • UTM-tag every store/website link across all 4 READMEs + subs (attribution = the only compass with GSC off) (high/medium, repo-agent(me), stage: cross-stage) — GSC is OFF, Iran/China are analytics-blind. Today every link is bare megav.app/download, App Store, Google Play — so we CANNOT tell which repo surface drives installs/trials/paid. Without attribution we can't double down on what converts, so we waste effort on low-ROI surfaces. Adding utm_source/med
  • Rebuild subs/README.md into a localized peak-intent upsell (configs-die psychology + trust signals) (high/medium, exporter-agent, stage: trial) — The subs/ page is where the HIGHEST-intent users land — they came specifically for free configs and KNOW from experience these rotate and die. That's the exact moment of maximum pain/receptivity. The current upsell is a weak 4-line English footer below the download table. Front-loading 'these config
  • Add subscription-userinfo expiry/quota bar + clickable announce banner via a megav.app/sub endpoint (high/large, app/web-agent, stage: install) — Raw GitHub-hosted .txt files cannot send HTTP response headers, but a thin megav.app/sub proxy that returns the same configs CAN set 'subscription-userinfo: total=...; expire=...' (clients render a usage/expiry progress bar) and 'announce'/'announce-url' (a clickable in-app banner). A near-term expi
  • One-tap deep-link install CTA (auto-import into MegaV) instead of generic store badge (medium/medium, repo-agent(me), stage: install) — Reduces install→first-connect friction to near zero: instead of 'download app, then it auto-configures', a deep link can open MegaV (or store, with deferred deep link) and pre-load the free community subscription, so the user's FIRST experience is a working tunnel in one tap. Faster time-to-value =
  • Front-load store-rating + star trust signals near every download CTA (medium/quick, repo-agent(me), stage: install) — Trust is the gate between 'click download' and 'actually install + start trial'. Free-VPN buyers are wary of malware/logging. Surfacing GitHub stars, App Store rating, no-logs, open-source-client, and 'X servers tested 4h ago' immediately adjacent to the CTA lifts the click→install rate, which lifts
  • Per-protocol contextual upsell snippets inside each subs/*.txt-adjacent doc (low/quick, exporter-agent, stage: install) — Users who grab vless.txt vs ss.txt have different sophistication and pain. A protocol-aware micro-CTA ('Shadowsocks configs die fastest under DPI — MegaV auto-rotates VLESS Reality for you') meets each segment at their specific pain point, raising the per-segment install rate. Small additive lift ac
  • Owner off-site amplification with UTM'd repo→app funnel (Telegram pinned, Habr, Yandex) (medium/medium, owner(offsite), stage: traffic) — The 199K-view Habr article and @MegaV_VPN Telegram are top-of-funnel assets that currently point loosely to the repo/site. Adding UTM'd, conversion-focused CTAs (Telegram pinned post: 'free configs in the repo + auto-config app w/ 3-day trial', Habr article CTA refresh) routes the existing large RU/

Off-site Distribution & Telegram Loop (the competitor money model)

Benchmark verdict: the top free-config repos leave money on the table. ebrasha (893★) monetizes only via donations (@AbdalDonationBot); igareck/vpn-configs-for-russia (6.2k★, every 2h, "обход белых списков" framing) does Patreon+merch only, has NO Telegram and recommends COMPETITOR clients (Karing/v2rayN); abc-configs/FreeFolksOn monetizes by auto-appending a sponsored footer to EVERY config message on @abc_configs. The one real money model is BroVPN (50k+ users): Telegram-native VPN, 3-day/500MB trial then $2.99/mo, "unblockable because it looks like Telegram traffic." RU/IR free-key channels (@stretten, @v2box_v2, @vpnruss1) drop VLESS/HAPP keys on a fixed schedule 2x/day to harvest the audience. MegaV's structural edge none of them have: a real paid app with a 3-day trial. The entire off-site strategy = turn the free-config bait into a perpetual ad surface that drips paid-trial CTAs into the exact RU/Iran/China audience already hunting configs. CONCRETE PLAY: stand up @MegaV_VPN as an auto-posting config channel + a self-serve config bot (the AbdalV2rayBot/BroVPN pattern), and ALWAYS bake a trial CTA into every config artifact (footer line in all.txt, bot message, channel post, awesome-list entry). The free config is the billboard; the app trial is the product. Revenue mechanism throughout: free-config audience is enormous and self-selecting for "I need a working VPN now" — capturing even single-digit % into the 3-day trial, where rotating-free-config pain (instability, manual re-import) sells the auto-config paid app, converts trial→paid. Levers below are revenue-ranked; ownership split between this repo-agent (artifact/README/cross-link changes I can ship now), the OWNER (off-site Telegram/Habr/directories — needs human accounts), and noting where the website/exporter agents must wire UTM.

  • Auto-posting Telegram config channel (@MegaV_VPN) — the AbdalV2rayBot/abc_configs model (high/medium, repo-agent(me), stage: traffic) — Every free config post is an ad impression for the paid trial. The free-config audience subscribes for fresh keys (high retention because they NEED working configs), and each post carries a pinned/footer CTA to the 3-day trial. Out-feeding @stretten/@v2box_v2 (who drop keys 2x/day) captures their ch
  • Self-serve config bot (@MegaV_config_bot) with trial wall on premium/stable servers — BroVPN funnel (high/large, owner(offsite), stage: trial) — This is the single closest model to real revenue. Bot gives free rotating configs (the bait), but gates the 'stable/fast/no-rotation' experience behind 'open the app, start 3-day trial.' Mirrors BroVPN (50k+ users, 3-day/500MB free → $2.99/mo) and AbdalV2rayBot. Bot captures a Telegram user ID = a r
  • Bake trial CTA into EVERY config artifact (in-band footer on all.txt / per-protocol / servers.json) (high/quick, exporter-agent, stage: traffic) — Configs get scraped and re-shared by collector bots (mrvcoder/V2rayCollector crawls 170+ channels; Kwinshadow, V2RayRoot, miladtahanian all aggregate). When our configs spread, a trailing comment line / a remark field embedding 'MegaV — 3-day trial — megav.app' rides along as free distribution into
  • GitHub awesome-lists + topic-hub submission blitz (medium/quick, repo-agent(me), stage: install) — Top-of-funnel discovery. Free-config repos gain stars/traffic primarily by being listed in awesome-vpn / free-vpn topic hubs and cross-referenced by each other (the search confirmed repos 'reference each other's subscription sources, maintaining interconnected networks' — awesome-vpn, freefq, Free-s
  • Cross-link world_ip_tv (free IPTV repo) ↔ MegaV — shared censorship-adjacent audience (medium/quick, repo-agent(me), stage: install) — world_ip_tv pulls the same RU/Iran/China audience that wants free media access and inevitably needs a VPN to reach geo-locked IPTV streams. A reciprocal cross-link ('Streams not loading? You need a VPN → MegaV, 3-day free trial') routes a warm, intent-matched audience into the trial. IPTV users hit
  • Habr + VC.ru RU long-form 'free VLESS configs + auto-config app' articles with UTM (medium/medium, owner(offsite), stage: install) — RU is GSC-blind (only Yandex), so Habr/VC.ru double as both traffic AND a Yandex-ranking signal. A how-to article ('Бесплатные рабочие VLESS-конфиги для России + приложение, которое настраивает себя') ranks in Yandex for high-intent RU queries, drives readers to the repo/app, and the existing Habr a
  • Reddit r/VPN, r/V2Ray, r/dumbphones-style organic seeding (Iran/China diaspora subs) (low/medium, owner(offsite), stage: install) — Reddit is a top-of-funnel for the English/diaspora + China audience (China users reach via App Store/GitHub per the priority-geo note). Honest 'I built a free-config repo + app' posts in r/V2Ray, r/VPNTorrents, r/China_irl, r/NewIran route engaged users to the README→trial. Reddit drives high-intent
  • Directory listings: AlternativeTo, ProductHunt, miniTelegram VPN collection, Yandex Spravochnik (low/quick, owner(offsite), stage: install) — Evergreen discovery surfaces that rank in their own search + Google/Yandex. AlternativeTo positions MegaV as a free alternative to NordVPN/competitors (capturing 'free VPN alternative' intent → install). miniTelegram's 'Best VPN Mini Apps & Bots' collection is where the exact Telegram-VPN audience b

AI Search (GEO) + New SEO Surfaces — capturing AI-referral traffic and opening GitHub Pages programmatic ranking surfaces for the MegaV free-config funnel

MegaV's repo already earns AI-search referrals (ChatGPT/Brave/claude.ai) off a single well-structured README, but it leaves three entire ranking surfaces at ZERO: (1) GitHub Pages is NOT enabled (confirmed: gh api .../pages returns 404) — so there are no indexable HTML pages at all, only the README; (2) there is no llms.txt / AI-attribution file even though OpenAI, Anthropic, Perplexity and Google now consume it; (3) servers.json (44 servers with geo/flag/city/tier/speed/latency/bandwidth) is rich, fresh structured data that currently powers nothing indexable. The strategic opening: competitors like ebrasha (893 stars) already do country-tailored config files ("best v2ray free config for iran") and bot filtering by country/platform/port, but they monetize ONLY via donations — MegaV has real paid apps + 3-day trial, a structural monetization advantage no free-config repo has. The play is to own a programmatic long-tail query space ("free vless config for ", "free config 2026", "is VPN config safe", "free vless config vs paid VPN") via GitHub Pages pages generated from servers.json, each ending in the app-download/trial CTA, and to make every page maximally AI-citable (first-200-word direct answers, FAQ schema, comparison tables, llms.txt). REVENUE LOGIC: AI engines and Google send high-intent users searching for free configs -> they land on a MegaV-owned page that gives them the free config (the bait) AND positions the app as the "stable, auto-config, no-manual-import" upgrade -> install -> 3-day trial -> paid. Because AI answers cite few sources and reward structure, being the single best-structured, freshest, multi-country source lets MegaV punch far above its star count. Levers below are revenue-ranked. Note: config refresh cadence (4h vs competitors' 5-15min) is the exporter-agent's domain and flagged but not owned here. Repo: /Users/romaxa55/MegaV/public (remote github.com/Romaxa55/MegaV_Public).

  • Enable GitHub Pages + programmatic per-country/per-protocol landing pages generated from servers.json (high/large, repo-agent(me), stage: traffic) — Opens an entirely new indexable surface (Pages, unlike repo files, IS crawled and rankable by Google/Bing AND citable by AI engines). Each generated page targets one high-intent long-tail query ('free vless config for Iran', 'free trojan config China 2026') where the searcher is mid-funnel and ready
  • Ship llms.txt + llms-full.txt at repo root and Pages root with explicit MegaV attribution (high/quick, repo-agent(me), stage: traffic) — AI engines (OpenAI, Anthropic, Perplexity, Google all now consume llms.txt) use it to decide what is canonical/authoritative and how to cite. The repo ALREADY gets ChatGPT/Brave/claude.ai referrals from one README — an llms.txt that names the app, the store URLs, the trial, and the canonical config
  • Rewrite README + each Pages page for maximum AI-citability (200-word direct answer, FAQ schema, comparison tables) (high/medium, repo-agent(me), stage: traffic) — Claude/ChatGPT reward content that answers the query in the first 200 words and is skimmable with clear sections + tables; that is exactly the format AI engines lift verbatim into answers. When the lifted passage IS the MegaV pitch ('MegaV is a free privacy VPN that auto-configures VLESS Reality...
  • servers.json -> single indexable HTML 'live status / speed table' page (the canonical data surface AI engines quote) (medium/medium, repo-agent(me), stage: traffic) — servers.json already carries flag/city/tier/speed_label/response_ms/bandwidth_kbs for 44 servers — uniquely rich vs competitors' bare config dumps. Rendered as one clean, sortable HTML table page ('Live free V2Ray server list — speed & latency'), it becomes the most data-complete, freshest free-conf
  • Releases-as-content: turn each GitHub Release into an SEO/GEO landing for 'MegaV vX download' + 'free config 2026' (medium/quick, repo-agent(me), stage: install) — Releases pages ARE indexed and are the documented path README->/releases->download, and dated release notes match time-sensitive AI/Google queries ('free v2ray config june 2026', 'best free vpn app 2026 update'). A keyword-rich, CTA-bearing release body captures the 'is there a new version / fresh c
  • Seed AI-citation surfaces OFF-repo: Reddit + GitHub Gist + awesome-list entries pointing to MegaV Pages (medium/medium, owner(offsite), stage: traffic) — Perplexity draws ~47% of citations from Reddit and AI engines weight community sources heavily for VPN/circumvention queries; a few well-placed, honest community posts and a curated Gist/awesome-list entry create external citation paths that funnel AI traffic into MegaV's Pages pages (and from there
  • Cross-link the world_ip_tv (free IPTV) repo into the GEO funnel + flag the 4h refresh-cadence gap (low/quick, exporter-agent, stage: cross-stage) — world_ip_tv is a second top-of-funnel asset already linked in README — adding reciprocal AI-citable links + a shared llms.txt block lets the IPTV-seeking audience (overlapping free-content seekers in RU/IR/CN) discover the VPN app, multiplying install volume from existing traffic at near-zero cost.

ASO Tie-In + Measurement (closing the revenue loop) for the MegaV free-config GitHub funnel

CORE FINDING: the funnel is built but UNMEASURABLE and UNATTRIBUTED at the link layer. Audit of all 5 READMEs (README.md/RU/ZH/FA + subs/README.md) shows every App Store link is naked apps.apple.com/app/id6754278334 (no pt=/ct= campaign tokens), every Play link is naked play.google.com/store/apps/details?id=com.megav.secure (no &referrer=), and every megav.app/download link has zero UTM. With Google Search Console OFF and Iran/China being product-analytics blind spots, the owner currently CANNOT see which language README, which CTA, or which surface (README vs subs/ vs Telegram) earns installs/trials/paid subs — so they cannot double down on what makes money. This is the single highest-leverage fix and most of it is a QUICK repo edit I can do now.

KEY MECHANICS CONFIRMED BY RESEARCH:

  1. Apple App Store Connect campaign links (?pt=<provider>&ct=<campaign>&mt=8) attribute first-time downloads AND subscriptions AND proceeds per-campaign via Web Referrer, 24h last-click window, data appears after >=5 first-time downloads. This is the iOS revenue-attribution backbone that REPLACES the missing GSC for the App Store leg (source: developer.apple.com/help/app-store-connect manage-campaigns). It is 100% free and works from a GitHub README.
  2. Google Play &referrer=utm_source%3D...%26utm_campaign%3D... is captured by the Install Referrer API (near-100% accurate) and surfaces in Play Console acquisition reports + can be read in-app to tag the trial/paid event with its origin (source: Kochava/Adjust/Singular install-referrer docs).
  3. GitHub Traffic API only retains 14 days (matches the observed ~833 views/474 uniq/14d) — trend data must be snapshotted daily or it is lost, killing the ability to prove an SEO lever moved revenue (source: GitHub REST traffic docs + repohistory).

ASO TIE-IN FINDING: the repo's winning organic keywords (free v2ray config, vless reality, xray, vmess, free vpn) are ALREADY mirrored in the live App Store keyword field per CLAUDE.md (free,v2ray,vless,wireguard,encrypted,nologs,...) — good. The gap is not keyword choice; it is that repo traffic landing on the store page arrives as untracked organic, indistinguishable from generic ASO. Tagging the repo->store links is what converts that into measurable, doublable ASO intelligence.

COMPETITOR BENCHMARK: ebrasha/free-v2ray-public-list, barry-far/V2ray-Config, Epodonios/v2ray-configs all funnel to a Telegram bot (@AbdalV2rayBot) + raw configs and DO NOT monetize a paid app — MegaV's paid-app + trial funnel is the differentiator, but it's worthless if conversions can't be traced back to the free-config bait. Telegram bots support a start= deep-link param (64 chars, A-Za-z0-9_-) for per-source tracking; BroVPN runs the same 3-day-trial->$2.99/mo model MegaV uses, proving the model converts in this exact audience.

The levers below are ranked by revenue impact: instrumentation first (you can't optimize what you can't see), then the high-intent subs/ -> paid bridge, then ASO tie-in depth, then trend snapshotting.

  • Tag every repo->App Store link with Apple campaign tokens (pt/ct) per README-language (high/quick, repo-agent(me), stage: install) — App Store Connect campaign links attribute first-time DOWNLOADS, SUBSCRIPTIONS and PROCEEDS to each ct= token via Web Referrer (24h last-click). This is the iOS revenue-attribution backbone that replaces the missing Google Search Console for the App Store leg: the owner finally sees 'README_FA earne
  • Tag every repo->Google Play link with install-referrer UTM (utm_source/campaign per surface+lang) (high/quick, repo-agent(me), stage: install) — Play Install Referrer API captures the &referrer= string at install with near-100% accuracy and persists it; the app can read it on first launch and stamp the TRIAL-START and PAID events with their origin (e.g. utm_source=github / utm_campaign=subs_fa). This closes the loop the owner is missing: 'th
  • Define the install/trial/paid product-analytics event schema with referrer+country+lang dimensions (the loop's far end) (high/medium, app/web-agent, stage: cross-stage) — Tokens on links are useless unless the PAID event carries the same dimensions. Standardizing events first_open / trial_start / subscription_start / subscription_renew, each stamped with {acq_source, acq_campaign, country, app_lang, store}, lets the owner build one revenue-by-SEO-lever view that work
  • Daily snapshot of GitHub Traffic API (views/clones/referrers/top-paths) into a committed CSV/JSON (medium/quick, repo-agent(me), stage: traffic) — GitHub only keeps 14 days of traffic (matches the observed 833 views/474 uniq/14d window). Without snapshotting, the owner can never prove an SEO/CTA change moved the funnel — every before/after comparison is destroyed every 14 days. Persisting the trend lets the owner correlate a README keyword pus
  • Make subs/README.md the highest-converting bridge: tracked, urgency-framed CTA from free configs to paid app (high/quick, exporter-agent, stage: trial) — subs/ is the deepest-intent surface — these visitors are actively importing free configs into v2rayN/Hiddify RIGHT NOW, the exact moment to upsell 'tired of dead links? install the app that auto-rotates them'. The existing 'Configs unstable? Get stable MegaV' block is good but its 3 links point at b
  • Single tracked smart-redirect domain (megav.app/dl?c=) as the one link to rule the funnel (medium/medium, app/web-agent, stage: install) — One short link that device-detects (iOS->App Store campaign link, Android->Play referrer link, desktop->EXE) and logs the inbound c= source before redirecting gives ONE clean server-side tally of click->store handoff per source, independent of GitHub's 14-day window and independent of GSC. The owner
  • Add a tracked Telegram start-param funnel from repo -> @MegaV_VPN bot -> app, mirroring competitor distribution (medium/medium, owner(offsite), stage: install) — Iran/China are GitHub+Telegram-first and App-Store/Yandex-blind. Telegram is where ebrasha/barry-far actually capture the free-config audience. A bot that serves the same free configs (the bait) and tags each user with a start= source param, then pushes the tracked app-install link, recovers the geo
  • Deepen ASO tie-in: align release-asset names + repo topics with the live App Store keyword field and add a 'Why the app vs raw configs' ASO bridge section (medium/medium, repo-agent(me), stage: install) — Repo organic keywords (free v2ray config, vless reality, xray) already match the live ASC keyword field (free,v2ray,vless,wireguard,encrypted,nologs per CLAUDE.md) — so a user who Googles a keyword, lands on the README, then searches the SAME term in the App Store finds MegaV ranking for it. Reinfor
  • Append #-fragment campaign tag and a tracked landing-comment to the free config URLs / all.txt header (low/quick, exporter-agent, stage: trial) — Each config URL already ends with the #megav.app fragment (a branding remark shown in clients). Extending the bait itself with a one-line tracked CTA in the all.txt/per-protocol file headers ('# Get the app that auto-rotates these: megav.app/dl?c=subs_all') puts the paid-app offer in front of users