CoinGecko and CoinMarketCap listing remediation under one point of contact

Begin with the record the platform has marked

A listing notice identifies something that needs attention on an asset profile; its wording is the best starting point. It may concern supply information, a contract or chain reference, a market, project details, or a broader status. These are different situations, so a discreet first review avoids speculative edits.

Keep a copy of the notice, its location on the profile, and the listing URL. Note when your team saw it, then compare the wording with current project records. A screenshot is useful context, while copied text makes the issue easier to discuss internally. The aim is to identify a specific discrepancy, not to infer a reason the notice does not state.

If the asset has not been listed, an application is a separate matter. The CoinGecko listing guide and CoinMarketCap listing guide address preparation for those applications. For an existing profile, keep the record of the notice at the centre of the work.

A quiet review in five passes

A useful review moves from the visible notice to its source, then to a focused request. Keep one working record so the evidence and proposed correction remain aligned.

1. Record the notice. Copy its exact wording, the affected listing area, and the profile URL. Keep a screenshot as supporting context.
2. Locate the source. Compare the flagged detail with the project website, documentation, explorer references, and current records.
3. Correct what the project controls. Update inconsistent public materials and retain a clear note of what changed.
4. Prepare the evidence. Link directly to sources, explain what each one demonstrates, and identify any unresolved difference.
5. Shape the request. Name the asset, quote the notice, describe the correction, and state the review being requested.

A named contact can keep this sequence composed and discreet. If Premium Promotions is asked to assist, its review can identify gaps in the source material and shape a concise evidence package. Your team retains the decision on what to submit.

Let the evidence follow the source

Evidence is clearest when each statement points to a source that can be checked directly. Keep the explanation narrow, use consistent terms, and separate facts from estimates or internal assumptions.

Supply and contract references

For a supply concern, prepare a short reconciliation that defines the figures being discussed and links each to its source. Include the relevant contract and chain references. Explain any project-specific exclusions only when they apply, and make their basis visible. Do not present an estimate as an on-chain fact. The listing profile remediation service can help organize the source record and identify missing context.

Markets and project details

For a market concern, identify the venue and pair, then explain what has changed or what should be reviewed. For contract, chain, or project-information concerns, compare the profile with current official project materials. If a migration or other change matters, retain enough context to make old and current references understandable. Correct outdated links where the project controls them. A concise index helps a reviewer see what each source supports without searching through unrelated material.

What should you expect after submitting the request?

After submission, retain the exact request and evidence, then monitor the affected profile and the project-controlled sources. A separate request may be needed for each platform because one submission does not update the other listing. Keep each record distinct, even when the underlying project facts are shared.

CoinGecko and CoinMarketCap have their own review processes, channels, and profile displays. Their reviewers decide whether a correction is sufficient and whether a notice or status changes; a project cannot compel that outcome. Our role, where engaged, is to help make the factual case legible and keep the submission aligned with your approved material.

If a platform asks for clarification, respond to the point raised and add relevant evidence rather than resending the whole package. Avoid follow-up messages that add no new facts. This keeps the correspondence orderly and gives your named contact a clear record of what has been provided.

A considered hand-off, with clear timing

A well-prepared file makes the work easy to follow: the notice, the correction, and the supporting source sit together. If Premium Promotions assists, one named point of contact coordinates the material with your team. Draft wording is shown to you first; nothing is submitted on your behalf without your written sign-off.

This arrangement keeps confidential material separate from public evidence. Share only records needed to explain the notice; private keys, credentials, and unrelated personal information do not belong in the file. The listing remediation pricing guide explains the separate question of service pricing.

Keep the public record composed

Routine ownership of listing details makes later corrections easier. Assign someone on the project team to know the source for each public field. Revisit those sources after a material change to the contract, chain, supply description, project links, or active markets.

CoinGecko and CoinMarketCap control their review decisions and the wording or display of notices. Even a carefully sourced correction cannot ensure that either platform changes a profile or removes a notice. The project can control the accuracy of its own materials and the clarity of its request.

A quiet internal check can be as simple as confirming that:

• The listing, website, and documentation use consistent project details. - Current contract and chain references are easy to verify. - Superseded market or project references are clearly explained.

With the listing URL and exact notice, your named contact can identify the source records to assemble next, keeping the material confidential until your sign-off.

How it works

1. Record the noticeCopy its wording and note the affected listing area. Keep the profile URL and a screenshot for context.
2. Trace the sourceCompare the flagged detail with current project records, public materials, and relevant contract or market references.
3. Correct and documentUpdate information the project controls and retain a clear account of each change.
4. Prepare the requestQuote the notice, explain the correction, and link to evidence that can be checked directly.
5. Submit and monitorKeep the submission record and respond to any platform request with relevant additional facts.