A clear next step for a CoinGecko or CoinMarketCap listing warning

What is the notice asking you to look at?

A listing warning points you toward information that needs attention, but it may not explain every detail behind the concern. Your first job is to identify the field or display it refers to, then compare that with the project’s current public records.

Copy the notice exactly and save the page where you saw it. Note the platform, asset page, affected detail and any recent project changes. That small record gives your team a shared starting point. It also helps you avoid a broad request that leaves a reviewer guessing which fact needs checking.

Look at the wording alongside the listing itself. A notice connected to a supply figure calls for different evidence than one tied to a contract address, project link or market. If the wording does not identify a clear issue, ask for clarification before changing unrelated details. For the larger listing process, our guides to CoinGecko listings and CoinMarketCap listings explain how to prepare a profile. Here, keep the task narrow: identify what appears inconsistent and what source could confirm it.

When a public report meets an old listing detail

Say a volunteer who runs a fan group reaches the week an audit report is published. Members begin sharing the report, and someone notices that a listing page still shows a detail the team wants to check. The volunteer gathers the exact notice, the listing link and the project’s current public information before asking anyone to edit the page.

We’d help separate confirmed facts from assumptions. The report may help explain a project detail, but it does not automatically confirm every listing field. We’d compare what the notice names with the public records that speak directly to that point. If the issue concerns supply, the team should explain its supply categories and link records that support them. If it concerns a contract or network, the official project page and a relevant explorer record may help verify the current details.

That care matters because a busy community can pass around several versions of the same information. Keep one correction note that says what the current fact is, where it is published and which listing needs attention. If the question is specifically about supply, see our guide to CoinGecko supply verification for more context on preparing listing information.

Match each concern to a source people can check

A strong correction connects one listing detail to one clear source. Gather the records that support the specific change instead of sending a bundle of unrelated project material.

• Supply figures: Explain the supply category in question and link suitable public records. Keep the terminology consistent across your explanation and project materials.
• Contract or network details: Confirm the current address and network on an official project page, then compare them with a suitable explorer record.
• Project profile information: Check names, descriptions and official links against pages or channels the project controls.
• Market references: Confirm that the named market or pair is still available and represents the asset accurately.

Before sending anything, open every link without relying on a private account. Check that the project name, symbol, network and address agree wherever they appear. A screenshot can add context, but a live source is usually easier for someone else to inspect. Mark estimates and planned changes clearly; do not present them as confirmed facts. If the notice covers several fields, write a separate explanation for each one. For broader help with a profile correction, listing profile remediation can organize the notice and relevant fields. It can also help prepare a clear evidence package.

A simple sequence for CoinGecko and CoinMarketCap

Treat each platform as its own listing record. Even when the project fact is shared, the affected page, field and support route may differ. Prepare a distinct request for each platform involved.

1. Name the asset. Include the project name, symbol, network and contract address where relevant.
2. Quote the notice. Copy its wording and point to the affected listing page and detail.
3. State the correction. Say what appears inaccurate and what should be checked.
4. Link the evidence. Add a short note explaining what each public source confirms.
5. Keep a record. Save the message, submission reference and any follow-up in one shared place.

For example, suppose both profiles show an older contract address after a project change. Confirm the current address on project-controlled materials first. Then identify the page that needs attention on each platform. Send a separate, focused request with the relevant evidence. Check the current instructions on each platform’s official support site before submitting. Avoid duplicate requests unless the platform asks you to follow up. If a reviewer asks a new question, answer that point directly and attach the source that resolves it.

Keep your part clear while the listing is reviewed

You can make the facts, sources and request easier to check. Before submitting, confirm who on your team owns the contract details, supply explanation, official links and market references. Review each item against the current public record, and wait to submit a detail that is still changing.

A useful final check is simple: can someone open each link, see the relevant fact and understand how it supports the requested correction? Remove old addresses or conflicting figures from project-controlled materials where appropriate. Keep the notice and the evidence together so another team member can answer a follow-up without rebuilding the case.

CoinGecko and CoinMarketCap control their review decisions, any follow-up they request and how their listing pages appear. Clear evidence helps explain your correction, but it cannot require either platform to remove a notice or change a display.

Give the next profile check a clear owner

A shared source of truth makes future listing checks easier. Choose who keeps contract and network details, supply notes, official links and market references current. When one of those facts changes, update the project’s public information first, then check the relevant CoinGecko and CoinMarketCap pages.

A small change log can hold the platform, affected field, previous detail, corrected detail, evidence link and submission status. Keep it brief enough for a teammate to update. This is especially helpful when the person who first spotted the warning is not the person handling the listing request. For a wider view of listing preparation, browse our listings and verification resources.

If you want another set of eyes, Brand Community compares the exact notice with the listing fields and public evidence. We then return a prioritized correction checklist. Send the platform, asset page and notice text. We’ll identify what needs checking before you prepare the next submission.

How it works

1. Save the exact noticeRecord the platform, asset page, wording and affected detail. Keep the original notice beside your working notes.
2. Check the underlying factCompare the listing with current project materials and relevant public records. Mark anything that is not yet confirmed.
3. Correct project-owned informationUpdate inaccurate details on sources the project controls, where appropriate. Keep a note of what changed.
4. Connect evidence to the correctionLink each requested change to a source people can open. Check names, network and contract details for consistency.
5. Submit and track separatelyUse the current process for each platform, save the reference and answer any follow-up directly.