[Plugin: WordPress SEO by Yoast] Invalid Markup Validation

  • robscott

    (@robscott)


    11 years, 7 months ago

    WordPress version: 3.4.1
    WordPress SEO version: 1.2.7

    I did this: Installed and ran the plugin.

    I expected the plugin to do this: SEO etc.

    Instead it did this: It did everything we wanted (excellent tool) however is throwing up a few HTML validation issues.

    Twitter card meta info isn’t self-closed (i.e. no “/>” at end of meta tags). Simple to fix – just a bug notice.

    Facebook’s Meta Tags are also “not valid” XHTML. This can be fixed by commenting out the Facebook meta data (as suggested here http://stackoverflow.com/questions/2761622/new-facebook-like-button-html-validation ).

    Very small issues on an otherwsie excellent plugin – just thought I’d post ’em up as I picked them when about to write a post on HTML validation for our web visitors, only to find we’re not “valid” anymore…

    The above workarounds work for us, and should probably be taken into consideration for future versions of the plugin.

    Top marks for an excellent plugin though – very impressed, and have indeed taken a lot of hand coding out from our (and our client) websites which your plugin addresses perfectly.

    http://wordpress.org/extend/plugins/wordpress-seo/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter robscott

    (@robscott)

    11 years, 7 months ago

    Actually had a bit of battle with quite a bit of Facebook & Twitter code not being valid it turned out. But fixed after 30-40 minute’s tinkering. Was it worth the hassle? Maybe not, but if we’re going to talk to clients about validation, would make sense to be doing so from a website which is, itself, valid!

    Thanks again for an excellent plugin.

    Ovidiu

    (@ovidiu)

    10 years, 9 months ago

    Is this still the case? Is the output validated now in more recent versions?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: WordPress SEO by Yoast] Invalid Markup Validation’ is closed to new replies.