Yoast Local SEO Part Three

Support
#1

Today while editing a Location page for Yoast Local SEO, I discovered that a global component displayed on the location page was working, but it had stopped working on all the other pages where it was used. I recorded a video to show you how the problem was manifesting. AFTER I recorded the video, I tried disabling plugins and discovered that Yoast SEO: Local was causing the component not to work on the non-location pages. After turning the Yoast SEO: Local back on, the content in my location page has gone missing.

I’d like to be able to use components with Yoast SEO: Local, but more importantly, I’d like to get my the content for my location page back. Can you help me?

#2

Hello Jon,

Thanks for writing in! Regretfully we cannot view your video because it is private. Please change it to public or viewable to anyone who has the link to it.

Best Regards.

#3

Sorry about that. I went back and none of the options were selected. Now it is unlisted, but you should have access.

#4

Hello Jon,

I have just watched the video. Yes, this is known conflict with most some of the builder elements and the SEO plugins which is why we have introduced the HTML Content Storage. Kindly checkly check out this documentation first to know more about it.

Best Regards.

#5

He Ruenel,

I backed up the site, switched to HTML Content Storage, and then checked for regressions. The switch to HTML seems to have worked, but it did NOT resolve the issue I am having where a component I am using loses it’s CSS if the Yoast SEO: Local plugin is activated.

Thanks for your help with this.

Jon

#6

Thank you for the update. We may need to log in to the site to properly check the issue. Please provide the login details in the secure note.

secure-note
secure-note1040×250 15.3 KB

Since the plugin is not natively supported by the theme, we also recommend reaching out to the plugin developers for additional assistance.

– https://theme.co/docs/version-compatibility#third-party-extensions

Best regards.

#7

I would think it would be best if Themeco could claim compatibility with Yoast Local, but maybe I am an outlier.

In any case, I would appreciate it if you could have a look.

#8

I noticed that we do have components on the same page that are working correctly. There must be something unique about the one that is not working.

#9

Thank you for the info. When the plugin is activated, the internal styles of the component are removed. Unfortunately, we are not yet sure why this happens. As a workaround, we exported the “Schedule an Inspection” component to the Element Library. So instead of using the Components element, you can directly add the “Schedule an Inspection” element to the builder. We cloned the maintenance page and added the exported component at the very end of the page (see secure note).

1
11970×968 188 KB

– https://theme.co/docs/component-builder-overview#component-shortcode

#10

Understood. It is interesting that there are other components that don’t seem to be affected by the problem, on the same page even.

#11

Hi Jon,

We will also investigation on this. We will try to replicate it on our local testing server.

Thanks.

#12

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.