Using Schema.org Notation to enrich your html with structured data will provide additional information to a search engine, and will help it display the right relevant information on their result page. For an academic personal page this could help people find your contact information, affiliation, and your publications as well.

Schema.org

Semantic notations for html documents have a long story. I've always been a microformats aficionado, but apparently Google is ignoring those. I'm honestly confused, you can read some more information around, but for now I will (probably cowardly) proceed with the most sponsored way.

Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond.

Schema.org vocabulary can be used with many different encodings, including RDFa, Microdata and JSON-LD. These vocabularies cover entities, relationships between entities and actions, and can easily be extended through a well-documented extension model. Over 10 million sites use Schema.org to markup their web pages and email messages. Many applications from Google, Microsoft, Pinterest, Yandex and others already use these vocabularies to power rich, extensible experiences.

The basic idea is write you content down in plain html, add some bloated additional markup, and when a search engine will parse your page, they will pick up this extra information, and possibly show it in a more prominent or readable way in the search-result page.

There is a long philosophical detour we could take, about the fact that this will actively disincentive people from visiting our website, and will just stop at the search engine result-page, but I'll leave that for another time.

In this case, one can either adopt the JSON-LD format, or the Schema.org format. I am in favor of enriching the document markup, and against adding javascript metadata to a page.

I will show two examples: the personal contact snippet, and the publication. They may not be 100% correct, but the Google Structured-Data Validator, and they are currently on-line on this very website.

In general every self-contained piece of information is identified by an itemscope, and each item scope is characterized by an itemtype. For instance, if your markup is about a person, then you can look on schema.org/Person and you will find all properties that you can mark-up. Those should be html elements inside the parent element with itemscope and should be defined with an itemprop attribute/value pair. For instance the full name <span itemprop="name">Matteo Lissandrini</span> or <span itemprop="givenName">Matteo<span> along with <span itemprop="familyName">Lissandrini</span>.

Note that you can put other items inside each other. For instance, you can have an itemprop=address which is also an item scope with type itemtype="https://schema.org/PostalAddress". You will see below.

The Personal Contact

This is from my home page, but I have removed a lot of things here, to make it more readable and focus only on the important bits.

NOTICE: DO NOT COPY PASTE! It won't work.
The code below embeds some magic HTML character coded &zwj;, this is a non-visible zero-width space, and allows my HTML code to display verbatim.


<‍aside itemscope itemtype="https://schema.org/Person">
    <‍figure>
        <‍img itemprop="image" src="http://people.cs.aau.dk/~matteo/images/me.jpg" alt="Matteo Lissandrini's photo" />
    
    <‍address>
        <‍strong class="secsubhead">Contact:<‍/strong><‍br />
        <‍strong itemprop="name">Matteo Lissandrini<‍/strong>
        <‍a itemprop="url"  href="http://people.cs.aau.dk/~matteo">http://people.cs.aau.dk/~matteo<‍/a>
        <‍a itemprop="email" href="mailto:matteo@cs.aau.dk">matteo@cs.aau.dk<‍/a>
        <‍div itemprop="address" itemscope itemtype="https://schema.org/PostalAddress">
          <‍span itemprop="streetAddress">Via Sommarive 9,<‍br />University of Trento<‍/span>
          <‍span itemprop="postalCode">38123<‍/span> —
          <‍span itemprop="addressLocality">Povo, Trento<‍/span><‍br />
          <‍span itemprop="addressCountry">Italy<‍/span>
        <‍/div>
    <‍/address>

    <‍p>
        <‍em itemprop="jobTitle">PhD. Student<‍/em>
        in the
        <‍span itemprop="affiliation" itemscope itemtype="https://schema.org/Organization"
              itemprop="name">
              <‍a itemprop="url" href="https://db.disi.unitn.eu/">
                <‍span itemprop="name">dbTrento<‍/span>
              <‍/a>
        <‍/span>
        research group<‍br />
        and <‍em itemprop="jobTitle">Teaching Assistant<‍/em>
for the course of <‍em>Database Management Systems<‍/em> and <‍em>Information Systems<‍/em>
at the <‍em itemprop="affiliation" itemscope itemtype="https://schema.org/Organization"> <‍a itemprop="url" href="https://www.unitn.it/" > <‍span itemprop="name">University of Trento<‍/span> <‍/a> <‍/em>, <‍/p> <‍/aside>

The Publication

This is one of my publications, the item type is ScholarlyArticle and it has pretty rich properties, you can read them all on schema.org/ScholarlyArticle.

Important to note here is that the Schema.org specification requires both a name and an headline for the article. They are not really exploiting the name property apparently, so you can conflate them both with itemprop="headline name".

NOTICE: DO NOT COPY PASTE! It won't work.
The code below embeds some magic HTML character coded &zwj;, this is a non-visible zero-width space, and allows my HTML code to display verbatim.


  <‍blockquote itemscope itemtype="https://schema.org/ScholarlyArticle">
  <‍span itemprop="author" itemscope itemtype="https://schema.org/Person">
    <‍span itemprop="name">Mottin, Davide<‍/span>;
  <‍/span>
  <‍span itemprop="author" itemscope itemtype="https://schema.org/Person">
    <‍span itemprop="name">Lissandrini, Matteo<‍/span>;
  <‍/span>
  <‍span itemprop="author" itemscope itemtype="https://schema.org/Person">
    <‍span itemprop="name">Velegrakis, Yannis<‍/span>;
  <‍/span>
  and
  <‍span itemprop="author" itemscope itemtype="https://schema.org/Person">
    <‍span itemprop="name">Palpanas, Themis<‍/span>.
  <‍/span>
  <‍br />
  “<‍span itemprop="headline name">Exemplar Queries: A New Way of Searching<‍/span>.”

  <‍div class="hidden">
  <‍time datetime="2014-01-27" itemprop="datePublished">December, 2016<‍/time>
  <‍span itemprop="image">https://disi.unitn.it/~lissandrini/images/xq-logo.png<‍/span>
  <‍/div>

  <‍div itemprop="isPartOf" itemscope itemtype="https://schema.org/Periodical">
    <‍em><‍span itemprop="name">The VLDB Journal<‍/span><‍/em>
  <‍/div>
  <‍span itemprop="isPartOf" itemscope itemtype="https://schema.org/PublicationVolume">
    <‍span itemprop="volumeNumber">25<‍/span>
  <‍/span>,
  <‍span itemprop="isPartOf" itemscope itemtype="https://schema.org/PublicationIssue">
    (<‍span itemprop="issueNumber">6<‍/span>)
    (<‍time datetime="2016-12-01" itemprop="datePublished">December, 2016<‍/time>):
  <‍/span>
  <‍span itemprop="pageStart">741<‍/span>-765<‍/span>.
<‍/blockquote>