The way people find apps in 2026 looks nothing like it did three years ago. A founder building a budgeting app in 2023 pointed her marketing budget at App Store Search Ads and Reddit. The same founder today loses half her acquisition pipeline to a different question entirely: when someone opens ChatGPT and types “what is the best app to track my spending if I have ADHD,” does her app come up?

Most app developers have not adjusted to this. They still optimize for the App Store algorithm, still write the same product page descriptions, still chase the same 4.5-star review threshold. Meanwhile their growth dies because the user research phase has migrated to AI assistants, and their app is invisible inside the new discovery surface.

This is the operator’s guide to changing that. Specific tactics, specific numbers, specific examples. The work that gets an app named when ChatGPT, Claude, Perplexity, Gemini, and the search-grounded systems answer real recommendation questions.

When someone asks an AI tool for an app suggestion, several things happen in sequence. The model parses the request and identifies the category and constraints. It then retrieves passages from its training corpus, web index, or browse tool. It synthesizes a response and chooses which apps to name, usually three to seven of them.

Three signals decide whether your app shows up. The first is presence in the training data the model already saw. The second is presence in whatever index the model retrieves from at runtime, which now includes the open web for most major systems. The third is the model’s confidence that the app actually fits the requested constraint, which depends on how the app gets described across the corpus.

An app that gets named in a recommendation is one that has all three signals working. Mentioned often enough across the corpus to be in training memory. Indexed and retrievable when the model browses. Described in language that matches real user constraints, not just generic marketing copy.

The categories that produce the most app recommendation traffic

Not every app category is queried equally inside AI tools. The categories with the most embedded recommendation behavior, based on shared anonymized search logs from a half-dozen tools and SimilarWeb’s AI traffic panel through Q1 2026, are productivity, mental health, fitness, finance, language learning, AI tooling itself, parenting, and developer tools. These categories combine high uncertainty (people are not sure what to pick), low brand consolidation (no single dominant app), and high stakes (the user will commit time or money).

If your app sits in one of these categories, you have a tailwind. People are asking AI tools recommendation questions every minute of every day. If your app sits outside these categories, you have to find the adjacent recommendation surface. A specialty app for veterinarians does not get queried for general use, but it does get queried by veterinarians inside their professional research, which surfaces inside AI assistants when those vets ask for tooling recommendations. The discovery happens. It just happens at lower volume.

Where AI tools find the writing they cite

Look at the actual citations on a Perplexity or You.com response and you see the same sources keep appearing. App review sites with editorial standards (TechCrunch reviews, Wired’s app coverage, The Verge, MacRumors). Listicle sites that maintain category lists (Zapier blog, Notion’s app picker articles, app comparison directories like AlternativeTo). Reddit threads, especially r/productivity, r/iosapps, r/androidapps, r/personalfinance, and category-specific subs. YouTube videos with detailed transcripts. Substack newsletters from category specialists. The major app stores’ own editorial picks. Industry-specific publications.

Each surface has a different threshold for entry. Getting into a TechCrunch app review takes a real story angle. Getting into a Zapier blog comparison takes a credible product and the right pitch. Reddit can be earned over months of community participation. YouTube takes outreach to specific creators in your category.

The pattern holds across categories. The apps that get recommended are the ones with twenty or thirty pieces of independent third-party writing scattered across the surfaces above. Not pieces with brand-controlled messaging. Pieces written by humans who tested the app and explained why it solved a problem.

The minimum viable AI visibility footprint

A working baseline footprint for an app that wants to start surfacing in recommendations looks like this. Five to ten product reviews on review sites or category-specific blogs in the first six months. Two to four comparison articles on third-party sites that name your app alongside the obvious incumbents. A clear, frequently-updated FAQ section on your own site that mirrors how users describe their problem. Twenty to thirty Reddit threads where the app has been mentioned in a relevant context, voted up, and not flagged as spam. Three to five YouTube videos that show the app inside a real workflow, ideally with creator-narrated content rather than pure tutorials. A Wikipedia entry if the app has the notability to support one. A Crunchbase or product database listing with current data.

That is a minimum. The apps that actually win category-level recommendations have ten times that footprint. But the minimum is enough to start showing up in long-tail recommendation queries, which is where most apps need to start anyway.

The on-app-page work that actually moves AI recommendations

Most app developers underweight their own site as a recommendation signal. The model sees your homepage, your product pages, your help center, your changelog, your blog. The way that content reads affects whether the model names you in a response and how it describes you when it does.

Three kinds of writing on your own site matter the most. The first is what you call your app and how you describe its use cases. If your app is a Pomodoro timer, the homepage should say “Pomodoro timer” in actual prose, not just in the page title. AI tools weight body text heavily because that is how they understand what a thing is. Marketing taglines that avoid naming the category waste this signal.

The second is the use-case page. A help-center or marketing page that describes a specific problem, says who the app is for, and explains how to solve it gives the model exactly the kind of passage it can quote. “How to track sleep with [App Name] when you work night shifts” reads natively to a model answering a query about sleep tracking for night shift workers.

The third is the comparison page. A page on your site that compares your app to two or three obvious alternatives, with specific feature differences and use-case fits, gets cited heavily. The page does not have to bash competitors. It has to be honest and specific. “[App Name] is better for X if you care about Y; [Competitor] is better if you need Z.” Models love this format because it gives them ready-made constraint-matched content.

Reddit is the highest-leverage off-site surface

Most app categories have one or two subreddits where category recommendations get asked daily. r/personalfinance for finance apps. r/productivity for productivity apps. r/sysadmin for IT tools. r/buildapc for hardware-adjacent software. r/keto for keto-adjacent apps. r/parenting for parenting apps. The list is long.

The pattern that works on Reddit is not corporate Q&A. It is sustained presence over months. Have a real engineer or founder account that posts regular contributions in the sub, answers questions on adjacent topics, and only mentions the app when the question genuinely calls for it. Other users will mention the app for you, and those mentions, voted up by the community, become the citations AI tools use.

The pattern that does not work is showing up cold with a launch post and a discount code. Reddit detects this in seconds. The post gets removed, the account gets flagged, and the brand becomes harder to mention organically because users in the sub now associate it with spam.

A real example. A focus-and-time-tracking app that launched in 2024 quietly assigned its CTO to spend three hours a week in r/productivity for nine months. He posted answers to other people’s questions, occasionally referenced the app when it was the right answer, and built a reputation as a useful contributor. By month nine, other users were posting “you should try [App Name]” in unrelated threads. By month twelve, the app started showing up unprompted in ChatGPT recommendations for “best focus app for ADHD.”

YouTube is the second-highest-leverage surface

A specific cohort of YouTube creators owns the app recommendation niche on the platform. Tech reviewers like Marques Brownlee for general tech, Matt D’Avella for productivity, Caleb Hammer for finance, Ali Abdaal for student tools, and a long tail of category specialists.

These creators get pitched constantly. The pitches that work are not “would you review my app.” The pitches that work are: a specific reason your app fits their content series, a working free tier or pro code so they can actually use it, a clear story about what makes the app different, and patience. Most app integrations into YouTube content take three to six months from first contact to published video.

The transcript is what gets cited by AI tools more than the video itself. So a video where the creator talks through the workflow in detail, names the app multiple times, and explains who it is for produces more recommendation lift than a flashy demo with minimal narration. Optimize for the spoken description.

What to track to know if it is working

The lagging indicator is recommendation share, which is hard to measure precisely without manual probes. The leading indicators are easier. Track branded search volume on Google. Track direct app store search for your brand name. Track referral traffic from review sites and Reddit. Track Reddit and YouTube mention frequency. Track citation frequency in tools that show citations (Perplexity, You.com, Bing Copilot, Brave Leo).

The simplest test is a manual probe panel. Pick fifteen to twenty real questions a user might ask about your category. Run them through ChatGPT, Claude, Perplexity, and Gemini once a month. Track how often your app gets named, where it ranks in the response, and how it gets described. The trend line over six months is the signal you care about.

Apps that put serious work into the off-site visibility footprint usually start seeing meaningful improvement on this panel inside the second or third quarter. Apps that ignore the off-site work and only optimize their own site rarely move the needle, because the model has nothing to cite besides the brand-controlled messaging on the homepage.

The discovery layer for apps has shifted. The work to win it is concrete, traceable, and doable. The apps that do it now will compound an advantage that is harder to take away than App Store ranking ever was.