What information should Solana token metadata include?
Solana token metadata should give a person one clear, consistent way to identify the project. Begin with the token’s mint address: it distinguishes the asset from other tokens that may use a similar name or symbol. Build the rest of the record around that identifier, not around a ticker alone.
Create a canonical record your team can copy from whenever it updates a wallet, explorer, or discovery profile. Include:
- Exact token name and symbol, with agreed spelling and capitalization.
- The correct mint address, copied from a trusted project record.
- The approved logo file and a note identifying it as the current version.
- Official website and social links, using URLs the project controls.
- A concise project description that matches the language used on the website.
- A contact owner who can confirm future changes.
Keep the record in a shared document with an owner and a review date. If the project changes its name, logo, or primary URL, update this record first. That simple order prevents different team members from submitting different versions. Consistent project references also give search systems clearer material to associate with the token; they do not replace useful, substantive project information.
How do you audit token metadata before making changes?
Audit the visible pages before submitting changes so you know what is already correct and where information diverges. Search using the mint address as well as the token name; a name-only search can surface a different asset or an outdated mention.
Record the result for each surface in a small audit table. Capture the page URL, displayed name and symbol, logo, project links, description, and the date you checked it. Mark each item as correct, missing, outdated, or unclear. Save a screenshot when a profile is ambiguous, and note whether the issue appears on a wallet, explorer, or discovery page.
Separate visible profile details from information your project cannot edit directly. For each discrepancy, identify the platform’s current submission or support route before preparing a request. The work may involve wallet logo and token list inclusion or an explorer token information and logo update; those are distinct tasks, not one universal submission. An audit turns a vague request to “fix the metadata” into a specific list of fields and pages to address.
How should you prepare a logo, links, and project description?
Prepare a small, approved asset package before you contact a platform. The goal is to make each submission easy to review and to avoid conflicting versions of the project identity.
Use this checklist:
- Select one logo master file and export the formats requested by the destination. Do not assume every platform accepts the same file type or dimensions; check its submission instructions first.
- Confirm the logo is legible at a small display size and does not include temporary campaign text.
- Open every official URL and make sure it leads to the intended project page. Prefer stable pages over short-lived campaign links.
- Write a short description that explains what the project does without unsupported claims. Reuse it consistently, adjusting only when a form has a specific field or limit.
- Keep the mint address beside every asset and submission note to reduce the chance of mixing up similar tokens.
Name files clearly, for example with the project name and “logo-current,” and archive older versions rather than leaving several files labelled final. Keep an owner-approved copy of the description and links in the canonical record. If profile details on trading discovery pages also need attention, a DEXTools and DEXScreener profile update can be handled as its own workstream.
What is the practical workflow for updating Solana token metadata?
Update one platform at a time, using its own submission route and recording what you sent. That makes it easier to identify whether a mismatch comes from your source material, an incomplete request, or a page that has not yet changed.
A dependable workflow is:
- Finalize the canonical record and confirm the mint address with the project owner.
- List the wallets, explorers, and discovery pages where the project needs corrected information.
- Check each destination’s current instructions and prepare only the requested fields and files.
- Submit the request using a project-controlled email or account where available, and save the confirmation or reference.
- Revisit the public page and compare every visible field with the canonical record.
- Log the outcome, remaining discrepancy, and next action for each surface.
A useful status table has columns for destination, requested changes, submission date, confirmation, visible result, and follow-up owner. Do not close an item just because a form was submitted: verify the public page. For consistency beyond token profiles, review how the project’s token page social signals support the same official identity and destinations.
How does consistent token metadata support search discovery?
Consistent metadata makes it easier for people and search systems to connect a token’s public references with the project behind it. A matching name, logo, mint address, and set of official links reduces avoidable ambiguity when someone moves from a wallet or explorer to the project website.
Treat metadata as the identity layer, not the whole discovery strategy. A complete profile can improve the clarity of what a visitor sees, but it cannot explain a project’s use case, answer detailed questions, or make outdated third-party pages disappear. Support the identity record with clear pages on your own site: explain the product, describe the token’s role accurately, and link to the correct mint address and official community channels.
For an AI-search review, compare the project’s own pages with the facts shown on the public token profiles. An AI Presence Scan can identify whether core project descriptions and links are consistent across the material a researcher can inspect. An Answer Map can then organize the questions a reader is likely to ask and point to the project pages that answer them. Keep these reviews grounded in visible sources rather than assuming how any platform selects or displays information.
What can affect how a platform displays a token update?
Each wallet, explorer, and discovery platform controls its own review and display process, so a correct submission is not the same as a confirmed public update. The practical limits are specific: the destination may review eligibility, request different evidence, or refresh the visible profile on its own schedule. A complete submission cannot guarantee acceptance or a particular search placement; the controllable work is supplying accurate information through the appropriate route and checking the result.
Keep the request focused on facts the team can substantiate. Use official links, provide the exact mint address, and make sure the website and submitted project description agree. If a platform asks for additional material, respond with the relevant source rather than changing the canonical record to match an unverified assumption.
When a page remains unchanged, compare the saved request with the destination’s instructions and the current public display. Check for a mismatched mint address, an expired or redirected URL, an obsolete logo file, or a missing confirmation. Then follow up through the same official route and update the status log. This creates a clear record for the next person who manages the token profile.
How should a team maintain token metadata after an update?
Maintain metadata by treating every identity change as a coordinated release, not as an isolated edit to one profile. Before changing a name, logo, website, or social destination, decide which surfaces need the new information and assign someone to verify them afterward.
Keep a simple change log with the date, field changed, approved replacement, destinations contacted, and visible status. Store the current logo and canonical links in one shared location, and make older versions clearly inactive. When a team member finds a mismatch, ask them to report the page URL and mint address rather than sending an unsourced screenshot or a name-only description.
If you want help coordinating the review, send AIPromote the mint address, the canonical website and social links, the approved logo, and a short list of pages that need attention. We can check the identity package, map the visible discrepancies, and help organize platform-specific updates through relevant wallet logo and explorer information work. Start with the audit, and you will have a concrete list of corrections to act on.
Frequently asked questions
What should I prepare before asking a wallet to update a Solana token’s logo and links?
Prepare the exact mint address, the approved logo file, the official website and social URLs, and the token name and symbol as they should appear. Check the wallet’s current instructions for required file formats or supporting information, then keep a copy of what you submit. This makes the request easier to verify and helps your team repeat the same details elsewhere.
Why does my token show different details on different discovery platforms?
Each destination may have its own profile, submission route, and visible fields. One page may still show an older logo or link while another displays the current information. Compare the public pages against your canonical record, note exactly which fields differ, and submit a separate, focused update request to each relevant platform.
How long does it take for a Solana token metadata update to appear?
There is no single timeline that applies to every wallet, explorer, or discovery platform. Review and display timing are controlled by the destination, and the visible page may not change when a request is first submitted. Save the confirmation, check the public page again, and follow up through the same official route if the submitted details are still missing.
Can consistent token metadata guarantee that my project appears in AI answers?
No. Consistent metadata helps make the project’s identity and official destinations clearer, but AI answers are produced by systems outside the project’s control. Keep the token profile aligned with accurate, useful information on your own website, then review what those systems actually display instead of treating a profile update as a promise of citation.
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…