Skip to content

Docs - fix slash #15749

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Docs - fix slash #15749

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs-v2/next.config.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ const withNextra = nextra({

export default withNextra({
basePath: "/docs",
trailingSlash: true,
trailingSlash: false,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Be aware of potential SEO and navigation impacts from changing trailingSlash to false.

Changing trailingSlash from true to false means URLs will no longer have a trailing slash (e.g., /about instead of /about/). This has several implications:

  1. Search engines consider URLs with and without trailing slashes as different URLs, which could impact SEO if both versions were previously indexed.
  2. Existing external links to your documentation might break if they used URLs with trailing slashes.
  3. The extensive redirect configuration in this file has many source patterns with trailing slashes - verify these will still match properly.

Consider adding appropriate redirects from the trailing slash versions to the non-trailing slash versions to maintain backward compatibility.

🏁 Script executed:

#!/bin/bash
# Check if redirect patterns in the file might be affected by the trailing slash change

# Count how many redirect sources end with trailing slashes
echo "Redirect sources ending with trailing slashes:"
grep -E "source: \".*\/\",$" docs-v2/next.config.mjs | wc -l

# Show examples of such patterns
echo -e "\nExamples of redirect sources with trailing slashes:"
grep -E "source: \".*\/\",$" docs-v2/next.config.mjs | head -5

Length of output: 502

Review trailingSlash change impact on SEO and redirects

Changing trailingSlash to false means URLs will no longer include the trailing slash. Our verification shows that the configuration currently contains 81 redirect sources ending with a trailing slash (e.g., /v3/, /what-is-pipedream/, /integrations/, etc.). This could lead to:

  • SEO issues since search engines index trailing and non-trailing slash URLs separately.
  • Broken external links if users or external sites reference the trailing slash version.
  • Mismatches with existing redirect rules that expect trailing slashes.

Action Items:

  • Review all 81 redirect sources in docs-v2/next.config.mjs to ensure they correctly handle non-trailing slash requests.
  • Consider adding or adjusting redirect rules to map old trailing slash URLs to the new non-trailing slash format for backward compatibility.
  • Verify that search engines and any external integrations are updated or receive proper redirects to prevent SEO penalties.

images: {
remotePatterns: [
{
Expand Down
Loading