Submission tracker
GetBlock directory submission tracker
Priority order and rules for where to submit, what URL to use, and what must be ready first.
| Priority | Surface | Submit URL | Destination | Rules |
|---|---|---|---|---|
| P0 | Asset kit + rendered QA | Submit | Finish before mass submissions | Need screenshots, copy variants, schema/H1 report, proof bullets. |
| P1 | LinkedIn Company | Submit | Homepage | Entity profile; use short factual company description. |
| P1 | Crunchbase | Submit | Homepage | Use company/entity facts only; no unverified traction claims. |
| P1 | GitHub org/profile | Submit | Docs + homepage | Developer credibility; link docs and public examples if available. |
| P2 | StackShare | Submit | Nodes/docs page | Technical stack framing; explain RPC/API role. |
| P2 | SourceForge | Submit | Homepage/docs | Software listing; add screenshots and pricing/doc links. |
| P2 | Slashdot | Submit | Homepage/docs | Same operator as SourceForge family; avoid duplicate copy. |
| P3 | AlternativeTo | Submit | GetBlock vs competitor pages | Use comparison pages; honest alternatives framing. |
| P3 | SaaSHub | Submit | Comparison/pricing pages | Needs category + alternatives copy; include use cases. |
| P4 | G2 | Submit | Enterprise + case studies | Do only after review campaign is ready; zero-review listing has low value. |
| P4 | Capterra/Gartner Digital Markets | Submit | Enterprise + pricing + case studies | Need review candidates and category match. |
| P4 | TrustRadius | Submit | Enterprise + SLA + case studies | Review-led; avoid launching without customer asks. |
| P5 | Product Hunt | Submit | rpc.run/tools | Launch the free tools asset, not generic homepage. |
| P5 | DevHunt | Submit | rpc.run/tools | Dev/tool angle; calculators give concrete launch object. |
| P6 | AI directories | Submit | AI-agent RPC page | Wait until dedicated AI-agent RPC landing page exists. |
| P6 | MCP registries | Submit | MCP landing/docs | Wait until installable MCP route/docs are clear. |