Repository navigation
test(seo): lock APISIX documentation ownership signals - #2119
Merged
Merged
Conversation
Yilialinn
force-pushed
the
codex/stabilize-doc-search-signals
branch
from
September 11, 2026 09:27
59f4b71 to
0d75826
Compare
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No unresolved review issues were identified.
Pull request overview
Adds automated SEO ownership checks for APISIX documentation across Astro and Docusaurus.
Changes:
- Adds canonical, robots, hreflang, sitemap, redirect, and historical-documentation tests.
- Extracts reusable versioned-document SEO logic.
- Updates dependencies and CI validation.
File summaries
| File | Description |
|---|---|
next/tests/fixtures/documentation-search-signals.mjs |
Shared SEO fixtures and document discovery |
next/tests/e2e/seo-signals.spec.mjs |
Browser-level SEO assertions |
next/scripts/generate-sitemaps.test.mjs |
Sitemap ownership coverage |
next/scripts/check-ingress-redirects.mjs |
Redirect validation |
next/scripts/check-historical-doc-signals.mjs |
Historical documentation signal tests |
next/scripts/check-documentation-ownership-signals.mjs |
Built-site ownership audit |
next/package.json |
Test script and dependency updates |
next/package-lock.json |
Locked dependency updates |
doc/src/theme/LayoutHead/versionedDocSignals.mjs |
Shared versioned-document signal logic |
doc/src/theme/LayoutHead/versionedDocSignals.d.mts |
Signal logic type declarations |
doc/src/theme/LayoutHead/index.tsx |
Uses shared SEO signal logic |
.github/workflows/lint.yml |
CI synchronization and validation |
Review details
Files not reviewed (1)
- next/package-lock.json: Generated file
- Files reviewed: 11/12 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
kayx23
approved these changes
Sep 14, 2026
bzp2010
approved these changes
Sep 14, 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
No reproducible production signal conflict was found, so this PR does not add speculative redirects or change the existing API7 acquisition strategy.
Validation
The full Astro build, post-build ownership audit, and desktop/mobile Playwright suite run in PR CI.