fix(seo): use derived noindex for shadow-banned profiles#6019
Merged
Conversation
Selects the new server-derived `noindex` field from the API on the public profile page, so shadow-banned (vordr) users get `<meta name="robots" content="noindex,nofollow">` without changing the visible page content. Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Touched by the noindex change, so the strict-changed guard surfaces pre-existing errors. Narrow types via guards/optionals without changing runtime behavior. Co-authored-by: Cursor <cursoragent@cursor.com>
idoshamun
approved these changes
May 10, 2026
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
Companion to dailydotdev/daily-api#3864.
The profile page's
getStaticPropscurrently usesnoindex: user.reputation <= 10, which misses shadow-banned (vordr) users withreputation > 10— they get indexed and inbound links pass equity. This PR consumes the new server-derivedUser.noindexfield from the API instead.noindexinUSER_BY_ID_STATIC_FIELDS_QUERY.noindex?: booleantoPublicProfile(optional to avoid touching unrelated test/storybook fixtures; the API guarantees a value at runtime).noindex: user.reputation <= 10withnoindex: !!user.noindexinProfileLayout/getStaticProps.The visible page content is unchanged — only the
<meta name="robots">tag changes, preserving the shadow-ban illusion.Test plan
curl https://app.daily.dev/<vordr-user-slug>-> 200 with<meta name="robots" content="noindex,nofollow">.curl https://app.daily.dev/<vordr-user-slug> | grep robotsfor a non-vordr rep>10 user -> no robots meta tag (or only the default).Made with Cursor
Preview domain
https://fix-vordr-profile-noindex.preview.app.daily.dev