Yoast FAQ Schema Error – No p element in scope but a p end tag seen.

Hi @thepauluk,

This is a strange issue because we checked and the page source on the example page and this doesn’t match HTML that causes the errors in the validator. You can confirm this by looking at the HTML markup using view source or the browser developer tools (F12), for example.

Since most of the invalid tags are related to AMP, we believe that the validator is getting the AMP version. Since AMP’s tags are not included in HTML or XHTML, we don’t expect this validator to accurately evaluate this page. The page is marked as valid using Google’s AMP Test and the AMP Validator.

Just to confirm that there isn’t a problem with the FAQ block markup, we used the “Validate by direct input” feature, then we removed all the page tags except the minimum HTML required and the FAQ block (<div class="scheam-faq-wp-block-yoast-faq-block">). The validator did not show any HTML errors.

Hope this helps!

Hi,

Thanks for your response. It looks like the results that you got differed from mine.

I have record the results I see below with some greater context if you can watch for clarity of my issue please.

https://drive.google.com/file/d/1nZbqn5A_idIfCPbqGOZsKTB9jC5gwry2/view

Any advice would be appreciated.

Hi @thepauluk,

Thanks for the video to make it more clear what you’re seeing. Because of how HTML works, if you have an incorrect tag anywhere on the page, it can make all of the following tags invalid as well. These errors would need to be fixed in the theme, plugin, content that generated it.

Since we’ve already tested just the FAQ block HTML on the page and didn’t find any HTML errors, we’d like you to test this on your side by doing the following test:

Temporarily remove the FAQ block and then re-validate the page or a copy of the page. Are there are still the same errors? If so, this would mean that the problem is due to something else on the page.

Are you able to get the same results?

Hi Priscilla,

I have done the troubleshooting as suggested.

The error disappeared.

Here is a video of the testing – https://drive.google.com/file/d/1ED6Ee-RzHfLMXNMHfO4ZyPzM-LzrGCQ2/view

Any help would be appreciated.

Thanks,

Paul.

Hi @thepauluk,

Thank you for the extra video.

It looks like the FAQ sections have extra </p> where it shouldn’t have. We were looking at a non-cached version of the page, like here and see that on line 255, it ends with the closing paragraph tag. See screenshot here: https://snipboard.io/j2SUg4.jpg

We believe that there is something going on with the copying and pasting this into the classic editor experience. We would recommend to manually remove this out of this code and check if that helps :-).

Hi,

Thanks for checking that out. I have had a look at the code, but I can’t seem to find the </p>.

Please see the html here. https://snipboard.io/DeOXRr.jpg

Thanks,

Paul.

Hi @thepauluk,

Not sure what the differences are but we don’t see the same code as your last screenshot. In both the cached version and non-cached version on https://www.motorverso.com/does-motor-oil-expire/, we see the extra </p> tags, as seen here: https://snipboard.io/XCoxZD.jpg.

Since you are running/using the Classic Editor experience, do you happen to run the TinyMCE advanced plugin by any chance? We know that that plugin has a functionality that does something with paragraph tags. It might not be related here though, just thinking out loud.

If you don’t have that plugin, we would like you to do a conflict check to see when the extra tags come back after activating plugins/your theme. You can do this with the Health Check plugin troubleshooting mode. More details here: https://kb.yoast.com/kb/how-to-check-for-plugin-conflicts/

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.