Skip to content

Add redirection tools page#22606

Merged
thijsoo merged 6 commits intotrunkfrom
add/redirection-tools-page
Sep 30, 2025
Merged

Add redirection tools page#22606
thijsoo merged 6 commits intotrunkfrom
add/redirection-tools-page

Conversation

@leonidasmi
Copy link
Copy Markdown
Contributor

@leonidasmi leonidasmi commented Sep 29, 2025

Context

  • We want to increase the visibility of our Redirects page, so we're adding a Redirects page under the main Tools menu item, that will redirect to Yoast's dedicated redirects page.
  • We also want to track the users that clicked on the upsells in the Redirects page that came from this new flow.

Summary

This PR can be summarized in the following changelog entry:

  • Adds a Redirects page under WP's Tools page, that redirects to the Yoast Redirects page.

Relevant technical choices:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

  • As an admin/editor/seo manager, visit the admin, without Premium enabled, and confirm that you get a Tools->Redirects page
  • Navigate there and confirm that you are redirected to Yoast->Redirects page
  • There, confirm that the upsell's link point to https://yoa.st/redirect-manager-upsell-tools
  • Go to Yoast->Redirects page via the normal Yoast menu and confirm that the page looks exactly the same although the upsell link is the old https://yoa.st/redirect-manager-upsell one.
  • Confirm that with an Author, the new redirects submenu item is not visible.
  • Confirm that with Premium enabled, the new redirects submenu item is still visible and redirects to the same page. Smoke test the redirection feature there.

Relevant test scenarios

  • Changes should be tested with the browser console open
  • Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
  • Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
  • Changes should be tested on different browsers
  • Changes should be tested on multisite

Test instructions for QA when the code is in the RC

  • QA should use the same steps as above.

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

Other environments

  • This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

  • I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

  • I have tested this code to the best of my abilities.
  • During testing, I had activated all plugins that Yoast SEO provides integrations for.
  • I have added unit tests to verify the code works as intended.
  • If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
  • I have written this PR in accordance with my team's definition of done.
  • I have checked that the base branch is correctly set.

Innovation

  • No innovation project is applicable for this PR.
  • This PR falls under an innovation project. I have attached the innovation label.
  • I have added my hours to the WBSO document.

Fixes #

@leonidasmi leonidasmi added the changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog label Sep 29, 2025
@coveralls
Copy link
Copy Markdown

coveralls commented Sep 29, 2025

Pull Request Test Coverage Report for Build b39c043fd672e92f98a084f8f7c6dfe6cc5d57fd

Details

  • 6 of 31 (19.35%) changed or added relevant lines in 4 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.02%) to 53.218%

Changes Missing Coverage Covered Lines Changed/Added Lines %
packages/js/src/redirects/components/route-layout.js 0 3 0.0%
src/integrations/admin/redirects-page-integration.php 0 4 0.0%
src/integrations/admin/redirections-tools-page.php 0 18 0.0%
Totals Coverage Status
Change from base Build 8f5eaca296fd39aa9dca066d8260d96f1caeed93: -0.02%
Covered Lines: 31770
Relevant Lines: 59935

💛 - Coveralls

@leonidasmi leonidasmi marked this pull request as ready for review September 30, 2025 07:44
@thijsoo thijsoo self-assigned this Sep 30, 2025
@thijsoo thijsoo added this to the 26.2 milestone Sep 30, 2025
Copy link
Copy Markdown
Contributor

@thijsoo thijsoo left a comment

Choose a reason for hiding this comment

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

CR + ACC 👍

@thijsoo thijsoo merged commit 52ee80b into trunk Sep 30, 2025
39 checks passed
@thijsoo thijsoo deleted the add/redirection-tools-page branch September 30, 2025 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants