dutchbb
Well-known member
Google indexes every page as a separate page for some time now. Adjusting the DiscussionForumPosting structured data would be a good idea.
For example, i use the date of first post on a thread page for 'dateModified'. This has the possible advantage that google uses that date in search results (it already does it sometimes without structured data). And the more recent the date in search results, the higher the change somebody will click on it.
This is what i use on xf1. I also added some extra data suggested by google for 'Article' (DiscussionForumPosting is a part of that) so it could be used in search results.
developers.google.com
www.seroundtable.com
www.seroundtable.com
For example, i use the date of first post on a thread page for 'dateModified'. This has the possible advantage that google uses that date in search results (it already does it sometimes without structured data). And the more recent the date in search results, the higher the change somebody will click on it.
This is what i use on xf1. I also added some extra data suggested by google for 'Article' (DiscussionForumPosting is a part of that) so it could be used in search results.
Code:
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "DiscussionForumPosting",
"headline": "{xen:jsescape $thread.title}",
"description": "{xen:helper snippet, $firstPost.message, 200}",
"articleSection": "{xen:jsescape $forum.title}",
"datePublished": "{xen:datetime $thread.post_date, 'Y-m-d'}",
"dateModified": "{xen:datetime $firstPost.post_date, 'Y-m-d'}",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "{xen:link 'canonical:threads', $thread, 'page={$page}'}"
},
"image": {
"@type":"ImageObject",
"url":"{xen:helper avatar, $firstPost.message, m, 0, 1}",
"width": "96",
"height": "96"
},
"author": {
"@type": "Person",
"name": "{xen:jsescape $firstPost.username}"
},
"publisher":{
"@type":"Organization",
"name":"",
"logo": {
"@type":"ImageObject",
"url":"logo",
"width": "190",
"height": "60"
}
}
}
</script>Learn About Article Schema Markup | Google Search Central | Documentation | Google for Developers
Learn how adding article schema markup to your news articles and blogs can enhance their appearance in Google Search results.
developers.google.com
Google Now Says Rel=prev/next Is Not An Indexing Signal Anymore
Yesterday during the webmaster hangout, I noticed that the documentation on "Indicating paginated content to Google" that talks about rel=next/prev is now gone, 404ing. Also, the blog post about it from 2011 in bold reads at the top "Note: The information in this post is outdated. Rel=prev/next...
Google's Advice On Pagination & Page Series Post rel=next and rel=prev
As you know, Google told us they just realized that rel=next and rel=prev is no longer supported for the past year or so. Yea, I know. So now what? How do you ensure Google can find your paginated content? How do you communicate to Google a series of pages is part of a set? Mihai Aperghis...
Upvote
2
