How to get listed on CoinMarketCap: prepare a review-ready application

What should be ready before a CoinMarketCap application?

Before you apply, make sure a reviewer can identify the asset, understand where its information comes from, and find the same core facts across your public materials. Readiness is not a claim that CoinMarketCap will accept the project; it is a way to avoid preventable gaps and contradictions.

Start with a compact internal checklist. Confirm that the project name and ticker are used consistently, the official website and social channels are accessible, and the asset’s network and contract details are stated clearly where relevant. Gather links to public market information and any project documentation that supports what you submit. Then have someone who did not prepare the materials check whether each statement can be traced to a source.

Before opening the form, ask:

• Are the project’s official links clearly identified and current?
• Do the asset details match the information shown on the relevant network and public market pages?
• Can the team explain any recent change, migration, or naming difference in plain language?
• Is there a named contact who can respond to a follow-up?

If important facts are still changing, resolve them first. For broader platform-readiness context, see our listings and verification guide and CoinGecko listing guide.

Build an evidence pack that makes project details easy to check

An evidence pack is a concise set of current links and records that supports the details in your application. It helps your team submit one coherent account of the project and makes it easier to answer a reviewer’s question without reconstructing the history from chat messages.

Organize the pack by topic rather than by the order files happened to arrive. A simple index can point to the project’s official identity, asset and network details, public market references, supply information where applicable, and supporting documentation. For each item, record its source, the date your team checked it, and the person responsible for keeping it current. Do not add claims merely because they sound persuasive; include information that is relevant and can be substantiated.

Use a final consistency pass before submission:

• Compare names, tickers, network references, and links across every item.
• Check that public pages load and lead to the intended project or asset.
• Note differences between current information and older announcements, then explain them briefly.
• Remove duplicate or superseded files so the reviewer is not left choosing between versions.

Keep the working pack private to the project team and share only what the form or a legitimate follow-up calls for. This is a practical record, not a substitute for CoinMarketCap’s own review criteria.

How do you complete the CoinMarketCap listing form carefully?

Complete the current CoinMarketCap submission form from verified project records, not from memory or copied promotional text. The form is the formal way to present the request; your job is to make every answer precise, consistent, and easy to support.

Assign one person to coordinate the submission and one knowledgeable reviewer to check it before it goes in. Use the evidence pack to answer each field, and keep a copy of the submitted information and any confirmation or reference details. If a field is unclear, consult the instructions shown in the form or official CoinMarketCap support resources rather than guessing what a reviewer wants to see.

A useful review pass checks three things:

• Identity: project and asset names, ticker, and official links are consistent.
• Support: factual statements have a source the team can point to.
• Clarity: explanations use direct language and distinguish current facts from plans.

Avoid sending repeated applications with slightly different information. If something material changes after submission, document what changed and prepare a concise explanation for the appropriate follow-up channel. For hands-on form preparation and evidence review, MediaStrategy uses a kickoff checklist to confirm ownership, source links, and unresolved discrepancies before the application is assembled.

How long does CoinMarketCap listing review take?

There is no reliable date to promise for a CoinMarketCap decision from the information available to a project applicant. The review and any listing update are controlled by CoinMarketCap, and the project should plan for an open-ended wait rather than treat submission as a scheduled launch event.

Separate the work your team controls from the platform’s review. You can set an internal deadline for completing the evidence pack, assign a contact to monitor official communications, and prepare a short response process for questions. You cannot set the platform’s queue, its review pace, or the timing of a decision. Avoid building a public announcement around an assumed listing date; communicate only confirmed status.

A practical operating plan looks like this:

• Submit once the application has passed an internal consistency check.
• Keep the submission record and official correspondence together.
• Check the designated contact channel on a regular team schedule.
• If asked for information, answer the exact question and attach only relevant support.
• Update public messaging only after a status change is confirmed.

This approach keeps the application from becoming a last-minute dependency for a token launch. If listing work is one part of a broader launch plan, coordinate it with the token launch checklist and review the separate CoinMarketCap listing service scope.

Why might a CoinMarketCap application be rejected?

A rejection means the project has not received the requested listing outcome; it does not, by itself, explain which part of the application needs attention. Read the response closely, preserve its wording, and identify whether the issue concerns missing information, inconsistent project details, or a readiness concern that requires a substantive change.

Do not respond by sending the same application again with cosmetic edits. Build a short issue log that records the point raised, the evidence reviewed, the owner of the fix, and what changed. If the response is not specific, prepare a focused clarification through the appropriate official channel. Keep the tone factual, and avoid arguing from promotional claims or implying that a platform decision is owed.

Before any follow-up, check:

• Does the response identify a field or piece of supporting information to correct?
• Have the underlying public records or project materials actually changed?
• Can you explain the correction without contradicting the original submission?
• Is a new application appropriate, or should the team first seek clarification?

A rejection can also reveal a real mismatch in the project’s public information. Correct that source material first, then make sure the application reflects the updated facts. If the issue concerns a profile or project data already visible on the platform, the relevant next step may be CoinMarketCap profile remediation, rather than starting over.

Is a CoinMarketCap listing the same as CoinGecko or trending visibility?

No. A listing request, a CoinGecko listing, and a visibility placement are different activities, with different platform processes and outcomes. A CoinMarketCap listing application asks CoinMarketCap to review project information; it does not purchase a position in a trending area or guarantee attention from users.

The comparison often phrased as “CoinGecko vs CoinMarketCap listing” is most useful when treated as a planning question: which platform’s application is the team preparing, and what information does each current form ask for? Do not assume approval on one platform carries over to the other. Review each platform’s own current instructions and submit information tailored to that request.

Trending campaigns are also separate from listing readiness. A project can plan for a listing review without commissioning a visibility placement, and a placement does not replace an application or determine its outcome. If you are comparing those goals, read the distinct guides to CoinMarketCap trending and CoinGecko trending before choosing a campaign.

Keep the sequence disciplined: establish accurate public project information, prepare each platform application on its own terms, and plan visibility activity separately. That separation makes it easier to explain what has been submitted, what has been approved, and what remains a marketing activity.

What does assisted CoinMarketCap application preparation cover?

Assisted preparation should make the application clearer and easier for your team to manage; it cannot replace the platform’s review. For teams that want structured support, MediaStrategy starts with a kickoff checklist covering asset identity, official source links, available records, application ownership, and open questions.

The work can then be organized into practical deliverables: a readiness review, an evidence-pack index, a consistency check across supplied materials, form-preparation support, and a follow-up file for correspondence. The exact scope should be agreed before work begins, especially if the project has a migration, a recent change in identity, or gaps in its public information. Assisted preparation from MediaStrategy is available from $6,000 / project.

A useful handoff leaves the project team with a clear record of what was checked, which sources support each key detail, what remains unresolved, and who is responsible for the next action. Ask for a written scope that distinguishes document preparation from work controlled by CoinMarketCap. For related planning, compare the CoinMarketCap listing cost guide and the broader listings and verification hub.

To begin, send the project’s official website, asset and network details, relevant public market links, and any previous application correspondence. We will review the materials, flag gaps for your team, and agree the preparation scope before anything is submitted.

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. Confirm the asset recordGather current project identity, network, asset, and official-source details. Resolve inconsistent names or links before drafting.
2. Create the evidence indexOrganize the relevant public links and supporting records by topic, with an owner responsible for checking each source.
3. Review the current formUse CoinMarketCap’s current form and instructions. Answer from verified records, and flag unclear fields rather than guessing.
4. Run a second-person checkAsk a team member who did not assemble the application to compare its claims and links with the evidence pack.
5. Submit and manage follow-upKeep the submission and official correspondence together. Respond to specific requests with concise, relevant information.