[No QA] Remove outdated redirect for Split Expenses

[garrettmknight]

Explanation of Change

Fixed Issues

$https://github.com/Expensify/Expensify/issues/491348
PROPOSAL: Removing the redirect so users can learn how to split expenses the biz way!

Tests

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[melvin-bot]

@brunovjk Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

NOTE: It looks like docs/redirects.csv was modified in this PR. Please see this SO for special instructions on how to review changes to that file.

[melvin-bot]

@ShridharGoel Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

NOTE: It looks like docs/redirects.csv was modified in this PR. Please see this SO for special instructions on how to review changes to that file.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR removes a single outdated redirect entry from docs/redirects.csv. The redirect was pointing users from Split-Expenses to Split-Personal-Expenses, but the target article (Split-Personal-Expenses.md) no longer exists, and a valid, well-structured article now lives at the source path (Split-Expenses.md). Removing this redirect is the correct action -- it eliminates a broken redirect chain that would have sent users to a non-existent page instead of the article that now properly serves the Split-Expenses URL.

Scores Summary

• Readability: 10/10 - Not applicable in the traditional sense (no prose was added or modified), but the change itself improves readability of the help site by ensuring users land on the correct, existing article rather than being redirected to a missing page.
• AI Readiness: 10/10 - By removing the redirect, search and retrieval systems will now correctly resolve the Split-Expenses URL to the existing article, which has proper YAML metadata including internalScope, task-based headings, and feature-specific keywords. This change directly improves AI discoverability.
• Style Compliance: 10/10 - The change is a single CSV line deletion. No style, naming, or formatting concerns apply. The existing Split-Expenses.md article that will now be served follows governance standards (verified: proper frontmatter, task-based headings, FAQ section, exact UI terminology).

Key Findings

• The redirect was actively harmful. The target Split-Personal-Expenses.md does not exist in the repository. This means the redirect was sending users to a 404 or broken page rather than letting them reach the valid Split-Expenses.md article.
• The existing Split-Expenses.md article is well-formed. It includes proper YAML frontmatter with title, description, keywords, and internalScope. It uses task-based ## headings (e.g., "How to split an expense by amount", "How to edit a split expense"), has an FAQ section, and follows the governance standards from HELP_AUTHORING_GUIDELINES.md and TEMPLATE.md.
• No risk identified. Since the source URL now has its own article and the redirect target no longer exists, removing this redirect is strictly beneficial. There is no scenario where keeping it would help users.

Recommendations

• Approve as-is. This is a clean, low-risk maintenance change that fixes a broken redirect.
• Consider auditing other redirects. It may be worth periodically checking redirects.csv for other entries where the target article no longer exists, to prevent similar issues.

Files Reviewed

• docs/redirects.csv -- One line removed. The deleted redirect (Split-Expenses to Split-Personal-Expenses) was outdated and pointed to a non-existent article. Removal is correct and improves the user experience.

This review was conducted against the governance files: docs/HELPSITE_NAMING_CONVENTIONS.md, docs/HELP_AUTHORING_GUIDELINES.md, and docs/TEMPLATE.md.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://d7d14183.helpdot.pages.dev ⚡️

[trjExpensify]

Looks good to me:

[OSBotify]

🚀 Deployed to staging by https://github.com/trjExpensify in version: 9.3.44-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to staging by https://github.com/trjExpensify in version: 9.3.47-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/grgia in version: 9.3.48-2 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅