Yoast SEO Analysis

Support
#8

Hello Guys,

Thanks for the feedbacks. At this point, I cannot give you the right response as to why we haven’t integrated Yoast in X yet. I already have forwarded this thread to one of our developers so that they can explain more between Yoast and Cornerstone.

Please bear with us.

#9

Thank you @RueNel, appreciate the follow up. Looking forward to hearing more soon!

1 Like
#10

Hi There,

This is a known issue that we need to address somehow, but haven’t found the best way yet. The content for V2 elements is stored differently, so Yoast doesn’t see it and isn’t able to analyze it.

Rest assured that our Dev Team is aware of this bug and looking for the best way to resolve it.

Thank you for understanding,

#11

Hello, people.

If you want to use the Yoast you should use the “Classic Text” element of the Cornerstone.
If you will use “Text” element then SEO plugin does not work (words counter).

Give it try. I have succes. :slight_smile:

#12

Thanks for lettings us know. Have a nice day! :slight_smile:

#13

Hi there,

Just wanted to clarify a few things here.

  1. This is a known issue that we have a bug report open for. Specifically, we’ll be investigating what can be done to make that analysis work again.
  2. This does not have an impact on your site SEO. Everything outputs correctly on the front end. The problem is that Yoast can’t properly access content of our V2 elements.
  3. The suggestion about using a classic text element is the best workaround.
3 Likes
#14

This Question comes often maybe the Time for an KB Entry to Yoast SEO and X / Pro. So long this “Problem” extists.

Greets Uwe.

#15

I second that idea - this should not be a difficult thing to find. The KB article can simply be updated to show how the V2 elements work correctly with Yoast once it’s fixed up.

#16

Thank you for the input guys.

I have forwarded to the responsible person for consideration.

Thanks

#17

@RueNel @friech Thanks for the updates and I am thrilled to hear that the development team is looking into this.

#18

You’re welcome.

#19

Thank you team for looking into this, I appreciate your efforts and interim workaround suggestion.

#20

You are most welcome. :slight_smile:

#21

Evening chaps!

Any further news on this as yet? Although it’s only a tick-box exercise it’s very useful when you have a large site to optimise.

Cheers!

#22

Hi There,

Unfortunately no news regarding this issue yet.

Thank you.

#23

Just popping up to say I’m looking forward to seeing Yoast working with the V2 content elements :smiley:

#24

Duly Noted.
Best Regards.

#25

@RueNel - Can you please set this thread to not close until this issue has been fully resolved and you have posted here to confirm as much? Just want to be sure we get to a full resolution in this thread and it doesn’t get lost.

Thank you!

1 Like
#26

Hey @sAustinPower,

We’ve added this thread in our issue tracker so it won’t get lost.

Thanks.

#27

Threads will automatically close 10 days after the last reply. It’s not part of our process to keep feature request threads open because to be transparent not all requests are implemented. This request however is important to us, and while I can’t give an ETA to when it will be implemented, it’s something that I can confirm is part of our issue tracker and will be properly investigated.