How to address a warning on a CoinGecko or CoinMarketCap listing

What kinds of CoinGecko and CoinMarketCap listing warnings appear?

A warning is best understood by its exact wording and the listing field or data feed it refers to. CoinGecko and CoinMarketCap operate separate listing and data systems, so do not assume that the same label has the same cause on both platforms. First capture the notice, the asset page, and the date you saw it.

Common areas to investigate include:

• Supply information: the displayed circulating or total supply may not match the project’s published methodology or on-chain evidence.
• Market data: a market or pair may be inactive, incorrectly mapped, or reporting information that no longer reflects the current venue.
• Contract or network details: a contract address, chain, migration, or token version may be unclear or out of date.
• Profile information: links, project descriptions, names, or other public details may conflict across official sources.
• Data integrity concerns: a platform may ask for clarification when available information appears inconsistent or cannot be independently checked.

These are investigation categories, not a claim that every platform uses the same warning taxonomy. Do not guess at the trigger from a screenshot alone. Record the exact platform, token page, notice text, and any linked help article. If the notice is unclear, organize your evidence around the field in question rather than sending a broad message about the whole project.

How do you find the source of a CoinGecko or CoinMarketCap warning?

Find the source by tracing each disputed listing field back to the most direct, current evidence. A useful diagnosis distinguishes a project-side error from an exchange, explorer, or platform display issue before anyone edits metadata or submits a correction.

Use this sequence:

• Save the warning text and the public listing URL. Note which asset, chain, or market it concerns.
• Identify the specific claim that appears disputed: supply, contract, market, name, website, or another profile field.
• Compare the listing with project-controlled sources, such as the official website, token documentation, verified contract page, and current exchange market page.
• Check whether the source itself is current. A link to an old contract or a retired pool does not substantiate the present listing.
• Write down what differs, where the authoritative value can be checked, and what correction you propose.

Keep facts and interpretation separate. “The listed address differs from the current verified contract” is more actionable than “the listing is wrong.” If the notice concerns circulating supply, use the methodology and evidence described in how to verify supply on a token listing. If the issue is a broader profile mismatch, a listing profile remediation review can help turn scattered records into a focused correction package.

How to verify supply on CoinGecko before requesting a correction

Verify supply by documenting what each supply figure means and how it can be checked. A single number without a definition is rarely enough to resolve a discrepancy, especially when tokens are locked, vested, bridged, or held across several contracts.

Prepare a short supply note that covers:

• The figure in question: quote the platform’s displayed value and identify whether the concern is circulating, total, or another supply field.
• The contract and chain: list the relevant addresses and link to a public explorer page for each one.
• The calculation method: explain which balances are included or excluded and why. Avoid presenting an estimate as a verified on-chain total.
• Special allocations: identify locked, vesting, treasury, bridge, or other balances only where they affect the stated method. Link to verifiable records where available.
• Consistency across sources: compare the project website, documentation, explorer information, and token data submission. Update outdated project-controlled pages before resubmitting.

A good correction makes it possible for a reviewer to reproduce the logic without relying on private assurances. If a supply figure cannot be derived from public records, state that limitation and clarify which records are available. Do not change several unrelated figures at once: isolate the supply correction so the reviewer can see what changed and why. The supply verification service covers evidence organization for this type of listing issue.

Could a market or data feed be behind the listing notice?

Yes. A listing can display market information that needs investigation even when the project’s own profile is accurate. Check the actual venue, pair, token address, and current data source rather than assuming that a notice calls for a marketing or liquidity response.

Review each affected market individually. Confirm that the venue still supports the pair, that the pair points to the correct token and quote asset, and that the public page is accessible. Look for a renamed market, an old pool, a migrated contract, or a venue page that no longer represents active trading. If an exchange has changed its data endpoint or discontinued a pair, document that fact and identify the current source rather than describing the old market as live.

Keep a simple table in your working file:

If several markets are affected, separate them by venue. A list of links with no explanation makes review harder; a short note for each market shows exactly what the platform should verify.

What should you check after a contract migration or profile change?

After a migration, rebrand, or project update, check every public reference that could still point to the previous asset or identity. The objective is to make the current project details consistent and easy to verify, not to erase legitimate historical information.

Start with the listing’s contract address, chain, token name, ticker, website, and social links. Compare these with the project’s official announcements and current documentation. Then inspect the explorer page and market pages linked from the listing. If the project has migrated, state which contract is current, when the change was communicated, and whether holders need to take any action. Do not imply that an old contract is current simply because it still has historical activity.

Before requesting an update, check that project-controlled pages have already been corrected. Use stable, public links and make sure they load without a login. Where a name or symbol is shared with another asset, clearly identify the chain and contract instead of relying on the ticker alone. If the project has changed its website or official channels, update those references consistently and preserve an announcement explaining the transition. For a listing application or broader profile update, see the guides to getting listed on CoinGecko and getting listed on CoinMarketCap.

How should you prepare a listing profile remediation request?

Prepare one concise request for each platform, tied to the exact notice and the correction the project is asking it to review. A reviewer should be able to identify the asset, reproduce the relevant checks, and understand what changed without searching through unrelated campaign material.

Include these items:

• The platform name, listing URL, token name, ticker, chain, and relevant contract address.
• The exact warning text or affected field, copied accurately where possible.
• A brief explanation of the underlying cause and the correction already made, if applicable.
• Direct evidence links, with a short description of what each link demonstrates.
• A clear request, such as checking a corrected contract mapping or reviewing documented supply methodology.
• A contact who can answer factual follow-up questions.

Use a neutral tone. Avoid repeated submissions that say the same thing, unsupported claims about why the warning appeared, or requests for a particular review outcome. Keep a copy of the submitted message and the evidence version you used. If the platform asks for more information, answer the new question directly and add only the relevant records. For a structured review of the evidence and submission, see listing profile remediation and the guide to remediation costs.

What can you control while CoinGecko or CoinMarketCap reviews a warning?

You control the accuracy and completeness of your evidence, the corrections made to project-controlled information, and the clarity of your follow-up. You do not control how either platform classifies a notice, the outcome of its review, its response time, or when a public display changes. No service can promise that a platform will remove or alter a warning; the work that can be agreed is the investigation, correction package, and submission support.

This distinction matters because a platform may request additional information, keep a notice in place, or update a listing on its own schedule. A project should not describe a submitted request as an approved change until the public listing reflects that change. Nor should it alter on-chain or market information merely to match a displayed value without first confirming which figure is correct.

While a review is open, keep a current record of project-side facts and monitor the listing for changes. If you discover new evidence, add it in a focused follow-up that explains why it matters. Avoid flooding the platform with duplicate messages or turning a data correction into promotional copy. A clean record of the notice, correction, evidence, and response lets the team communicate accurately with holders and partners while the platform review is pending.

How can a project reduce the chance of another listing discrepancy?

A lightweight listing maintenance routine helps catch stale information before it becomes a public issue. Assign an owner for token data and make the owner’s checklist part of contract, market, and communications updates.

Review the public listing against the project’s authoritative sources whenever a material detail changes. That includes a contract migration, new chain deployment, market discontinuation, supply-method update, website change, or official-channel change. Keep a source-of-truth document with current addresses, supply definitions, official links, and market pages. Record who approved each change and where it was announced. This makes future corrections faster and avoids different team members sending conflicting details.

A practical routine is to:

• Confirm that contract and chain references still point to the intended asset.
• Check that public market links represent current venues and pairs.
• Reconcile supply language across documentation and project pages.
• Test that official website and social links remain accessible and current.
• Preserve dated announcements for migrations or other material changes.

Treat these checks as data hygiene, not a promise that a platform will display every update immediately. For a new application, use the appropriate listings and verification resources; for an existing issue, keep the correction narrow, evidenced, and easy to review.

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 exact wording, listing URL, affected field, and date you observed it. Keep the CoinGecko and CoinMarketCap cases separate.
2. Trace the disputed detailCompare the listing with current project records, explorers, and venue pages. Identify the source of the mismatch before editing or submitting anything.
3. Correct project-controlled sourcesUpdate outdated contract, supply, market, or profile information on the project’s own channels and document what changed.
4. Build the evidence packUse direct public links and a short explanation of what each one verifies. Keep the request focused on the affected field.
5. Submit and trackSend the correction through the appropriate platform channel, preserve the submission, and answer any follow-up with relevant evidence.