Your pair is not on the screener at all

Not the same as missing volume

Three symptoms get reported interchangeably and they have different causes, so it is worth separating them before diagnosing anything.

• A pair page exists but shows no recent volume. Usually the wrong pair, or activity that genuinely stopped.
• A pair page exists but the price is frozen. Usually a pair that stopped trading while activity moved elsewhere.
• No pair page exists at all. Something structural, and the subject of this page.

The third is narrower than the other two and therefore easier to solve. If nothing exists, the indexer never created a record, which means it either could not read the pool or decided not to list it. Both possibilities have concrete checks.

Five reasons a pair never appears

The last row catches more people than it should. Some indexers create a pair record on first trade rather than on pool creation, so a pool that exists and has never been used may be invisible until somebody actually swaps through it.

The program question

This is the check that resolves most cases, and it takes under a minute.

Every screener decodes a specific list of swap programs. When a trade happens, the indexer reads the instruction, recognises the program, and knows how to interpret what took place. If the program is not on its list, the transaction is just bytes it does not parse, and no pair, price or volume is ever recorded.

Solana has far more swap programs than any indexer covers. Newer venues, forks, and smaller projects can go uncovered for a long time or permanently. This is not a judgement about the venue's quality; it is a question of whether integrating it was worth somebody's engineering time.

To check: open a successful trade against your token in an explorer and read which program executed the swap. That single field tells you where your liquidity actually lives. If it is a mainstream venue, the problem is elsewhere on this list. If it is something unfamiliar, you have your answer, and the same root cause explains the more general missing volume problem.

Minimum thresholds

Screeners hide very small pairs from lists, searches and filters, because otherwise those surfaces would be unusable. The exact rules are not published and they differ between sites.

The symptom is distinctive: a direct link to the pair works, but browsing, searching or filtering never surfaces it. That is not the same as no page existing, and it is worth distinguishing because the fix is different. Here the fix is depth, and adding it is something you control.

It is also worth noting that a pool small enough to be hidden is a pool too small to trade against meaningfully, so the threshold is usually flagging something real rather than being an obstacle. The liquidity guide covers the test that tells you whether your pool is in that category.

There is an asymmetry between screeners worth knowing before concluding anything. They do not all support the same programs, so a pair can be perfectly visible on one and entirely absent from another with nothing wrong on your side. Before treating a missing page as a fact about your token, check two or three separate screeners. If one of them has it, the pool is fine and what you have learned is which surfaces cover your venue, which is itself useful when deciding where the token should be trading.

What to check, in order

1. Has anything traded? Some indexers only create a record on first trade.
2. How long ago was the pool created? Under an hour, wait before doing anything else.
3. Which program executed the swap? Open a real transaction and read it. This is the decisive check.
4. What is the pool quoted against? SOL or a stablecoin is straightforward; anything obscure is not.
5. How much liquidity is in it? Very small pools are hidden from browsing surfaces by design.
6. Does a direct pair URL work? If yes, the record exists and the issue is visibility rather than indexing.

Steps three and six together separate the two families of cause. A working direct link with no browse visibility is a threshold problem. Nothing at all, on an unfamiliar program, is an indexing problem.

One thing worth ruling out before any of the above, because it costs nothing and catches a surprising share of cases: confirm you are searching by the mint address rather than by name or symbol. Duplicate tickers are the norm on Solana, and a search for a common symbol returns other people's tokens while yours sits at an address the search never surfaced. Paste the mint itself. If the pair appears, nothing was ever missing and the problem was that your token is not searchable by name yet, which is a separate and much easier situation covered in the listing guide.

When to wait and when to act

Wait if the pool is very new and the program is mainstream. Indexing is fast but not instant, and the situation usually resolves itself within the hour.

Add depth if the pair is reachable directly but hidden from lists. This is a threshold problem and it is the one with the most straightforward fix.

Move liquidity if the program is genuinely unsupported and there is no sign that will change. That is a bigger decision than it sounds, since it means creating a pool elsewhere and dealing with liquidity in two places, but the alternative is a token that no discovery surface can see. Trading that nobody can observe produces none of the effects the trading was for.

Do not spend on visibility until this is resolved. A campaign routed through an unindexed venue confirms swaps, moves real money and produces no visible figure anywhere. That is the clearest possible example of buying an outcome the infrastructure cannot deliver, and the check that prevents it takes one minute. If you want to see which venues currently hold liquidity for your mint without reading transactions by hand, the campaign console reads them live.