Loopcard SEO pages — titles, meta, FAQ, keywords

Date: 18 September 2026
Product: Loopcard (Virtus Labs)
Preview: https://cryptobook.space
Canonical later: swap every URL below when loopcard.ai / loopcard.app / getloopcard.com points at 173.249.19.205. Until then, canonical is the preview host.

Rule: social is the growth unit (a PNG). SEO is a support file, not a traffic forecast. Do not invent rankings, sessions, or “X searches/month.” Do not cite residual cryptobook.space hit counts in public meta.

Tone: Virtus. Short. Specific. Name what we are not.

Companion: website/seo.md (holding-page leftovers), marketing/claims-we-will-not-make.md, 11-loopcard-product.md.

Global tags (every indexed page)

robots: index,follow
og:type: website
og:image: https://cryptobook.space/og.png
twitter:card: summary_large_image
twitter:image: https://cryptobook.space/og.png
theme-color: #e91e8a

Footer on every page (not a meta tag; required copy):

Not legal advice. Not a compliance certification. Not an auditor. US-oriented. 18+. Not affiliated with Anthropic or Anysphere.

robots.txt (preview):

User-agent: *
Allow: /
Disallow: /api/
Sitemap: https://cryptobook.space/sitemap.xml

When /app or /login exist: noindex,nofollow on those. Do not sitemap them.

llms.txt (honest, already live):

# Loopcard
> Shareable bill cards for coding agents. Files stay in the browser.
> Not an MCP gateway. Not CryptoBook social. Virtus Labs.
> https://cryptobook.space

Update llms.txt when the new domain is live. Keep the two “not” lines.

Page briefs (paste-ready)

`/` Home

title: Loopcard — the screenshot after a runaway agent
description: Turn a Claude or Cursor bill into a shareable agent bill card. One click. No account. Files stay in the browser. Not a gateway.
canonical: https://cryptobook.space/
og:title: Loopcard — the screenshot after a runaway agent
og:description: Someone’s Claude Code ran overnight. About $6,000. Here’s the card. Make yours.
og:url: https://cryptobook.space/
h1: The screenshot after a runaway agent.

H1 already live. Do not put “CryptoBook” in the H1. Do not put “MCP” in the title.

JSON-LD SoftwareApplication (home only):

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Loopcard",
  "applicationCategory": "DeveloperApplication",
  "operatingSystem": "Web",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  },
  "description": "Shareable bill cards for coding agents. CSV parsed in the browser. Not an MCP gateway.",
  "url": "https://cryptobook.space/",
  "publisher": {
    "@type": "Organization",
    "name": "Virtus Blockchain Labs",
    "url": "https://virtusblockchainlabs.com"
  }
}

Do not add aggregateRating. We have no public ratings to cite.

`/docs` Docs

title: Loopcard docs — export Claude Code, Cursor, Anthropic CSV
description: How to export a Claude Code, Cursor, or Anthropic usage CSV, how the in-browser parser works, and what never leaves your machine.
canonical: https://cryptobook.space/docs
og:title: Loopcard docs — make a card from your export
og:description: Drop a usage CSV. Parsed here, not uploaded. ccusage JSON becomes a CSV first.
og:url: https://cryptobook.space/docs
h1: Make a card from an export you already have.

Source copy: website/docs-page.md.

`/integrations` Integrations

title: Loopcard integrations — web drop, PWA, CLI later
description: v1 is a browser drop zone. A PWA can wrap the same page. No Electron. No App Store. A CLI is later, not now.
canonical: https://cryptobook.space/integrations
og:title: Loopcard integrations — web, then PWA, then CLI
og:description: We parse a file you already exported. We do not sit in front of your agent.
og:url: https://cryptobook.space/integrations
h1: Three surfaces. One job. No store listing.

Source copy: website/integrations-page.md.

`/pricing` Pricing

title: Loopcard pricing — free at launch
description: Card PNG is free. If we charge later, it is $19/mo Pro or $49/mo Studio, and this page will say so before Stripe is on.
canonical: https://cryptobook.space/pricing
og:title: Loopcard pricing — free at launch
og:description: Download the card for $0. Unwatermarked history is a later SKU, not a silent charge.
og:url: https://cryptobook.space/pricing
h1: Simple prices. No theatre.

Paste-ready body (pricing page, not a promise of conversion):

Plan	Price	What	Status
Card	$0	Demo + on-device CSV parse → PNG	Live
Pro	$19/mo	Unwatermarked PNG, public share URL, 90-day history	Later. Not billed.
Studio	$49/mo	Team cards, CSV of the week	Later. Not billed.

On-page sentence, required:

Stripe when billing is on. Nothing is charged today. If that changes, this page changes first.

Do not show a fake checkout. Do not use $29 (Langfuse’s number). Do not say “cheaper than Cursor.”

JSON-LD Offer trio is allowed only if the visible table matches. Price 0 for Card; Pro/Studio marked availability: https://schema.org/PreOrder or omit them until billed.

`/legal` Legal

title: Loopcard legal — terms posture, not a certificate
description: Not legal advice. US-oriented. 18+. We do not scrape vendor accounts. Files stay in the browser unless you Publish aggregates.
canonical: https://cryptobook.space/legal
og:title: Loopcard legal
og:description: Not an auditor. Not AI Act certified. VPS in Germany; we will not print a fake Delaware.
og:url: https://cryptobook.space/legal
h1: Legal posture. Counsel still reviews.

Outline: 08-legal-posture.md. Do not publish Terms as if counsel signed them. Subpaths when they exist: /legal/terms, /legal/privacy. Same title pattern: Loopcard {Terms|Privacy}.

Governing law line until counsel fills it:

Governing law: to be confirmed. The VPS is in Germany. We will not invent a US entity in this footer.

FAQ schema ideas

Use FAQPage JSON-LD only for questions whose answers are already on the page in visible HTML. Do not hide answers in JSON-LD. Do not add “How much can I save?” — we do not save you money.

Home and /docs may share this block. Keep answers short.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is an agent bill card?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A shareable PNG of a coding-agent spend number — the screenshot after a runaway loop. Loopcard is that card. It is not a dashboard, a gateway, or an invoice."
      }
    },
    {
      "@type": "Question",
      "name": "What was the Claude Code overnight cost in the demo?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "About $6,000, from published 2026 reporting. The demo card is a labeled re-creation of that story. It is not anyone’s Anthropic invoice and not access to an account."
      }
    },
    {
      "@type": "Question",
      "name": "Do I need an account or API keys?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. The demo is one click. Optional CSV or JSON is read with FileReader in this browser. We never ask for model keys."
      }
    },
    {
      "@type": "Question",
      "name": "Does Loopcard upload my usage file?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No, not for parse or download. The file never leaves the device unless you later hit Publish. Publish, when it exists, sends aggregates only (amount, source label, row count, kind) — not the file, not prompts, not keys."
      }
    },
    {
      "@type": "Question",
      "name": "Is Loopcard an MCP gateway?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. We do not proxy tools, sit in front of MCP servers, or store traces. Permit.io already is that URL. We make the PNG."
      }
    },
    {
      "@type": "Question",
      "name": "Does this stop a runaway agent?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Cursor spend limits and Claude usage caps do that. Loopcard shows the bill after. We will not claim we stop the loop."
      }
    },
    {
      "@type": "Question",
      "name": "Is this CryptoBook social?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. CryptoBook social is retired as a product. Loopcard is a bill card from Virtus Labs. The preview may live on cryptobook.space until a clean domain is bought."
      }
    },
    {
      "@type": "Question",
      "name": "How much does Loopcard cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Free at launch. If we bill, Pro is $19/mo and Studio is $49/mo, stated on the pricing page before Stripe is on."
      }
    }
  ]
}

Optional extras (only if the matching page ships):

Page	Extra FAQ
`/docs`	How do I export Anthropic CSV? How do I turn ccusage JSON into a CSV? Why did “no cost column” fire?
`/integrations`	Why no Electron? Why no App Store? When is the CLI?
`/legal`	Do you scrape Anthropic or Cursor? (No. CFAA path. You export.) What logs exist? (nginx IP/UA. Theme in `localStorage`.)

Keywords we WILL target

These match the job: make the agent bill into a card. Bid or write pages only for this list. Match copy already on the home page.

Primary (use in title or H1 somewhere in the set):

agent bill card
claude code overnight cost

Secondary (H2, body, FAQ — not stuffed into every title):

coding agent bill card
shareable agent spend card
claude code bill card
cursor usage card
cursor spend screenshot
anthropic usage csv card
overnight agent bill
runaway coding agent screenshot
ccusage to png
claude code cost card

Long-tail we may answer in /docs (informational, not ads):

how to export anthropic usage csv
how to export cursor usage csv
ccusage json to csv
claude code /usage vs csv export

On-page entities we may name (as sources or “not us,” never as our category):

Claude Code, Cursor, Anthropic Console, ccusage
Virtus Labs
the published ~$6,000 overnight (labeled re-creation)

Do not buy ads until the operator says so. Default media spend is $0. If ads ever run, they use the primary pair only.

Keywords we will NOT target

Do not rank, bid, or write comparison pages for these. They are either killed products, other companies’ jobs, or leftover domain tax.

Do not target	Why
MCP gateway / “best MCP gateway 2026”	Permit.io owns it. Slip is dead.
MCP proxy, agent.security, “permit for agents”	Same kill.
quantum / quantum computing as a service / QPU classroom	IBM gives it away. We are a pink square.
AI Act compliance / NIST / SOC 2 software	We have not been audited. Forbidden claim.
observability, traces, Langfuse, LangSmith	Different job. We do not store prompts.
agent SSO / control plane	Okta Agent SSO is $0 extra on core SSO.
“cheaper than Cursor” / “Cursor alternative”	Different job. We are not a model lab.
crypto twitter alternative / CryptoBook social	Retired product. Conversion tax.
token ticker, airdrop, community coin	Securities surface.
“stop runaway agents” as a keyword	We show the bill. Vendors stop the loop.

If a contractor drafts a blog titled “MCP gateway vs Loopcard,” delete it.

Sitemap (when the inner pages exist)

https://cryptobook.space/
https://cryptobook.space/docs
https://cryptobook.space/integrations
https://cryptobook.space/pricing
https://cryptobook.space/legal

Omit /app, /login, /c/* until share URLs are real. Preview today is a single / — do not 200-fake the other routes in the sitemap before they render.

What success is (honest)

A ranked page is optional. A posted PNG is the metric. If / is indexed and the card still looks like the live preview, SEO did its job. If someone finds us by searching “MCP gateway,” we wrote the wrong title.