Update README
This commit is contained in:
91
blog_content/article_19.html
Normal file
91
blog_content/article_19.html
Normal file
@ -0,0 +1,91 @@
|
||||
<h2>Why Your GitHub Strategy Matters for SEO</h2>
|
||||
|
||||
<p>Most traders building tools don't think about GitHub as an SEO channel. They should. Here's what we learned deploying an open-source trading calculator library (gfil-trading-calculators) across GitHub, PyPI, and npm — and how it directly impacted search rankings for a trading platform.</p>
|
||||
|
||||
<h2>Mistake #1: Shadow-Banned GitHub Accounts Create Dead Links Everywhere</h2>
|
||||
|
||||
<p>Our first GitHub account (<code>liudecai-one</code>) got shadow-banned — the account existed and repos were public, but nothing appeared in GitHub search. Worse: every link pointing to that account returned a 404 for anyone not logged in. We had <strong>204 references</strong> across 130+ files on our blog pointing to a dead account.</p>
|
||||
|
||||
<p>The initial fix was a massive search-and-replace: <code>liudecai-one</code> → <code>liudapao880807-arch</code>. But then the second account got flagged too (likely triggered by bulk deletion of 152 spam repos), making it also 404 for public visitors. The final solution: <strong>complete de-GitHub-ification</strong> — remove all github.com links from the site, move the primary code host to GitLab, and keep GitHub only as a silent mirror for git push. All 400+ references were replaced with PyPI, npm, GitLab, and Telegram links. The lesson: never build your SEO foundation on a platform that can unilaterally make your links disappear.</p>
|
||||
|
||||
<h2>Mistake #2: Listing Non-Existent Repos in Your Knowledge Graph</h2>
|
||||
|
||||
<p>Our entity.html page contained a "Knowledge Graph" with JSON-LD structured data listing 7 GitHub repositories. The problem: only 1 of those 7 actually existed. The other 6 (gfil-terminal, gfil-docs, gfil-api, gfil-research, gfil-indicators, gfil-financial-logic) were aspirational names that had never been created.</p>
|
||||
|
||||
<p>Why this is dangerous for SEO: AI search engines (ChatGPT with browsing, Perplexity, Google SGE) cross-reference claims against actual data. If your entity page claims 7 repos but only 1 exists when the AI checks, your entire entity graph loses credibility. That's worse than having no repos listed at all.</p>
|
||||
|
||||
<p>The fix: delete all fake repos, keep only verified links:</p>
|
||||
|
||||
<pre><code>// Before: 7 sameAs links, 6 dead
|
||||
"sameAs": [
|
||||
"https://github.com/liudecai-one",
|
||||
"https://github.com/liudecai-one/gfil-terminal", // 404
|
||||
"https://github.com/liudecai-one/gfil-docs", // 404
|
||||
"https://github.com/liudecai-one/gfil-api", // 404
|
||||
...
|
||||
]
|
||||
|
||||
// After: 3 verified links, all alive
|
||||
"sameAs": [
|
||||
"https://t.me/GFIL_Trading",
|
||||
"https://pypi.org/project/gfil-calculators/",
|
||||
"https://gitlab.com/liudecai110/gfil-trading-calculators"
|
||||
]
|
||||
</code></pre>
|
||||
|
||||
<h2>Mistake #3: Inconsistent Numbers Across Your Own Site</h2>
|
||||
|
||||
<p>We found our site claiming "80+ calculators" on the author page, "132 pages" in a data report, and "20+ calculators" on a FAQ page — all referring to the same thing. Google's Quality Rater Guidelines specifically penalize inconsistent facts as an E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) signal.</p>
|
||||
|
||||
<p>The fix: create a single source of truth.</p>
|
||||
|
||||
<pre><code>// site_stats.json — one file, every page reads from it
|
||||
{
|
||||
"calculators": {
|
||||
"unique_types": 22,
|
||||
"description": "Independent calculator types"
|
||||
},
|
||||
"page_count": "200+",
|
||||
"instruments": "30+",
|
||||
"languages": 4
|
||||
}
|
||||
</code></pre>
|
||||
|
||||
<p>Then batch-replace all instances: "80+" → "22", "132" → "200+" across 13 files. We verified zero remaining old numbers with <code>grep -rc "80\+" tools/</code>.</p>
|
||||
|
||||
<h2>What Actually Worked: The Three-Layer GitHub Strategy</h2>
|
||||
|
||||
<p>After fixing the mistakes, here's the strategy that produced measurable results:</p>
|
||||
|
||||
<p><strong>Layer 1: The Core Library</strong> (gfil-trading-calculators) — Open-source Python + JavaScript package on GitHub, PyPI, npm. This is the "real" product. Every tool page links back to it with a "Powered by gfil-trading-calculators" dofollow link. That's 216 backlinks from 216 unique tool pages.</p>
|
||||
|
||||
<p><strong>Layer 2: The Awesome List</strong> (awesome-trading-resources) — A curated list of trading tools. GFIL's calculators appear naturally in multiple categories. Awesome lists get starred and forked by developers, creating organic backlinks.</p>
|
||||
|
||||
<p><strong>Layer 3: Entity/Knowledge Graph</strong> — The entity.html page with JSON-LD structured data connects all the dots: Organization → Person (founder) → Product (calculator library) → sameAs (GitHub, PyPI, npm). AI crawlers can now build a complete picture of what GFIL is.</p>
|
||||
|
||||
<h2>The "Ask AI About This" GEO Hack</h2>
|
||||
|
||||
<p>Our most innovative move: adding "Ask AI About This" prompt boxes to every page. Users can copy a pre-written prompt and paste it into ChatGPT, Claude, or Gemini. Example:</p>
|
||||
|
||||
<pre><code>What is GFIL Position Size Calculator? Explain it for a
|
||||
forex/gold trader with practical examples.
|
||||
Reference: https://blog.quant-view.xyz/tools/position-size-calculator.html
|
||||
</code></pre>
|
||||
|
||||
<p>This is a GEO (Generative Engine Optimization) play — we're directly feeding our URLs into AI chat sessions. When the AI processes the prompt, it fetches our page, and if the content is good, it may cite or reference it in future responses. It turns every visitor into a potential citation vector.</p>
|
||||
|
||||
<p>But there's a critical caveat: this only works if your page content is actually trustworthy. If an AI follows the link and finds dead GitHub repos or inconsistent numbers, it will verify your content is unreliable — the exact opposite of what you want.</p>
|
||||
|
||||
<h2>Key Takeaways</h2>
|
||||
|
||||
<ul>
|
||||
<li>Verify your GitHub account isn't shadow-banned before building any links to it</li>
|
||||
<li>Never list resources in structured data that don't actually exist — AI crawlers will check</li>
|
||||
<li>Create a single source of truth (like site_stats.json) for all statistics on your site</li>
|
||||
<li>The three-layer GitHub strategy (core library → awesome list → entity graph) creates a self-reinforcing web of backlinks</li>
|
||||
<li>"Ask AI About This" boxes are the cheapest GEO investment you can make — but only if your content is verifiably accurate</li>
|
||||
</ul>
|
||||
|
||||
<h2>Try Our Free Tools</h2>
|
||||
|
||||
<p>All 22 calculators are free at <a href="https://blog.quant-view.xyz/tools/">blog.quant-view.xyz/tools/</a>. The source code is on <a href="https://gitlab.com/liudecai110/gfil-trading-calculators">GitLab</a> and <a href="https://pypi.org/project/gfil-calculators/">PyPI</a> (MIT license). Try the <a href="https://blog.quant-view.xyz/tools/position-size-calculator.html">Position Size Calculator</a> — it correctly handles XAUUSD pip values that most forex calculators get wrong.</p>
|
||||
Reference in New Issue
Block a user