Thijs van der Heijden

## Context * This prepares our elementor integration for if ever tinymce changes the way the handle the content. If that happens we don't want to start loading every image....

## Context * We added new options to change the robots txt output, but we did not add them to our tracking. ## Summary This PR can be summarized in...

## Context * We want to explain everything that happens on the indexables page ## Summary This PR can be summarized in the following changelog entry: * Updates copy on...

## Context * Adds a check to make sure we don't overwrite tracking preferences when a user chooses them. ## Summary This PR can be summarized in the following changelog...

Based on the found distinctions in #21106 We need to create an actual design for the Data object that can be filled by the system and passed trough to the...

Map out data in `wpseoScriptData` to be able to refactor

1

We want to figure out how to map the script data in /admin/metabox/class-metabox.php and other classes used there to fill the `wpseoScriptData` field. And create a design to make this...

Introduces indexables verification cron

1

## Context * We want to add a system that verifies that your indexables are all in an up to date state. This means that we need to re-index all...

Investigate how to verify indexable content after re-activating plugin and remedy obsolete/stale content

5

We have a couple of situations now where we clean up wrong indexables via the cleanup routine and when the plugin is activate. We have a background index to index...

Reference [Build list for unprepared table/field names, to be improved with WP 6.2's %i placeholder#20194](https://github.com/Yoast/wordpress-seo/issues/20194) for more context and the sheet with the placeholder to fix. ```[tasklist] ### Tasks -...

In the greater refactor of the script data we need to isolate the fields that are mostly just website settings, This might include + siteIconUrl + linkParams + PluginUrl +...