Explorer token info and logo updates: make the on-chain page clear

What does an explorer token info update change?

Quick test: Open your token on each explorer you use. Do the name and logo match your site? Write down each mismatch.

An explorer token info update helps visitors connect a token contract with the project’s public identity. Depending on the explorer and available fields, the page may display a token name, symbol, logo, description or links to official channels. The service is about preparing and coordinating that information—not changing the token contract or its on-chain activity.

A consistent explorer profile is useful when holders, partners or researchers open a contract page and need to identify the project. It also gives the team a practical place to catch mismatches between its website, social accounts and published token details. Review these basics before requesting an update:

• Use the exact contract address for the relevant network, copied from a trusted project source.
• Confirm that the token name and symbol match the project’s approved materials.
• Check that the website and social links resolve to accounts the project controls.
• Use a logo the project has permission to publish and that remains legible at small sizes.

The same preparation can support other listing work. If you are planning broader directory coverage, see listings and verification; for a separate DEX profile update, review DEXTools and DEXScreener profile updates.

What to prepare before requesting an update

A complete, internally consistent submission is easier to review than a collection of links and files assembled at the last minute. Start with the contract address and network, then gather the public sources that establish which project and token the request concerns. The exact fields and submission route can vary between Etherscan, BscScan, Solscan and Tonviewer, so we check the destination before formatting the request.

Prepare one source folder with:

• The contract address and network name, checked against the project’s own documentation.
• The preferred token name, ticker and a short, factual project description.
• A clean logo file and any requested supporting image assets.
• The canonical website and official social links, checked for spelling, ownership and access.
• A contact who can respond if the explorer asks for clarification or evidence.

Avoid sending alternate versions of the logo or conflicting descriptions without explaining which is current. If the token has changed name, migrated contracts or been rebranded, establish the relationship between old and new details first; our contract migration and rebranding update support may be relevant. For a project also preparing wallet-facing assets, see wallet logo and token list inclusion.

How the process differs across Etherscan, BscScan, Solscan and Tonviewer

The destination explorer determines where information is requested and which details it can display. We treat Etherscan, BscScan, Solscan and Tonviewer as separate destinations: the project supplies the same verified source facts, while the request is checked against the explorer’s current public process and available profile fields.

This distinction matters when a project is active on more than one network. A logo or social link update on one explorer should not be assumed to update another explorer automatically. Before the request, confirm the relevant network and contract for each destination, and keep a simple record of what was submitted and when. That record helps the team answer follow-up questions without mixing network-specific information.

MarketingExtra checks that the information package agrees across the project’s own channels and the selected contract page. We also flag practical inconsistencies, such as a social link that points to an old account or a project description that names a different token. We do not guess which details an explorer will accept; if the form or guidance leaves a requirement unclear, we identify the open question for the project team before submission. If an existing explorer profile has a separate issue, see listing profile remediation to assess that work.

What explorer update support includes and when it starts

Rule of thumb: Prepare one logo file and one fact sheet, then reuse them on all explorers.

Explorer update support covers the preparation and coordination needed to send a clear, consistent request. Work begins with a short review of the target explorer, contract details and existing public project sources, so the team knows what information is ready and what still needs confirmation.

Depending on the project’s needs, the work can include:

• A review of the contract address, network, token name and symbol supplied by the team.
• A check of the logo file, description and official social links for consistency.
• Formatting the information for the relevant explorer’s available submission route.
• Coordination of the submission and help organizing any requested clarification.
• A concise handover showing what was prepared, where the request was directed and what remains open.

To keep the work moving, assign one project contact who can confirm the final wording, provide access to any required project-owned account and respond to questions. The schedule starts once those materials are available; explorer handling and any request for additional evidence can affect completion. Before kickoff, MarketingExtra shares the required inputs and confirms the work plan. For additional verification needs, compare this service with circulating supply verification.

Your 6-point explorer update checklist

Tick these 6 points before you ask for an update. They give every explorer the same exact facts, so your token looks the same wherever a buyer checks it before trading. Keep the ticked list with your records, because it is the quickest way to explain later what was agreed.

• Open your token on each explorer.
• List every mismatch.
• Prepare the logo in the required size.
• Write a 3-line description.
• Collect official links, no extras.
• Prove ownership as each explorer asks.

Terms in one line

Explorer (in plain words: a website where anyone can look up blocks, wallets and tokens on a chain).

Token info update means a request to change the name, logo and links shown on a token's explorer page.

What the explorer can decide after a request

The project controls the accuracy of its submitted information and the quality of the materials it supplies; the explorer controls its own review and publication decisions. Etherscan, BscScan, Solscan and Tonviewer may apply different procedures, request further evidence or decline to display submitted details, so MarketingExtra commits to the agreed preparation and coordination work rather than a particular approval or publication outcome.

For a clean handoff, keep the approved logo, final description, official links and contract details together, and make sure the designated contact can respond during follow-up. If the explorer requests a change, assess it against the project’s verified sources rather than making an unsupported claim to get the page updated. Teams handling a wider listing plan can coordinate this work with CoinMarketCap listing support or CoinGecko listing support, while keeping each platform’s request distinct.

Send 3 things: your contract address on each chain, your logo files and your official links. With those, we prepare the requests and confirm the cost in writing before work starts.

How it works

1. Share the target and contractSend the explorer name, network and contract address, plus the project’s official website and social accounts.
2. Gather the source materialsProvide the approved token details, logo file and a project contact who can verify the information.
3. Review consistencyMarketingExtra checks the supplied details against the project’s public sources and flags gaps or conflicting versions.
4. Prepare and coordinate the requestWe organize the agreed materials for the relevant explorer and support the submission and any follow-up.
5. Hand over the recordYou receive a clear summary of what was prepared, where it was directed and which items remain open.