Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inform the user about debugging constants #21845

Open
Djennez opened this issue Nov 20, 2024 · 0 comments
Open

Inform the user about debugging constants #21845

Djennez opened this issue Nov 20, 2024 · 0 comments

Comments

@Djennez
Copy link
Member

Djennez commented Nov 20, 2024

Is your feature request related to a problem? Please describe.

With the release of WordPress 6.7, we saw a lot of sites outputting notifications due to a change in WordPress. This would only happen if a site had had WP_DEBUG and WP_DEBUG_DISPLAY set to true though.

Describe the solution you'd like

Introduce a notification (maybe with the new dashboard in WordPress) that would inform the user about the use of these DEBUG constants. Though this might sound like a technical issue that we should not care about, we should brand this as a "Warning, SEO issue detected" notification. Because outputting these notification on the front-end of your website will get picked up by search engines and therefore likely influence your SEO reputation (this is an assumption though).

Why do you think this feature is something we should consider for the Yoast SEO plugins?

A website in production should simply not have any debugging online, as it's both performance reducing (SEO again) as well as possibly cause unwanted debug to show up on the frontend (SEO and security related).

Additional context

Some examples of the DEBUG output influencing search results:

image
Google search results showing the notification was picked up

image
A notification showing up on the frontend of a website

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

No branches or pull requests

2 participants