feat(indexing): discourage search indexing of generated directory pages - #349
feat(indexing): discourage search indexing of generated directory pages#349seonghobae wants to merge 1 commit into
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Warning Review limit reached
Next review available in: 16 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Comment |
seonghobae
changed the title
1 participant
Product behavior
Generated directory pages may be served on a public web origin even when the operator does not want them listed by cooperative search engines. Add one page-level robots directive in
<head>:Claim boundary
This is a discoverability preference, not authentication, authorization, access control, confidentiality, or a crawler firewall. Google documents that
noindexis applied only after a supporting crawler can fetch and read the page; other crawlers may interpret directives differently. Confidential content must be removed or protected at the server boundary. The PR must not describe this hint as preventing every bot from crawling, following, discovering, or accessing a page.Current status
This branch overlaps the HTML
<head>changed by canonical CSP PR #363 and is intentionally not merge-ready. After #363 integrates, it must be rebuilt or updated on protectedmasterwithout changing the exact emitted-style/CSP byte contract.Before returning to ready-for-review it must:
CHANGELOG.mdand authoritativedocs/doctoringdocumentation with an APA 7 reference to current Google Search Central guidance;noindexrequires the crawler to access the page and that private data still requires server-side protection;Queued, pending, skipped-required, cancelled, absent, stale-head, or failed checks are not success. Reviews and checks from duplicate robots-meta branches are not reusable.