Repository navigation
fix(seo): exclude intentional hubs from recovery decisions - #661
Conversation
|
🤖 Harlan Agent Kit Agent assessment of head 2cba8a6. The Service reported The independent review found no defects. Confidence: 95/100. Future Monday report generation was traced, not executed. CI passed for this head, including build, tests, typecheck, lint, and the harness and declared-Skills checks. NuxtSEO's saved keychain credential was unavailable, so this check-in provides no new Google indexing or traffic result. |
|
🤖 Harlan Agent Kit Agent assessment of head 4a6156c. The Service reported The independent review found no defects. Confidence: 95/100. Future Monday report generation was traced, not executed. CI passed for this exact head, including build, tests, typecheck, lint, and the harness and declared-Skills checks. This assessment supersedes the earlier head's authentication limitation: renewed NuxtSEO pairing succeeded during this check-in. |
🔗 Linked issue
SEO recovery check-in for the 11 November gate.
❓ Type of change
📚 Description
The recovery panel counted an intentionally noindex Repository hub among ten active baseline URLs.
Record its dated exclusion and require later measurements to report it separately, preserving all 41 original URLs and their history.
Log the dated Google Checkpoints, search totals, and evidence gaps without treating them as a complete Monday comparison.