Wincher integration doesn't work for a static page that is set to the frontpage with the Classic Editor or a page builder

[josevarghese]

Issue moved from Jira: https://yoast.atlassian.net/browse/IM-1670 Reporter: @michaelbriantina

• [x] I've read and understood the contribution guidelines.
• [x] I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened

In Yoast SEO 17.9, we introduced a Wincher integration to track your keyphrase performance. It works just fine for homepages using the default WP block editor. However, the Wincher integration doesn't seem to work on a static page that is set to the frontpage/homepage using the Classic Editor plugin or Divi theme/Divi page builder because the 'slug' field in the Yoast SEO meta box is blank.

There will be an error message of: Before you can track your SEO performance make sure to set either the post’s title and save it as a draft or manually set the post’s slug.

To Reproduce

Step-by-step reproduction instructions

1. Install and activate the Classic Editor plugin (or Divi Theme/Divi Page Builder and use its classic editor)
2. Install and activate Yoast SEO for WordPress
3. Set a static published page as your homepage under WP admin dashboard > Settings > Reading
4. Edit that page, add a title, add a focus keyphrase, and then try to use the Wincher integration

Expected results

That you could connect your Wincher account and use the Wincher integration'

Actual results

You get a message of:

Before you can track your SEO performance make sure to set either the post’s title and save it as a draft or manually set the post’s slug.

Even if you set a slug and update the page, it will then appear as blank upon reload.

Impact Users of the classic editor plugin and Divi/other page builders who want to use the Wincher integration on their static homepage

Error messages Before you can track your SEO performance make sure to set either the post’s title and save it as a draft or manually set the post’s slug.

Screenshots, screen recording, code snippet

If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.

Technical info

• If relevant, which editor is affected (or editors):
• [ ] Block Editor
• [ ] Gutenberg Editor
• [ ] Elementor Editor
• [x] Classic Editor : 1.6.3
• [ ] Other:

• Which browser is affected (or browsers):
• [ ] Chrome
• [ ] Firefox
• [ ] Safari
• [ ] Other:

Used versions

• Device you are using:
• Operating system:
• PHP version:
• WordPress version: 6.2
• WordPress Theme:
• Yoast SEO version: 20.7
• Gutenberg plugin version:
• Elementor plugin version:
• Classic Editor plugin version:
• Relevant plugins in case of a bug:

[josevarghese]

Please inform the customer of conversation # 939088 when this conversation has been closed.

[josevarghese]

Please inform the customer of conversation # 944994 when this conversation has been closed.

[josevarghese]

Please inform the customer of conversation # 945345 when this conversation has been closed.

[josevarghese]

Please inform the customer of conversation # 956111 when this conversation has been closed.

[josevarghese]

Please inform the customer of conversation # 988298 when this conversation has been closed.

[josevarghese]

Please inform the customer of conversation # 913758 when this conversation has been closed.

[josevarghese]

Please inform the customer of conversation # 910447 when this conversation has been closed.

[josevarghese]

Please inform the customer of conversation # 881598 when this conversation has been closed.

[josevarghese]

Please inform the customer of conversation # 857794 when this conversation has been closed.

[josevarghese]

Please inform the customer of conversation # 859106 when this conversation has been closed.

[monbauza]

Still reproducible in Yoast SEO 20.7.

[toyinogunseinde]

Please inform the customer of conversation # 1035785 when this conversation has been closed.

[VictoriaMcCarter]

Please inform the customer of conversation # 1109606 when this conversation has been closed.

[RitchelLauron]

Please inform the customer of conversation # 1114255 when this conversation has been closed.

[rmarcano]

Please inform the customer of conversation # 1132179 when this conversation has been closed.

[y-noel-baguio]

Please inform the customer of conversation # 1178472 when this conversation has been closed.

[VictoriaMcCarter]

Please inform the customer of conversation # 1181978 when this conversation has been closed.