Skip to content

About

Website-layer marketing audit of popdex.xyz — technical SEO, AI-search visibility, structured data, site architecture, and homepage CRO.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

1 Commit

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 

Repository files navigation

PopDEX — Marketing Site & Docs Audit

A website-layer marketing audit of popdex.xyz and its documentation, conducted 2026-08-18. Five reports covering technical SEO, AI-search visibility, structured data, site architecture, and homepage conversion.

Method: direct inspection of the live product — raw HTTP fetches (including under Googlebot and GPTBot user agents), rendered-DOM analysis in a headless browser, and public web/search data. No client analytics access (see Caveats).


Reports

# Report Focus Verdict
01 Technical SEO Crawlability, indexation, on-page Critical
02 AI Search Visibility AEO / GEO / LLM citability Critical
03 Structured Data Schema.org / JSON-LD High
04 Site Architecture Hierarchy, URLs, internal linking High
05 Homepage CRO & Copy Conversion, messaging, proof 4.3 / 10

Supporting context lives in context/: project.md (product reference built from the docs) and product-marketing.md (positioning, personas, objections).


Executive Summary

Five reports, converging on five root causes. Fix these and most individual findings resolve as side effects.

1. One rewrite rule is de-indexing the entire documentation corpus

Every /docs/* URL returns the same 3,566-byte SPA shell — 30 characters of visible text — and canonicals to /docs/. Verified under Googlebot and GPTBot; no prerendering for either.

$ curl -s -A "GPTBot/1.1" https://popdex.xyz/docs/product-docs/trading/fees | wc -c
3566     # visible text: "d8746c1 · 2026-08-17 07:26 UTC"

PopDEX's single best marketing asset is ~140 pages of excellent technical documentation. It is the ideal AI-citation corpus and it is invisible to search engines, LLMs, and any non-JS crawler. The canonical tag additionally instructs Google to drop every page. This one fix resolves findings across reports 01–04.

2. A Bitget template leak is in the page head

The homepage <head> declares og:url and hreflang="x-default" as https://www.bitget.com/, and every image loads from img.bgstatic.com (Bitget's CDN). A leftover HTML comment confirms the origin. Every social share of popdex.xyz resolves its canonical identity to a competitor, and machine entity-resolution points at the wrong company. (Reports 01, 02.)

3. Zero structured data sitewide

No Organization, WebSite, Article, FAQPage or BreadcrumbList — verified in the rendered DOM, not just raw HTML. With no Wikipedia entry and the og:url pointing at bitget.com, PopDEX currently has no asserted machine-readable identity. (Report 03.)

4. No commercial-intent pages exist

The marketing site is a single page. The header nav is two items. There is no /fees, /security, /vaults, or comparison page — so every high-intent query ("perp DEX fees", "Hyperliquid alternative") has nowhere to land, while the depth that could rank sits in the de-indexed docs. (Report 04.)

5. Strong copy, no proof, and an unclear access model

The positioning is genuinely differentiated — "100% value return to real contributors" is a claim no competitor can copy. But the homepage carries no proof (no volume, no audit badge, no investor number — the only figure on the page is "100%"), and it never makes its own status legible. Mainnet is a live invite-only private beta — trading requires a referral/genesis code — yet the two hero CTAs (Join Waitlist and Launch App) sit co-equal with nothing signalling that trading is gated. A non-invited visitor can be walked through the entire wallet-connect flow before hitting the referral wall. (Report 05.)


Scores at a Glance

Metric Score Band
Homepage CRO 4.3 / 10 Copy strong; proof and objection-handling weak

Consolidated Action Plan

Week 1 — stop the bleeding

  1. Restore static per-route HTML for /docs/* (01)
  2. Self-referencing canonical per page (01, 03)
  3. Publish robots.txt + sitemap.xml (01, 02)
  4. Replace both bitget.com URLs; grep the build for remaining Bitget references (01, 02)
  5. Give the hero one primary CTA (the waitlist is correct — access is invite-only) and disclose the referral gate before wallet connect (05)
  6. Publish llms.txt + pricing.md (drafts in report 02) (02)
  7. Rewrite the homepage <title>; add per-page docs titles (01)

Weeks 2–4 — build the missing surface

  1. Build /fees and the other L1 pages (/security, /vaults, /builders) (04)
  2. Add a live stat bar / proof block under the hero (05)
  3. Ship OG images; fix the "Show pictures" placeholder (01)
  4. Add Organization + WebSite + TechArticle + FAQPage schema (03)
  5. Fix hreflang self-reference; return real 404s (01, 04)
  6. Alt text on all images; fix heading hierarchy (01, 05)
  7. Normalize docs URLs to lowercase; rename opaque segments (04)
  8. Remove or substantiate the grid / martingale / dual-direction claims (05)

Month 2+ — compound

  1. /vs/hyperliquid + /hyperliquid-alternatives (04)
  2. Glossary + comparison content (04)
  3. Free tools on the public API (funding comparison, liquidation calculator) (02, 05)
  4. Per-market programmatic pages, once >3 markets (04)
  5. Trader + market-maker testimonials (05)
  6. Baseline AI-visibility monitoring; set up Search Console + Bing Webmaster (01, 02)

Decisions Only the Client Can Make

These block copy and positioning work and can't be resolved from the outside:

  1. Is there a token? The entire differentiation rests on not leading with token expectations. Needs one consistent public answer. (Most commercially consequential item here.)
  2. When does the invite-only beta open to the public? Confirmed: mainnet is live but gated by a referral/genesis code, so the "invite-only early access" framing is accurate. The open question is the public-launch timeline — it changes how the homepage and CTAs should be framed.
  3. Do grid trading / dual-direction orders / martingale ship at mainnet? Advertised on the homepage, absent from both the docs and the live app.
  4. When does MegaPop go public? The fee-funded weekly BTC lottery (contract 0x…1013) is deployed but unannounced — a live copy/novelty opportunity.

Caveats

  • Scope. This repo is the website layer — the marketing site and docs. The audit set also produced strategy/ops reports (activation funnel, fee strategy, measurement/analytics, competitor profiling); those were scoped out of this repo.
  • No analytics access. No Search Console, GA4, or product analytics were available. Traffic, conversion rates, indexed-page counts, and Core Web Vitals field data are therefore unavailable — every finding is from public inspection of the live product.
  • Snapshot. All findings reflect the site as observed on 2026-08-18 and should be re-verified before acting, as production may have changed.

Notes

  • The source Foresight Ventures research article referenced in context/project.md is not included in this repository (third-party copyright).
  • context/product-marketing.md is a working draft (v2); sections marked [VERIFY] need client confirmation.

About

Website-layer marketing audit of popdex.xyz — technical SEO, AI-search visibility, structured data, site architecture, and homepage CRO.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors