Repository navigation
fix(seo): list pub.dev packages on the pub registry page - #33
Merged
Merged
Conversation
Packages and the registries API use "pub", so filtering by "pub.dev" matched nothing and left an empty page that could be indexed. A registry page with no packages is now noindex. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
Makes the pub.dev registry page list its packages, and keeps any registry page with no packages out of search results.
Why
Closes #32
The filter added in #29 used
pub.dev, while the packages and the registries API usepub. The page showed none of the 57 packages, answered 200 and could be indexed, and the sitemap andllms.txtlinked to it.Changes
/packagestreatspubas the registry value and acceptspub.devas an alias, so the chip now shows as selected.llms.txtlink to/packages?registry=pub.noindex.Notes for reviewers
No config or data change is needed. The sitemap is cached in memory for an hour, so the new URL can take up to an hour to appear after deploy. No build or test was run locally.
Checklist
Closes #NNNabove)developand is about one thingfeat(scope): ...,fix(scope): ...)src/frontend/src/app/core/models