feat: add Economy Designer + improve Reality Checker & SEO Specialist (#748)

Consolidated landing of three gated contributions:

- Economy Designer (game-development) — virtual economy specialist:
  currency systems, sources/sinks, monetization modeling, inflation
  control, live economy tuning. Distinct from the generalist Game
  Designer. (#651, @blockersiontko)
- Reality Checker — add the missing "Critical Rules You Must Follow"
  section, filling a canonical-template gap. (#746, @a01066983478-lgtm)
- SEO Specialist — add a Pre-GSC keyword-cannibalization audit and
  hreflang implementation template (URL inventory, query-intent overlap,
  title/H1 deconfliction, canonical/language hygiene). (#747, @kyle1188)

README roster row added for Economy Designer; Hermes generated count
269 -> 270. All guards green (divisions/tools/runbooks/hermes-plugin/lint).

Closes #651
Closes #746
Closes #747

Co-authored-by: blockersiontko <blockersiontko@users.noreply.github.com>
Co-authored-by: a01066983478-lgtm <a01066983478-lgtm@users.noreply.github.com>
Co-authored-by: kyle1188 <kyle1188@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Michael Sitarzewski
2026-07-30 16:06:51 -05:00
committed by GitHub
co-authored by blockersiontko a01066983478-lgtm kyle1188 Claude Opus 4.8
parent 8ef49232e0
commit c89557f785
5 changed files with 220 additions and 1 deletions
+49
View File
@@ -159,6 +159,44 @@ For each conflict:
- [ ] Verify canonical tags are self-referencing (no cross-canonicals unless merging)
```
### Cannibalization Audit Without GSC (Pre-Access Fallback)
The template above assumes Search Console access. When it isn't available yet — new site, client
hasn't granted access, or you're auditing a competitor — use this sitemap + query-intent method
instead. Battle-tested on a single-page-anchor + sub-page architecture (e.g. a game-guide site where
the homepage holds anchor sections for multiple entities and each entity also has a dedicated
`/guides/entity-build` sub-page).
```markdown
# Pre-GSC Cannibalization Audit: [Topic Cluster]
## Step 1: Inventory Every URL Touching the Topic
Pull the full sitemap.xml and list every URL whose <title>, H1, or body mentions the target entity
(e.g. a character name). Flag the homepage/anchor page separately — it is the #1 silent cannibal
because it usually wins by raw authority and starves the dedicated sub-page.
| URL | Mentions Topic? | Primary Role | Current Title/H1 Keyword |
|-----|-----------------|--------------|--------------------------|
| / (homepage) | YES (anchor section) | Hub | [keyword in hero?] |
| /guides/entity-build | YES | Dedicated | [entity] build |
## Step 2: Query-Intent Overlap Check
For each URL pair, ask: "If a user searches [primary keyword], which ONE page should win?"
- Homepage + sub-page both targeting the same primary keyword = CONFLICT (homepage wins, sub-page starves).
- Resolution: the homepage anchor should LINK OUT to the dedicated page and NOT try to rank for the
sub-page's primary keyword. Give the homepage its own distinct primary keyword.
## Step 3: Title/H1 Deconfliction (no GSC needed)
Grep every page's <title> and H1 for the target primary keyword. Two pages sharing the same primary
keyword in title+H1 = guaranteed internal competition. Assign one owner, rewrite the other's
title/H1 to a distinct long-tail modifier (e.g. "...build" vs "...best team comps 2026").
## Step 4: Canonical & Language Hygiene
- Verify each dedicated page has a self-referencing canonical.
- If a URL mixes languages (e.g. Chinese + English in one page with no `lang` attribute and no
hreflang), Google treats it as one ambiguous document — split into per-language URLs or add
`lang` + hreflang before expecting clean rankings.
```
### On-Page Optimization Checklist
```markdown
# On-Page SEO Optimization: [Target Page]
@@ -296,6 +334,17 @@ For each conflict:
- International site architecture decisions: ccTLDs vs. subdirectories vs. subdomains
- Geotargeting configuration and Search Console international targeting setup
**Hreflang Implementation Template** (validated on a mixed CN/EN game-guide site):
```html
<!-- On EVERY language-variant URL, declare the full set RECIPROCALLY -->
<link rel="alternate" hreflang="en" href="https://site.com/guides/zhongli-build-en" />
<link rel="alternate" hreflang="zh" href="https://site.com/guides/zhongli-build-zh" />
<link rel="alternate" hreflang="x-default" href="https://site.com/guides/zhongli-build-en" />
```
- **Reciprocity is mandatory**: every `hreflang` URL must link back to all others, or Google ignores the entire set.
- **`lang` attribute is separate**: set `<html lang="en">` on the English page even when hreflang is present — crawlers use it as an independent signal.
- **Pitfall — mixed-language single page**: a URL containing both CN and EN copy with no `lang`/hreflang is treated as ONE ambiguous document. Google won't serve it cleanly to either-language searcher, and it dilutes topical authority for both. Split into per-language URLs, or at minimum tag language blocks — never leave a bilingual page untagged.
### Programmatic SEO
- Template-based page generation for scalable long-tail keyword targeting
- Dynamic content optimization for large-scale e-commerce and marketplace sites