光标 +分页&搜索引擎优化

发布于 2024-12-05 09:58:57 字数 301 浏览 2 评论 0原文

我想知道是否可以使用光标进行分页，同时保持这些页面针对 SEO 进行优化。

/page/1
/page/2

使用偏移量，可以向 Google 机器人提供一些有关深度的信息，但游标的情况并非如此：

/page/4wd3TsiqEIbc4QTcu9TIDQ
/page/5Qd3TvSUF6Xf4QSX14mdCQ

我应该只将它们用作参数吗？

/page?c=5Qd3TvSUF6Xf4QSX14mdCQ

原文

I would like to know if it's possible to paginate using cursors and keep those pages optimized for SEO at the same time.

/page/1
/page/2

Using offsets, gives to Google bot some information about the depth, that's not the case with curors:

/page/4wd3TsiqEIbc4QTcu9TIDQ
/page/5Qd3TvSUF6Xf4QSX14mdCQ

Should I just only use them as an parameter ?

/page?c=5Qd3TvSUF6Xf4QSX14mdCQ

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

情未る 2024-12-12 09:58:57

嗯，这个问题真的很有趣，我会尽力彻底回答你的问题。

简介

一般（易于解决）的缺点

如果您使用分页系统，您可能会为每个页面显示项目的片段（新闻、文章、页面等）。因此，您正在处理著名的重复内容问题。在我链接的页面中，您也可以找到此问题的解决方案。在我看来，这是你能做的最好的事情之一：

使用 301：如果您已重组网站，请使用 301 重定向
(“RedirectPermanent”) 在 .htaccess 文件中进行智能重定向
用户、Googlebot 和其他蜘蛛。（在 Apache 中，您可以使用
.htaccess 文件；在 IIS 中，您可以通过管理来执行此操作
控制台。）

对一般性讨论的一点说明：几周以来，Google 一直在引入一个“系统”来帮助他们识别页面之间的关系，正如您在此处看到的：使用 rel="next" 和 rel="prev" 进行分页

说了这么多，现在我可以进入问题的核心了。这两种解决方案各有利弊。

作为子文件夹（第/1页）

缺点：您将失去页面“页面”上的链接权，因为分页系统的每个部分（页面）都将被视为独立来源，因为它们具有不同的url（事实上你没有使用参数）。
优点：如果您的整个系统使用“/”作为参数之间的分隔符（这在很多情况下是一件好事），则此解决方案将为您的系统提供连续性。

作为参数 (page?param=1)

缺点：虽然 Google 和其他 SE 可以毫无问题地管理参数，但您需要让他们来决定某个参数是否重要以及是否必须这样做小心管理它们或忽略它们。显然，这是正确的，除非您不决定如何在各自的网站管理员工具面板中管理它们。
优点：您将获取“页面”页面上的所有链接权重，但这实际上并不那么重要，因为您希望将链接权重提供给那些将显示详细项目的页面。

分页的“替代方案”

如您所见，我在该网站上发布了一个与您相关的问题。总而言之，我想知道分页的替代方案。这是问题（阅读接受者的答案）：如何避免网站中的分页以获得扁平架构？

嗯，我真的希望我已经彻底回答了你的问题。

Well, this question is really interesting and I'll try to answer your question thoroughly.

Introduction

A general (easy to solve) con

If you are using a pagination system, you're probably showing, for each page, a snippet of your items (news, articles, pages and so on). Thus, you're dealing with the famous duplicate content issue. In the page I've linked you'll find the solution to this problem too. In my opinion, this is one of the best thing you can do:

Use 301s: If you've restructured your site, use 301 redirects
("RedirectPermanent") in your .htaccess file to smartly redirect
users, Googlebot, and other spiders. (In Apache, you can do this with
an .htaccess file; in IIS, you can do this through the administrative
console.)

A little note to the general discussion: Since few weeks, Google has been introducing a "system" to help they recognise the relationship between pages as you can see here: Pagination with rel="next" and rel="prev"

Said that, now I can go to the core of the question. In each of the two solutions, there are pros and cons.

As subfolder (page/1)

Cons: You are losing link juice on the page "page" because every piece (page) of your pagination system, will be seen as an indipendent source because they have a different url (infact you are not using parameters).
Pros: If your whole system is doing using the '/' as separator between parameters (which is in a lot of case a good thing) this solution will give coninuity to your system.

As parameter (page?param=1)

Cons: Though Google and the other S.E.s manage the parameters without problems, you're letting them decide for you if a parameter is important or not and if they have to take care to manage them or ignore them. Obviously this is true unless you're not deciding how to manage them in their respective webmaster tool panel.
Pros: You're taking all the link juice on the page "page" but indeed this is not so important because you want to give the link juice to those pages which will show the detailed items.

An "alternative" to pagination

As you can see, I posted on this website a question which is related to your. To sum up, I wanted to know an alternative to pagination. Here is the question (read the accepter answer): How to avoid pagination in a website to have a flat architecture?

Well, I really hope I've answered your question thoroughly.

回复收藏 0 原文

~没有更多了~