Fake News or Humor: Flash!


You’re writing humor and let’s say you want your piece to be recognized as funny. You don’t want the pitfall of being misunderstood as fake news. But you don’t want to be too obvious. An ethical solution exists.

Write your HTML page so that search engines display that it’s really just meant as satire or parody or whichever slice of humor gets you. Then, visitors will see what they’re in for before opening your page. This is not a checkbox; you can describe your content any way you like.

Real-world examples exist. A humorist for The New Yorker magazine wrote >an article that said that President Trump had granted American citizenship to President Obama, who was, according to the humorist, emotionally relieved to have finally had his dream fulfilled. Of course, this was during the Presidential campaign, and the magazine, usually published weekly and with a large nationwide circulation for some decades, has a good reputation for reporting, analysis, and fact-checking. It would not want readers to get confused about its intention with humor. This is what they put into their HTML meta description: “Andy Borowitz jokes that President Barack Obama was overwhelmed with gratitude when he was granted citizenship by Donald Trump.” And Google displayed that in its search results

You can easily do something equally useful.

Use the meta element for “description” to write out, in your own words, your description of your page’s content. When Google displays a snippet under the title and the URL, and you have a meta description tag, Google usually uses that. It seems to work best if you keep it to being within 143 characters long (including spaces and punctuation), roughly twenty words of common English. Each page should have a different description; don’t write one description for the whole website.

A few other meta tags should get the same description text. These are named “dc.description”, “dcterms.description”, and “twitter:description”; and one more, which does not have a name but has the property “og:description” and may be used by Facebook. For all of them, the description is the value of the content attribute. They all go into the head element. I put them all next to each other for my convenience, but you don’t have to do that.

I don’t know how other search engines deal with this, but it’s likely some other engines also show description texts you’d supply this way.

You can use these as models for your head element (replace the ellipses):

 

<meta name="description" content=". . . .">

<meta name="dc.description" content=". . . .">

<meta name="dcterms.description" content=". . . .">

<meta name="twitter:description" content=". . . .">

<meta property="og:description" content=". . . .">