> ## Documentation Index > Fetch the complete documentation index at: https://docs.waniwani.ai/llms.txt > Use this file to discover all available pages before exploring further. # After you submit: drive traffic to your app > Submitting your app is the start, not the finish. The three levers that get traffic to your app and capture it: putting the agent on your website, GEO, and PR, plus the KPIs to track. Getting listed is the start, not the finish. Today, ChatGPT and Claude do **not** suggest apps proactively: your app shows up when the assistant searches the web and finds content saying it exists and how to use it. So once you are submitted, the real work is to **drive traffic to the app** and **capture that value on your own site**. This page explains what to do, in what order, and how to measure it. ## The two milestones 1. **Traffic on the app** inside ChatGPT and Claude: installs, conversations, and the quotes or leads it generates. 2. **Traffic on the agent on your website:** sessions, leads captured, and conversion compared to your classic funnel. ## The three levers | Lever | What it is for | | --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | **Put the agent on your website** | Capture value where you control the experience, without depending on the assistant's recommendation. | | **Do GEO** | Make the assistants aware the app exists so they suggest it when a user asks. | | **Do PR and comms** | Create third-party corroboration (assistants weigh information that appears across several sources) and drive direct traffic. | ### Lever 1: put the agent on your website The fastest way to capture leads is to run the same agent on your own site, where you control the experience and do not depend on an assistant surfacing your app. The Waniwani [chat widget](/sdk/chat/embed) embeds the agent on any page. This is the highest-leverage step, so do it first. ### Lever 2: GEO (generative engine optimization) GEO is the practice of publishing content that teaches assistants your app exists and how to install it, so they describe it correctly and suggest it when relevant. It works. We ran a controlled experiment on an app with zero starting authority (NA Drink Finder, an independent ChatGPT app) on a brand-new domain, with no other marketing input, just content: 74 GEO-optimized articles over 33 days, with 1,881 prompts tracked across ChatGPT, Perplexity, and Google AI Overview. | Metric | Before | After | | ------------------------------------------------------------------- | ------ | --------------------------------------- | | ChatGPT describes the app correctly as a ChatGPT app | 4.5% | 45.7% (10x) | | Hardest case: prompts where the app name is **not** in the question | 0% | about 30% | | ChatGPT wrongly describes it as a mobile app | 40.9% | 17.1% | | ChatGPT denies the ChatGPT app exists | 4.5% | 0% | | Install syntax `@AppName` present in the answer | 0% | up to 50% of answers citing our content | The takeaway: before GEO, ChatGPT did not suggest the app, described it as a mobile app, or said it did not exist. After publishing content, it described the app correctly **and** explained how to install it. Answers citing our content described the app correctly 2.3x more often. Read the full write-up at [waniwani.ai/research/chatgpt-app-geo-experiment](https://waniwani.ai/research/chatgpt-app-geo-experiment). ### Lever 3: PR and comms Comms has two goals: create third-party corroboration and generate direct traffic. A reusable plan for a launch: 1. **Press release** (under 500 words, with a "first" or "new" angle, your site URL, and your app URL). 2. **Pitch one reference industry publication** (one trade outlet beats ten generic tech blogs). 3. **LinkedIn:** one post from the company page and one personal post from the founder (personal posts reach further). 4. **Email** your prospect and partner base announcing the launch. 5. **A results post at day 30 or 60** ("we generated X quotes through ChatGPT in one month"). This is highly citable and creates a second wave of content. A strong angle compounds: the first live insurance app on ChatGPT got picked up by industry press precisely because "first" is newsworthy. Find the equivalent "first" or "new" angle for your category. ## KPIs to track **The app (ChatGPT and Claude)** | KPI | Source | | ------------------------------------------------------------- | ---------------------------- | | App installs | OpenAI / Anthropic dashboard | | Sessions and conversations on the app | Waniwani | | Quotes or leads generated via the app | Waniwani | | Redirects to the website (UTM) | Your analytics | | Share of tracked prompts where the assistant mentions the app | Waniwani (GEO) | | Answer quality (app described correctly, install flow given) | Waniwani (GEO) | | Citation rate of your content | Waniwani (GEO) | **The agent on your website** | KPI | Source | | ------------------------------------------------------------------------------- | ---------------------- | | Sessions on the agent | Waniwani | | Funnel: visitors, engaged (more than 1 prompt), email captured, qualified leads | Waniwani | | Email capture rate | Waniwani | | Conversion vs the classic form funnel | Waniwani and your data | ## What to expect Set expectations early: the assistants will not surface your app on day one. Treat the weeks after launch as an ongoing program rather than a single event. Review the KPIs above on a regular cadence (a bi-weekly check-in works well), and let the data point you at which lever to push next. Put the same agent on your website with the chat widget. The sessions, events, and funnel metrics behind these KPIs.