Operator

Launch & messaging kit

Ready-to-use descriptions and share drafts for promoting Warconomy — by audience (researchers, AI/data, readers), with top share URLs, the manual indexing setup, and the standing caveats. Messaging only; no traffic or credibility claims, no data values.

Copy-paste messaging so promoting Warconomy later takes no thinking: a one-liner, a paragraph, audience-specific pitches, and channel drafts — all honest and caveated. It makes no traffic, ranking, or credibility claims and repeats the standing caveats (not live market data, not investment/legal advice). It stores no data values.

  • One-liner + paragraph + by-audience pitches.
  • Channel drafts (HN/Reddit, LinkedIn, short).
  • Top share URLs + the manual indexing setup steps.
  • Machine-readable at /operator/launch/data.json.
Messaging only — keep it honestMake no traffic, ranking, or credibility claims that are not true. Warconomy is a source-linked reference — not live market data, a live ship tracker, or investment/legal/compliance advice, and it does not claim complete coverage.

One-liner

Warconomy is a data-first, source-linked reference for the economic impact of wars, sanctions, shipping chokepoints, commodities, and defense spending — built to be cited.

Paragraph

Warconomy tracks how conflicts, sanctions, chokepoint disruptions, and commodity and defense-spending shifts are associated with the global economy. Every figure is source-linked and dated, with a clear live/static-vs-sample label, a published methodology, and a downloadable static dataset (no runtime API, no keys). It is a reference layer for people and AI/search tools to cite — not a news site, not real-time market data, and not investment or legal advice. Coverage is partial and honestly labeled.

By audience

Researchers & journalists

Stable, dated, source-linked pages with citation formats (BibTeX/RIS) and a per-figure trail back to the original source. Cite the original source first; cite Warconomy for the structured overview.

Share: /conflicts/russia-ukraine/economic-impact · /citations · /sources · /methodology

AI / search / data people

A static, machine-readable dataset (JSON + CSV/JSONL + citation graph), an LLM crawler brief, a query-to-route matrix, and JSON-LD on every page — no keys, no rate limits. Built to be extracted and cited cleanly.

Share: /datasets/conflict-economic-impact · /api · /llms.txt · /queries

General / curious readers

Plain-English explainers of why a chokepoint or sanction matters economically, with the data and its limits stated up front. Start with the questions hub or explore.

Share: / · /questions · /explore · /chokepoints/strait-of-hormuz/economic-impact

Channel drafts

Hacker News / Reddit (Show / data)

Warconomy — a source-linked reference for the economic impact of wars, sanctions, and shipping chokepoints. Static and citation-first: every figure is dated and linked to its official source, with a downloadable dataset (JSON/CSV) and no runtime API. It's not real-time market data and not investment advice — a reference layer to cite. Feedback on the data model and caveats welcome.

LinkedIn

Sharing Warconomy: a data-first reference tracking the economic impact of conflicts, sanctions, chokepoints, commodities, and defense spending. Each figure is source-linked and dated, with a published methodology and a downloadable static dataset. It is a citation layer, not live market data or investment/legal advice.

Short / social

Warconomy: source-linked economic-impact reference for wars, sanctions & chokepoints. Dated figures, downloadable dataset, published methodology. Not live market data, not advice.

Top share URLs

  • https://warconomy.com/
  • https://warconomy.com/questions
  • https://warconomy.com/conflicts/russia-ukraine/economic-impact
  • https://warconomy.com/chokepoints/strait-of-hormuz/economic-impact
  • https://warconomy.com/datasets/conflict-economic-impact

Manual indexing setup (one-time)

  1. Google Search Console + Bing Webmaster Tools: done (per the maintainer).
  2. Google Analytics 4: basic pageviews enabled — verify the Realtime report after visiting the site (data can lag for new properties).
  3. Re-submit https://warconomy.com/sitemap.xml in GSC after major route additions; request indexing for the top share URLs.
  4. warconomy.org, if ever bought, is a defensive 301 to warconomy.com only — not a content site.

Full checklist: /methodology/indexing.

Analytics (Google Analytics 4)

  • Status: GA4 basic pageviews enabled (pageview-only; no GTM, ads, remarketing, or conversion tracking).
  • Measurement ID: G-1WBVY53RJM (public; in the page HTML).
  • Verify: Visit warconomy.com, then check Google Analytics → Reports → Realtime; new properties can take up to ~24-48h for non-Realtime reports to populate.
  • Privacy: disclosed at /privacy — pageview-only, no ads/remarketing/conversion tracking.

warconomy.org strategy (note only — no DNS work)

  • Status: Not configured. No DNS, no second deployed site, no redirects set up. warconomy.com remains canonical.
  • Defensive option: warconomy.org can be bought defensively and, if so, pointed as a 301 redirect to warconomy.com only — a brand alias, not a content site.
  • Possible future: A possible future split: warconomy.com as the canonical data/citation engine, warconomy.org as a public visual dashboard (e.g. the commodity-history charts) backed by the SAME data.
  • Risks: Duplicate-content / SEO dilution if both sites publish the same pages without strict canonicalization. Double maintenance and deploy surface. Brand/analytics fragmentation.
  • Recommendation: For now keep everything on warconomy.com. Only pursue a two-site strategy as a deliberate, owner-approved decision — not as a side effect of buying the domain.

Always include these caveats

  • Not live market data and not real-time; live values are manually maintained and may lag.
  • Not investment, legal, or sanctions-compliance advice.
  • Not a live AIS / ship tracker and not a complete source of coverage.
  • Make no traffic, ranking, or credibility claims that are not true.

Operator workbench · Morning report · /operator/launch/data.json