Paginated Pages Which Shouldnt' Exist..

[WebMarkets]

This post is deleted!

[WebMarkets]

Nice website by the way. It looks very professional. And your 49 DA is very impressive.

[TylerReardon]

If you view your source code, you'll notice you are actually using rel="next" and rel="prev" on the main category page (https://www.key.co.uk/en/key/chairs). This is why you (and most likely Googlebot as well) are crawling these paginated pages. Even though you don't have links to the paginated pages on the main category page, they still exist and you're giving crawlers the directive (rel next / rel prev) to crawl them.

If you remove rel="next" on the category home page, that should help but you should really remove rel="next" and rel="prev" on the paginated pages as well. Unless you do that, Google will still find them and crawl them because they're aware these pages exist and they're likely indexed.

Here's a great resource on understanding pagination as well as the correct use of rel="next" and rel="prev" from Maile Ohye at Google: https://www.youtube.com/watch?v=njn8uXTWiGg

Hope this helps!
Cheers!
-Tyler

a7jXKhU

[BeckyKey]

Hi

Thank you both.

We do have issues with our pagination which I've raised with developers, but it's taking forever to sort out. I'll flag this as well.

So even though the content on the paginated pages for Chairs doesn't exist we still need to remove the tags on these - https://www.key.co.uk/en/key/chairs?page=10

[TylerReardon]

Yes exactly. Even though the pages don't exist to the user, they still technically exist. If I were you, I'd take a very deep look at pagination on your site. If this is happening at scale, then fixing it could be a major improvement to your site. I took a look and it seems to be happening on all your top-level category pages like Chairs, Office Furniture, Shelving & Racking, etc.

These paginated pages are essentially a bunch of duplicate pages of your main category pages, each with a self-referencing canonical (which is the proper way to set up pagination). So Google could be extremely confused about which one to rank. In most cases, Google will rank page 1 because the use of rel="next"/rel="prev" is essentially telling Google that page 1 is the canonical version. However, you're still opening yourself up to the possibility of Google crawling all of these duplicate pages which is a huge waste on your crawl budget.

Hope that helps!

[BeckyKey]

Yes I've just gone through every top level page too & pagination is awful, so I'm compiling a list and a case to push it.

It's pretty bad across the site, so I'll push for this to be updated. I find new issues with it all the time..

Thanks for your help!

[Nigel_Carr]

This post is deleted!

[BeckyKey]

Hi Nigel

Thanks for jumping in. I'm confused as I have found the pages on my screaming frog crawl?

This page https://www.key.co.uk/en/key/chairs shouldn't have any pagination as there are no additional pages, but there is rel=next in the source code...

Now I'm a bit confused!

Becky

[Nigel_Carr]

Hi Becky

I can see chairs:

https://www.key.co.uk/en/key/chairs

But the paginated versions above are not in there. (can you see them?)

All you need to do is remove this directive for pages without a page 2: rel="next" href="https://www.key.co.uk/en/key/chairs?page=2" > as there is no page 2 for chairs.

Regards

Nigel

9e989787-5595-4deb-92b6-ce2220b21197

[Nigel_Carr]

This post is deleted!

[Everett]

You will also have to get those URLs out of the index once you fix the rel next/prev issue. In order to do that effectively, they should return a 404 or 410 status code in the HTTP header so Google knows that they no longer exist (even though they never really did in the first place). Otherwise, it's what is known as a "soft 404" in which the page doesn't really exist, but returns a 200 (OK) status code, which is confusing to Google if you don't want them indexed.