Getting listed on CoinMarketCap: requirements, form and next steps in order

What a CoinMarketCap listing involves

Quick test: Compare your contract, supply and links across 3 places: site, docs and the form. They must match exactly.

A CoinMarketCap listing is a platform profile for a crypto asset; it is not an exchange listing and does not itself create trading activity. The practical goal of an application is to give reviewers clear, consistent information they can check against the project’s public footprint.

Before you start, identify the exact asset and the reason you are applying. Make sure your team can point to the project’s official website, public channels, token or contract information where applicable, and relevant market references. These are preparation materials, not a promise that any one item meets a platform requirement.

It is also useful to separate a listing request from other CoinMarketCap activity. A listing application is not the same as a CoinMarketCap trending campaign, a paid visibility placement or advertising. If your immediate goal is a profile update rather than a new listing, review whether the request should instead be handled as a listing profile service.

Write a one-paragraph internal summary before applying: what the asset is, how it can be identified, where to verify its details and which official channels belong to the project. If the team cannot answer those points consistently, pause and fix the underlying materials first.

What to check before you apply

A strong application starts with a consistent public record. Before opening the form, check that the project’s identity and asset details match across its website, social channels, explorer references and market pages that you control or can verify.

Use this preparation list:

• Project identity: Confirm the project name, ticker, website and official social accounts are written consistently.
• Asset details: Check the network and contract address, if the asset has one, and make sure public references point to the correct asset.
• Market references: Gather links to relevant trading venues and verify that the asset can be identified there without ambiguity.
• Supply information: Be ready to explain the supply figures you publish and where a reader can check them.
• Public communication: Make sure the website and official channels explain the project clearly and are accessible.
• Ownership and contact: Decide who is authorized to submit the request and who can answer follow-up questions.

This list helps your team remove avoidable inconsistencies; it is not a substitute for CoinMarketCap’s current criteria. Compare your package with the platform’s current CoinMarketCap information and support resources before submission. For another directory, use the separate CoinGecko listing guide, since its process should not be assumed to match CoinMarketCap’s.

How do you complete the listing form?

Complete the CoinMarketCap form with concise, verifiable information and make every answer consistent with the project’s public sources. The exact fields can change, so follow the live form rather than relying on an old checklist copied from another team.

Prepare a working document before you submit. For each requested detail, record the answer, its source and the person responsible for confirming it. Where a field calls for a link, use the most direct public reference available; where it asks for an explanation, state the facts plainly and avoid promotional claims that cannot be checked. Do not leave teammates to reconcile conflicting names, addresses or supply descriptions during submission.

Before sending, have someone other than the form’s author compare the application with the public pages. Check URLs for access, confirm that the correct asset is selected wherever the form asks, and remove outdated references. Save a copy of the submitted answers and any confirmation or case details the form provides.

For help with an application package, MarketingExtra reviews the project’s materials line by line, flags inconsistencies and returns a practical correction list before submission. If you need to compare listing approaches, the CoinMarketCap and CoinGecko comparison can help your team plan each request separately.

Your 7-point CoinMarketCap application checklist

Complete this checklist before you submit. A clean application is mostly about facts that agree with each other, so check every line twice.

• Open the current form and read all of its fields twice.
• Confirm name, symbol, contract and chain.
• Check supply facts and name 2 sources for each.
• List official links that all agree: at least 3 of them.
• Prepare a short, plain project description of 100 words.
• Prepare 1 trading venue link.
• Save a dated copy of the submission.

Terms in one line

Application route: the official page or form where a platform accepts listing requests.

Rejection reason (in plain words: the platform's note explaining what to fix before you try again).

Planning the listing timeline

Plan the work as a sequence of preparation, submission and follow-up rather than as a launch date tied to an expected listing. The preparation stage is the part your team can schedule: collect accurate details, resolve public inconsistencies, assign an authorized submitter and review the final package.

After submission, keep the record in one place. Note when the request was sent, which version of the materials was included and whether the form provided a reference or confirmation. Assign one contact to monitor the project’s official inbox and route any follow-up to the people who can verify the requested details. This prevents conflicting responses from different team members.

If your launch calendar includes several directories, create a separate task and evidence folder for each platform. Do not assume that a completed CoinMarketCap form also completes an application elsewhere. Use the listings and verification hub to map related work, then keep owners and next actions distinct.

A useful planning rule is to finish the public information before you submit, not while the application is pending. That gives your team a clean baseline and makes it easier to explain any later change to project details.

Why an application may be rejected

Common mistake: Treating a rejection as the end. Read the reason, fix the data, and apply again when ready.

A declined application is a signal to review the submitted information and the project’s public references, not a reason to resend the same package unchanged. Start by checking whether the platform provided a specific explanation or requested additional details.

Work through the likely sources of confusion in the materials you control:

• The project name, ticker, network or contract details differ between pages.
• A supplied link is inaccessible, outdated or points to a different asset.
• Trading or supply information is difficult to reconcile with public references.
• The application is incomplete, vague or written in promotional language rather than verifiable facts.
• The project has changed since the information in the request was prepared.

These are practical checks, not a claim about CoinMarketCap’s internal review rules. Record the response, compare it with the original submission and correct only what you can substantiate. If the reason is unclear, use the platform’s official support route to ask what information is needed; do not send repeated requests with no material change.

A project can also use a neutral second review before resubmitting. MarketingExtra can compare the form answers with the public sources, mark discrepancies and help prepare a clear response to any specific information request.

How listing differs from trending

A listing request concerns whether an asset should have a profile on CoinMarketCap; trending is a separate visibility topic. They serve different goals, so a campaign or placement should not be treated as a substitute for an application or as evidence that a profile will be approved.

If the asset is not listed, focus first on accurate identity details and a complete application. If the profile already exists and the goal is to increase visibility, define that objective separately and review the relevant product or campaign details. Avoid building a plan around a search phrase such as “coinmarketcap popular coins” without first identifying the feature and outcome you actually mean.

The same distinction matters when comparing platforms. A CoinGecko listing request and a CoinMarketCap request should be prepared as separate submissions, while an advertising placement is a different activity again. The CoinMarketCap listing service overview explains listing-related support, and the CoinMarketCap listing cost guide is the relevant place to check pricing information.

Write down the intended outcome before allocating team time: profile coverage, correction of existing profile information or a separate visibility campaign. That simple decision keeps the request focused and helps you choose the right next step.

What to do next

Your next step is to assemble a small, source-backed application file and compare it with CoinMarketCap’s current form. The file should help the submitter answer accurately without searching through team chats or guessing which public link is authoritative.

Include the project’s preferred name and ticker, relevant network and contract details, official website and channels, market references, supply explanations and a contact who can verify each item. For every entry, note its source and whether it has been checked recently. Keep a separate list of unresolved questions; do not fill gaps with assumptions just to complete the package.

Then ask a colleague to check the form against those sources. If you find differences, correct the public information first or explain the discrepancy plainly where the form allows. Once the request is submitted, preserve the exact answers and any confirmation details so that future follow-up refers to the same record.

If you want an outside review, send MarketingExtra the project links, asset identifiers and any previous response from CoinMarketCap. We will check the materials against one another, return a concise list of corrections and help you prepare the next submission step.

What an application cannot control

Your team controls the accuracy and completeness of its application but does not control CoinMarketCap’s review decision, eligibility assessment or response timing; it cannot require a particular outcome by adding promotional language or submitting the same request again. CoinMarketCap assesses whether the asset meets its current listing criteria and whether the submitted information supports a profile; a complete package may make the facts easier to review but it does not settle that assessment or set a response date. Keep the request marked pending in launch plans until the platform responds, preserve the submitted answers, and avoid announcing an approved listing before confirmation. If CoinMarketCap identifies a specific information gap, correct the relevant source material you control and use its official follow-up route rather than changing unrelated details.

How it works

1. Confirm the assetAgree on the exact project name, ticker, network and contract details. Identify the official website and channels the team will use as sources.
2. Gather public referencesCollect the links and explanations needed to support the information in the application. Resolve inconsistencies before opening the live form.
3. Complete the current formFollow the fields shown by CoinMarketCap and answer in verifiable language. Assign one authorized submitter and a colleague to check the answers.
4. Save the submission recordKeep a copy of the answers, the date submitted and any confirmation details. Give one team member responsibility for monitoring official correspondence.
5. Review and respondIf CoinMarketCap asks for information or declines the request, compare the response with your saved application and address the stated issue before taking the next step.