Repository navigation
feat(seo): enable production indexing and structured metadata - #36
Draft
whateveriiwant wants to merge 1 commit into
Draft
whateveriiwant wants to merge 1 commit into
whateveriiwant wants to merge 1 commit into
Conversation
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.
Production robots.txt currently blocks all crawling while the homepage returns noindex and D1 pages force index independently. Enable indexing only for seungjun.sh and apply one metadata policy to public pages, keeping staging and version previews blocked.
Add BlogPosting, BreadcrumbList, WebSite and ProfilePage JSON-LD, visible article author links, descriptive page titles and summaries, consistent canonical/Open Graph/Twitter metadata, and canonical redirects for homepage/profile aliases. Exclude private/template routes from the static sitemap and omit inaccurate series lastmod values. CI now supplies the production origin and verified media origin, enables static indexing only on main pushes, and runs the new SEO regression test.
Validation: pnpm check (0 errors, 0 warnings, 4 hints); production build (326 pages); pnpm verify:seo with real Workers HTMLRewriter and synthetic CMS fixtures; existing D1 routes, series pagination, search and security checks; ESLint on the new SEO module/test; git diff --check; Wrangler dry run. The security verifier bundles site imports for the Workers runtime.
This change does not modify CMS code, D1/R2 data, analytics configuration, or existing user changes. Deployment must target the site Worker alone: the existing main workflow also deploys CMS. Indexing, ranking and traffic gains require subsequent Google processing and are not guaranteed by these checks.
Production rollout on 2026-10-12: deployed site Worker version 71318baa-c3d6-451e-a797-d58e86504238 at 100%, replacing b9635362-3c6d-4d49-a8bb-6d92868d5cbc. The version preview was checked to remain Disallow/noindex. Live robots now returns Allow plus the sitemap location; the runtime sitemap contains 327 public URLs. Six representative live pages passed indexing, canonical and JSON-LD checks, and deployment smoke checks passed. Search Console robots.txt issue validation visibly reports Started (2026-10-12). Google reindexing/ranking results remain unverified.
PR CI: https://github.com/whateveriiwant/devlog/actions/runs/38246688403 (success). Keep this PR unmerged until the CMS deployment side effect in the main workflow has been handled; a normal main deployment currently redeploys CMS as well. The SEO site rollout did not deploy CMS.