Thanos Adamidis

Search has changed. No longer is it possible to manage your on-site SEO with a single “All-in-one” Plug-In.
Semantic search has not only arrived, but it underpins everything Google’s Hummingbird algorithm is about.
Our Plug-In raises your game. Unlike others, ours gets to the very source code of your content.
This enables Google and other search engines to understand what your content relates to, even giving you the ability to link out to authority resources from the tag itself.
<h3>How to use the Semantic Tag Plug-In</h3>
Unlike other tags that you simply enter into a sidebar widget, these tags are extremely editable. You are “marking up” the tags, giving them a whole new dimension and purpose.
Once you have installed the Plug-In, click through your WordPress.org dashboard into the “Posts” section, as you would if you were going in to edit existing posts.
Once through, you will be prompted to “Add new Semantic Tag”. A Word Cloud of the most popular tags will appear above the data entry board. A full list will simultaneously appear to the right, should you need to edit any tags.
Please bear in mind that an edit to the tag will be reflected across your site.
If you’ve created the Semantic Tags or used them in posts before you publish your content, you can add them to your post in the “New Post” dashboard as with the previous tag widget. Only this time, our Plug-In will render in the sidebar, too.
<h3>Creating your Semantic Tag</h3>
There are 10 possible entry fields – don’t panic. You’ll soon get used to filling these in quickly and efficiently.
The features are as follows:
<ul>
<ol>1. Name – this is the name of your tag and what will appear beneath your post as a Semantic Tag.</ol>
<ol>2. Link – this is the relevant content that you would like your customer to be taken to once they click on the tag.</ol>
<ol>3. Rel – here, you can enter multiple rel= attributes. If you’re linking to external sources, it is well worth entering a “nofollow“ here as your first rel. A space in between each is all you need to enter multiple rel properties</ol>
<ol>4. Title – is the text that customers see when they hover over the tag; needless to say, it should be relevant to the content you’re linking to.</ol>
<ol>5. Property – what is the type of tag you are entering, such as a Ctag that would be in the source code of your page</ol>
<ol>6. Resource – is a background link that provides authority to your tag. It will not be clickable on site</ol>
<ol>7. Content – describe the related content to the tag within your article</ol>
<ol>8. Typeof – defines the type of operand to the search engine</ol>
<ol>9. Target – if you want the tag link (2.) to open in new tab, check this box</ol>
<ol>10. Popup – similarly, if you’d prefer a popup (keeping the reader on page), check this box</ol>
</ul>
And that’s all there is to it.
Press update and the tag, with all its configuration data, will save in the “Saved/Editable Tag” list.
You can add each tag to your post from the Semantic Tag Sidebar Widget and, when published, they will render on the screen.
Please proceed to our FAQ where we have a list of queries we had ourselves when creating this Plug-In.
Thanks for downloading our Semantic Tag Plug In; don’t forget to write a rave review!

Semantic Tags

Semantic Tags plugin provides you everything you need to create and semantically markup your Tags.

aveltens

The plugin publishes Linked Data about your blog contents and helps you hosting or connecting your WebID.
<h4>Linked Data</h4>
Turtle and RDF/XML documents can be retrieved performing a HTTP GET request with an appropriate HTTP-Accept-Header set. Blog posts and pages are identified by their original document URI appended by the fragment identifier #it.
E.g. if a blog post ist available at http://example.org/2013/04/my-first-blog-post, the post itself (as an “abstract thing”) is identified by http://example.org/2013/04/my-first-blog-post#it
You may use curl to retrieve Linked Data, e.g.:
curl -H ‘Accept: text/turtle’ http://example.org/2013/04/my-first-blog-post#it
An author, as a person, is per default identified by the author page URI appended by the fragment identifier #me.
E.g. if the authors page is http://example.org/author/alice, the person Alice is identified by http://example.org/author/alice#me
You may try curl again, to retrieve a FOAF-Profile:
curl -H ‘Accept: text/turtle’ http://example.org/author/alice#me
Instead of using WordPress to host the FOAF-Profile, you are able to link your existing WebID to your WordPress account. (See next section)
<h4>WebID</h4>
The Plugin adds a WebID section to the user profile screen in the admin backend. (Note: The section is only available, when editing your own profile).
WebID Location
You can choose, where your WebID is hosted:
<ol>
<li>Locally hosted WebID: The WebID is hosted within your wordpress blog at http://[your-domain]/author/[your-username]#me</li>
<li>Custom WebID: You may enter whatever your WebID URI is and your WordPress account will be linked to it.</li>
</ol>
Whatever option you choose, your wordpress account will always be identified as “http://[your-domain]>/author/[your-username]>#account”. The option only affects, how you, as a person, will be identified.
If you do not have a WebID yet, choose the first option, or get a WebID at https://solidcommunity.net. More Information about WebID: http://webid.info/
RSA Public Key
You may enter the exponent and modulus of the public key of your WebID certificate. This will allow you to use your WordPress WebID for authentication elsewhere on the web. The wp-linked-data plugin is not yet capable of creating WebID certificates, so you will have to create the certificate with another tool (e.g. openssl) and enter the data into this section afterwards.
Additional RDF
You may enter any RDF triples as RDF/XML, Turtle or N3. The triples will occur in the RDF representation of your WordPress profile document at at http://[your-domain]/author/[your-username]

wp-linked-data

Publishes blog post & author data as Linked Data.

Semantic Tags vs wp-linked-data