feat(seo): ship WA3 keyword-cluster hubs#39
Merged
Merged
Conversation
…treatments, properties) Adds four content-cluster hub pages claiming high-intent head terms from the v3 keyword landscape: - /learn/identification — "how to identify gemstones" (9-step protocol, 14 child articles linked, LearningResource JSON-LD with hasPart) - /learn/equipment — "how to use a refractometer (and the rest of the gemmological toolkit)" (7-step refractometer workflow table, 13 child articles, LearningResource JSON-LD) - /learn/identification/treatments — "synthetic diamond identification, treatments & composite stones" (11-row detection matrix, LearningResource with about[] covering HPHT/CVD/heat/diffusion/composite stones) - /reference/properties — "gemstone properties chart" (50-row RI/SG/hardness/ birefringence/system/cleavage reference table, Dataset + WebPage mainEntity:Table JSON-LD for table-rich-result eligibility) Each hub renders >=400 body words, emits at least one JSON-LD block, links to >=4 existing child pages, and breadcrumbs back to /learn/. The treatments hub collides with the dynamic [...slug] route from the gemmology-knowledge YAML article of the same path; the static hub takes precedence and the YAML slug is filtered from getStaticPaths so its content remains in the collection (referenced by the hub) without producing a duplicate route.
|
🚀 Preview deployed to: https://06272442.gemmology-dev.pages.dev |
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
1 participant
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.
Summary
Adds the four remaining keyword-cluster hub pages from the SEO v3 plan, completing WA3:
/learn/identification//learn/equipment//learn/identification/treatments//reference/properties/(new route)Each hub follows the template defined in
~/.claude/plans/piped-frolicking-matsumoto.md§WA3:<h1>claims the head term verbatim, a ~200-word lead positions the page, a child-link grid points at existing articles, and the JSON-LD declares the hub as a study unit (LearningResourcewithhasPart) or a structured dataset (the properties table). The properties hub'smainEntity: Tableis the table-rich-result eligibility lever flagged inkeywords.md.Route collision
The treatments YAML article (
gemmology-knowledge/docs/learn/identification/treatments.yaml) generates/learn/identification/treatmentsvia the dynamic catch-all. This PR adds a staticpages/learn/identification/treatments/index.astroat the same URL. The catch-all is updated to filter the slug fromgetStaticPathsso the content stays in the collection (referenced by the hub) without producing a duplicate-route build error.Acceptance (plan §WA3)
<a>npm run buildclean (916 pages, 0 schema errors)audits/seo-2026-05/v3-validation.mdTest plan
npm run buildsucceeds locallydist/with the expected word count / JSON-LD count / child-link count