Skip to content

Update label of AI+ card#22918

Merged
JorPV merged 1 commit intotrunkfrom
1024-change-copy-for-yoast-seo-ai-on-plans-page
Jan 29, 2026
Merged

Update label of AI+ card#22918
JorPV merged 1 commit intotrunkfrom
1024-change-copy-for-yoast-seo-ai-on-plans-page

Conversation

@thijsoo
Copy link
Copy Markdown
Contributor

@thijsoo thijsoo commented Jan 28, 2026

Context

  • We want to update the label to reflect the product name.

Summary

This PR can be summarized in the following changelog entry:

  • Renames the Yoast SEO AI+ card on the plans page for better clarity.

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:

  • Go to the plans page and make sure the card is now labeled Yoast SEO AI+

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.

QA can test this PR by following these steps:

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.
  • This PR also affects Yoast SEO for Google Docs. I have added a changelog entry starting with [yoast-doc-extension], added test instructions for Yoast SEO for Google Docs and attached the Google Docs Add-on 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.
  • I have run grunt build:images and commited the results, if my PR introduces new images or SVGs.

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 #

@thijsoo thijsoo added the changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog label Jan 28, 2026
@coveralls
Copy link
Copy Markdown

Pull Request Test Coverage Report for Build f041b7d238e051b8841454bd78b56f269f8a28f3

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 56.339%

Totals Coverage Status
Change from base Build df0e03d12f5fb37b50456b5a96c3aea71d37d593: 0.0%
Covered Lines: 15005
Relevant Lines: 25959

💛 - Coveralls

@JorPV JorPV added this to the 27.0 milestone Jan 29, 2026
@JorPV
Copy link
Copy Markdown
Contributor

JorPV commented Jan 29, 2026

It does what it says 👍🏼

@JorPV JorPV merged commit 57060b6 into trunk Jan 29, 2026
21 checks passed
@JorPV JorPV deleted the 1024-change-copy-for-yoast-seo-ai-on-plans-page branch January 29, 2026 15:45
@FAMarfuaty FAMarfuaty added changelog: other Needs to be included in the 'Other' category in the changelog changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog and removed changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog changelog: other Needs to be included in the 'Other' category in the changelog labels Feb 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog: other Needs to be included in the 'Other' category in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants