Why your token is not showing on Jupiter

Three states that get reported as one problem

Before diagnosing anything, separate what you actually mean. On an aggregator, a token can be in three independent states, and being in one says nothing about the others.

Almost every complaint resolves into one of these. "I cannot trade it" is routing. "My community cannot find it" is search. "It shows a scary warning" is verification. Working out which one you have is most of the diagnosis.

Routable: does an indexed pool actually exist

Routing is mechanical. An aggregator builds routes from pools it indexes, so if it cannot quote your token, one of a small number of things is true.

• No pool exists yet. More common than people expect, particularly right after a launch where liquidity was announced but not actually seeded.
• The pool is on an unsupported program. Solana has far more swap programs than any aggregator integrates. A pool on an exotic venue may be invisible to routers for a long time.
• The pool is too thin to quote. A pool holding a trivial amount of liquidity produces quotes with impact so large that they are effectively unusable, and some routers will decline to offer them at all.
• It was created minutes ago. Indexing is fast but not instant.

The check is quick: open a successful transaction against your token in an explorer and read which program executed the swap. That tells you exactly which venue your liquidity lives on, and whether it is one an aggregator would recognise.

Searchable: why the name does not come up

This is the state that frustrates teams most, because the token is perfectly tradeable and yet a community member typing the ticker sees nothing.

Search is backed by a curated list rather than by routing. Anyone can create a token with any name, and duplicate symbols are the norm rather than the exception, so aggregators do not surface everything by name. Inclusion has criteria, and while the details differ between interfaces and change over time, the recurring themes are consistent: a pool with meaningful and reasonably stable liquidity, working metadata, some history rather than a token minted an hour ago, and evidence of genuine usage.

Two practical points follow. First, being unlisted is a default state, not a punishment. Second, the instruction "share the contract address" exists precisely because of this gap, and it is a perfectly normal thing to tell your community while a listing works its way through.

There is a timing trap here that catches teams during launches. A token is at its most talked-about in the first hours, which is exactly when it is least likely to be searchable, because curated lists move on a slower clock than launch hype does. Planning around that gap is cheap: pin the mint address everywhere before you need it, put it in the profile bio rather than only in a post that scrolls away, and assume that anyone arriving in week one will need it. Teams that skip this lose a share of their most motivated arrivals to a search box that returns nothing.

Verified: what the warning label is actually saying

A warning on an unlisted token is an absence rather than an accusation. The interface is telling the user it has not confirmed the token is what it claims to be, which is the honest thing to display given how many tokens impersonate others.

This matters commercially because that label costs conversions. A trader arriving from a screener, seeing a warning dialog, and having to type a confirmation is a trader who sometimes just leaves. It is worth treating list inclusion as a real growth task rather than as cosmetic, and worth being patient with, because nothing you spend makes it instant.

What actually moves each one

1. Fix the pool first. Enough liquidity that a realistic buy does not move the price several percent. Everything downstream depends on this, and it is the item most often skipped.
2. Fix the metadata. Name, symbol, a description, an image that loads from a permanent location. This costs nothing and its absence is an easy reason to skip you.
3. Make sure the pool is on a mainstream venue. Exotic programs are cheaper and slower to be seen.
4. Accumulate genuine history. Trades, distinct participants, days rather than hours. There is no shortcut that skips the calendar.
5. Then apply through the proper channel and expect it to take time.

Where activity helps and where it does not

Trading activity supports the criteria that measure whether a token is actually used. It moves trade count, unique participating addresses and the visible fact that the pool sees flow rather than sitting idle. Those are real inputs.

What it does not do is substitute for the structural items. A campaign cannot deepen your pool, fix broken metadata, or make a token minted this morning older. Running one before those are in place spends money on the one input that is easiest to discount while leaving the ones that actually block you untouched.

There is also an execution point specific to aggregators. Swaps routed through an aggregator land on the underlying pool, so the volume appears against that pool rather than against the aggregator. This confuses people who expect campaign activity to show up somewhere aggregator-branded, and it is the same pool-versus-token distinction that causes the more general missing volume confusion on screeners.

The order to work through

Do these in sequence rather than in parallel, because each one makes the next one easier and doing them out of order wastes money.

Confirm a pool exists and note which program it belongs to. Simulate a realistic buy and a realistic sell, and fix depth if either moves the price more than a percent or two. Repair metadata completely. Only then think about activity, and think about it as evidence rather than as a lever. The liquidity guide covers the depth test in detail, including why a thin pool wastes budget twice over.

If you want to see which venues hold liquidity for your mint right now, without running anything, paste the address into the console on the home page. It reads the pools live, which answers the routing half of this question in a few seconds.