Fix tech SEO issues: sitemap cleanup and broken link fixes (DOC-2396)#1035
Conversation
- Remove 56 dead/redirect URLs from sitemap.xml (30x301, 26x404) - Fix 12 broken internal links across 11 docs files - Update terminal install links in copilot FAQs to testsigma-terminal/ paths - Replace dead genai-capabilities/ links with current atto/ equivalents - Fix relative .md links in test-data files to absolute paths - Update features-and-scenarios URL to correct create-test-cases/ path Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 26 minutes and 37 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughMultiple documentation pages are updated to replace relative markdown hyperlinks with absolute ChangesDocumentation Link Fixes, Sitemap Refresh, and .gitignore
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
src/pages/docs/copilot/faqs-on-copilot.md (1)
220-222: 💤 Low valueFix markdown blockquote formatting (extra spaces).
Lines 220–222 have multiple spaces after the blockquote marker
>. Remove the extra spaces to match markdown best practices.🎯 Proposed fix for blockquote spacing
-> - [Documentation on installing Terminal for macOS](https://testsigma.com/docs/testsigma-terminal/installing-testsigma-terminal/). -> - [Documentation on installing Terminal for Windows](https://testsigma.com/docs/testsigma-terminal/installing-testsigma-terminal-on-windows/). -> - [Documentation on installing Terminal for Linux](https://testsigma.com/docs/testsigma-terminal/installing-testsigma-terminal-on-linux/). +> - [Documentation on installing Terminal for macOS](https://testsigma.com/docs/testsigma-terminal/installing-testsigma-terminal/). +> - [Documentation on installing Terminal for Windows](https://testsigma.com/docs/testsigma-terminal/installing-testsigma-terminal-on-windows/). +> - [Documentation on installing Terminal for Linux](https://testsigma.com/docs/testsigma-terminal/installing-testsigma-terminal-on-linux/).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/docs/copilot/faqs-on-copilot.md` around lines 220 - 222, The blockquote formatting on lines 220–222 in the faqs-on-copilot.md file has multiple spaces after the blockquote marker `>`. Remove the extra spaces between the `>` character and the list items (the documentation links for Terminal installation on macOS, Windows, and Linux) so that there is only a single space after the `>` marker, following markdown best practices.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/pages/docs/test-data/create-data-profiles.md`:
- Line 51: The link "[Create a Test Data
Profile](/docs/test-data/create-data-profiles/)" at line 76 is self-referential,
pointing to the same page it appears on. Given the context "For more
information, see...", this should be corrected by either replacing it with a
link to a related external page that provides additional guidance (such as a
page explaining how to fill in profile fields), converting it to an anchor link
that points to a specific section within this same page using the format
[text](`#section-anchor`), or removing the link entirely if no additional external
reference is needed. Evaluate the surrounding content and user intent to
determine the most appropriate fix.
---
Nitpick comments:
In `@src/pages/docs/copilot/faqs-on-copilot.md`:
- Around line 220-222: The blockquote formatting on lines 220–222 in the
faqs-on-copilot.md file has multiple spaces after the blockquote marker `>`.
Remove the extra spaces between the `>` character and the list items (the
documentation links for Terminal installation on macOS, Windows, and Linux) so
that there is only a single space after the `>` marker, following markdown best
practices.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 5dd336e9-da3b-4307-8e5c-e89ce6f61478
📒 Files selected for processing (14)
.gitignoresrc/pages/docs/atto/generative-ai/overview.mdsrc/pages/docs/auto-healing/intro.mdsrc/pages/docs/copilot/faqs-on-copilot.mdsrc/pages/docs/copilot/introduction.mdsrc/pages/docs/sitemap.xmlsrc/pages/docs/test-cases/create-test-cases/test-cases-for-mobile-applications.mdsrc/pages/docs/test-cases/create-test-cases/test-cases-for-web-applications.mdsrc/pages/docs/test-cases/create-test-steps/overview.mdsrc/pages/docs/test-data/add-values-to-test-data-profile.mdsrc/pages/docs/test-data/create-data-profiles.mdsrc/pages/docs/test-data/folder-structure-for-test-data-profiles.mdsrc/pages/docs/test-data/import-data-profiles.mdsrc/pages/docs/test-data/update-test-data-profile.md
💤 Files with no reviewable changes (1)
- src/pages/docs/sitemap.xml
| > Before you begin, ensure that you have: | ||
| > 1. An active Testsigma project with the required permissions to manage test data. | ||
| > 2. A Feature and Scenario set up in Test Data Profiles. For more information, see [Folder Structure for Test Data Profiles](folder-structure-for-test-data-profiles.md). | ||
| > 2. A Feature and Scenario set up in Test Data Profiles. For more information, see [Folder Structure for Test Data Profiles](/docs/test-data/folder-structure-for-test-data-profiles/). |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify all test-data links point to canonical routes in left-nav-title.json
# Check left-nav-title.json for test-data routes
echo "=== Canonical test-data routes in left-nav-title.json ==="
rg -A 1 'create-data-profiles|folder-structure|add-values|import-data|update-test' src/left-nav-title.json | head -40
# Also verify the file structure exists
echo ""
echo "=== Checking if markdown files exist ==="
fd -t f 'create-data-profiles|folder-structure|add-values|import-data|update-test' src/pages/docs/test-data/Repository: testsigmahq/testsigma-docs
Length of output: 797
🏁 Script executed:
cat -n src/pages/docs/test-data/create-data-profiles.md | sed -n '45,80p'Repository: testsigmahq/testsigma-docs
Length of output: 2624
Self-referential link at line 76 should be corrected.
Line 76 contains a link to /docs/test-data/create-data-profiles/ from within the same file. This creates a self-referential link in the "Create a Test Data Profile" section with link text "Create a Test Data Profile". Given the context ("For more information, see...") this is likely unintentional. Consider:
- Whether this should link to a related page instead (e.g., a guide on filling in profile fields)
- Using an anchor link to guide users to a specific section within this page
- Removing the link if no additional context is needed
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/pages/docs/test-data/create-data-profiles.md` at line 51, The link
"[Create a Test Data Profile](/docs/test-data/create-data-profiles/)" at line 76
is self-referential, pointing to the same page it appears on. Given the context
"For more information, see...", this should be corrected by either replacing it
with a link to a related external page that provides additional guidance (such
as a page explaining how to fill in profile fields), converting it to an anchor
link that points to a specific section within this same page using the format
[text](`#section-anchor`), or removing the link entirely if no additional external
reference is needed. Evaluate the surrounding content and user intent to
determine the most appropriate fix.
…2396) For each removed 301 redirect entry, ensure the canonical destination URL is present in the sitemap. Adds 7 missing URLs: live-editor/introduction, 5 testsigma-terminal install pages, and integrations/test-labs/testmu. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… it) The live-editor/ directory doesn't exist in this repo — adding this URL would have introduced another potential redirect chain. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2 participants
Summary by CodeRabbit
Documentation
Chores