How to resolve a CoinMarketCap or CoinGecko listing warning

What does a CoinMarketCap or CoinGecko listing warning mean?

A listing warning indicates that a platform wants attention directed to an aspect of an asset’s profile or the information used to assess it. The notice itself—not a general assumption about the project—should determine what you investigate first.

Teams often encounter notices connected to supply details, trading markets, contract or chain information, project links, or a change in the asset’s status. Treat these as areas to check, not as a universal list of platform warning categories: each platform may display different wording and request different evidence.

Record the notice before changing anything. Capture the full text, the affected listing page, the date you saw it and any instructions or links shown with it. Then compare the relevant profile fields with the project’s official sources and on-chain information. If the notice does not identify the issue clearly, ask the platform through its official support or listing channel what specific field or evidence needs attention.

This approach is useful whether you are reviewing a CoinMarketCap listing or learning how to get listed on CoinGecko. A warning is not a reason to rewrite every project claim: fix the discrepancy the platform has identified and leave unrelated fields intact.

How should you diagnose a listing warning before making changes?

Diagnose the notice by matching its wording to a specific profile field, source of data or project update. A written issue log helps the team avoid speculative edits and keeps the review request coherent.

Use this checklist:

• Save the full notice and note which asset, network and profile it refers to.
• List the affected claims or fields, such as circulating supply, total supply, contract address, market pair or official project URL.
• Compare each claim with its primary source: the relevant explorer, official project site, exchange or pool page, and published project documentation.
• Mark each item as confirmed, outdated, inconsistent or not yet verifiable.
• Assign an owner and record the correction made, where it was made and what evidence supports it.

Check whether the discrepancy comes from the listing itself or from a source it relies on. For example, a project may have corrected its website while a linked document still shows an older contract address. Sending a request before the underlying public sources agree can create more questions instead of resolving the original one.

Do not infer that a warning is caused by a ranking position or a trending campaign. Listing review and visibility placements are different matters. If both are relevant, address the profile issue first; see the separate guides to CoinMarketCap trending and CoinGecko trending for those mechanics.

How do you verify supply and contract information on CoinGecko?

To verify supply information, make the project’s stated figures traceable to the correct contract and chain, then ensure the public materials explain how those figures are calculated. The platform’s requested evidence and accepted presentation remain authoritative for its own review.

Begin by confirming the asset’s contract address on the project’s official channels and the relevant block explorer. Check that the listing points to the intended network and contract, especially after a migration or deployment change. Next, compare the figures shown on the listing with the project’s token documentation and the information that can be checked on-chain. If circulating supply differs from total or maximum supply, explain the distinction plainly and support it with the appropriate source.

Before submitting, prepare a compact evidence set:

• Contract address and explorer page for the correct network.
• Current token documentation with definitions for each supply figure.
• A short explanation of any locked, vested, burned or otherwise excluded tokens, if relevant and verifiable.
• Links to the exact listing fields that need correction.

For a focused workflow, use the guide to verify supply on CoinGecko and review the project’s listing profile remediation options. Avoid sending unexplained spreadsheets or changing supply descriptions to make figures appear consistent; explain the actual methodology and let the evidence support it.

Which market and project details should you check?

Review the markets, project identity and public links that appear on the affected profile, then verify each against a current primary source. A correct token contract does not by itself confirm that every market or project detail remains current.

For markets, check that the listed pair and venue still correspond to an active, relevant market for the asset. Confirm that the pair uses the correct token and quote asset, and that the project has not moved liquidity to a replacement pool or contract. If a market is inactive or points to an obsolete pool, document what changed and identify the current source rather than leaving an outdated reference unexplained.

For project information, review the website, official social profiles, chain details, ticker and token name. Look for old links, conflicting token symbols, an outdated roadmap or announcements that describe a migration without clearly identifying the new contract. Make the project’s own channels consistent before asking a platform to update its profile.

Use a simple change log with three columns: field as displayed, verified current source, and action taken. This gives the reviewer a direct path from the reported issue to the correction. For initial listing context, compare the broader CoinGecko listing requirements with the CoinMarketCap listing guide; do not assume one platform’s process automatically applies to the other.

What should a platform review request include?

A strong review request identifies the affected listing, states what changed and links directly to evidence that supports the correction. Keep it factual and organized so a reviewer can verify the issue without reconstructing the project’s history.

Include the asset name and ticker, chain and contract address, the URL of the relevant listing, the exact warning or field under review, and a concise description of the correction. Add only the evidence needed for that issue: for example, an explorer page for contract details, current token documentation for supply methodology, or the official project page for a corrected link. If a migration or market change is involved, explain the sequence and distinguish the old reference from the current one.

A useful request structure is:

1. Identify the listing and quote or summarize the displayed issue.
2. State the verified correction in one or two sentences.
3. Link each key claim to its primary source.
4. Note any profile fields already updated by the project.
5. Ask whether any additional evidence is required.

Use the official submission route for the relevant platform and retain a copy of the request and attachments. Avoid sending repeated messages with different explanations while the same request is under review. If the issue requires broader coordination across project data, supply evidence and listing communications, a profile remediation service can help organize the work. Guided projects start at $1,300 / project.

What can the project control during CoinMarketCap or CoinGecko review?

The project controls the accuracy of its own materials, the evidence it submits and whether it responds to a request for clarification. The platform controls its review, data treatment and any decision to change a notice or listing status.

This distinction matters because fixing a source does not itself change a platform’s display. CoinMarketCap and CoinGecko have separate listing processes, support routes and review decisions; a correction accepted by one does not automatically update the other. A profile field may also draw on external market or project data, so identify the source of the discrepancy before assuming the platform can edit it directly.

No outside adviser can promise that a platform will remove or change a warning, accept a particular evidence format, or complete review by a chosen date. The platform may request more information or keep its current display after reviewing the submission. What a project can reasonably require from an adviser is an agreed scope of work: diagnosis, evidence organization, correction guidance and submission support—not control over the platform’s decision.

To keep the process accountable, agree in advance on the deliverables, who owns each project-side correction, which official channel will be used and how status updates will be shared. Keep the underlying evidence available after submission, and respond to follow-up questions with the same documented facts rather than creating a new account of events.

How can you reduce the chance of another listing issue?

Maintain a small, owned record of listing facts and review it whenever the project changes its contract, supply information, markets or official links. A listing profile is easier to keep consistent when updates are treated as part of launch and post-launch operations, not as a one-time submission task.

Assign an owner for each source of truth: contract and chain details, token supply documentation, official project links, and market references. When one changes, update the project’s public materials first, then check whether the affected listing needs a separate update request. Keep dated copies of important documentation and a change log that records what changed and why.

A practical maintenance checklist includes:

• Confirm that contract and chain details still match official project channels.
• Review supply definitions and supporting sources after material token changes.
• Check that project links resolve to current pages and accounts.
• Revisit markets after migrations, pool changes or venue updates.
• Keep listing submissions and platform correspondence accessible to the responsible team.

For teams also comparing discovery options, understand that a listing correction is not the same as a visibility campaign. Read about CoinGecko trending or CoinMarketCap trending separately, and base any campaign decision on its own objectives. Keeping that distinction clear helps teams prioritize data accuracy before promotional activity.

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. Capture the noticeSave the full text, the affected listing URL and the relevant asset and chain details. Keep the wording available for every person working on the issue.
2. Trace the underlying sourceMatch the notice to the profile field or data source involved. Compare it with primary project, market and on-chain references before editing the listing.
3. Correct and documentUpdate inaccurate project-controlled information and record the change. Prepare only the evidence that supports the specific correction.
4. Submit through the official routeIdentify the listing, explain the correction clearly and link to verifiable sources. Keep a copy of the request and any follow-up.
5. Track the review and maintain the recordAssign an owner to monitor replies and provide requested clarification. Preserve the evidence and update other project materials if the underlying facts change.