Brandon Kraft

<p>Jetpack automatically disables its Open Graph tags when there’s a known plugin that already adds Open Graph tags, which is good. Sometimes, though, you might want to use Jetpack’s version instead. Even if you disable the tags in the conflicting plugin, Jetpack won’t add Open Graph tags without being told to do so.</p>
<p>This is great for when you want to use the awesome WP SEO by Yoast plugin or others like All-in-One SEO, but, for whatever reason, would like to use Jetpack’s OG tags instead.</p>


Always Use Open Graph with Jetpack

Jetpack automatically disables its Open Graph tags when there's a known plugin that already adds Open Graph tags, which is good.

Alex MacArthur

<p>There’s no shortage of plugins that promise to be THE all-in-one solution for all things SEO. Unfortunately, this often means lack of flexibility, confusing implementation, or just a big, bloated plugin that carries way too many features for your needs.</p>
<p>This plugin is built on an alternative philosophy: do one thing and one thing well. Complete Open Graph provides automatic, comprehensive, just-makes-sense Open Graph management, whether it’s for a simple blog or a complex site with diverse sets of content.</p>
<p>Out of the box, Complete Open Graph generates all the basic tags your site should have, making it ready for social sharing on platforms including Twitter, Facebook, LinkedIn and Google+, and gives you full programmatic access to filter this data as you need.</p>
<p>TL;DR: This plugin does Open Graph. Freaking good Open Graph.</p>
<h3>Using the Plugin</h3>
<p>Upon activation, Complete Open Graph is ready to generate Open Graph meta tags, with an intuitive set of fallbacks in place. Literally no configuration is required to begin making your site socially shareable.</p>
<h4>Available Fields</h4>
<p>On each page and post, the following fields are automatically generated, based on available page data. Many of these can be manually set at the page/post level.</p>
<ul>
<li>og:site_name</li>
<li>og:locale</li>
<li>og:type</li>
<li>og:title</li>
<li>og:url</li>
<li>og:description</li>
<li>og:image</li>
<li>og:image:width</li>
<li>og:image:height</li>
<li>twitter:card</li>
<li>twitter:creator</li>
<li>twitter:title</li>
<li>twitter:description</li>
<li>twitter:image</li>
<li>twitter:url</li>
<li>twitter:site</li>
<li>profile:first_name (Currently only displayed on individual author pages.)</li>
<li>profile:last_name (Currently only displayed on individual author pages.)</li>
</ul>
<h4>Default Settings</h4>
<p>As a fallback for values that aren’t filled automatically by a page or post, you can set default values for Open Graph data. If desired, you can force these individual values to be used globally, overriding whatever is set at a page/post level. You’re able to force individual fields, or force all of them at once.</p>
<ul>
<li>og:type</li>
<li>og:title</li>
<li>og:image</li>
<li>og:image:width</li>
<li>og:image:height</li>
<li>og:description</li>
<li>twitter:card</li>
<li>twitter:description</li>
<li>twitter:creator</li>
<li>twitter:site</li>
<li>fb:admins</li>
<li>fb:app_id</li>
</ul>
<h3>Filters</h3>
<p>The <code>complete_open_graph_all_data</code> filter allows the customization of the entire set of Open Graph values, as well as the addition of new meta tags (including those that aren’t Open Graph).</p>
<p>Example for customizing out-of-the-box Open Graph data:</p>
<pre><code>function modify_open_graph_data($data) {
  $data['og:site_name']['value'] = 'whatevs';
  return $data;
}
add_filter('complete_open_graph_all_data', 'modify_open_graph_data');
</code></pre>
<p>Example for adding a standard, old meta tag:</p>
<pre><code>function add_new_open_graph_fields($data) {
    $data['keywords']['attribute'] = 'name';
    $data['keywords']['value'] = 'keyword1,keyword2,keyword3';
    return $data;
}
add_filter('complete_open_graph_all_data', 'add_new_open_graph_fields');
</code></pre>
<p>The <code>complete_open_graph_processed_value</code> filter allows you to modify a single field after it’s gone through the progression of priorities. For that reason, it will only be effective on the following fields:</p>
<ul>
<li>og:description</li>
<li>og:title</li>
<li>og:type</li>
<li>og:image</li>
<li>twitter:card</li>
<li>twitter:title</li>
<li>twitter:image</li>
<li>twitter:description</li>
<li>twitter:creator</li>
</ul>
<p>Example for manipulating a processed value:</p>
<pre><code>function manipulate_processed_value($value, $field_name) {
    if($field_name === 'og:description') {
        return 'WHATEVER I WANT.';
    }
    return $value;
}
add_filter('complete_open_graph_processed_value', 'manipulate_processed_value', 10, 2);
</code></pre>
<p>The <code>complete_open_graph_{$tagName}</code> filter allows you to modify a single field by identifying it by name and returning a modified value. These names are the “name” or “property” attributes on the meta tags. See “Available Fields” above for these names.</p>
<p>Example for manipulating a single value by name:</p>
<pre><code>function modify_title($value, $field_name) {
    return 'My Newly Modified Title!'
}

add_filter('complete_open_graph_og:title', 'modify_title', 10, 2);
</code></pre>
<p>The <code>complete_open_graph_maybe_enable</code> filter allows you to disable tag generation altogether by returning a boolean.</p>
<p>Example for disabling generation altogether:</p>
<pre><code>add_filter('complete_open_graph_maybe_enable', '__return_false');
</code></pre>
<p>Example for disabling generation on a specific page:</p>
<pre><code>add_filter('complete_open_graph_maybe_enable', function ($maybeEnable) {
    global $post;

    if($post->post_name === 'my-page') {
        return false;
    }

    return $maybeEnable;
});
</code></pre>
<h3>Order of Priority</h3>
<p>There’s a fallback system set in place for you to effectively leverage this plugin. Below is the order of priority:</p>
<ol>
<li><em>Filters</em> – Any filters you apply in your code will take priority over any fields you have filled in the admin.</li>
<li><em>Forced Global Settings</em> – If you’ve checked the box on these fields on the settings page, they’ll override everything non-filtered.</li>
<li><em>Post/Page COG Fields</em> – Filling out the meta box fields on a page or post in the WordPress Admin will give it priority over any default settings (unless they’re forced).</li>
<li><em>Post/Page Content</em>  – If no specific COG fields on the post/page are set, the post/page content itself will be used. For the Open Graph description, the excerpt will be respected if it’s filled.</li>
<li><em>Default COG Settings</em> – Next, the default COG global settings will used to populate Open Graph tags.</li>
<li><em>Blog Info</em> – When nothing else is overriding them, Open Graph fields will default to your general WordPress site settings.</li>
</ol>
<p>After flowing through this order of priority, if there is still no content to be pulled, those respective Open Graph tags will not be generated. So, don’t worry about having extra, useless tags just sitting there in your markup.</p>
<h3>Feedback</h3>
<p>You like it? <a href="mailto:alex@macarthur.me" rel="nofollow ugc">Email</a> or <a href="https://www.twitter.com/amacarthur" rel="nofollow ugc">tweet</a> me. You hate it? <a href="mailto:alex@macarthur.me" rel="nofollow ugc">Email</a> or <a href="https://www.twitter.com/amacarthur" rel="nofollow ugc">tweet</a> me.</p>
<p>Regardless of how you feel, your review would be greatly appreciated!</p>


Always Use Open Graph with Jetpack vs Complete Open Graph