大网数据广告活动
网站运营与故障问答

How to correctly mark up different versions of the same document which are non-canonical

· 52CE 我爱测

The use case is a document which has multiple versions which are all simultaneously available. For example, documentation on a product for each version of that software: /v1/install-guide /v2/install-guide /v3/install-guide These…

问题原文

原帖链接 · Brendan Heywood · CC BY-SA 3.0

The use case is a document which has multiple versions which are all simultaneously available. For example, documentation on a product for each version of that software:

  • /v1/install-guide
  • /v2/install-guide
  • /v3/install-guide

These are not the same content in the sense that it would be incorrect to specify in the v1 and v2 pages that the canonical URL is v3. If I searched in Google for 'product install guide v2' I'd expect to be able to find v2. Each version of the document would be slightly different but they'd have a lot in common with each other.

So the question is: can I mark up these pages in some way to signal to Google and friends that the latest version (v3) is preferred, so a simple search for 'product install guide' is more likely to show the v3 page instead of the v1 or v2 page?

社区高分解答

原帖链接 · Seb · CC BY-SA 3.0

given your question I have to make the following assumptions:

  1. your website is offering a section for install-guides for a product
  2. guides differ from product version but stay relevant for customers using older product versions
  3. your customers are aware of that and know exactly which version they may need

First: this indeed is not the use-case for a rel="canonical".

One approach of dealing with situations like yours is structure: You can implement a static guide page for your product that always contains the most recent guide. This page is linked from the product or category page, so it gains a lot of importance.

Scheme:

exapmle.com/product/guide/
exapmle.com/product/guide/guide-v1
exapmle.com/product/guide/guide-v2
exapmle.com/product/guide/guide-v3

Each time a new guide is released it gets published to the static page and the old one moves down to a new URL deeper in the URL structure. Those "old guide" URLs are linked to from the static page, but not from the category pages. Therefor they will be seen "less important"

Make sure, the v1, 2, 3, … n versions are only linked from the main guides page and each to each. The main page must be well linked across your whole site.

Compared to your existing URL structure this give more relevance to the guide published on exapmle.com/product/guide/.

  • /v1/install-guide
  • /v2/install-guide
  • /v3/install-guide

In this structure each URL is "worth" the same and Google needs to rely on other signals to decide which URL is the most relevant.

The next step is optimizing the guide pages in a way search engines quickly understand the difference between the individual versions:

  • individualize the page's title, e.g.: <title>Version 1.0 install Guide for Product XY</title>
  • individualize the page's main heading, e.g.: <h1>How to Install Version 1.0 of Product XY</h1>
  • individualize the page's description, e.g.: <meta name="description" content"Here you can find your guide to install version 1.0 of Product XY […]" />
  • make use of the anchor texts to point out different versions when linking to the guides <a href="http://example.com/product/guide/guide-v2" >Install guide for V 2.0</a>

Each to point out the version it was designed for and maybe the year/month/date.

Hint: it may be helpful to point out the differences at the top of the individual pages. So customers can easily see why they need different guides ans search engines get additional information an unique content for each page lowering your risk of "near duplicate content" issues.

This way you make sure that the most recent guide is always present on example.com/product/guide/ and will served as result for generic searches like "install guide product". Search engines will recognize that content on this page gets updated frequently and also will recognize that sub-items of this pages exist and serve them for more specific search terms like "install guide Product V 2.0". By optimizing the pages for the specific versions they represent you make sure clients find their version by searching for it.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2016-10-05)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。