Skip to content

Change sitemap text.#22421

Merged
leonidasmi merged 1 commit intofeature/llms-txt-phase-2from
670-change-wording-for-sitemap-links-in-llmstxt-file
Jul 14, 2025
Merged

Change sitemap text.#22421
leonidasmi merged 1 commit intofeature/llms-txt-phase-2from
670-change-wording-for-sitemap-links-in-llmstxt-file

Conversation

@thijsoo
Copy link
Copy Markdown
Contributor

@thijsoo thijsoo commented Jul 9, 2025

Context

  • We want to make the text more clear for the sitemap link.

Summary

This PR can be summarized in the following changelog entry:

  • Updates the sitemap link text in the llms.txt file.

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:

  • Re-generate the llms.txt file and make sure the sitemap text is the same as in the issue.
    • test both the case where XML sitemaps are enabled from Yoast settings and when they are disabled and we fall back to the WP native sitemaps

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:

UI changes

  • This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

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 #

@thijsoo thijsoo added this to the feature/llms-txt-phase-2 milestone Jul 9, 2025
@thijsoo thijsoo added the changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog label Jul 9, 2025
@coveralls
Copy link
Copy Markdown

Pull Request Test Coverage Report for Build 414b5c3dfdab9507fa0579aa452442f4b0240e74

Details

  • 3 of 3 (100.0%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall first build on 670-change-wording-for-sitemap-links-in-llmstxt-file at 48.112%

Totals Coverage Status
Change from base Build 2de329ec8556e60faca1007d85c5714fa42d0e25: 48.1%
Covered Lines: 16369
Relevant Lines: 34023

💛 - Coveralls

Copy link
Copy Markdown
Contributor

@leonidasmi leonidasmi left a comment

Choose a reason for hiding this comment

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

CR + Acceptance test is ✅

@leonidasmi leonidasmi merged commit f84a8ac into feature/llms-txt-phase-2 Jul 14, 2025
30 checks passed
@leonidasmi leonidasmi deleted the 670-change-wording-for-sitemap-links-in-llmstxt-file branch July 14, 2025 11:51
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