Repository navigation
Fix pregnancy hub ItemList: recommend only crawl-eligible locale tool pages - #100
Merged
Merged
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
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.
Problem
Toolify's pregnancy hub is sitemap-indexed for EN/JA. It currently publishes
ItemListJSON-LD for all seven steps, including deliberatelynoindexdestinations (menstrual-cycle-calculator,pregnancy-weight-gain-calculator,hcg-calculator). The normal/toolscatalog already correctly filters its ItemList byisIndexableIn(locale, slug), but/pregnancydid not. This creates inconsistent crawl/index recommendations and dilutes site-focused guidance.Changes
ItemListJSON-LD using the existingisIndexableIn(locale, tool.slug)—the same source of truth as tool-page robots metadata andsitemap.ts. FixnumberOfItemsto match emitted URLs.site/package.jsonprebuild before network-dependent fetch-rates.Verification
13/13 structural/policy assertions passed against current PR branch read back from GitHub, including 7 visible steps, canonical index policy, sitemap consistency, counted JSON-LD and prebuild test. Native Node suite, full Next build, live VPS deployed SHA, GSC recrawl and ranking impact were not verified in this connector runtime. No indexing directives or URLs changed. This is a truthful structured-data correction, not evidence of traffic growth.