8000 ci: require SEO checks for article work by geminiKim · Pull Request #11 · geminiKim/geminikim.github.io · GitHub
[go: up one dir, main page]

ci: require SEO checks for article work - #11

Merged
geminiKim merged 1 commit into
mainfrom
chore/enforce-article-seo
Aug 12, 2026
Merged

geminiKim merged 1 commit into
mainfrom
chore/enforce-article-seo

Conversation

@geminiKim
Copy link
Copy Markdown
Owner

Summary

  • add a repository-wide mandatory SEO contract for every article add/edit/translation/removal
  • add a fail-closed verifier for all English/Korean article pairs and generated metadata
  • run the verifier in the existing PR and deployment build gate
  • document the publishing workflow in the README
  • update vulnerable transitive lockfile packages discovered during dependency installation

Enforced article contract

  • complete EN/KO pairs, matching translation keys, dates, draft state, and ordered tags
  • valid calendar dates and mapped taxonomy tags, including drafts and nested content paths
  • unique localized titles/descriptions with bounded lengths
  • localized browser title, meta description, and H1
  • canonical, hreflang, x-default, RSS, and sitemap coverage
  • English social title policy plus localized social descriptions
  • exact BlogPosting headline, description, publication date, language, and canonical ID
  • source-date-only handling for video-derived articles

Verification

  • npm ci
  • npm run build
  • node --no-experimental-strip-types scripts/verify-article-seo.mjs
  • node --no-experimental-strip-types scripts/verify-taxonomy.mjs
  • npm audit --audit-level=high
  • git diff --check
  • independent Codex review: no remaining correctness regressions

@geminiKim
geminiKim merged commit b5b8090 into main Aug 12, 2026
2 checks passed
@geminiKim
geminiKim deleted the chore/enforce-article-seo branch August 12, 2026 04:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0