Contribute

Editorial guidelines

How we evaluate submissions, assign categories, and keep web3.observer accurate — so the directory stays useful, not noisy.

Our editorial goal

web3.observer is a curated index, not an open registry. Every listing should help someone discover a real tool, protocol, or product — with enough context to decide whether it is worth their time.

We favor clarity over hype, maintenance over launch-day buzz, and usefulness to builders and researchers over raw project count.

What we look for

A project is more likely to be listed when it meets most of the following:

  • Live and accessible — The official site loads, the product or protocol is usable or clearly documented, and links are not broken.
  • Relevant to Web3 — It belongs in at least one of our core categories: DeFi, NFT, Infrastructure, Gaming, DAO, or Wallets.
  • Actively maintained — Recent updates, responsive docs, or visible ongoing development within the last 12 months.
  • Clear purpose — A visitor can understand what the project does within a minute of landing on its site.
  • Accurate metadata — Name, category, chain support, and description match what the project actually offers.

What we generally exclude

We may decline or remove listings that fall into these areas:

  • Scams, phishing sites, or projects with credible reports of fraud or exit activity.
  • Placeholder or “coming soon” pages with no working product or meaningful documentation.
  • Pure marketing landing pages, affiliate funnels, or duplicate listings for the same product.
  • Token-only promotions with no underlying tool, protocol, or application.
  • Projects that cannot be verified through a stable official domain or recognized repository.

Inclusion is never an endorsement. A listing means the project passed our editorial review at the time of publication — not a recommendation to invest or adopt.

How review works

  1. Submission — Email info@web3.observer from a project domain address when possible. Include the project name, URL, category, supported chains, description, and your contact details. Use the template on our submit page.
  2. Initial check — Editors verify the link, skim documentation, and confirm the suggested category fits.
  3. Metadata pass — We assign chain tags, write or refine the short description, and capture a screenshot when applicable.
  4. Publication — Approved projects appear in the directory and relevant category page. Declined submissions may not receive a individual reply, but repeated spam is filtered.

Review is manual and typically completed within one to two weeks. Urgent corrections to existing listings can be flagged by email with “Listing correction” in the subject line.

Featured slots on the homepage are editorial picks, rotated weekly. They are chosen for timeliness, quality of execution, or usefulness to the community — not paid placement.

Being listed in the directory does not guarantee a feature. Likewise, featured status can change as the ecosystem evolves.

Updates and removals

We re-check listings on a rolling basis. Projects may be updated when branding, categories, or chain support changes, or removed when they become inactive, redirect to unrelated content, or no longer meet our standards.

If you maintain a listed project and notice outdated information, email info@web3.observer with “Listing correction: [Project Name]” as the subject.

Ready to submit?

Make sure your project meets the criteria above, then send it in for review.