Bruno DC

<p>In an effort to remain as lightweight as possible, LTI SEO will only add metadata information to the html header of your pages (the data <strong>won’t be visible on the page</strong>), and only specialized programs such as <a href="https://en.wikipedia.org/wiki/Web_crawler" rel="nofollow ugc">search engine bots</a> will be able to parse and use that information.</p>
<p>It turns out that this metadata is fairly easy to generate and can make a ton of difference when it comes to <strong>the visibility of your content</strong> on the web. WordPress is very good at creating search engine friendly content; we simply take it one notch further!</p>
<h4>Available languages</h4>
<ul>
<li>English</li>
<li>Français</li>
</ul>
<h4>SEO-friendly metadata</h4>
<p>The following information can be added, if the corresponding option is activated:</p>
<ul>
<li><em>Link rel</em> tags:
<ul>
<li><em>Canonical</em>, helps search engine determine a single URL for specific content,</li>
<li><em>Author</em>, allows search engines to link the author with their contributed content,</li>
<li><em>Publisher</em>, helps identify the entity that’s responsible for the content.</li>
</ul>
</li>
<li><em>Keywords</em> meta tag,</li>
<li><em>Robots</em> meta tag:
<ul>
<li>NOINDEX</li>
<li>NOFOLLOW</li>
<li>NOODP</li>
<li>NOYDIR</li>
<li>NOARCHIVE</li>
<li>NOSNIPPET</li>
</ul>
</li>
<li><em>Description</em> meta tag, featured in search results</li>
<li>JSON-LD tags, using <a href="//schema.org" rel="nofollow ugc">Schema.org</a> namespace objects:
<ul>
<li>Front page:</li>
<li>Publisher (shown as an <em>Organization</em> : name, alias, logo image, website, social accounts),</li>
<li>Author (shown as a <em>Person</em>: public e-mail, job title, work location, social accounts),</li>
<li>Type of site (<em>Blog</em> or <em>WebSite</em>),</li>
<li>Pages and posts:</li>
<li>Type of post (<em>Article</em>, <em>Blog post</em>, <em>News</em>, <em>Scholarly article</em>, <em>Tech article</em>)</li>
<li>Author information (same person object as a above)</li>
</ul>
</li>
<li><a href="https://dev.twitter.com/cards/overview" rel="nofollow ugc">Twitter cards</a>:
<ul>
<li><em>Summary card</em> by default</li>
<li><em>Summary with large image</em>,</li>
<li><em>Gallery</em> for gallery post types,</li>
<li><em>Photo</em> for attachments</li>
</ul>
</li>
<li><a href="http://ogp.me/" rel="nofollow ugc">Open Graph</a> tags:
<ul>
<li>Type <em>website</em> on the frontpage</li>
<li>Type <em>article</em> on posts, with attached or featured images, if any.</li>
</ul>
</li>
</ul>
<h4>Taking advantage of the Google Search Console</h4>
<p>LTI SEO wants to make sure WordPress users know about the Search console by facilitating the process of adding and verifying sites directly from WordPress. Without these types of tools, it would be hard to assess whether our SEO efforts are worth putting time and effort into!</p>
<h4>Contribution</h4>
<p>You can help us by:</p>
<ul>
<li>Translating the plugin in your own language (get in touch with us for details),</li>
<li>Submitting bugs and feature requests in the github project’s <a href="https://github.com/DeCarvalhoBruno/lti-wp-seo/issues" rel="nofollow ugc">issue tracker</a>,</li>
<li>Submitting code via <a href="https://github.com/DeCarvalhoBruno/lti-wp-seo/pulls" rel="nofollow ugc">pull requests</a>,</li>
<li><a href="http://dev.linguisticteam.org" rel="nofollow ugc">Visiting our blog</a> and associated resources to interact with us.</li>
</ul>


LTI SEO

In an effort to remain as lightweight as possible, LTI SEO will only add metadata information to the html header of your pages (the data won't be …

Nazmul Hasan Robin

<ul>
<li>🚀 <a href="https://github.com/nhrrob/nhrrob-core-contributions" rel="nofollow ugc">GitHub Repository</a>: Found a bug or have a feature request? Let us know!</li>
<li>💬 <a href="https://join.slack.com/t/nhrrob/shared_invite/zt-2m3nyrl1f-eKv7wwJzsiALcg0nY6~e0Q" rel="nofollow ugc">Slack Community</a>: Got questions or just want to chat? Come hang out with us on Slack!</li>
</ul>
<p>In the vast tapestry of the WordPress universe, let your contributions shine like stars. The NHR Core Contributions Plugin elegantly weaves your efforts into your website, displaying your dedication with real-time stats. Let the world witness the story of your commitment to the WordPress community.</p>
<pre><code><?php echo 'Shine a Light on Your WordPress Core Work!'; ?>
</code></pre>
<h3>✨ Features</h3>
<ul>
<li>Real-Time Stats: Your latest WordPress core contributions are automatically displayed.</li>
<li>Customizable Display: Display core contributions based on username.</li>
<li>Simple Integration: Easily add contribution stats using the Gutenberg block – no shortcode needed.</li>
<li>Pagination: Fetch all of your contributions with pagination.</li>
</ul>
<h3>📦 Block Usage</h3>
<p>Easily add contribution stats using the Gutenberg editor:</p>
<ul>
<li>Open the post or page in the block editor.</li>
<li>Add the “NHR Core Contributions” block.</li>
<li>Enter your WordPress.org username in the block settings.</li>
<li>Select a design style and publish.</li>
</ul>
<h3>External Services</h3>
<p>This plugin uses the WordPress Core Trac API to retrieve core contributions data. By using this plugin, data is sent to the following service:</p>
<ul>
<li><strong>WordPress Core Trac</strong>: https://core.trac.wordpress.org/</li>
<li><a href="https://wordpress.org/about/privacy/" rel="ugc">Privacy Policy</a></li>
</ul>
<p>No personal or sensitive data beyond the specified username is shared. This data is used solely to fetch and display the user’s contributions to the WordPress core project.</p>


NHR Core Contributions

Display Core Contributions stat in your own website.

LTI SEO vs NHR Core Contributions