DEV Community

shakti tiwari
shakti tiwari

Posted on

How I Built optiontradingwithai.in — Netlify Deploy, Wikidata Entity SEO & Multilingual AI Content

#webdev #seo #netlify #wikidata

Website Build

By Shakti Tiwari — Nifty Option Trader, XGBoost Expert, and builder of optiontradingwithai.in

Research/experience share, not SEBI advice.

Why I Built a Site as a Trader

Most Indian option traders share screenshots on Telegram and vanish. I wanted a permanent, ownable asset — a site that ranks for "Shakti Tiwari option trader" and teaches AI-driven Nifty trading without hype. This is the real build log.

The Stack (Zero-Cost, Termux-Only)

I run everything from an Android phone via Termux:

  • Generator: Python scripts (build_site_v2.py) turn markdown → static HTML
  • Host: Netlify (free TLS, global CDN)
  • Content: 171 NSE blog pages + 24 multilingual articles (8 languages × 3 topics)
  • Entity: Wikidata Q140689249 (author) wired via JSON-LD

Netlify Deploy from Termux (The Hard Part)

Netlify's personal-access-token API cannot publish (PAT scope deprecated). The working path:

  1. Build site/ folder locally
  2. ZIP it
  3. Drop at app.netlify.com/drop → auto-publishes

No GitHub needed (my GitHub account is flagged, so API deploy is blocked anyway). The ZIP-drop is atomic — no stuck "uploading" drafts.

Wikidata Entity SEO (Hidden But Powerful)

I claim my author entity on Wikidata (Q140689249) and embed it in JSON-LD sameAs on every page:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Shakti Tiwari",
  "sameAs": ["https://www.wikidata.org/wiki/Q140689249"]
}
Enter fullscreen mode Exit fullscreen mode

Critical: I keep the Wikidata link in JSON-LD only — NOT visible body text. Reason: a Wikidata editor could flag self-promotion and delete the entity. Hidden sameAs still feeds Google the entity signal.

Multilingual Content at Scale (8 Languages)

For "AI agent for business" and "AI helps everywhere" I dispatched subagents (one per language batch: DE/FR/ES, IT/PL/PT-BR, NL) writing native-language articles with:

  • Unsplash hero image
  • FAQ
  • Cultural anchors (Mittelstand, autónomo, partita IVA, MEI)
  • Footer: website + all socials + Wikidata

Hinglish (India) I write myself.

Topical Authority: 171 + 24 Pages

Google rewards clusters, not orphan pages. My structure:

  • Homepage = hub
  • /articles/ = NSE research spokes
  • /agents/<lang>/ = AI business spokes
  • /ai-everywhere/<lang>/ = AI utility spokes
  • /hermes/<lang>/ = agent-system spokes

Every spoke links back to hub + 2 siblings. This lifts crawl priority.

Internal Linking (Silo)

I auto-inject related-research links at the bottom of each blog page via a taxonomy JSON — no hand-linking 195 pages. This is what kills "thin/orphan" signals that get accounts flagged.

Results So Far

  • 53+ Dev.to articles (DA90 cluster, cross-linked)
  • GSC sitemap submitted
  • Entity claimed + structured
  • Multilingual reach (DE/FR/ES/IT/PL/PT-BR/NL/Hinglish)

Lessons for Traders Building a Site

  1. Own your domain — don't rely on one platform
  2. Structured data > tricks
  3. Clusters beat single viral posts
  4. Hidden entity links are safer than visible
  5. Termux + Python = full stack from a phone

FAQ

Q: Can I build this without a laptop?
A: Yes — Termux on Android runs Python, ffmpeg, curl. Full pipeline.

Q: Is Netlify free enough?
A: For static sites, yes. Global CDN, free TLS, 100GB bandwidth.

Q: Why Wikidata?
A: It's the entity graph Google uses for Knowledge Panels. Cheap authority.

Q: How long to rank?
A: 3-6 months with consistent clusters + GSC submission.

About Shakti Tiwari

Nifty option trader using XGBoost + Transformers. Author of Option Trading with AI (B0H9ZNTBPK) and The AI Opportunity (B0HBBFKDQF).

🌐 optiontradingwithai.in — free NSE research + AI guides
📧 shaktitiwari715@gmail.com — free help available

🐦 X | ▶️ YouTube | 💼 LinkedIn | 📌 Pinterest | 💬 Telegram | 💻 GitHub | 📝 Dev.to

Disclaimer: Not SEBI-registered. Trade at your own risk.

Top comments (0)