"Submitted by..." placement is not optimal for search engines and sharing [#1361388]

Hello!

Nowadays, in case we are trying to share Kanji-formatted node in Google+, it will offer us description like this:

Tracking station at Perth received signal from Phobos-Grunt probe. Submitted by Renat on Wed, 2011-11-23 09:57. It is reported, that tracking station at Australian city Perth once again tried to made ...

As you can see, there are "Submitted by..." row between node title and text. Even worse, we can see something like this in the Google search snippets, and such texts do not motivate users to visit your site. Of course, there are some ways to correct snippets, but they are not always trivial, and many site builders do not use them.

Wouldn't it be better to place "Submitted by..." row below node body, at least at "Default" node display? It will solve most of the problems for robots, and, from my point of view, at least will not harm human site visitors. Maybe this is not the case for "Teaser" node view, because there "Submitted by..." is in it's place - from the human point of view.

By the way, this problem will be solved in case "Submitted by..." row will be placed in the end of appropriate HTML block, and then replaced with CSS.

Comments

Comment #1

DonnyCarette CreditAttribution: DonnyCarette commented 5 December 2011 at 13:16

Hi Renat,

You have a point and i agree it would be better to move the 'submitted msg' to the node bottom.
But i don't want to confuse many people that are using this theme when they update to a new release, and them posting issues about the new 'submitted msg' location :-)
I will leave this open for a while, so i can see if many other people want to see the msg moved to the bottom.
In your case, you could add it now by adding a custom node.tpl for the types you want to put the msg on the bottom.
Because the theme will not have custom node tpl files for types, your file(s) will not be overriden while updating.

Comment #2

renat CreditAttribution: renat commented 5 December 2011 at 14:36

Thank you for the piece of advice about node.tpl. I use them yet, and in combination with page "Description" tag and Schema.org mapping it solves this problem.