How to get listed on CoinGecko: requirements, form and timeline

What does a CoinGecko listing involve?

A CoinGecko listing is a platform review of a project’s public information and market data. Your practical task is to make the project easy to identify and its key details straightforward to check before you submit a request.

Start by collecting a single source of truth for the information you plan to provide. The project name, ticker, website, official social channels, blockchain and contract address should agree across your site, explorer and application. Make sure a visitor can understand what the project does and locate its token information without relying on private explanations.

Then review the token’s market presence. Identify the markets where it is actively traded and ensure the pair, asset and contract details are presented consistently. Keep links that let a reviewer verify each detail. CoinGecko’s own current guidance is the authority for eligibility and required information, so compare your package against its official support resources before filing.

A listing is useful as a reference point, but it is not an exchange listing or an endorsement. If you are also preparing a CoinMarketCap request, treat that as a separate application with its own requirements; this CoinGecko and CoinMarketCap comparison helps clarify the distinction.

Which CoinGecko listing requirements should you check first?

The best pre-submission check is whether an independent reviewer can verify the information from public sources. This readiness pass catches gaps that a polished application cannot solve on its own.

Use this checklist before opening the form:

• Project identity: Confirm the project name, ticker, website and official channels use consistent details.
• Token identification: Record the network and contract address, and link to the relevant public explorer page where applicable.
• Market information: List the active markets and trading pairs you want reviewed, with links and accurate asset identifiers.
• Supply explanation: Document the supply figures you publish and how they relate to available on-chain information. If you need to validate this separately, see our guide to verifying token supply.
• Public context: Make sure the website explains the project and the token clearly, and that linked channels are accessible and maintained.
• Evidence folder: Save the source URLs, screenshots where useful, and the exact wording you intend to submit.

This is a preparation checklist, not a claim that every item is a formal CoinGecko rule. Requirements can change, and the platform’s own listing instructions take precedence. If a figure differs between your website, explorer and application, resolve the discrepancy first and note the reason in plain language. For a broader application-readiness review, compare your materials with the CoinGecko listing service scope.

How do you prepare the CoinGecko listing form?

Prepare the answers and evidence before you submit the CoinGecko form. This reduces avoidable corrections and gives your team a reliable record of exactly what was sent.

Open the official listing request route from CoinGecko’s website or support centre, then follow the current fields and instructions shown there. Do not rely on an old saved copy of a form: the platform may revise its process. Enter the project and token details exactly as they appear on the public sources you have checked. For each claim, provide the most direct supporting URL rather than a general homepage when a specific page or explorer is available.

Before submitting, have someone who did not assemble the application read it as a reviewer would. Ask them to find the contract, confirm the network, locate the cited market information and understand the supply explanation without asking you for context. Save the completed responses, links and submission confirmation in a shared project folder. Keep access limited to people handling the application; internal notes should not expose private keys, credentials or sensitive personal information.

MediaStrategy uses a named submission-readiness review: a senior reviewer checks identity, source links, market references and supply wording against the application before it goes out. That review helps your team send a coherent package; it does not replace CoinGecko’s own assessment.

How long does CoinGecko listing review take?

There is no dependable public review duration to plan around, so treat submission as the start of an open-ended platform process rather than a dated launch commitment. The platform controls whether it needs more information and when it responds.

Build a schedule with decision points your team controls. Complete the source checks before filing, assign one person to monitor the contact channel used in the application, and agree who can answer technical or project questions. Keep a copy of the submitted materials so the response can be matched to the original application rather than reconstructed from memory.

If CoinGecko asks for clarification, answer the specific question directly, provide the relevant public source and explain any correction. If you have found an error independently, distinguish the corrected fact from the earlier submission and link to the updated source. Avoid sending repeated requests that do not add information; maintain a dated internal log of correspondence instead.

Listing planning can sit alongside other visibility work, but do not announce a confirmed listing before the platform confirms it. For a separate discovery objective, review how CoinGecko trending works; a listing application and a trending campaign are different tasks and should have distinct expectations and owners.

What should you do about supply discrepancies or a CoinGecko warning?

Resolve a supply discrepancy by locating the source of the mismatch and making the public explanation consistent before asking for a profile review. Do not submit a new figure without being able to show where it comes from.

Compare the supply statements on your project website, token documentation and relevant public explorer data. Record which supply is circulating, total or otherwise defined in your materials, and explain any lockups, allocations or changes in terms a reader can verify. If the issue concerns a profile warning, capture the exact displayed wording and identify the underlying detail it appears to refer to; then correct that detail or prepare a concise, evidence-backed explanation. Our supply verification guide and listing profile remediation service cover those distinct types of work.

CoinGecko controls its review, profile labels and any decision to update displayed information; a project cannot compel a particular outcome by editing its own website or sending a request. The useful next step is to correct verifiable source material, document the change and submit a focused clarification through the appropriate official channel.

Keep claims measured: describe what you can demonstrate now, not what you expect the platform to display later. A clean correction trail helps your own team answer follow-up questions accurately.

What should your team do after submitting?

After submitting, preserve the application record, keep your public information current and assign one owner for any platform correspondence. This keeps the process orderly without implying that continued outreach can accelerate review.

A simple internal handoff should include:

• the submitted form and confirmation;
• the URLs and supporting evidence used in the request;
• the named owner for responses and the technical contact for token details;
• a change log for any later edits to the website, token information or markets.

If a material project detail changes while the request is under review, assess whether the original application is now inaccurate. Update the relevant public source and use the official route to explain the change when appropriate. Keep announcements, exchange discussions and listing requests separate: each has its own approval and publication path.

For parallel work, the CoinGecko listing service can support application preparation, while the listings and verification hub maps related profile and supply tasks. Send us your project website, token network and contract address, known market links, and any existing CoinGecko correspondence. We will review the source material first, identify gaps for your team to resolve, and then confirm the scope of application support.

Prices

Starting prices in USD. Custom bundles and volume discounts on request. Payment in USDT, USDC, BTC, ETH, SOL, TON or your project token.

How it works

1. 1. Consolidate the project recordGather the website, official channels, token identifiers, explorer references and market links in one working file. Assign an owner for each fact that may need confirmation.
2. 2. Reconcile public detailsCompare names, network and supply explanations across public sources. Resolve discrepancies before they reach the application.
3. 3. Check current instructionsOpen CoinGecko’s official listing route and follow the form and eligibility guidance currently displayed. Prepare direct evidence links for the relevant answers.
4. 4. Run a submission-readiness reviewHave a second reviewer follow the evidence without private context. Correct unclear wording and save the final answers and confirmation.
5. 5. Manage the review recordMonitor the appropriate contact channel, respond to specific requests with verifiable information and log material changes to the submitted details.