Skip to content

943 seo data optimization error reporting refactoring#23402

Draft
pls78 wants to merge 11 commits into
trunkfrom
943-seo-data-optimization-error-reporting-refactoring
Draft

943 seo data optimization error reporting refactoring#23402
pls78 wants to merge 11 commits into
trunkfrom
943-seo-data-optimization-error-reporting-refactoring

Conversation

@pls78

@pls78 pls78 commented Jun 24, 2026

Copy link
Copy Markdown
Member

Context

Summary

This PR can be summarized in the following changelog entry:

  • WIP.

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:

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 committed the results, if my PR introduces or edits 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 #

@pls78 pls78 added the changelog: enhancement Needs to be included in the 'Enhancements' category in the changelog label Jun 24, 2026
@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 80

Coverage increased (+0.1%) to 53.887%

Details

  • Coverage increased (+0.1%) from the base build.
  • Patch coverage: 9 uncovered changes across 3 files (133 of 142 lines covered, 93.66%).
  • No coverage regressions found.

Uncovered Changes

File Changed Covered %
packages/js/src/components/AbstractIndexation.js 55 48 87.27%
packages/js/src/first-time-configuration/tailwind-components/steps/indexation/indexation.js 1 0 0.0%
src/commands/index-command.php 15 14 93.33%
Total (8 files) 142 133 93.66%

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 70114
Covered Lines: 37478
Line Coverage: 53.45%
Relevant Branches: 18101
Covered Branches: 10058
Branch Coverage: 55.57%
Branches in Coverage %: Yes
Coverage Strength: 42921.86 hits per line

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog: enhancement Needs to be included in the 'Enhancements' category in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants