Mitigating mixed signals: effectively consolidating page URLs

Intermediary transaction SEO diagnosis Taobao guest Cloud host technology Hall

The topic of pagination has been discussed in the SEO community, whether it is an E-commerce product category or a blog post, or a lengthy news article, with countless examples across web paging. From a usability perspective, Web paging solves the user's need for endless scrolling, browsing pages, loading faster, and providing a good experience for mobile users.

In the process of using Web paging, we use the wrong or correct signal to tell the search engine that our content is pagination, in particular we will view rel = "prev" and rel = "Next" link elements, implement rel = "Spec" link elements, and use URL parameters recommended in Google Webmaster tools.

Simplify pagination

Since September 2011, Aunt announced the use of rel = "prev" and rel = "Next" link elements to implement page pagination, which makes SEO practitioners around the world a sigh of relief, but in the use of the process, its code to achieve more difficult.

For example: This is a fictitious urlhttp://www.shinybucketsthatcarrydreams.com, this URL is good in, we assume that this is an E-commerce site URL, the site is divided into more than 40 different categories. Webmaster, want to show 10 categories per page, now they want to make things simpler, no advanced sorting options to view all the pages, they don't want to create additional catalogs, all decide to use the page URL parameter tag category, each page displays 10 categories, which requires 4 pages.

The webmaster decides to implement rel = "prev" and rel = "Next" link element at the head of each page. Let's see how this is done.

Page 1:http://www.shinybucketsthatcarrydreams.com/happy-buckets

Note that the URL for the first page (top-level category page) does not contain page query parameters. Remember, do what you can to make your URL simple. In the head, we may encounter the following link elements:

<link rel= "Next" href= "http://www.shinybucketsthatcarrydreams.com/happy-buckets?page=2"/>

Missing a rel = "prev" link element in this element is to tell Spider crawler that this is the first page in a series paging URL, the sequence of the next URL, shown in the href attribute.

Page 2:http://www.shinybucketsthatcarrydreams.com/happy-buckets?page=2

In this series the second page of the head first reflected in our eyes is:

<link rel= "prev" href= "Http://www.shinybucketsthatcarrydreams.com/happy-buckets"/>
<link rel= "Next" href= "Http://www.shinybucketsthatcarrydreams.com/happy-buckets? Page=3 "/>

Here we have two link elements, one rel = "prev"; another rel = "Next". In this case, the rel = "prev" link element points to the previous series, while rel = "Next" link element points to subsequent pages in the series.

Page 3:http://www.shinybucketsthatcarrydreams.com/happy-buckets?page=3

He looks no different from the front.

<link rel= "prev" href= "http://www.shinybucketsthatcarrydreams.com/happy-buckets?page=2"/>
<link rel= "Next" href= "http://www.shinybucketsthatcarrydreams.com/happy-buckets?page=4"/>

Note that our href attribute in the rel = "prev" link element now points to a URL and page parameter. On the second page, this is not the case, because the previous page (page 1th) is the top-level category page.

Page 4:http://www.shinybucketsthatcarrydreams.com/happy-buckets?page=4

This is the last page.

<link rel= "prev" href= "http://www.shinybucketsthatcarrydreams.com/happy-buckets?page=3"/>

Because there is no next page in the sequence, only rel = "prev" link elements are required in page 4. Doesn't it look intuitive to die?

According to the color specification

I've seen a very successful case where they use colors to regulate the URL of a page. The URL parameter used for the sort is the color, which may be red, blue, and green. When the user chooses a blue page, the page reloads the page with the user's choice of color, so this will increase the URL of the Sort=blue, some of the URL of the classification page may look like the following series:

Http://www.shinybucketsthatcarrydreams.com/happy-buckets?page=2&sort=green (2nd page)

http://www.shinybucketsthatcarrydreams.com/happy-buckets?sort=red (1th page)

Http://www.shinybucketsthatcarrydreams.com/happy-buckets?page=4&sort=blue (4th page)

At this point, it's important to note that the amount of page parameter changes appears to be rearranged on the simple URLs we talked about earlier. This is an important difference when dealing with URL parameters and normalization. If the user happens to sort the link to a page (that is, the URL contains the sort parameter), webmasters can have a duplicate content problem, although rel = "Next" and rel = "prev" link, page element signal parameters make paging (so different content), there is no indication of how Google should handle sorting parameters. This is the rel= "spec" proof useful in processing pagination.

Let's look at a couple of pages in our series and see rel = "spec" link elements can be used to counter repetitive content issues.

Page 1th (press red)-)--http://www.shinybucketsthatcarrydreams.com/happy-buckets?sort=red

The dispatch parameter does not actually change the content of the page, but rather rearranges it, because on a page also the content in a URL and the parameter is the same on the page, with no parameters at the same URL. Let's look at the rel= "spec" link elements that compliment our rel= "next" link element.

<link rel= "canonical" Href= "Http://www.shinybucketsthatcarrydreams.com/happy-buckets"/>
<link rel = "Next" href = "http://www.shinybucketsthatcarrydreams.com/happy-buckets?=2&red"/>

Our rel = "spec" link element tells Google the page at this URL (sort parameter) is a canonical version of the page in the top-level category url (href attribute). While this is a generic best practice specification URL, it will prove to be more useful when we arrive at dynamically generated rel = Next "and rel =" prev "link markers.

We are trying to consolidate pagination URLs and avoid sending mixed signals to Google and other search engines. By using rel = "Spec", rel = "Next", and rel = "prev" link element with the GWT URL parameter setting.

by:http://www.thebaiduseo.cn/news-2-1.html Reprint Please keep valid link address, thank you!