Token profile edits across DEXTools and DEXScreener

Which profile fields belong in the request sheet?

We create a request sheet with 2 platform columns. It separates DEXTools fields from DEXScreener Enhanced Token Info materials. This makes each requested change clear before preparation begins.

For DEXTools, the scope can cover token information, social links and a logo update. For DEXScreener, Enhanced Token Info can include a logo, banner, description and social links. We mark each field as new, unchanged or requested for correction. Your approver confirms the wording and assets before submission.

The service fits a live token profile with missing, outdated or inconsistent project information. It also fits a launch or rebrand when the public identity needs alignment. The deliverable is profile information and presentation, not a change to the token contract or market activity.

If the request includes explorer records, keep that work distinct through explorer token information and logo updates. For a contract migration or brand change, coordinate the canonical identity through migration and rebranding updates. Broader directory work belongs under listings and verification.

How do the two profile workflows differ in practice?

The field map shows 2 different platform tracks. DEXTools work here covers token information, social links and logo updates. DEXScreener work uses Enhanced Token Info for the profile materials. We prepare each track against its own requested fields rather than treating one asset folder as a ready-made submission.

Before approving scope, confirm these 4 inputs:

• Chain and contract address for the token page.
• Official website and social URLs to display.
• Approved logo, plus a banner and description when requested.
• A short change note naming fields to edit and fields to leave alone.

A complete profile helps visitors inspect project identity and official links. It does not create a trending placement. A DEXScreener boost or a DEXTools trending campaign is a separate visibility activity, with a separate scope. See the trending campaigns overview when visibility is also part of the plan.

The practical decision is simple: approve profile fields and assets as one workstream. Add visibility activity only when you want that separate deliverable.

What evidence should your team assemble before edits?

The source folder is the main reference for 3 checks: token identity, public links and approved visuals. We compare the submitted materials with the requested profile changes before preparing anything for a platform. One project approver resolves conflicting versions.

Include the following items where they apply:

• Contract address and chain, copied from a project-approved source.
• Preferred token name and approved public description.
• Current logo file and any banner intended for Enhanced Token Info.
• Official website and social account URLs, checked for spelling.
• A note naming the exact fields to change and preserve.

We do not fill gaps by inventing project details. If a link, claim or asset has unclear ownership, we flag it for confirmation. The approver should also check destinations that lead to a wallet, exchange or community. This reduces the chance of publishing a link the team has not authorized.

If the token recently changed its name or contract, settle the current identity first. A profile edit should not combine legacy and current information without approval. Explorer-specific corrections can be scoped through explorer token information and logo updates; migration details can be handled through contract migration and rebranding updates.

What does the handoff record let your team verify?

The handoff record compares the public profile with the approved source folder. We check the token identity, requested logo, description and each social link. The record distinguishes fields that appear correctly from items still awaiting platform handling.

Our default record has 6 fields: platform, profile URL, token identity, requested changes, visible status and follow-up note. We review the request before submission, then check the public page after the platform’s handling. If a field differs from the approved version, the note identifies that specific mismatch.

This gives your team an artifact for internal review and future edits. It also clarifies what was included in the agreed scope. You can use the profile URL and field notes to brief whoever manages later updates.

We align reporting format before kickoff. The work sequence has 5 steps: receive the request, confirm identity and assets, approve scope, coordinate the update, then check the visible result. For related process details, see how we work. Send a page URL and name the field if a mismatch appears after handoff.

Where does the public profile record stop?

The page record shows what visitors can see at the time of review. It captures the profile URL, requested fields and any visible difference from the approved materials. That makes the result inspectable without presenting a submission as a platform decision.

Use the record to confirm whether the public page shows the intended logo, description and official links. Keep the approved source folder with it. If the project later changes a social account or brand asset, the same folder gives the approver a clear reference for another edit.

DEXTools and DEXScreener control their own profile review, acceptance and display. We can prepare and coordinate the agreed changes, but cannot promise approval, a publication time or a particular display outcome.

When should profile edits connect to other listing tasks?

A shared source folder is useful when the same token identity and official links appear across several directories. Keep each platform request separate. That makes review ownership and the expected deliverable clear.

For broader tracker coverage, consider CoinMarketCap listing support or CoinGecko listing support as separate workstreams. A DEX listing or liquidity setup is also distinct from profile presentation; review that scope through DEX listing and liquidity setup. The same approved project facts may support each request, but the profile update does not substitute for another platform’s listing process.

To start this service, send the token contract address, chain, current DEXTools and DEXScreener URLs, approved logo and official social links. Add a concise field-by-field change note and name the person who can approve materials. We will confirm the platform scope, flag missing inputs and return a work plan. Begin through contact with those materials attached.

How it works

1. Send the profile detailsShare the contract address, chain, current profile URLs and requested field changes.
2. Confirm the source materialsWe check the token identity, logo, description and official social links. You resolve any unclear or conflicting information.
3. Approve the platform scopeYou confirm which DEXTools and DEXScreener fields are in scope and name the materials approver.
4. Coordinate the requested editsWe prepare and coordinate the agreed submission or edit using the confirmed information and assets.
5. Check the public profilesWe review the visible pages and provide a record of completed fields and pending items.