Repository navigation
seo: deepen the /unit/* crawl graph — /ranks no-JS body + related-unit links - #151
Merged
Merged
Conversation
…t links Indexing-lag investigation (recorded in docs/seo-followups.md): no bug — /unit/* pages serve 200 with unique SSR kit text, correct canonicals, no noindex, and the sitemap carries all 199 unit URLs. External site: sampling at ~4.5 weeks shows ~25-30 unit URLs indexed, cutting across BOTH the rich (overload-table) and kit-only tiers — the rule-4 branch, so thinness is not the cause. The closable gap was the crawl graph: /ranks (the strongest indexed page) served zero links without JS, and unit pages only linked outward to tools. - /ranks now injects ranksStaticHtml: the chart's default cell (solo.neutral.c100.scope) as a ranked list of real links to /unit/:slug, read from dist/dpschart.json — the same artifact the React chart fetches. Profiled dupes deduped to their top row; synthetic rows skipped. - Every /unit/:slug body now links its same-element and same-weapon neighbours (capped at 6 per group), in unitStaticHtml, the serve.mjs mirror, and the React UnitPage (same source: data/characters.json). - Lockstep tests in serve-api/serve-headers pin both bodies on both servers, including the synthetic-skip and profiled-dupe edges. Co-Authored-By: Kimi k3 <noreply@moonshot.cn>
Infernal-Crack-LED
added a commit
that referenced
this pull request
Oct 2, 2026
Conflicts resolved by keeping both sides: - docs/DECISIONS.md: 2026-09-03 aigis + drake-great-villain entry and the 2026-09-04 sameWeapon landing, in date order. - docs/handoffs/QUEUE.md: kit-code-audit open items + new-units follow-ups. - docs/unmodeled-entries-review.md: regenerated from merged kit-status.json. Also regenerated the engine-modeling-gaps primitive census (doc-drift --update). verify.sh green on the merged tree. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The per-character pages were appearing in Google's index far more slowly than expected (a fraction of the 199
/unit/*URLs ~4.5 weeks after launch). Investigation found no indexing bug: every/unit/:slugserves 200 with unique server-rendered kit text, correct canonical, nonoindex; the sitemap carries all 199 unit URLs; robots.txt allows everything. The indexed sample cuts across both the data-rich and kit-only page tiers — the rule-4 branch ofdocs/seo-followups.md, so thinness is not the cause.The closable gap was the no-JS crawl graph: it was hub-and-spoke.
/characterslinked every unit, but/ranks— the site's strongest indexed page — served zero links in its HTML (its unit links are React-only), and unit pages only linked outward to tools, never to each other.What
/ranksno-JS body (ranksStaticHtml, both servers): the chart's default cell (solo.neutral.c100.scope) as a ranked<ol>of real links to/unit/:slug, read fromdist/dpschart.json— the same artifact the React chart fetches, so the crawler's view can't disagree with the visitor's. Profiled duplicates deduped to their top row; synthetic DPS-test rows skipped./unit/:slugpage (relatedUnitsHtml, the serve.mjs mirror, and the ReactUnitPage): same-element and same-weapon neighbours (6 per group), same source (data/characters.json) on all three surfaces. Every crawled unit page now surfaces a dozen more unit URLs.serve-api/serve-headerspin both bodies on both servers, including the synthetic-skip and profiled-dupe edges.docs/seo-followups.md;docs/frontend-conventions.md§7 body-source table updated.Notes
site:nikkesim.app/unit/in a few weeks to confirm the indexed share is moving.Test plan
bash scripts/verify.sh— green (fast gate, post-merge)serve-api.test.ts+serve-headers.test.ts— 74/74, including new/ranksbody and related-links assertions on both servers