The CoinGecko listing form, field by field

What a CoinGecko listing involves

Quick test: Compare contract, supply and links in 3 places: your site, docs and the form. Fix any gap first.

A CoinGecko listing is a platform review of information about a cryptocurrency and its markets; it is not simply a profile page that a project publishes for itself. Your practical task is to make the project easy to identify and the information in the application easy to check.

Before starting, assemble a short source file with the project name and ticker, official website and channels, chain and contract details where relevant, supply information, and the markets where the asset is traded. Keep a source next to each claim: for example, a contract address should point to the relevant explorer, while market details should match the exchange or market page you identify. This preparation helps your team catch conflicts before they reach the form.

A listing can help users find and compare an asset through CoinGecko, but it is separate from an exchange listing and does not replace your own documentation. If you are also preparing an application to another tracker, handle each platform’s form and status separately. See the CoinGecko listing service for application support, or compare the separate process in our guide to getting listed on CoinMarketCap.

Which requirements to prepare for

The safest readiness check is to confirm that every key project detail is public, current, and consistent across your website, channels, blockchain records, and market pages. CoinGecko’s current guidance and application form are the authority on what it asks for; use this checklist to organize your evidence, not as a substitute for those instructions.

Prepare these records

• Project identity: official name, ticker, concise description, website, and active public channels.
• Asset details: network, contract address where applicable, and an explorer page that lets a reviewer inspect the asset.
• Supply: the figures you publish, the definitions behind them, and a source that supports them. If your supply explanation needs work, use our guide to verifying token supply.
• Markets: the exchange or market name and the exact asset pair or page you want reviewed. Check that the pages are accessible and describe the same asset.
• Supporting context: links that help explain the project and resolve any unusual details, such as a migration or multiple contracts.

If a field does not apply, do not fill it with a guess. Note why it is not applicable and keep a source or explanation ready. Resolve mismatched names, symbols, addresses, or supply descriptions before submission; reviewers should not have to infer which version is correct.

Your 6-point CoinGecko form checklist

Go through this checklist field by field before you submit. Use the platform's current form and rules, since they can change from one month to the next. Print the list, tick each line with a pen, and keep it next to the brief so everyone works from the same page.

1. Open the current CoinGecko form and read every field.
2. Confirm name, symbol, contract and chain.
3. Prepare supply facts with sources.
4. List official links that all agree.
5. Prepare one market or trading venue link.
6. Save a dated copy of what you submitted.

Terms in one line

Circulating supply (in plain words: the number of tokens currently available to trade).

Warning label means a note a platform adds to a token page to flag something readers should know.

How to complete the listing form

Complete the current form with direct, traceable information, then review the full application as one document before sending it. Use the official CoinGecko support and listing guidance to find the applicable submission route and confirm the form’s latest fields.

Start by assigning one person to own the submission and one person to verify technical details. Copy stable project facts from approved sources rather than rewriting them from memory. For links, open each page in a logged-out browser if possible and confirm that it goes to the intended project, contract, or market. Make the project description clear enough for a new reader to understand what the asset is and where its information can be checked.

Before you submit, run a final pass:

• Compare the project name and ticker across all linked pages.
• Confirm contract and chain details against the relevant explorer.
• Reconcile supply wording with the public source you provide.
• Check that market links resolve to the correct asset and pair.
• Save a copy of the answers and evidence links for your records.

For fitted help with preparing and checking an application file, see the CoinGecko listing support page. Submit once the file is internally consistent; repeated submissions with conflicting details make it harder to keep track of which information is current.

How long does the review take?

Common mistake: Submitting before the project site lists the contract. Reviewers will check it.

There is no fixed review duration to plan around unless CoinGecko states one in its current guidance or in a direct response to your project. The useful planning assumption is that submission, review, clarification, and any resulting profile updates are separate parts of the process, and their timing is not fully in your hands.

Build your launch calendar so the project does not depend on a listing appearing by a particular day. Submit when the evidence is ready, keep a record of the submission, and make sure the person monitoring the project inbox can respond with the requested source material. If a response asks for clarification, answer the specific question and point to supporting public evidence rather than sending a new, unrelated pitch.

While the application is under review, keep official pages available and avoid changing core details without recording what changed. If a contract, ticker, market page, or supply description does change, prepare a concise explanation and the new authoritative links. That makes a follow-up easier to understand and reduces the chance that your own team shares outdated information. For a parallel application, treat CoinMarketCap as a separate review; the CoinMarketCap listing guide explains that process.

What if CoinGecko asks about supply or shows a warning?

Treat a supply question or profile warning as a request to clarify the underlying data, not as a reason to submit unsupported claims. First identify the exact field or message, then compare it with your contract, explorer information, project documentation, and any public supply explanation.

For supply, write down what each figure means before editing public copy. Distinguish the terms your project uses, explain any relevant exclusions or locked amounts, and link to evidence a reviewer can inspect. If the available on-chain view does not tell the whole story, provide a concise explanation and appropriate supporting documentation rather than presenting an estimate as a verified figure. Our token supply verification guide covers how to make that explanation clearer.

For a warning, capture the wording and location, check whether the related project information is accurate, and gather evidence that addresses the specific concern. Correct factual errors in the places your team controls, then follow the platform’s stated route for review or profile updates. Our guide to CoinGecko warning remediation can help you organize that response. Keep a dated internal note of changes and links so follow-up answers stay consistent.

What you control, and what to do next

Your team can control the accuracy and completeness of its submission, the accessibility of its public evidence, and the speed and clarity of its replies. CoinGecko controls its review decision, any request for additional information, whether or when a profile is updated, and how its site presents or ranks information; no agency can promise approval, a review date, or a particular position in platform features. Keep this limit in mind when planning visibility work around a listing.

CoinGecko and CoinMarketCap are separate platforms with separate forms and review decisions. A listing on one does not mean the other will approve the same project, so prepare a platform-specific evidence file for each. After the profile is live, check that its public details match your approved sources and submit a correction through the appropriate channel if you find an error. If your next goal is discovery rather than application readiness, read our guide to CoinGecko trending and evaluate that as a separate activity.

For a working review, MarketingExtra can check the application field by field, flag conflicting source data, and return a clear list of items to resolve before submission. Send 3 things: your project website, your contract or asset details and your market links. Add any CoinGecko correspondence and we tell you the practical next step.

How it works

1. Collect the source materialGather the official website, channels, asset and contract details, supply explanation, and market links. Use sources your team can keep current.
2. Check consistencyCompare names, tickers, addresses, and supply wording across the form and public pages. Resolve contradictions before applying.
3. Complete the current formFollow CoinGecko’s latest submission instructions and answer relevant fields with direct evidence. Save a copy of what you send.
4. Monitor for a responseAssign an owner to check the appropriate inbox and prepare to answer clarification requests with specific sources.
5. Verify the public profileIf a profile is published, compare its visible details with your authoritative project information and report any factual discrepancy through the appropriate route.