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

What should be ready before a CoinGecko application?

Before applying, make sure someone outside your team can verify the project, token, and market information from public sources. CoinGecko’s current eligibility rules are the final reference, so check the official CoinGecko support center before submitting. Requirements and form fields can change.

Build a readiness folder with the following items:

• The project’s official website, explaining what the product does and how to contact the team.
• The correct token name, ticker, network, and contract address, with a public explorer page.
• Live market information from exchanges or markets that meet CoinGecko’s current criteria.
• Supply definitions and supporting sources that distinguish circulating, total, and maximum supply where applicable.
• Active official channels that match the website and provide current project information.

Review each item from the perspective of a reviewer who does not know your project. Links should open, pages should load, and labels should match across sources. A project with a clear public record is easier to assess than one whose application depends on explanations shared only in a private message. If your project has changed its name, network, or contract, make that history clear before submitting.

How do you complete the CoinGecko listing form?

Complete the form with one authoritative version of your project information and use public links to support claims. The application is not the place to introduce several ticker spellings, unexplained contract changes, or market details that cannot be checked independently.

Prepare a source sheet before opening the form. For every requested field, record the exact value, the public URL that confirms it, and the person responsible for keeping it current. Use the project’s official website and channels as the source for identity. Use a block explorer for contract details and credible market pages for trading information. Follow the latest instructions in CoinGecko’s own support documentation; do not rely on an old screenshot or a third-party checklist when the live form differs.

Before you submit, check that:

• The chain and contract address match the explorer and project materials.
• The website and social links are official, accessible, and consistent.
• The market information refers to the correct asset and trading pair.
• The description is factual, specific, and free of claims your links cannot substantiate.

Save a copy of the answers and submitted URLs. If CoinGecko requests clarification, that record helps your team respond consistently rather than rebuilding the application from memory.

How long does CoinGecko listing review take?

CoinGecko controls the review queue and decision, so there is no dependable review date to promise. Your practical timeline includes preparation, submission, any request for clarification, and the platform’s review. A clean application can reduce avoidable back-and-forth, but it cannot set the reviewer’s schedule.

Plan around readiness rather than a launch-day assumption. Gather the evidence before submitting, and leave room for the platform to ask questions or for your team to correct a broken link or inconsistent field. If you are coordinating an announcement, tell partners that the listing is pending until it is visible on CoinGecko. Do not present a submitted form as an approved listing.

After submission, assign one person to monitor the contact channel provided in the application. Keep replies concise: answer the question, include the relevant public source, and identify any change since submission. Avoid sending repeated applications with different versions of the same information. If a material detail changes while the review is open, document the change and use the platform’s instructed route to update it. This keeps the application trail understandable and gives the reviewer a stable set of facts to assess.

How to verify supply on CoinGecko

To verify supply, reconcile the figures shown in your project materials with the contract, explorer, and any documentation CoinGecko asks you to provide. A number without a clear definition or a checkable source is difficult to assess. Start by writing down what each supply figure means, rather than treating circulating, total, and maximum supply as interchangeable labels.

For each figure, note its calculation method and evidence. If tokens are locked, vested, reserved, burned, or held across multiple contracts, explain how that affects the figure and link to public documentation or explorer data. Check whether the chain’s token model makes the supply directly readable from the contract or requires additional context. Then make sure the same definitions appear consistently on the website, in the application, and in any public token documentation.

If the figure shown by CoinGecko does not match your current evidence, identify the exact field and provide the clearest supporting source. Our separate guide to verifying token supply covers the evidence trail in more detail. Avoid changing several public figures without explaining why; unexplained revisions can make a straightforward discrepancy harder to resolve.

How do I address a CoinGecko warning?

Address a CoinGecko warning by identifying the underlying issue, correcting the relevant public information, and supplying evidence through the platform’s stated channel. A warning can concern different aspects of a listing, so the right response depends on the notice and the affected data; changing profile wording alone may not resolve it.

First, preserve the warning text and note which token, market, supply field, or project detail it identifies. Compare that detail with the contract, explorer, market source, and official project pages. Correct errors at the source where possible, then collect links that show what changed. If you believe the warning is based on outdated or incorrect information, explain the discrepancy directly and provide verifiable evidence rather than making broad claims about the review.

Do not create a new profile or submit conflicting data as a workaround. Keep a record of the issue, corrective action, and any communication with the platform. CoinGecko’s response and the display of a warning remain part of its review process. For organized support with a listing profile issue, see CoinGecko listing profile remediation and compare the situation with our warning response guide.

CoinGecko vs CoinMarketCap listing: what is different?

CoinGecko and CoinMarketCap run separate listing processes. Approval or visibility on one does not automatically create a listing on the other, and each platform may ask for information or evidence through its own process. Prepare a distinct application for each instead of assuming one submission covers both.

The shared preparation is still useful: verified token identity, consistent contract details, transparent supply definitions, public project information, and eligible market evidence. The practical difference is the platform-specific form, instructions, and review. Confirm the live requirements for each platform and tailor your answers to the fields it actually requests. Our guide to getting listed on CoinMarketCap explains that platform’s separate application path.

Listing is also different from appearing in a trending area. A listing concerns the platform’s project and market data pages; a trending feature concerns visibility within a particular product surface and follows its own rules. If your goal is discovery rather than basic listing, read how CoinGecko trending works. Do not treat trending, advertising, or a listing as interchangeable outcomes. Choose the task based on what users need to verify or find.

What does CoinGecko listing support include?

Listing support should make your application more complete and easier to review; it should not imply control over CoinGecko’s decision. Before engaging help, ask who checks the evidence, who submits the form, how follow-up questions are handled, and which work is included. The project remains responsible for accurate information and access to its official sources.

A useful support scope can include a readiness review, a consistency check across project materials, organization of public evidence, form preparation, and help drafting a clear response if the platform requests clarification. Agree on responsibilities before work begins. For example, decide who confirms supply figures and who can approve changes to the website or token documentation. Keep credentials private wherever possible; application preparation usually calls for accurate public links and authorized project contacts, not unrestricted access to project accounts.

Our CoinGecko listing support starts at from $1,150 / project. This is a service starting price, not a CoinGecko charge. For the breakdown of the service price, see CoinGecko listing pricing. Compare any proposal by its deliverables and scope, not by claims that an outside team can influence the platform’s reviewer.

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. Audit the project’s public informationCheck the website, official channels, contract, market details, and supply data. Note inconsistencies before starting the application.
2. Confirm current platform requirementsRead CoinGecko’s current listing instructions and make sure the project and its markets fit the stated criteria.
3. Prepare answers with evidenceMatch each application field to a public source. Keep wording, token identifiers, and supply definitions consistent.
4. Submit and keep a recordSave the submitted information and links, and assign a team member to monitor the contact channel used in the application.
5. Respond to follow-up clearlyAnswer the specific request with relevant evidence. Record any changes and do not describe a pending review as an approval.