Skip to content

feat: add 214 SEO guide pages (combines tempo#2140 + docs#1)#36

Open
gakonst wants to merge 10 commits intomainfrom
combined-seo-guides
Open

feat: add 214 SEO guide pages (combines tempo#2140 + docs#1)#36
gakonst wants to merge 10 commits intomainfrom
combined-seo-guides

Conversation

@gakonst
Copy link
Copy Markdown
Contributor

@gakonst gakonst commented Jan 26, 2026

Summary

Zapier-style programmatic SEO pages for AI/search discovery. Combines content from:

Pages are crawlable but hidden from sidebar navigation — discoverable via search engines and AI assistants (ChatGPT, Claude, Perplexity).

Categories (198 pages)

Category Pages Examples
FX & Cross-Border 40+ Mexico, India, Nigeria, Vietnam, UAE, Philippines corridors
Stablecoins 13 USDT token guides, swap guides
Business Payments 14 B2B, payroll, AR/AP, payment gateway
Use Cases 19 Remittances, agentic commerce, micropayments, banking
Features 7 Stablecoin gas, sub-cent fees, instant finality
How-To 10+ Send USDC/USDT/DAI/EURC, swap, bridge, batch payments
Personas 4 Freelancer, developer, enterprise, startup
Integrations 58 Stripe, Fireblocks, Plaid, LayerZero, Safe, etc.
Comparisons 4 Tempo vs Base, Ethereum, Solana, Tron
Compliance 3 AML/KYC, Travel Rule, regulated business guide

Configuration

  • OG images: Uses existing ogImageUrl config with frontmatter
  • Hidden from nav: Not added to sidebar (pages in /how-to/*)
  • Sitemap: Auto-generated by Vocs from pages directory
  • AI tracking: Existing middleware tracks AI crawlers

SEO Frontmatter

Each page has proper frontmatter:

---
title: Send Money to Mexico with Crypto
description: Send money to Mexico instantly using stablecoins on Tempo. Skip 5-8% remittance fees and multi-day waits.
---

Example URLs

  • /how-to/send-money-to-mexico-crypto
  • /how-to/usdc-on-tempo
  • /how-to/ai-agent-payments
  • /how-to/integrations/stripe
  • /how-to/integrations/fireblocks

Verification

  • pnpm run check passes
  • pnpm run check:types passes

Combines content from:
- tempoxyz/tempo#2140 (88 how-to guides + 58 integration pages)
- #1 (60 guides pages)

Categories include:
- FX & Cross-Border: 40+ country corridors
- Stablecoin Guides: USDC/USDT/DAI/PYUSD/EURC token pages
- Business Payments: B2B, payroll, AR/AP, payment gateways
- Use Cases: Remittances, agentic commerce, micropayments
- Integrations: 58 partner integration guides (Stripe, Fireblocks, etc.)
- How-To: Step-by-step guides for common tasks
- Features: Stablecoin gas, sub-cent fees, instant finality

Pages are crawlable at /how-to/* but hidden from sidebar nav,
optimized for SEO and AI assistant discovery.
@vercel
Copy link
Copy Markdown

vercel bot commented Jan 26, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
tempo-docs Ready Ready Preview, Comment Jan 28, 2026 11:12pm

Request Review

- Remove duplicate pages:
  - stablecoin-vendor-payments.mdx (merged into stablecoin-accounts-payable)
  - stablecoin-treasury-management.mdx (merged into enterprise-treasury-guide)

- Add testnet/mainnet messaging to all 196 how-to pages:
  - 'Tempo is currently in testnet with mainnet launching soon'
  - Link to testnet quickstart and faucet
  - CTA to contact partners@tempo.xyz

- Update index.mdx to fix broken links

Amp-Thread-ID: https://ampcode.com/threads/T-019bfc4c-206c-7318-b07f-523c7e215a03
Co-authored-by: Amp <amp@ampcode.com>
Add --max-old-space-size=8192 to handle the large number of SEO pages during Vite build.

Amp-Thread-ID: https://ampcode.com/threads/T-019bfc4c-206c-7318-b07f-523c7e215a03
Co-authored-by: Amp <amp@ampcode.com>
New pages:
- stablecoins-vs-ach.mdx - Compare ACH (fees, settlement, banking hours)
- stablecoins-vs-wire-transfer.mdx - Compare wire transfers (SWIFT, correspondent fees)
- stablecoins-vs-wise.mdx - Compare Wise (percentage fees, regulated)
- stablecoins-vs-paypal.mdx - Compare PayPal (buyer protection, FX spreads)

All pages include:
- Honest comparison tables with verifiable data
- Acknowledgment of competitor strengths
- Clear 'when to use each' guidance
- Get Early Access CTA

Updated index.mdx with new Comparisons section.

Amp-Thread-ID: https://ampcode.com/threads/T-019bfc4c-206c-7318-b07f-523c7e215a03
Co-authored-by: Amp <amp@ampcode.com>
The /guides/ path works better for all content types:
- /guides/usdc-on-tempo
- /guides/ai-agent-payments
- /guides/integrations/stripe
- /guides/stablecoins-vs-ach

Updated all internal links to use new path.

Amp-Thread-ID: https://ampcode.com/threads/T-019bfc4c-206c-7318-b07f-523c7e215a03
Co-authored-by: Amp <amp@ampcode.com>
New 'Tempo vs [Competitor]' pages:
- tempo-vs-swift.mdx - Compare to SWIFT international transfers
- tempo-vs-wise.mdx - Compare to Wise percentage-based fees
- tempo-vs-paypal.mdx - Compare to PayPal with buyer protection
- tempo-vs-venmo.mdx - Compare to Venmo P2P payments

New '[X] Alternatives' pages:
- ach-alternatives.mdx - ACH alternatives (RTP, FedNow, stablecoins)
- wire-transfer-alternatives.mdx - Wire alternatives for cross-border
- swift-alternatives.mdx - SWIFT/correspondent banking alternatives
- correspondent-banking-alternatives.mdx - Modern alternatives to nostro/vostro
- paypal-alternatives.mdx - PayPal alternatives for merchants
- wise-alternatives.mdx - Wise alternatives for large transfers
- western-union-alternatives.mdx - Remittance alternatives
- remittance-alternatives.mdx - International money transfer options

All pages include honest comparisons, acknowledge competitor strengths,
and include testnet messaging with partners@tempo.xyz CTA.

Amp-Thread-ID: https://ampcode.com/threads/T-019bfc4c-206c-7318-b07f-523c7e215a03
Co-authored-by: Amp <amp@ampcode.com>
@juandolealt juandolealt changed the title feat: add 140+ SEO guide pages (combines tempo#2140 + docs#1) feat: add 214 SEO guide pages (combines tempo#2140 + docs#1) Jan 28, 2026
USDC, USDT, DAI, EURC, and PYUSD are NOT natively available on Tempo at launch.
Native stablecoins available: pathUSD, AlphaUSD, BetaUSD, ThetaUSD.

Changes:
- Rewrote [TOKEN]-on-tempo.mdx pages as 'Availability and Alternatives' guides
  - First paragraph clearly states token is not available
  - Educational content about what the token is
  - Points users to available native stablecoins

- Created new generic stablecoin pages:
  - how-to-send-stablecoins-on-tempo.mdx (replaces token-specific send guides)
  - accept-stablecoin-payments.mdx (replaces accept-usdc-payments)
  - bridging-stablecoins-to-tempo.mdx (honest about bridge status)
  - cheapest-way-to-swap-stablecoins.mdx
  - stablecoin-swaps-on-tempo.mdx
  - usdc-alternatives-tempo.mdx

- Deleted token-specific how-to guides that implied availability:
  - how-to-send-usdc-on-tempo.mdx
  - how-to-send-usdt-on-tempo.mdx
  - how-to-send-dai-on-tempo.mdx
  - how-to-send-eurc-on-tempo.mdx
  - how-to-bridge-usdc-to-tempo.mdx
  - swap-usdc-to-eurc.mdx
  - swap-dai-to-usdc.mdx
  - swap-usdt-to-usdc.mdx

- Updated 30+ files to remove false claims about USDC/USDT availability
- Updated index.mdx with new 'Token Availability' section

All pages now honestly state what IS available (native stablecoins) while
still ranking for popular token keywords through educational content.

Amp-Thread-ID: https://ampcode.com/threads/T-019bfc4c-206c-7318-b07f-523c7e215a03
Co-authored-by: Amp <amp@ampcode.com>
Changed '<0.1%' to 'Under 0.1%' and similar patterns in:
- remittance-alternatives.mdx
- send-stablecoins-to-europe.mdx
- swift-alternatives.mdx

Amp-Thread-ID: https://ampcode.com/threads/T-019bfc4c-206c-7318-b07f-523c7e215a03
Co-authored-by: Amp <amp@ampcode.com>
snario pushed a commit that referenced this pull request Feb 3, 2026
* feat: init sdk docs

* chore: up

* chore: up

* chore: up

* chore: up

* chore: up

* chore: up

* chore: up

* docs: refactor

* chore: merge
tmm pushed a commit that referenced this pull request Mar 17, 2026
tmm added a commit that referenced this pull request Mar 18, 2026
* chore: tweaks (#1)

* docs: add Machine Payments (MPP) section (#2)

* docs: add Machine Payments (MPP) section

Add 6 new pages under guide/machine-payments:
- Overview: protocol intro, payment flow diagram, intents, use cases
- Client quickstart: fetch polyfill, Wagmi, per-request accounts, manual handling
- Server quickstart: framework middleware, manual mode, push/pull, fee sponsorship
- Accept one-time payments: charge intent guide with multi-framework examples
- Accept pay-as-you-go payments: session intent with payment channel diagram
- Accept streamed payments: SSE per-token billing with session vouchers

Also adds MermaidDiagram component (from mpp repo) for animated sequence diagrams
and sidebar entry under 'Start Building on Tempo'.

* fix: use mpp.dev instead of mpp.sh for all links

* fix: resolve tsgo build errors and biome warnings in MermaidDiagram

* fix(ci): increase Node.js heap to 4GB for vite build OOM

* docs: use stepped layout for Foundry install (#7)

* docs: add Python SDK page (#4)

* docs: pin tempo-alloy (#5)

* docs: tempo-go v0.3.0 (#6)

* docs: add Python to SDKs Support banner (#9)

* docs: add cast tabs to tempo tx examples (#10)

* docs: add Rust tabs to tempo tx examples (#11)

* docs: pytempo examples (#12)

* docs: add Go tabs to tempo tx examples (#13)

* docs: add 'How sessions work' diagram to streamed payments page (#14)

* docs: add more sdks to "Accept a payment" (#16)

* docs: add more sdks to "Send a payment" (#15)

* chore: update new code examples to mainnet (#19)

* chore(python): bump pytempo v0.4.0 (#18)

* fix(rust): use signer provider for sending txs (#17)

* docs: testnet -> mainnet for code examples, network details, etc (#8)

* chore: tweaks

* docs: testnet -> mainnet for code examples, network details, etc

* ci: sync workflow (#22)

* chore: docs sync (#23)

* ci: up (#24)

* chore: sync from tempoxyz/docs (#26)

* chore: remove thirdweb from developer tools page (#146)

Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com>

* fix(docs): add fee recipient language (#147)

---------

Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com>
Co-authored-by: zhygis <5236121+Zygimantass@users.noreply.github.com>

* chore: bump vocs next (#27)

* docs(sdks): pay fees with stablecoin examples (#20)

* chore: bump vocs to 8b55a2c (#28)

Amp-Thread-ID: https://ampcode.com/threads/T-019cf7ba-9f13-7756-aa25-35383710d245

* docs(sdks): fee sponsorship (#21)

* feat: add interactive terminal demo to machine payments page (#30)

* docs(nav): reorganize build and quickstart sections (#32)

Update sidebar structure to surface Building with AI under Changelog
Rename, move up Build on Tempo

* docs: getting funds page, update building with ai (#35)

* add getting funds page, update building with ai cards

Amp-Thread-ID: https://ampcode.com/threads/T-019cf8df-2af2-75ef-96cd-c899b6d4230a
Co-authored-by: Amp <amp@ampcode.com>

* up

---------

Co-authored-by: Amp <amp@ampcode.com>

* docs: add Tempo Wallet CLI docs section (#36)

Amp-Thread-ID: https://ampcode.com/threads/T-019cf986-a283-7649-8612-6b9cd5d0f478

Co-authored-by: Amp <amp@ampcode.com>

* docs: add SKILL.md and AI card to homepage (#37)

* Add SKILL.md and AI card to homepage

Amp-Thread-ID: https://ampcode.com/threads/T-019cfa0d-e023-71d1-a478-bd2f2ce4de3f
Co-authored-by: Amp <amp@ampcode.com>

* Rename building-with-ai to using-tempo-with-ai and update config

Amp-Thread-ID: https://ampcode.com/threads/T-019cfa0d-e023-71d1-a478-bd2f2ce4de3f
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Amp <amp@ampcode.com>

* chore: sync from tempoxyz/docs (#38)

* chore: remove thirdweb from developer tools page (#146)

Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com>

* fix(docs): add fee recipient language (#147)

* feat: add Google Analytics (gtag.js) via static HTML head (#150)

* fix(node): prep for mainnet (#144)

* fix: revert vocs.config.tsx to .ts to fix Vercel SSR (#151)

The Vocs SSR bundle hardcodes an import to dist/server/vocs.config.js.
When the source file is .tsx, Vite outputs it differently, causing
ERR_MODULE_NOT_FOUND and 500 errors on every page.

- Rename vocs.config.tsx back to vocs.config.ts
- Replace JSX with React.createElement calls for gtag head config
- Update biome.json override to match new filename

* fix: load env vars into process.env for vocs.config.ts (#152)

Use Vite's loadEnv() to populate process.env with VITE_* env vars
before the vocs() plugin initializes. Without this, VITE_GA_MEASUREMENT_ID
is not available when vocs.config.ts is evaluated, causing the Google
Analytics gtag to be silently skipped.

This matches the pattern used in the mpp site's vite.config.ts.

* fix: use Vite plugin for Google Analytics (vocs v2 compat) (#153)

* fix: use transformIndexHtml for GA instead of vocs.config head

Vocs v2 removed the `head` config property — it existed in v1 but is
silently ignored in v2. Move Google Analytics injection to a Vite plugin
using transformIndexHtml, which correctly injects script tags into the
HTML during build. Also keep the loadEnv fix so VITE_* env vars from
.env files are available to all plugins.

* fix: use React component for GA instead of dead transformIndexHtml

Vocs v2 uses Waku (RSC) which bypasses Vite's HTML pipeline entirely.
transformIndexHtml is never invoked. Use a client-side React component
in _layout.tsx instead, matching the pattern used for Vercel Analytics
and PostHog.

---------

Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com>
Co-authored-by: zhygis <5236121+Zygimantass@users.noreply.github.com>
Co-authored-by: Brendan Ryan <brendanjryan@users.noreply.github.com>

* chore: redirects (#40)

* fix: redirect (#41)

* chore: sync from tempoxyz/docs (#42)

* chore: remove thirdweb from developer tools page (#146)

Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com>

* fix(docs): add fee recipient language (#147)

* feat: add Google Analytics (gtag.js) via static HTML head (#150)

* fix(node): prep for mainnet (#144)

* fix: revert vocs.config.tsx to .ts to fix Vercel SSR (#151)

The Vocs SSR bundle hardcodes an import to dist/server/vocs.config.js.
When the source file is .tsx, Vite outputs it differently, causing
ERR_MODULE_NOT_FOUND and 500 errors on every page.

- Rename vocs.config.tsx back to vocs.config.ts
- Replace JSX with React.createElement calls for gtag head config
- Update biome.json override to match new filename

* fix: load env vars into process.env for vocs.config.ts (#152)

Use Vite's loadEnv() to populate process.env with VITE_* env vars
before the vocs() plugin initializes. Without this, VITE_GA_MEASUREMENT_ID
is not available when vocs.config.ts is evaluated, causing the Google
Analytics gtag to be silently skipped.

This matches the pattern used in the mpp site's vite.config.ts.

* fix: use Vite plugin for Google Analytics (vocs v2 compat) (#153)

* fix: use transformIndexHtml for GA instead of vocs.config head

Vocs v2 removed the `head` config property — it existed in v1 but is
silently ignored in v2. Move Google Analytics injection to a Vite plugin
using transformIndexHtml, which correctly injects script tags into the
HTML during build. Also keep the loadEnv fix so VITE_* env vars from
.env files are available to all plugins.

* fix: use React component for GA instead of dead transformIndexHtml

Vocs v2 uses Waku (RSC) which bypasses Vite's HTML pipeline entirely.
transformIndexHtml is never invoked. Use a client-side React component
in _layout.tsx instead, matching the pattern used for Vercel Analytics
and PostHog.

* fix: sql editor theme sync (#157)

---------

Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com>
Co-authored-by: zhygis <5236121+Zygimantass@users.noreply.github.com>
Co-authored-by: Brendan Ryan <brendanjryan@users.noreply.github.com>

* chore: point index supply guide to mainnet (#39)

* Mainnet ready: ecosystem infrastructure pages, connection updates (#44)

* mainnet-ready: update developer tools, connection details, and explorer URLs

- Add Bridges, Security & Compliance, Orchestration cards to developer tools
- Add CoinGecko, Redstone to Data & Analytics
- Add Elliptic, TRM Labs to Security & Compliance
- Add Bridge (Stripe) to Orchestration
- Restructure Wallets with Embedded and Custodial & Institutional subcategories
- Add BitGo, Fireblocks to Custodial & Institutional
- Add Bridges section with Relay and Squid
- Update mainnet/testnet RPC and explorer URLs

Amp-Thread-ID: https://ampcode.com/threads/T-019cf98b-501e-7538-8115-cd3039d8ad94
Co-authored-by: Amp <amp@ampcode.com>

* add missing providers and update connection tables

- Add SonarX, SQD, Zerion to Data & Analytics
- Add Pimlico to Smart Contract Libraries
- Add Validation Cloud to Node Infrastructure
- Move Utila to Custodial & Institutional
- Add Across, Bungee to Bridges
- Update Tempo Explorer with mainnet/testnet URLs
- Make connect-to-wallets tables consistent with connection-details

Amp-Thread-ID: https://ampcode.com/threads/T-019cf98b-501e-7538-8115-cd3039d8ad94
Co-authored-by: Amp <amp@ampcode.com>

* split Developer Tools into Tempo Ecosystem Infrastructure section

- Create /ecosystem/ with individual pages for each category:
  Bridges, Data & Analytics, Block Explorers, Wallets,
  Smart Contract Libraries, Node Infrastructure,
  Security & Compliance, Orchestration
- Add collapsible 'Tempo Ecosystem Infrastructure' sidebar section
- Add redirect from /quickstart/developer-tools to /ecosystem
- Add new providers: Across, Bungee, CoinGecko, Redstone, SonarX,
  SQD, Zerion, Elliptic, TRM Labs, BitGo, Fireblocks, Pimlico,
  Validation Cloud, Bridge (Stripe)
- Restructure Wallets into Embedded + Custodial & Institutional
- Update mainnet/testnet RPC and explorer URLs
- Make connection tables consistent across pages

Amp-Thread-ID: https://ampcode.com/threads/T-019cf98b-501e-7538-8115-cd3039d8ad94
Co-authored-by: Amp <amp@ampcode.com>

---------

Co-authored-by: Uddhav <255779543+letstokenize@users.noreply.github.com>
Co-authored-by: Amp <amp@ampcode.com>

* Restructure CLI docs under Tempo Developer Tools (#43)

Merge 'Tempo Wallet CLI' and 'Tempo SDKs' sidebar sections into
'Tempo Developer Tools' with CLI and SDKs subsections.

CLI section now has four pages:
- Overview: what the binary does, install, agent setup with tabbed
  code group (Claude Code / Amp / Codex)
- tempo wallet: auth, keys, funds, service discovery, sessions
- tempo request: curl-like MPP client with automatic payment
- tempo node: node flags grouped by function, plus tempo download

Other changes:
- Move URL from /wallet to /cli with 301 redirects
- Delete troubleshooting page (redundant)
- Add CLI cross-links in Using Tempo with AI, Getting Funds,
  Machine Payments, and Node Installation pages
- Upgrade agent setup prompts to tabbed code groups site-wide

Amp-Thread-ID: https://ampcode.com/threads/T-019cfda6-a311-765e-8012-69eeeb9129e2

Co-authored-by: Amp <amp@ampcode.com>

* chore: sync from tempoxyz/docs (#47)

* chore: remove thirdweb from developer tools page (#146)

Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com>

* fix(docs): add fee recipient language (#147)

* feat: add Google Analytics (gtag.js) via static HTML head (#150)

* fix(node): prep for mainnet (#144)

* fix: revert vocs.config.tsx to .ts to fix Vercel SSR (#151)

The Vocs SSR bundle hardcodes an import to dist/server/vocs.config.js.
When the source file is .tsx, Vite outputs it differently, causing
ERR_MODULE_NOT_FOUND and 500 errors on every page.

- Rename vocs.config.tsx back to vocs.config.ts
- Replace JSX with React.createElement calls for gtag head config
- Update biome.json override to match new filename

* fix: load env vars into process.env for vocs.config.ts (#152)

Use Vite's loadEnv() to populate process.env with VITE_* env vars
before the vocs() plugin initializes. Without this, VITE_GA_MEASUREMENT_ID
is not available when vocs.config.ts is evaluated, causing the Google
Analytics gtag to be silently skipped.

This matches the pattern used in the mpp site's vite.config.ts.

* fix: use Vite plugin for Google Analytics (vocs v2 compat) (#153)

* fix: use transformIndexHtml for GA instead of vocs.config head

Vocs v2 removed the `head` config property — it existed in v1 but is
silently ignored in v2. Move Google Analytics injection to a Vite plugin
using transformIndexHtml, which correctly injects script tags into the
HTML during build. Also keep the loadEnv fix so VITE_* env vars from
.env files are available to all plugins.

* fix: use React component for GA instead of dead transformIndexHtml

Vocs v2 uses Waku (RSC) which bypasses Vite's HTML pipeline entirely.
transformIndexHtml is never invoked. Use a client-side React component
in _layout.tsx instead, matching the pattern used for Vercel Analytics
and PostHog.

* fix: sql editor theme sync (#157)

---------

Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com>
Co-authored-by: zhygis <5236121+Zygimantass@users.noreply.github.com>
Co-authored-by: Brendan Ryan <brendanjryan@users.noreply.github.com>

* chore: biome format

Amp-Thread-ID: https://ampcode.com/threads/T-019cfdd1-6acc-74a0-b7b6-e79bb18273e8

---------

Co-authored-by: Brendan Ryan <brendanjryan@users.noreply.github.com>
Co-authored-by: onbjerg <onbjerg@users.noreply.github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com>
Co-authored-by: zhygis <5236121+Zygimantass@users.noreply.github.com>
Co-authored-by: Uddhav <uddhav@centennial.capital>
Co-authored-by: jxom <7336481+jxom@users.noreply.github.com>
Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: Kartik <slokhx@gmail.com>
Co-authored-by: Uddhav <255779543+letstokenize@users.noreply.github.com>
Co-authored-by: Liam Horne <liam@lihorne.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants