How to List a Token on GeckoTerminal

GeckoTerminal tracks on-chain pools across supported networks and DEXes. Its support guidance says a token traded on a supported DEX should be visible when searched by contract address. A deployed token with no supported pool is not enough. Confirm that the intended network and DEX currently appear in GeckoTerminal's coverage.

Create and fund the pool through the official venue, then verify at least one successful trade and current reserves in the chain explorer. Save the pool address, token addresses, DEX program or factory, creation transaction, funding transaction, and first trades. Never give private keys or privileged contract access to a listing intermediary.

Record the complete contract or mint address, chain, decimals, pool address, quote asset, and official project URL. Confirm the pool actually contains the intended token and a correctly identified quote asset. Names, logos, and symbols can be copied, while a contract address is specific to a network.

If multiple pools exist, distinguish the official launch pool from later or unrelated markets. Compare reserves, liquidity, age, DEX, and transactions. A higher displayed liquidity number does not by itself establish that a pool is canonical, because quote assets and valuation methods can differ.

Use the token's complete address in GeckoTerminal search and select the correct network. If no token result appears, search the pool address. The GeckoTerminal API also supports address-based token and pool research, including finding pools that trade a token and retrieving market data. API availability does not guarantee that every interface field is populated.

Once found, compare the displayed token, pool, quote asset, liquidity, price, volume, and transactions with the explorer. Preserve the GeckoTerminal URL and observation time. Do not announce detection as verification, approval, or confirmation that the contract is safe.

CoinGecko's support instructions direct users to navigate to the token's pools, open the Token Info section, choose Update Token Info, and submit the requested information. This process concerns metadata such as project identity and links. It is separate from the on-chain pool being indexed.

Prepare a stable logo, official website, complete address, social accounts, description, and evidence that the requester represents the project. Keep the same identity across the project site, explorer, repositories, and existing data services. If the token is already listed on CoinGecko, GeckoTerminal may source information from that record, so resolve conflicts before filing another request.

• Use official domains and public social accounts.
• Submit the exact network and address.
• Avoid duplicate or conflicting update requests.
• Do not present review submission as approval.

Related research: How to Get a Token Listed on DEX Screener - Understand DEX Screener automatic token listing, the liquidity and transaction prerequisites, token information options, and missing-pair troubleshooting.

For a missing market, recheck network and DEX support, pool funding, successful trades, token and pool addresses, and the exact contract searched. New or custom DEX deployments may require separate DEX or chain coverage. Document the evidence before contacting support so the issue can be reproduced.

For a rejected information update, review the current GeckoTerminal guidance, project ownership evidence, website quality, social links, duplicate submissions, and consistency with CoinGecko. Do not repeatedly resubmit unchanged information or hire a third party that guarantees approval. Correct the public project record and submit through the official route.

Related research: Why a New Token Is Missing From DEX Trackers, Wallets, or Market Indexes - A diagnostic guide to indexing delays, unsupported pools, metadata gaps, liquidity thresholds, and address mistakes.

GeckoTerminal indexes DEX and DeFi market data, while CoinGecko maintains a broader reviewed aggregator record. A token can have a GeckoTerminal market page without a CoinGecko coin page. Teams should not describe one as automatic approval for the other. CoinGecko listing requirements, review, supply information, and project records follow their own current process.

Build one evidence pack that can support both workflows, but answer each form independently. Include network, address, explorer, official contacts, live pool, supply methodology, controls, allocations, and consistent links. Paid or expedited products should be documented separately from organic indexing and review.

Related research: CoinMarketCap vs CoinGecko Token Listing in 2026 - Compare CoinMarketCap and CoinGecko token listing paths, DEX indexing, review states, market data, and submission evidence in 2026.

Recheck the page after metadata updates, contract changes, pool migrations, or new material markets. Compare the token's main pools and quote assets rather than promoting a single screenshot. Keep official links current and remove compromised channels quickly through the documented update route.

Use GeckoTerminal as one market-data source alongside the explorer and another independent indexer. Provider disagreement can result from coverage, timestamps, pair selection, decimals, or price routes. Record those differences instead of treating any one interface as final proof.