The Moz Q&A Forum

    • Forum
    • Questions
    • My Q&A
    • Users
    • Ask the Community

    Welcome to the Q&A Forum

    Browse the forum for helpful insights and fresh discussions about all things SEO.

    1. SEO and Digital Marketing Q&A Forum
    2. Categories
    3. Technical SEO Issues
    4. Query string category pagination

    Query string category pagination

    Technical SEO Issues
    3 2 260
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as question
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • MickEdwards
      MickEdwards last edited by

      I've been reading some posts on the merits and pitfalls of using rel=prev, rel=next and canonical, but I just wanted to double check the right solution.

      example.com/birth-announcements

      example.com/birth-announcements?p=2

      example.com/birth-announcements?p=3

      With a small selection of products on each variation.

      So at the moment there is a canonical on all of them to the base example.com/birth-announcements.  The problem is we are having difficulty getting the products within p=* indexed.  I don't think from all I read that rel=prev/rel=next is the way to go.  Would the solution (or best way to go) be to create a "view-all" filter and set that to be the canonical URL, so all product URLs are in clear focus for Google.  The volume of products won't (shouldn't) have too much of an impact on page load.  Or am I wrong and rel=prev/rel=next  is a feasible solution?

      1 Reply Last reply Reply Quote 0
      • Andy.Drinkwater
        Andy.Drinkwater last edited by

        Hi Michael,

        The problem is we are having difficulty getting the products within p= indexed*

        If you have a canonical set on a p=* to the base URL, this will mean those pages never get indexed by Google.

        If each page is different /p=1, /p=2 et al, then a rel prev / next will handle this for you. However, it depends on what is on each of those pages. If they are virtually identical (or at least very similar) then the solution might be to leave the canonical in place - but that doesn't sound like what you want.

        If what I am reading is right, the nel=next & prev would work for you - but remove the canonical on each page. You could also use a view-all as this will work, but have a read of some of the options here. It covers what you need to know.

        https://support.google.com/webmasters/answer/1663744?hl=en

        -Andy

        MickEdwards 1 Reply Last reply Reply Quote 1
        • MickEdwards
          MickEdwards @Andy.Drinkwater last edited by

          Hi Andy,

          thanks for the reply.  Yes, each p=* is identical to the base category URL, the only differences are a small handful of products on each p=* which are not really offering anything to those pages in the way of uniqueness at all in the way they are presented.  So from that point of view the canonical makes sense.  However, I don't want to take Google's focus away from cleanly crawling all the products within p=*

          So rel=next & prev for me opens up duplication issues as there are no "parts" of content, it's going to be effectively the same category textual content.

          However if I implement &view-all and set the canonical to that version i'm then worried Google may be problematic and not play ball.

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post
          • How handle pages with "read more" text query strings?
            0
            1
            31

          • Query Strings causing Duplicate Content
            Alick300
            Alick300
            0
            3
            1.3k

          • How to Remove Old Comment Page Query String URLs
            jonmifsud
            jonmifsud
            0
            2
            151

          • Writing of url query strings to be seo frinedly
            smarties954
            smarties954
            0
            2
            2.0k

          • Query strings in Canoncials URLs
            irvingw
            irvingw
            0
            4
            373

          • Canonical solution for query strings?
            Saijo.George
            Saijo.George
            0
            6
            2.4k

          • Rel canonical with index follow on query string URLs
            panini
            panini
            0
            4
            1.4k

          • How to handle sitemap with pages using query strings?
            oneticsoft
            oneticsoft
            0
            2
            1.4k

          Get started with Moz Pro!

          Unlock the power of advanced SEO tools and data-driven insights.

          Start my free trial
          Products
          • Moz Pro
          • Moz Local
          • Moz API
          • Moz Data
          • STAT
          • Product Updates
          Moz Solutions
          • SMB Solutions
          • Agency Solutions
          • Enterprise Solutions
          • Digital Marketers
          Free SEO Tools
          • Domain Authority Checker
          • Link Explorer
          • Keyword Explorer
          • Competitive Research
          • Brand Authority Checker
          • Local Citation Checker
          • MozBar Extension
          • MozCast
          Resources
          • Blog
          • SEO Learning Center
          • Help Hub
          • Beginner's Guide to SEO
          • How-to Guides
          • Moz Academy
          • API Docs
          About Moz
          • About
          • Team
          • Careers
          • Contact
          Why Moz
          • Case Studies
          • Testimonials
          Get Involved
          • Become an Affiliate
          • MozCon
          • Webinars
          • Practical Marketer Series
          • MozPod
          Connect with us

          Contact the Help team

          Join our newsletter
          Moz logo
          © 2021 - 2026 SEOMoz, Inc., a Ziff Davis company. All rights reserved. Moz is a registered trademark of SEOMoz, Inc.
          • Accessibility
          • Terms of Use
          • Privacy