Skip to content

fix(seo): add missing journal article to sitemap.xml#46

Open
VaultSparkStudios wants to merge 1 commit into
mainfrom
autopilot/sitemap-journal-building-vault-membership
Open

fix(seo): add missing journal article to sitemap.xml#46
VaultSparkStudios wants to merge 1 commit into
mainfrom
autopilot/sitemap-journal-building-vault-membership

Conversation

@VaultSparkStudios

Copy link
Copy Markdown
Owner

What

Adds /journal/building-vault-membership/ to sitemap.xml.

Why

This public journal article was the only one of 12 journal articles missing from the sitemap. All 11 others (community-enters-the-vault, dreadspike-origins, first-sparks, etc.) are in the sitemap; this one was never added.

The page is fully public:

  • <meta name="robots" content="index, follow">
  • Canonical URL: https://vaultsparkstudios.com/journal/building-vault-membership/
  • JSON-LD BlogPosting schema with datePublished: 2026-03-10
  • No auth gating

Without a sitemap entry Google has to discover this URL via a link crawl rather than the authoritative sitemap, reducing crawl efficiency and delaying indexing.

Change

One 6-line <url> block inserted in alphabetical order between journal/archive/ and journal/community-enters-the-vault/, matching the priority (0.8) and changefreq (weekly) of every other journal article. Sitemap URL count: 127 → 128.

What to verify

  • The sitemap entry renders correctly at https://vaultsparkstudios.com/sitemap.xml
  • The article is publicly accessible at https://vaultsparkstudios.com/journal/building-vault-membership/
  • npm run build:check stays green (this change touches no generated artifact — the sitemap here is the source-of-truth file for journal entries, managed manually)

Automated quality pass — autopilot agent, 2026-07-13


Generated by Claude Code

/journal/building-vault-membership/ is a public, indexable BlogPosting
article (robots: index, follow; canonical URL; JSON-LD schema) but was
absent from sitemap.xml while all 11 other journal articles were present.
Adds the entry in alphabetical order at priority 0.8/weekly, matching
every other journal article in the sitemap.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0161AHwasiMsQExbJ4yhdQL7

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8f03d4f8ca

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread sitemap.xml
<priority>0.8</priority>
</url>
<url>
<loc>https://vaultsparkstudios.com/journal/building-vault-membership/</loc>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Anchor the vault-member sitemap exclusion

This sitemap entry will be removed the next time the Generate Sitemap workflow runs on main: I checked .github/workflows/sitemap.yml, and its generation step pipes every index.html through grep -vE "$EXCLUDE" while EXCLUDE contains the unanchored token vault-member, which also matches journal/building-vault-membership/index.html (verified with the workflow regex). Since the workflow rewrites sitemap.xml and commits changes on push/dispatch, fixing the missing article only in the generated file is not durable; tighten the exclusion to the private /vault-member/ path or otherwise update the generator so this URL survives regeneration.

Useful? React with 👍 / 👎.

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.

2 participants