Jetpack and WordPress SEO

JetpackThe Jetpack plugin for WordPress has quite a few nice bits and pieces. There’s one issue: the developers at Automattic seem to think they’re alone in the world. In their last release, they enabled OpenGraph tags by default with no setting to disable it. Even when you already have WordPress SEO enabled and OpenGraph enabled in that. This is making people freak  out everywhere as double OpenGraph tags lead to problems with Google+ and with Facebook.

Disable OpenGraph in Jetpack

The best solution, honestly, is to install another plugin by Mark Jaquith, called Manual Control for Jetpack. This disables Jetpack automatic activation of new modules. Now you at least have to manually do something for stuff to break on your site when the Jetpack team decides to push new stuff.

This particular OpenGraph feature is in the Publicize module, so you’d think you could disable that, but that doesn’t seem to work. Instead, adding this line in your functions.php should fix this particular problem:

add_filter( 'jetpack_enable_opengraph', '__return_false', 99 );

I understand that disabling OpenGraph in WordPress SEO could work too. I would recommend against that though, especially if you use our Video SEO plugin as that relies on our ability to control OpenGraph tags.

Calling for Automattic to be more responsible

I also want to call on Automattic‘s Jetpack team. You guys should know better than to do stuff like this. You’ve literally cost me about half a days worth of support work now with this single release. It’d be cool if you, just like the rest of Automattic, would work with the community instead of against it.

I know you’re capable of it, because this line in the plugin:

if ( in_array( 'facebook/facebook.php', $active_plugins ) )
add_filter( 'jetpack_enable_opengraph', '__return_false', 99 );

This shows me that you did think about what would happen if Facebook’s plugin was active. That’s logical because people at Automattic worked on that plugin too. Now next time, please look at some of the repositories most popular plugins too and adjust accordingly. At the very least start a conversation with plugin authors about what’s coming up when you create stuff that clashes.

Update: might be good to note, when Facebook’s plugin is active and OpenGraph is enabled in my SEO plugin, my plugin filters the output of the Facebook plugin to prevent two sets of OpenGraph tags. Niall Kennedy of Facebook has actually also submitted a patch to my SEO plugin to improve how it does OpenGraph. That’s how this community should work.

Tags: , ,


Yoast.com runs on the Genesis Framework

Genesis theme frameworkThe Genesis Framework empowers you to quickly and easily build incredible websites with WordPress. Whether you're a novice or advanced developer, Genesis provides you with the secure and search-engine-optimized foundation that takes WordPress to places you never thought it could go.

Read our Genesis review or get Genesis now!

85 Responses

  1. ZimbrulBy Zimbrul on 29 November, 2012

    Now let’s see what they do. I don’t normally use Jetpack and someone please tell me why should I?

  2. James McBrideBy James McBride on 29 November, 2012

    Not sure if this is relevant but I discovered that you can disable “Publicise” by clicking the “Learn More” button on the Publicise tile (inside the main JetPack configuration area) – once you do, the “Configure” button will turn into a “Deactivate” button and if you click that it will fully deactivate Publicise.

    I discovered this totally by accident whilst trying to shut off some of the other auto-loaded features in the latest update.

    • DrewAPictureBy DrewAPicture on 29 November, 2012

      This is true of all the Jetpack modules. The issue is that when you activate the plugin, it auto-activates all the modules, thus Mark Jaquith’s ‘Manual Control for Jetpack’ plugin.

    • AdrianBy Adrian on 4 December, 2012

      Seems to me that Jetpack did include the option to disable just didn’t make it too clear. Clicking the learn more button does provide the option to disable the publicize facility so no need to worry about adding code anywhere.

    • Imran HunzaiBy Imran Hunzai on 18 December, 2012

      That was helpful.

  3. Fashion blogBy Fashion blog on 29 November, 2012

    I’ve been able to disable the double tags successfully. I had to disable BOTH the publicize and the sharing Jetpack modules. After clearing the cache the duplicated og: tags disappeared.

    This is just a workaround. It would be good to be able to choose whether Jetpack should add or not the OpenGraph tags. Rgs

  4. David ArtissBy David Artiss on 29 November, 2012

    Joost,

    I’ve had similar problems with my Artiss YouTube Embed plugin. It uses the pretty standard [youtube] shortcode to display videos. However, Jetpack overrides this for its own uses. It has a shortcodes module, activated by default, which amongst other things includes the YouTube shortcode. Except you can’t disable individual shortcodes in Jetpack. Worst still, if you supply an invalid ID to their shortcode it doesn’t display a visible error, but preferring to add the error as an HTML comment. As a result users of my plugin that also have Jetpack wonder why videos aren’t displaying and blame it on my plugin. I’ve too lost an awful lot of time investigating numerous individual issues around this.

    In my next release of the plugin I’ll be looking to flag to users if they have this Jetpack module active – more time I have to spend to work around this plugin!

    David.

    • Joost de ValkBy Joost de Valk on 29 November, 2012

      Sigh, typical. I know that it overrides the shortcode yeah, noticed that when I was testing my Video SEO plugin.

      • David ArtissBy David Artiss on 29 November, 2012

        It’s a shame that WordPress doesn’t provide a method of identifying if a shortcode is in use and the name of the function that it calls. In which case I could easily make my plugin identify *any* plugin that’s already using the shortcode and inform the user.

        David.

        • Joost de ValkBy Joost de Valk on 29 November, 2012

          Don’t get me started about shortcodes. The number of shortcodes and regexes for them I’m now supporting in my Video SEO plugin is close to crazy.

          • David ArtissBy David Artiss on 29 November, 2012

            I take it all back, it is possible…

            global $shortcode_tags;
            $shortcode_use = $shortcode_tags[ 'youtube' ] ;

            (I looked at WordPress Core to see how they were handling shortcodes).

            In this case, $shortcode would contain any function that is using the [youtube] shortcode. Armed with this I can report on any plugins already using the shortcode I intend to use!

            David.

          • David ArtissBy David Artiss on 29 November, 2012

            Sorry, I mean shortcode_use will contain the function name.

      • David ArtissBy David Artiss on 29 November, 2012

        BTW, thanks for the tips above. I am using Jetpack myself so will implement the function.php fix (and install the manual control plugin for Jetpack too!).

        David.

  5. Avinash D'SouzaBy Avinash D'Souza on 29 November, 2012

    Hey Joost,

    Correct me if I’m wrong but can’t you quite simply disable the module in Jetpack?

    Should solve all problems, right?

    • Joost de ValkBy Joost de Valk on 29 November, 2012

      It should, but it doesn’t, apparently they enabled OpenGraph outside of that…

      • David ArtissBy David Artiss on 29 November, 2012

        Even if you could, you may wish to run the Publicize module but without this specific function. It’s a shame that Jetpack doesn’t allow anymore fine turning that turning off whole modules at a time.

        David.

      • Evan SolomonBy Evan Solomon on 29 November, 2012

        The open graph tags are included if the Publicize module or the sharing module are active. If you disable them both, the tags go away. If either module is active, the tags are on by default.

        I can understand not liking the feature and wishing it had its own setting, but settings have a cost to weigh. Decisions, not options, as the saying goes.

        As you point out, it’s controllable with a filter. Jetpack has over 100 unique filters in it, adding a setting UI for each one would would have a significant cost. Just for fun…

        $ ack "apply_filters\( '([^']+)" wp-content/plugins/jetpack --output="\$1" -h | sort | uniq | wc -l
        105

        • Joost de ValkBy Joost de Valk on 29 November, 2012

          Evan, it’s the combination of things that you guys did that makes it wrong. You enabled a new feature without telling users, that collides with plugins they were already using and that you could have known about. It’s not like my SEO plugin has a few users. I’m not saying you’d have to add an option, I’m asking you to be more responsible in what you do and reach out to other devs when you release stuff like this.

          • Evan SolomonBy Evan Solomon on 29 November, 2012

            I’m asking you to … reach out to other devs when you release stuff like this

            And I agree, as does the rest of the team that considered the Facebook plugin case, as you mention in your post. Clearly we made a mistake by not accounting for your plugin as well. That was a mistake for sure, but not reaching out to devs to try to avoid conflicting code doesn’t feel like a fair assessment to me.

            I’m not saying you’d have to add an option

            No, but the sibling comment to mine did and I figured I’d try to address the general idea in a single comment. The settings bit wasn’t meant purely for you.

          • Joost de ValkBy Joost de Valk on 29 November, 2012

            Well Evan, I’ve commented on Twitter several times about Jetpack and not heard anything back… I’m glad I know you’re working on it now, so I’ll drop you an email next time, just would have rather had it the other way around.

          • Evan SolomonBy Evan Solomon on 29 November, 2012

            Parallel comment since I’ve defeated your max nesting…

            Sorry if we missed something on Twitter. We do follow it (it’s where I saw this post) but it’s hard to cover 100%. If we didn’t respond to something, it’s not because we don’t care. It’s 5am here (San Francisco) and I’m still awake writing comments about filter names because I think it will be helpful — it’s a lot easier to respond to a tweet :)

            We have a beta feedback group that I’m sure you’d be welcome in if you’re interested. That’s aside from the fact that of course anyone is free to download trunk or whatever branch they like, but it’s a way for us to prioritize and focus feedback.

          • Joost de ValkBy Joost de Valk on 29 November, 2012

            It’s still the wrong way round though :) You could have, and should have, known about my plugin doing OpenGraph. I shouldn’t need to come to you, you should be coming to me.

            I’m hardly the first to write about this conflict with my plugin, check this query, yet there has been no response to me from Automattic yet.

        • Evan SolomonBy Evan Solomon on 29 November, 2012

          Well, okay. I think I was pretty direct here:

          Clearly we made a mistake by not accounting for your plugin as well.

          I can’t change what happened, so all I can do is try to make the best of the situation as it is. So far the ideas I’ve come up with to do that are:

          * Help explain how to work around the problem the best I can
          * Answer any Jetpack question (really any question at all) that I can
          * Try to get you involved in the feedback group we use for Jetpack testing
          * Explain a little bit of context for Jetpack’s settings
          * Clearly and publicly say that we made a mistake

          None of that changes history or the half day you lost to support, but it’s best best I can think of. Mistakes happen — in the best of times, we find a way to fix them and avoid making them again. What can I do to help make that happen?

          there has been no response to me from Automattic yet

          I work at Automattic and I’m responding, so that’s probably less true now than it was when you wrote this post. Hopefully next time — surely this won’t be the last mistake we ever make — we can respond even faster.

          • Joost de ValkBy Joost de Valk on 29 November, 2012

            It’s certainly less true now and I’m happy to see you responding. I’m going to push this little bit of code into my own plugin and just disable OpenGraph in Jetpack when it’s active in my plugin, or maybe even filter its output… Will need to give that a think. So, thanks for your responses.

        • Stéphane BergeronBy Stéphane Bergeron on 29 November, 2012

          The basic problem that you need to address here is that JetPack enables new modules on install. That is wrong on so many levels. JetPack has wasted me coutless hours disabling stuff I don’t need, espcially on a 82 sites multisite network I manage. It’s a tightly controlled evironment and, every damn time you release a new version with new modules I don’t need because I have a better alternative already installed (the majority of the time) I have to go through all sites and disable the new modules.

          I don’t know how I didn’t know about Mark Jaquith’s Control plugin but I’ll certainly install that.

          New modules should be opt-in, not opt out. Stop for a second and think of the ramifications of your actions for site owners and managers before you reply telling me enabling new module by default is a good thing for whatever reasons I already heard before. It needs to stop, period. Next time I should bill you for my time. Maybe that would make you think this through…

          • Kirk TaylorBy Kirk Taylor on 30 November, 2012

            Jetpack updated at the same time Pretty Links updated, the plugin I have been using to do my affiliate links. It took out my number one site, which does 90% of the revenue in a four hour period on Friday nights. Essentially I made zero from the site because I thought the problem was with Pretty Links. It took me twenty-four hours to figure out that two modules in Jetpack were the culprits, and I now I see this.

            JetPack was the last place I looked in my entire site because it was what I thought would be the least likely to cause problems. I realize that it was a mistake, but now I know better.

          • PietBy Piet on 30 November, 2012

            What I don’t understand is that if you have so many problems with Jetpack, why you would voluntarily install it onto your 82 sites multisite network in the first place?

            As an example for quite some time I have been using the stats plugin that has been integrated into Jetpack. At first I installed Jetpack, but as soon as I realised that all packed modules were on by default, I deleted the monster immediately and went back to the stats plugin. I accept the fact that it no longer receives updates (as a standalone plugin), but as long as it works that is a price I am willing to pay.

  6. palPalaniBy palPalani on 29 November, 2012

    I am using the below filter and it works well.
    add_filter(‘jetpack_enable_open_graph’, ‘rn_fb_og’, 10, 3);
    function rn_fb_og(){
    return false;
    }

    what is the difference between the “jetpack_enable_open_graph” and “jetpack_enable_opengraph” filters?

    • Evan SolomonBy Evan Solomon on 29 November, 2012

      The opengraph filter controls whether the Open Graph functionality loads. The open_graph filter controls whether the function runs once it does load (it’s hooked to wp_head). Most likely, returning false for either will have the same effect, but in theory using the later one (with the underscore) would give other plugins the opportunity to override your plugin later in the process.

      The naming is confusing for sure.

    • Joost de ValkBy Joost de Valk on 29 November, 2012

      It’s weird that that works. jetpack_enable_open_graph doesn’t exist in the code of Jetpack…

      Also, the return false function you use can just be replaced by __return_false :)

      • Evan SolomonBy Evan Solomon on 29 November, 2012

        Take a look here

        Apologies if this gets posted twice. I just tried and it didn’t seem to work.

        • Joost de ValkBy Joost de Valk on 29 November, 2012

          Ah that’s funny, inconsistency in the code? :)

          • Evan SolomonBy Evan Solomon on 29 November, 2012

            I think it’s probably confusing names rather than an inconsistency. The two filters have very similar but slightly different effects.

            I haven’t worked on Jetpack at all, so I may be wrong, but that’s my interpretation based on reading the code.

  7. FernandoBy Fernando on 29 November, 2012

    Oh my god, there is also a problem with the jetpack sharing buttons and the w3 total cache plugin, check this out

    http://wordpress.org/support/topic/combine-images-into-css-sprites-how-to-fix?replies=2

  8. Ryan HellyerBy Ryan Hellyer on 29 November, 2012

    It’s a crappy plugin, but I don’t think they’re intentionally trying to be dicks. I’m sure they’ll help out if they can.

    • Joost de ValkBy Joost de Valk on 29 November, 2012

      They didn’t, they just didn’t think it through enough.

  9. Syed BalkhiBy Syed Balkhi on 29 November, 2012

    I’m waiting for someone to come and argue decisions over options right now lol.

    This is just another example of why plugins should do 1 thing and do it well… rather than trying to do everything half-ass.

    • Joost de ValkBy Joost de Valk on 29 November, 2012

      Well… I don’t entirely agree with the “1 thing and do it well”, but I do agree with not doing anything half-ass :)

  10. Robert DallBy Robert Dall on 29 November, 2012

    I rarely use the plugin (actually I have only installed it once) because they just can’t play nicely with the rest of the community… 

    They are like the rouge agent of the WordPress community… I wish they would get there act together and be more developer friendly, they might attract more of a following… 

    my 2 cents

  11. Michael BorgerBy Michael Borger on 29 November, 2012

    How does Jetpack improve sharing of a blog site better than just using Disqus and a social sharing plugin like AddThis or DiggDigg? I haven’t used Jetpack on a site yet but am open to considering it – it just seems like a bear of a plugin and I don’t want to get swallowed by all the features.

  12. Antonio GalloBy Antonio Gallo on 30 November, 2012

    I hate Jetpack its on my blacklist of plugins.
    To maximize performance and avoid putting junk code in my websites i try to reduce the number of plugins to the maximum creating simpler plugins (many plugins are big and bloated for dummy users) or hacking genesis functions.php child theme directly… and ofc yoast seo its on my white list because it includes also the rss feed and the sitemap :)

  13. Homer JonesBy Homer Jones on 30 November, 2012

    Be happy! WordPress.com or whatever the parent corporation is called is creating plenty of work to help those that don’t know any better. This always happens when the Board and/or senior execs don’t understand the core fundamentals of the business they are in.
    I am sure the head techies are aware of the problem but after initial protests it’s easier to let the firestorm correct the situation rather than trying a more rational approach.

  14. HerrinBy Herrin on 30 November, 2012

    The worst of this is that many beginner that really should be using both of these plugins will find the problem come up and will have no idea how to solve it.
    Mention functions.php files and the blood will drain out of them.
    The whole auto activation thing is really damn stupid too.
    I love some of the functionality of Jetpack so why don’t they let you turn them on one by one instead of the other way around?
    I personally think the conclusion is clear.
    It’s calculated.
    WordPress is becoming a business that’s seeking to maximize it’s revenue.
    They deserve to make money don’t get me wrong.
    They just shouldn’t get all Microsoft on our asses that’s all.

    Thanks Joost for clearing up this problem and as usual, providing a solution.

    • ScottBy Scott on 30 November, 2012

      The apparent endorsement of Jetpack by Auttomatic implies that Jetpack is well constructed and safe. Apparently not. Time for me to hunt for replacements.

  15. John James JacobyBy John James Jacoby on 1 December, 2012

    The tone towards Automattic developers in this post, and in the comments, is pretty disappointing.

    Statements like “the developers at Automattic seem to think they’re alone in the world” are inaccurate and inflammatory. Plugin conflicts happen, and they’re easily addressed. Do you honestly think we maliciously hoped this would break things?

    You guys should know better than to do stuff like this. You’ve literally cost me about half a days worth of support work now with this single release. It’d be cool if you, just like the rest of Automattic, would work with the community instead of against it.

    Sorry that you had to do some investigating and damage control. Arguably, that’s the nature of WordPress plugin development — updates come in from all directions, things sometimes break; it’s your responsibility to figure it out what you can, and alert whomever is in a position to address it.

    I know you know this, because you and I have done this together personally in the past. Why not ping one of the 27 Jetpack contributors and tell us what happened?

    TL:DR – This is an easily solved problem that can be addressed without any negativity or criticism. We’re all just trying to do good things, and be the best that we can be.

    • Joost de ValkBy Joost de Valk on 1 December, 2012

      I think the disappointment was mine first JJJ, and if you read the post & comments well you’ll see that I actually don’t “attack” all people at Automattic, far from it. I do think Automattic has more of a responsibility to behave responsibly when it pushes out updates like this, because of how it’s able to push the plugin.

      Also, I’m far from the first to have issues with JetPack, if you can’t understand people getting fed up with it, well…

      • Evan SolomonBy Evan Solomon on 1 December, 2012

        Your post describes the Jetpack team as working against the community. That’s not selective paraphrasing, that’s a quote.

        It’d be cool if you, just like the rest of Automattic, would work with the community instead of against it.

        Maybe we habe different interpretation of attack. I guess there was no bloodshed. Thanks for that.

        • Joost de ValkBy Joost de Valk on 1 December, 2012

          Yes. The jetpack team, not Automattic. It’s hardly like I’m the first to comment on how that plugin develops and it’s not like it ever made them change things or even apologize. Automattic is using its power within WordPress to promote that plugin rather aggressively, that leads to aggressive responses. If you can’t stand the heat….

          • Evan SolomonBy Evan Solomon on 1 December, 2012

            Maybe you meant to quote “all” instead of “attack” in your previous comment.

          • Joost de ValkBy Joost de Valk on 1 December, 2012

            Well as is clear by now I’m frustrated but it wasn’t my intention to either attack or “hurt” people. It feels though as though there’s a bit of an ivory tower that sometimes needs a bit of toppling.

            Anyway, I’m very glad with the responses I got from you guys here and I hope that through Jetpacks beta group I’ll be able to prevent future issues.

  16. John OsmondBy John Osmond on 1 December, 2012

    Your solution did not work for me. But this one did:
    remove_action(‘wp_head’,'jetpack_og_tags’);

    • JaniceBy Janice on 3 December, 2012

      Thanks for sharing that here – I’ll have to give that a shot.

  17. Tim TariccoBy Tim Taricco on 1 December, 2012

    Adding remove_action(‘wp_head’, ‘jetpack_og_tags’); to the function.php file worked for me. The other recommendations did not.

  18. MarkBy Mark on 3 December, 2012

    I have 3 description with Jetpack and Yoast.
    When I disable Jetpack I have 2 description.
    Do I need 2 or this is bug from Yoast plugin?

    meta name=”description”
    meta property=’og:description’

    • Joost de ValkBy Joost de Valk on 3 December, 2012

      The one is a “normal” meta description for search engines, the other one is for Facebook and G+, so you need both.

  19. pat nelliganBy pat nelligan on 3 December, 2012

    As a new user it seems to me that a lot of plug-ins are not perfect. Look at yoast seo support forums at the number of people with sitemap errors. These queries go on and on and yet there is no resolution from yoast! Like many other’s I had to download another plug-in to create a sitemap because yoast seo would not do it. And of course, spend hours trying to fix the problem and reading support forums. It is a great plug in except for that one little thing!

  20. HoangBy Hoang on 4 December, 2012

    I just have trouble later with double title when sharing on Google Plus and glad that I read this post.

    Thanks.

    • HoangBy Hoang on 4 December, 2012

      Sadly it does not really work. I need to search for other solution then :(

  21. FredBy Fred on 4 December, 2012

    My view on Jetpack… well lets just say I will never use this monster anyway and am a little confused as to why people do all that bloat for a few features.

  22. MartinBy Martin on 4 December, 2012

    Joost,

    When do you think your update is ready?

    Don’t feel much for changing files manually.
    Regards,

    Martin

  23. IvanBy Ivan on 4 December, 2012

    I like the features of JetPack, but this is a bad move. Joost’s fix for the functions.php didn’t do the trick for me. However, I found the following on http://antesarkkinen.com which did, maybe it helps:

    // remove jetpack open graph tags
    remove_action('wp_head','jetpack_og_tags');
    • Wayne CochranBy Wayne Cochran on 12 December, 2012

      Ivan,

      I am thanking God you found that! I added that code in my functions.php, and it cleaned up some issues I was having between Publicize and the ShareThis plugin.

    • Naziman AzlyeBy Naziman Azlye on 17 December, 2012

      Thanks for that code, i have added that code in my functions.php and the issue gone. Thanks again ivan.

  24. Mark LewisBy Mark Lewis on 4 December, 2012

    Nice tutorial. With more websites moving toward WordPress in the web 2.0 world today, utilizing OpenGraph with WordPress was inevitable.

  25. Sue SurdamBy Sue Surdam on 5 December, 2012

    Thanks for the heads up. I love JetPack, but hate the way features are auto enabled, so have been using the Manual Control Plugin for WordPress for a while. Since I do enable the sharing module, I needed to add the code Ivan posted from Ante. The code provided in the post didn’t work for me either.

    Although, it is impossible to anticipate every situation when building modules for the JetPak plugin, I would think that not auto enabling plugin modules would be good insurance against possible conflicts. I would love the JetPak even more without auto-enable function.

  26. Dominic GreeneBy Dominic Greene on 6 December, 2012

    Though is it really worth installing Jetpack and WordPress SEO or just installing separate plugins to handle the features of Jetpack?

    I’ve always found Jetpack a bit of a worry and am considering whether I should keep it and disable aspects of it like stated in this or just remove it completely and install seperate addons.

    Does Jetpack actually help a great deal with search engines and increasing views or can WordPress SEO handle those aspects anyway?

    • Dominic GreeneBy Dominic Greene on 6 December, 2012

      One thing I was also curious about is what components of Jetpack should be removed to WordPress SEO to be most effective, like if there’s any conflicts, say with enhanced distribution.

  27. Bill RayBy Bill Ray on 7 December, 2012

    Jetpack is the best thing since sliced bread, I would not be without it.

  28. bruceBy bruce on 7 December, 2012

    I see from other places that Jetpack is killing all kinds of plugins, take as an example Quick Adsenes with over 250K downloads.
    Installing Jetpack kills that too. Its a shame that it doesn’t have an active spokesman, or team to bring it to their attention.

  29. JacoseoBy Jacoseo on 10 December, 2012

    To me Jetpack actually help a great deal with great features. Very easy to use..

    Great Post

  30. Stephanie SammonsBy Stephanie Sammons on 10 December, 2012

    JetPack has been a mess for our sites and I’m strongly considering deleted it altogether. Having it not be compatible with your SEO plugin is really the last straw. I also use ManageWP to maintain our sites and am unable to update plugins from there in bulk due to JetPack incompatibility. It is a huge pain and has caused me to have to update manually on a few occasions (100+ sites). My problem is, I need a reliable and clean way to show stats in the dashboard for our clients. If I take those stats away people will scream. I understand WordPress Stats is no longer being updated. We could use a Google Analytics Dashboard Plugin I suppose. Any recommendations? Also, has JetPack fixed this issue without having to install the manual control plugin?

    Thanks!

  31. SteveBy Steve on 11 December, 2012

    Hi,

    I seen you wrote above “might be good to note, when Facebook’s plugin is active and OpenGraph is enabled in my SEO plugin, my plugin filters the output of the Facebook plugin to prevent two sets of OpenGraph tags. ”

    But this i snto the case for me. I am running latest plugin from you 1.3.1.1 and latest official FB plugin. I am getting 2 sets of OG tags in my header. When I try uncheck the box in WordPress Yoast it does not remove from the header and therefore when I debug my content nothing shows due to duplicates.

    Are you sure that latest version solves this?

    • Joost de ValkBy Joost de Valk on 11 December, 2012

      Hi Steve,

      Facebook recently changed a global variable I was using to detect the plugin, Niall from Facebook sent me a patch for that that’ll be in the forthcoming 1.3.2 release, so it might not work right now for you, but it will again later today :)

      • SteveBy Steve on 11 December, 2012

        Hi Joost,

        great thanks for the quick reply. Looking forward to it as last few weeks my updates shared to linkedin were not pulling in any of the og info and I only figured out why today with the multiple og tags..

        Thanks for the awesome plugin too…

      • SteveBy Steve on 11 December, 2012

        also sorry 1 thing I forgot to mention, but just in case FB decide to change things again (which I am sure they will) do you think you could take a look at that checkbox for removing the OG info? I know a lot of people have written on the forums that it does not remove the og tags from the header once it is unchecked (and that is the case for me) cheers

        • Joost de ValkBy Joost de Valk on 11 December, 2012

          I fixed that in this release too.

  32. ShawnBy Shawn on 12 December, 2012

    Joost, couldn’t you just as easily add the functionality to the WP SEO plugin load process? While I can appreciate that the Jetpack team should have known better, you’re already creating special case code (like for the Facebook plugin), so you could readily address this within your own plugin to ensure that the Jetpack stuff isn’t loading. Why make all your users create a custom edit in their functions.php file when you can fix it for all of them automatically?

  33. ScottBy Scott on 12 December, 2012

    “1.3.3

    * Force remove Jetpack OpenGraph.”

    “YAAAAAAAAAAAAAY!” – Kermit the Frog

  34. mdawaffeBy mdawaffe on 13 December, 2012

    Hi Joost,

    I don’t recall if we’ve ever met in person (if you’ll forgive nothing else, I hope you forgive my memory); I’m Mike Adams/mdawaffe.

    Thanks for bringing the issue to our attention, and I’m super happy you’re witness now to our beta process. (Did you get access yet? If not, let me know.) We probably could have cleared this up faster if you’d contacted us directly (did you? If so, let me know so I can figure out what fell through.), but I certainly don’t mind the public discussion.

    I agree we should have been more proactive about finding incompatibilities with popular plugins. We don’t do enough of that in general (I imagine every plugin developer can always do more than they do :)), and for this issue specifically, we actually did have it on our list to check for more OG conflicts, but we messed up and it slipped through. My apologies. We acted mistakenly, not maliciously.

    I know you’ve patched WordPress SEO already, but we’re (finally?! :)) working on cleaning this up. I’m sure we’ll hit you up for feedback.

    Aside: Do you think OG support should be built in to core?

    PS: To anyone else following along, “access” to our beta process is just a faster communications channel between all the participants as new Jetpack things are developed. The beta code is never hidden: it’s always publicly available in the svn repo.

    • Joost de ValkBy Joost de Valk on 13 December, 2012

      Hi Mike,

      we haven’t met I think :) I did tweet to @automattic about the issue a few times, hence my annoyance. It’s patched now indeed.

      As for inclusion of OG in core: I don’t know, I’d mostly appreciate an enqueueing system for meta data just like for scripts and styles, you wouldn’t believe how many sites we’re seeing with double or even triple meta descriptions, og:data etc.

      • mdawaffeBy mdawaffe on 13 December, 2012

        As you discovered, Twitter isn’t the best way to contact us as :( We see some things, but not everything; It’s too ephemeral.

        I’m glad you got ahold of us in the end.

        For core, anything that’s more structured would help. Enqueueing seems like more work than is necessary. Maybe just a filter? It could be something generic for all meta:

        add_filter( ‘wp_head_meta’, ‘my_head_meta’ );
        function my_head_meta( $meta ) {
        $meta['og:description'] = array(
        ‘property’ => ‘og:description’,
        ‘content’ => ‘hello’,
        ‘name’ => false,
        // it’s annoying that opengraph doesn’t use the name attribute
        );
        );

        Then plugins would know what other plugins before them had done.

  35. Raaj TrambadiaBy Raaj Trambadia on 17 December, 2012

    THIS IS WHY I LOVE YOAST :)

  36. CarynBy Caryn on 20 December, 2012

    Yoast,
    I have your SEO on my WordPress blog. I also have Jetpack installed. As per your instructions I did add that bit of code to my php in regards to open graph. Despite this, certain pages and posts had content appearing in header in addition to appearing where they should in posts. I disabled Jetpack, then rolled it back to earlier version. Still this problem remained. Then I changed templates. Still same problem. Then on fluke I discovered that the ONLY pages that appeared in both the header and the posts were pages or posts that weren\’t properly optimized with your SEO plugin. Once optimized the duplicate content disappeared.

  37. MarlonBy Marlon on 26 December, 2012

    THANK YOU! I knew the tags were an issue with the latest versions of jetpack but couldn\’t figure out how to get it fixed. Your fix worked fantastically!

  38. HannahBy Hannah on 29 December, 2012

    Just picking up on what another commenter wrote re: the AddThis sharing plugin. I don\’t use Jetpack\’s Sharing or Publicize modules because I like the sharing analytics AddThis provides, and this prevents any conflict like those mentioned in your article and the comments. However, I do want to implement the nice Twitter sharing as mentioned here: http://yoast.com/twitter-cards/, so I\’d like to use your SEO plugin. Before I install it though, I\’d like to know if I can expect a conflict between the two and what I should do. Then I can apply to Twitter and see how long it takes for everything to be fully implemented. Thanks for the follow up post on Twitter too. My artists resource site consists of an html site and its companion blog, so I\’ll need to work out the og and twitter tags for all the pages on the html site and it appears that I\’ll get a good start with the info there.