-
-
Notifications
You must be signed in to change notification settings - Fork 289
fix(seo): restore query-matching titles + Related Terms on top glossary pages - #904
Open
nehagup wants to merge 1 commit into
Open
fix(seo): restore query-matching titles + Related Terms on top glossary pages #904nehagup wants to merge 1 commit into
nehagup wants to merge 1 commit into
Conversation
Contributor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟢 Approval recommended
Only a minor link-text spelling consistency issue was found, with no functional or structural problems in the restored metadata/sections.
Pull request overview
Restores SEO-optimized frontmatter titles/descriptions and reintroduces ## Related Terms internal-link blocks on high-impression glossary pages, aligning the aeo branch’s glossary metadata and cross-linking with main while leaving body/FAQ content intact.
Changes:
- Restored query-matching
titleanddescriptionfrontmatter on key glossary docs. - Re-added
## Related Termssections to strengthen internal linking between glossary concepts. - Applied the same "Related Terms" pattern to gRPC to restore cross-navigation consistency.
File summaries
| File | Description |
|---|---|
| versioned_docs/version-4.0.0/concepts/reference/glossary/mocks.md | Restores SEO frontmatter and adds Related Terms links for testing concepts. |
| versioned_docs/version-4.0.0/concepts/reference/glossary/load-testing.md | Updates title/description for search intent and adds Related Terms section. |
| versioned_docs/version-4.0.0/concepts/reference/glossary/integration-testing.md | Restores descriptive title/description and appends Related Terms cross-links. |
| versioned_docs/version-4.0.0/concepts/reference/glossary/idempotency.md | Restores query-matching title/description and adds Related Terms section. |
| versioned_docs/version-4.0.0/concepts/reference/glossary/grpc.md | Adds Related Terms block to restore internal glossary linking. |
| versioned_docs/version-4.0.0/concepts/reference/glossary/black-box-testing.md | Restores SEO frontmatter and adds Related Terms block (one link-text consistency nit noted). |
Review details
- Files reviewed: 6/6 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
...ossary pages The aeo branch downgraded the titles that match real search demand and removed the internal "Related Terms" blocks on the highest-impression glossary pages. Restore them from main (surgical — preserves the branch's body/FAQ edits): - idempotency (1M impressions/yr): "How Idempotent REST APIs Improve Reliability" -> "What is Idempotency in REST APIs? Complete Guide" - mocks: "How to perform Data Mocking using AI" -> "What are Mocks in Testing? Mocks vs Stubs vs Fakes" (recovers the mock-vs-stub cluster) - integration-testing: "Integration Testing With Keploy" -> "Integration Testing: Types, Tools & Best Practices" - black-box-testing (117K impressions): restore "What is Black Box Testing? Types, Techniques & Examples" - load-testing: restore descriptive title - grpc + all above: restore the deleted "## Related Terms" internal links Titles/descriptions and Related Terms taken verbatim from origin/main. No body content changed; no fabricated stats. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Neha Gupta <gneha21@yahoo.com>
nehagup
force-pushed
the
seo/aeo-glossary-corrections
branch
2 times, most recently
from
September 8, 2026 17:19
df7145f to
f3a7608
Compare
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.
Why
Stacked on
aeo. While preparing docs AEO work I found this branch is SEO-regressive on the highest-impression glossary pages — it downgraded the titles that match real search demand and deleted the internal## Related Termsblocks. This PR restores them (surgically, frommain), preserving the branch's body/FAQ edits.Evidence (GSC, 12 mo)
aeo→ restoredEvery one of these (+ grpc) also had its
## Related Termsinternal-link block deleted — restored on all six.What changed
title+description(verbatim frommain) on 5 pages.## Related Termsblock (internal links) on all 6.Note for the branch owner
The title/link downgrades look systematic across the glossary — worth checking the rest of the
aeobatch for the same pattern before merge, since narrower/branded titles and removed interlinks hurt both Google ranking and AI-answer citation.🤖 Generated with Claude Code