GetBlock directory launch readiness · 2026
GetBlock directory publication plan: what to finish before submitting, where to submit, and in what order
A practical, source-based launch plan for turning GetBlock's existing product pages, pricing, docs, case studies, comparison pages, AI/MCP assets, and rpc.run free tools into a directory/review/listing campaign.
Executive summary
GetBlock is not starting from zero. The current public site already has most of the trust foundation directories expect: pricing, docs, status/SLA, privacy/terms, case studies, comparison pages, machine-readable LLM files, and an AI/MCP angle.
The remaining work is not core positioning. It is the submission layer: asset kit, rendered SEO/schema QA, dedicated ICP landing pages, a review collection engine, and a launchable free-tool asset for Product Hunt / DevHunt style surfaces.
Entity profiles, dev/SaaS listings, StackShare, SourceForge, Slashdot, AlternativeTo/SaaSHub after schema QA.
G2/Capterra/TrustRadius until review candidates and ask sequence are ready.
Directory kit, ICP pages, AI-agent page, MCP page, rpc.run free tools.
What GetBlock already has
| Asset | Evidence / URL | Directory value |
|---|---|---|
| Public homepage | getblock.io | Primary brand destination. |
| Pricing | pricing + pricing.md | Hard requirement for many SaaS/review directories. |
| Docs | docs, docs LLM export | Developer trust, API listing proof, AI citation fuel. |
| Legal/trust | privacy, terms, SLA, status | Removes submission blockers for serious directories. |
| Comparisons | QuickNode, Alchemy, Infura, Helius, Chainstack, dRPC, Ankr, Moralis, Tatum | Strong destinations for AlternativeTo/SaaSHub and competitor-intent traffic. |
| Case studies | Tangem, Trust Wallet, ChangeNOW, EtherDrops, Blockaid, Revert.Finance | Needed for enterprise/review credibility. |
| AI/GEO material | llms.txt, llms-full.txt, MCP docs, getblock.ai | Useful for AI directories and LLM answer surfaces. |
What is missing before serious directory publication
- Directory asset kit. Logo SVG/PNG, square icon, screenshots, demo video, descriptions, tags, founder/company blurb, proof bullets.
- Rendered SEO/GEO QA. Verify single H1, canonical, OG image, FAQ schema, Product/SoftwareApplication/Organization JSON-LD, and CTA health on the pages used as directory destinations.
- Dedicated ICP landing pages. Homepage use-case cards exist, but directory traffic should land on focused pages for enterprise blockchain teams, RPC/API teams, Web3 infra teams, AI agents, wallets, and analytics/indexers.
- Review engine. G2/Capterra/TrustRadius need at least 20 review candidates and a 10-in-30 ask plan. A zero-review listing is weak.
- Launchable free-tool asset. Product Hunt/DevHunt should launch a concrete tool/hub, not the generic mature GetBlock website.
- AI/MCP landing page. The AI angle exists, but directory submissions need a single clear page: what it is, install/use path, examples, safety notes, and CTA.
P0: submission asset kit
Create a single internal/public kit before any batch. This prevents inconsistent descriptions and asset scrambles.
| Asset | Requirement | Use |
|---|---|---|
| Logo pack | SVG, transparent PNG, square 1024×1024, favicon | All directories. |
| Screenshots | 5–8 current product screenshots, 1920×1080 | Product Hunt, G2, Capterra, SaaS directories. |
| Demo video | 60–90 seconds, no hype, show endpoint creation + request + dashboard/stats | Product Hunt, DevHunt, review sites. |
| Descriptions | 10-word tagline, 60-char short, 150-word long, 500-word detailed | Copy variants per tier. |
| Proof bullets | 130+ networks, 50B+ monthly requests, 200k+ users, SOC 2 Type II, 99.99% dedicated SLA | Enterprise/review positioning. |
| Destination map | One URL per directory surface | Avoid homepage-only backlink waste. |
P1: pages to create or update before submissions
Dedicated ICP/use-case pages
/use-cases/enterprise-blockchain-teams/— banks, exchanges, custodians, enterprise dApps, procurement and SLA language./use-cases/rpc-api-teams/— developers choosing shared vs limitless vs dedicated RPC./use-cases/web3-infrastructure-teams/— infra/platform teams owning reliability and cost control./use-cases/analytics-indexing-rpc/— archive/log/backfill/indexing workloads./use-cases/wallet-infrastructure/— wallet read/write, multichain, WSS, failover, risk checks./use-cases/ai-agents-that-touch-crypto/— live RPC, risk APIs, MCP, freshness, degraded-provider behavior.
Comparison page updates
Existing comparison pages are valuable. Before directory traffic, verify or add: FAQ schema, honest “choose competitor when…” section, last-updated date, pricing caveat, and CTA to migration or benchmark.
Trust and proof updates
- Make SOC 2/GDPR/SLA proof easy to find from enterprise pages.
- Link status/SLA from every enterprise or reliability destination.
- Create a review-proof page tying case studies to buyer outcomes.
rpc.run tools
Use rpc.run as the launchable asset layer: archive estimator, RPC cost/plan-fit calculator, SLA/reliability risk calculator, migration estimator, indexer-vs-RPC tree, RFP checklist, error decoder, compatibility checker, agent-safe RPC readiness checker, and endpoint health checker.
P2: rendered SEO/GEO QA checklist
Run this on every destination page before using it in a directory listing.
- Exactly one rendered H1.
- Sequential heading hierarchy.
- Canonical URL.
- OpenGraph image and description.
- FAQPage JSON-LD where question/answer content exists.
- Organization + Product or SoftwareApplication JSON-LD.
- Visible pricing or “contact sales” path when relevant.
- Privacy/terms links reachable.
- Primary CTA works in incognito.
- Page is not blocked by robots/noindex.
Positioning variants
Web3 infrastructure
Tagline: Reliable multichain RPC infrastructure for production Web3 teams.
Use for StackShare, SourceForge, Slashdot, dev profiles, and infra directories.
RPC/API
Tagline: Blockchain RPC/API access with predictable production control.
Use for AlternativeTo, SaaSHub, API/tool directories, and comparison-driven listings.
Enterprise blockchain
Tagline: Enterprise RPC reliability for blockchain products that cannot silently fail.
Use for G2, Capterra, TrustRadius, procurement and enterprise directories.
AI-agent infrastructure
Tagline: Live RPC infrastructure for AI agents that touch crypto.
Use for AI directories and MCP/agent registries once the dedicated page/tool exists.
Submission order and rules
| Order | Surface | Destination | Rule |
|---|---|---|---|
| 1 | LinkedIn Company, Crunchbase, GitHub profile/org | Homepage, docs, GitHub | Entity authority first. Keep factual and consistent. |
| 2 | StackShare | /nodes/, docs, GitHub | Lead with developer stack and API coverage. |
| 3 | SourceForge / Slashdot | Homepage or /nodes/ | Use Web3 infra variant, no crypto hype. |
| 4 | AlternativeTo | Comparison pages | Use alternative framing; submit only after comparison-page schema QA. |
| 5 | SaaSHub | Comparison pages + pricing | Use RPC/API variant and ensure categories/tags are specific. |
| 6 | Dev.to / Hashnode / technical articles | Canonical blog/report/tool pages | Cross-post technical writeups with canonical link back. |
| 7 | Product Hunt / DevHunt | /tools/ | Only after a real free-tool hub exists; ask for feedback, never upvotes. |
| 8 | AI directories: TAAFT, Futurepedia, Toolify | AI-agent RPC page or agent-safe readiness tool | Only if framed as AI/on-chain live-state infrastructure. |
| 9 | MCP/agent registries: Glama, APITracker, LF MCP Registry | MCP install/docs page | Only if there is a real installable MCP server with examples. |
| 10 | G2 / Capterra / TrustRadius | Enterprise use-case + case studies + SLA | Do not start without review campaign and 20 review candidates. |
Weekly execution timeline
Week 0 — readiness build
- Assemble asset kit.
- Run rendered SEO/GEO QA on homepage, pricing, nodes, dedicated, limitless, enterprise, SLA, case studies, and comparison pages.
- Patch missing schema/FAQ/canonical/OG issues.
- Choose one destination URL per directory type.
Week 1 — foundation submissions
- Claim/update LinkedIn, Crunchbase, GitHub.
- Submit StackShare, SourceForge, Slashdot.
- Submit AlternativeTo/SaaSHub using comparison pages.
- Log status and backlink URL in tracker.
Week 2 — content and ICP layer
- Publish ICP pages.
- Publish one “best RPC providers / RPC alternatives” honest category article.
- Cross-post technical versions to Dev.to/Hashnode.
Week 3 — free-tool launch
- Launch rpc.run tools hub.
- Submit Product Hunt/DevHunt only after the tools are live and unique.
- Use Show HN only for a real technical benchmark/checker angle.
Week 4 — reviews
- Prepare 20 review candidates.
- Submit/claim G2/Capterra/TrustRadius.
- Run 10-in-30 review request protocol.
Per-submission operating rules
- Use a unique positioning variant. Do not paste the same long description everywhere.
- Submit only to directories where GetBlock is a genuine fit.
- Prefer destination pages over homepage links when the directory allows deep links.
- Log every submission: date, directory, URL, login owner, status, moderator notes, backlink status.
- After approval, verify the public listing and backlink. If the link is nofollow, still record it but do not count it as SEO-equivalent.
- Do not claim comparative superiority without source-backed proof and last-updated dates.
- Review pages quarterly; do not edit every week unless the product materially changed.
Immediate next actions
- Build the asset kit.
- Run rendered SEO/schema QA on the 12 most important existing GetBlock pages.
- Publish the first 4 ICP pages.
- Complete the rpc.run tools hub and first three calculators.
- Begin foundation submissions, then review-site submissions only after review candidates are ready.