What does a warning on CoinGecko or CoinMarketCap tell you?
A warning tells you that a listing needs attention, but the wording and affected profile can vary. Start by recording the exact text, where it appears, which asset or market it concerns, and when you first noticed it. Do not assume that every warning has the same cause or follows a shared platform taxonomy.
Separate the visible notice from your working diagnosis. For example, a mismatch between the listing and the project’s current contract is a data issue to investigate; an inaccessible website or obsolete social link is a profile-maintenance issue. These are practical diagnostic categories, not official labels used by either platform.
Before changing anything, save a screenshot and the relevant listing URL. Then compare the notice with the current project website, contract information, explorer records, and any market information that the listing shows. This preserves a clear before-and-after record and helps your team avoid making changes based on an incomplete reading.
If you are still establishing a profile rather than addressing an existing notice, use the separate guidance for CoinGecko listing requirements or CoinMarketCap listings.
Which listing issues should you check first?
Check the information a reader can verify publicly before drafting an appeal. A short, structured comparison is more useful than a broad claim that the listing is incorrect.
| Area to inspect | Compare against | Practical next step |
|---|---|---|
| Token identity | Contract address and network shown on the project’s official materials | Confirm the correct contract and make project references consistent |
| Supply information | Publicly available on-chain records and the project’s documented supply figures | Reconcile the figures and prepare a transparent explanation |
| Markets or trading references | The project’s current market information and any linked venue pages | Identify stale or incorrect references and document what changed |
| Profile details | Current website, project name, description, and public channels | Update obsolete information and ensure the links resolve |
| Project status | Current project communications and relevant technical changes | Explain a migration or other material change with dated records |
These checks help narrow the problem; they do not establish why a platform displayed a particular notice. Mark each item as confirmed, corrected, or unresolved, and keep the evidence beside it. For supply questions, the dedicated guide to verifying token supply can help organize the public records you will need.
How to remove a CoinGecko warning by fixing the cause
To address a CoinGecko warning, correct the underlying information you can verify and present the correction clearly. Begin with the notice and affected fields, then work through the contract, supply, project profile, and market references that could be relevant. Apply the same checks to a CoinMarketCap listing if its notice concerns similar information.
Use this order of work:
- Confirm the project’s canonical website and the contract address for the relevant network.
- Check that public descriptions, links, and current project details agree with one another.
- Reconcile supply statements with records that a reviewer can inspect, and explain any material distinction in plain language.
- Review whether the project has migrated, redeployed, or changed its supported network; make the relationship between old and current references explicit.
- Correct errors on project-controlled pages before asking the listing platform to review its record.
If you find several inconsistencies, resolve them as a set rather than sending separate, contradictory explanations. Do not conceal an unresolved discrepancy: describe what is known, what has been corrected, and what evidence is still being gathered. If the issue is a profile update rather than a warning, see listing profile remediation for the scope of that work.
What evidence helps verify supply and project details?
Useful evidence lets a reviewer compare the claim in your request with a public or project-controlled record. Build a small evidence pack around the specific discrepancy rather than attaching every document the team has collected.
For a supply-related concern, identify the relevant network and contract, explain which supply figure you are discussing, and link to the public record that supports it. If the project reports more than one supply measure, define each one and explain why the figures differ. The supply verification service covers a related verification need; it does not replace accurate project records.
For a profile or identity issue, provide the current official project page and the exact listing field that needs attention. For a migration, document the old and current contract references, the network, and the project’s explanation of how they relate. For a market reference, identify the affected market and describe the correction requested without asserting facts you cannot substantiate.
Prepare a dated change log with the old value, corrected value, and evidence for each change. Make sure links open without special access and that screenshots show enough context to identify the relevant page. If an attachment contains confidential information, do not include it unless the platform specifically requests it and the project has approved disclosure.
How should you submit a CoinMarketCap or CoinGecko review request?
A strong review request identifies the notice, states the correction, and points to evidence without asking the reviewer to infer what changed. Use the platform’s official support route for the relevant listing, and keep the request focused on that platform’s record.
Include these elements:
- Project name, listing URL, and the exact warning or field under review.
- A brief description of the issue and the correction already made.
- Direct links to relevant public records, project pages, or explorer data.
- A short explanation of any remaining difference, migration, or supply terminology.
- One clear request, such as reviewing a corrected field or reconsidering a notice.
The CoinGecko Support and CoinMarketCap Support sites are the appropriate starting points for current platform guidance. Keep a copy of the submitted text and attachments. If the platform asks for clarification, answer the specific question and add only the evidence needed to resolve it; repeating the original submission without addressing the request makes the record harder to assess.
What happens after you request a listing review?
After submission, maintain a single record of the request, any follow-up, and the listing’s visible status. Assign one project contact to monitor the official support channel and coordinate answers, so the team does not send inconsistent explanations from multiple accounts.
Check the listing against the same items you recorded at the start: warning text, profile fields, links, and any relevant market or supply information. If the notice remains, compare the platform’s reply with the evidence you provided and identify the precise unanswered point. Make a new correction only when it is supported by current records, then explain what changed since the previous request.
CoinGecko and CoinMarketCap control their review decisions, the wording or removal of a notice, and the timing of listing updates; a submitted correction cannot compel any of those outcomes. Keep the engagement limited to preparing accurate records, making agreed project-side corrections, and delivering a well-supported request. For a broader view of related work, browse listings and verification.
What should the project prepare before seeking remediation?
Prepare a compact case file before contacting the platform or engaging an adviser. It should let someone unfamiliar with the project understand the notice, see what was checked, and follow the evidence without relying on private explanations.
Project team provides:
- The listing URL, screenshot of the warning, and date observed.
- The canonical project website, relevant contract addresses, and supported networks.
- Current supply definitions and links to public records that support them.
- A concise account of recent migrations, contract changes, or profile updates.
- The platform’s prior correspondence, if any, and the team’s approved point of contact.
Remediation work should produce:
- A diagnosis that separates confirmed discrepancies from open questions.
- A prioritized correction list for information the project controls.
- An evidence pack and a draft request tied to the specific listing notice.
- A change log that can be used for follow-up and future profile maintenance.
At MegaSatoshi, a named review step checks the warning text against the listing and evidence pack before any request is drafted. The team can scope listing profile remediation from $1,400 / project. Send the listing URL, notice screenshot, and available contract or supply records; we will review the materials and confirm the proposed scope.
Prices
| Service | Price | Quote |
|---|---|---|
| Listing warning guide | from $1,400 / project |
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
- Capture the noticeSave the warning text, listing URL, screenshot, and date observed. Note whether it appears on CoinGecko, CoinMarketCap, or both.
- Compare public recordsCheck contract, network, supply, project links, and relevant market references against current project-controlled and on-chain information.
- Correct verified discrepanciesUpdate information the project controls and record what changed. Keep unresolved points explicit rather than presenting assumptions as facts.
- Assemble the evidence packCollect direct links, dated records, and a concise explanation that addresses the specific notice or listing field.
- Submit and trackUse the platform’s official support route, retain a copy of the request, and assign one contact to manage any follow-up.
Frequently asked questions
How do I remove a CoinGecko warning?
First identify the exact notice and the listing information it concerns. Check project details, contract and network references, supply evidence, and relevant market information; correct verified issues, then submit a concise request with supporting links through CoinGecko’s official support channel. Keep the request and any response in one case record.
Can a CoinMarketCap or CoinGecko warning be removed immediately?
There is no reliable way to determine the review outcome or timing from the fact that a request was submitted. The project can make its information accurate and provide clear evidence, but the platform controls its assessment and any visible change to the listing.
How can I verify supply on CoinGecko?
Start by identifying the relevant contract and network, then compare the supply figure being discussed with public on-chain records and the project’s own definition of that figure. Explain differences between supply measures rather than treating them as interchangeable, and provide direct links so the evidence can be checked.
What should I include in a listing-warning appeal?
Include the listing URL, exact notice, affected field, correction made, and direct evidence supporting the correction. If a migration or supply distinction is relevant, explain it briefly and attach the public records that show the relationship. A focused request is easier to assess than an unstructured collection of unrelated documents.
Does the same fix work for CoinGecko and CoinMarketCap?
The underlying project record may be relevant to both, but each platform has its own listing and support process. Check the notice and fields on each listing separately, tailor the evidence and request to the platform concerned, and avoid assuming that a response or profile change on one automatically updates the other.
What should I send before asking for listing profile remediation?
Send the listing URL, a screenshot of the notice, and the relevant contract or supply records you already have. Include any recent migration details and prior platform correspondence. This gives the reviewer enough context to identify the issue and propose a focused scope without asking you to assemble a broad, unrelated project dossier.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…