Super, thanks for posting. Alex will attend as soon as he’s online.
Plugin Contributor
alexgso
(@alexgso)
Hi yashjain27,
Sorry for the delay.
Can you please provide me with a screenshot of what you’re seeing in your Yoast info panel when using Page Builder? For reference, here’s a picture of the area I’m specifically after:
https://i.imgur.com/NzxvGBY.png
I’m asking because I need to see what Yoast is reporting to get a better idea of what is happening. Also, would it be possible for you to send me an export for the page that the screenshot is taken on? This will allow me to run tests against your layout. To export a page, please click the Layout button in the Page Builder toolbar. Then click import/export and then click download. Please upload the export to a 3rd party file hosting site such as teknik.io.
I found one example of many how SEO is not optimized with SiteOrigins. I used your page builder and widget called “SiteOrigin Image”. I attached an image to that widget, and Yoast was unable to pickup the image.
Hi @yashjain27. Sorry we missed the link you provided. Alex will reply ASAP in the morning.
We’ve done a patch for Page Builder and resolved, on our side, a big issue. You can see the chat here:
https://github.com/Yoast/YoastSEO.js/issues/1346#issuecomment-363706282
And the work here:
https://github.com/siteorigin/siteorigin-panels/commit/923c136fed1cbc8383687bfbd2c6d97f6ece7bca
Thanks for the further feedback. Alex will be with you ASAP.
Thanks! I am so excited!! This is my favorite builder as I have done 10 websites with this plugin! It would’ve been a disaster to redo those websites. I hope SiteOrigin can get 100% optimization
Plugin Contributor
alexgso
(@alexgso)
Hi yashjain27,
Sorry for the delay.
Can you please send me an export of your layout? This will allow me to run tests against your layout. To export a page, please click the Layout button in the Page Builder toolbar. Then click import/export and then click download. Please upload the export to a 3rd party file hosting site such as teknik.io.
Plugin Contributor
alexgso
(@alexgso)
Hi yashjain27,
Just reaching out to see if you received my last message. We really need to take a closer look at your layout to be able to work out if the above change will actually help, and if it doesn’t, how we can fix the issue you’re facing.
Thanks for the reply, sorry I never knew you replied before.
Here is my link of a page export: https://nofile.io/f/VMkXhetknmp/home.json
Plugin Contributor
alexgso
(@alexgso)
Hi yashjain27,
That’s absolutely fine mate – I completely understand, the same has happened for me a few of times. 🙁
Thanks. Okay so the vast majority of your widgets are theme specific so I think the above fix might help with that – I can’t be 100% sure as I’m not familiar with the inner workings of those widgets. The SiteOrigin Image widget isn’t currently set to output in the content section (which prevents it from being picked up), but that is something we could change – I’ve logged this as a feature request.
If it’s an absolute must that this image is included in the calculation, I would add the image via a SiteOrigin Editor widget. Please note that just because something doesn’t appear to Yoast, doesn’t mean Google can’t see it – it can, Yoast picks up on things in a completely different manner.
Plugin Contributor
alexgso
(@alexgso)
Hi yashjain27,
Correction – the SiteOrigin Image widget will be picked up after the fix is released.
You mentioned theme specific fix “mentioned above”. What are you referring too?
Plugin Contributor
alexgso
(@alexgso)
Hi yashjain27,
Sorry, my theme specific I meant the widgets for added by your theme rather than there being a theme specific fix. The update we’ll be pushing shortly should allow for those widgets to be picked up.
