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

Connecting multi-part blog post series for SEO purposes

· 52CE 我爱测

I remember reading about a technique at some point to connect multi-part pages or blog posts to indicate to the search engine that this is actually part of one article. I can't however remember the terminology so I can't find any…

问题原文

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

I remember reading about a technique at some point to connect multi-part pages or blog posts to indicate to the search engine that this is actually part of one article.

I can't however remember the terminology so I can't find anything on the web.

This question is somewhat similar but doesn't seem to have the answer I'm looking for.

I thought this might have something to do with pagination, but can't find anything on that either.

已采纳解答

原帖链接 · Dave Sottimano · CC BY-SA 3.0

You're looking for the rel next, rel previous HTML attributes: https://support.google.com/webmasters/answer/1663744?hl=en

From the source link above, here is the generic example:

http://www.example.com/article-part1.html
http://www.example.com/article-part2.html
http://www.example.com/article-part3.html
http://www.example.com/article-part4.html

In the section of the first page (http://www.example.com/article-part1.html), add a link tag pointing to the next page in the sequence, like this:

<link rel="next" href="http://www.example.com/article-part2.html">

Because this is the first URL in the sequence, there’s no need to add markup for rel="prev".

On the second and third pages, add links pointing to the previous and next URLs in the sequence. For example, you could add the following to the second page of the sequence:

<link rel="prev" href="http://www.example.com/article-part1.html">
<link rel="next" href="http://www.example.com/article-part3.html">

When developing, one of the most common development mistakes is to not end the rel next attribute on the final item in the cluster. For example, if your 5 part article ends at /article-part5, ensure you do not include a rel next to /article-part6. Seems obvious, but it's a common oversight - the real problem occurs when the server /article-part6 returns "something' with a 200 response code, which also contains a rel next directive. That means these rel next links to "fake" pages get crawled, indexed and bloat your site, add overhead for crawlers and create unnecessary duplication.

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

资料来源与适用范围

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

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

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