A catalog can show different products on page two while its canonical tag still points to page one. This often happens when a shared template always prints the collection’s base address. Check the product list and the generated head together before treating the second page as a duplicate.
This walkthrough uses a fictional model-kit collection. It covers numbered pages of one collection, rather than filtered views or campaign tracking links.
Confirm that page two contains a different part of the collection
Open both addresses directly and record a few product names. For our example:
| Page URL | Example products displayed |
|---|---|
https://example.com/model-kits/ |
Cedar Loop and Marsh Plane |
https://example.com/model-kits/?page=2 |
Willow Glider and Pebble Tug |
The shared category heading does not make those product lists identical. In its pagination guidance, Google recommends giving each page a unique URL and its own canonical instead of using the first page as the canonical for the whole sequence.
Confirm that the second URL actually loads the second list without requiring a previous button click or a saved session. If it always returns page one, investigate the pagination response first. A self-referencing tag cannot create content that the server does not provide.
Compare the incorrect and intended canonical values
On page two, this example points at the wrong member of the sequence:
<link rel="canonical" href="https://example.com/model-kits/">The intended page-two line retains the parameter that selects the second product list:
<link rel="canonical" href="https://example.com/model-kits/?page=2">Page one can point to its own base address; page three should identify its own working URL. Do not hard-code the second address into every page of the collection.
A page-number parameter has a different job from an analytics parameter that opens unchanged content. Our canonical guide for tracking parameters explains that separate comparison. Decide from the content and the parameter’s function before removing a query string.
Draft the second-page line with the tool
- Open the Meta Tag Generator.
- Enter Model kits – Page 2 in Page title.
- Enter Browse the next set of model kits, including Willow Glider and Pebble Tug, with links to each kit. in Meta description.
- Enter
https://example.com/model-kits/?page=2in Canonical URL. Leave the optional social-tags checkbox off for this exercise. - Select Generate Meta Tags and find the canonical line shown above.
For a control, change only Canonical URL to the base address and generate again. The line changes to the incorrect page-one target even though the entered title and description still describe page two. The tool formats what you enter; it does not fetch the catalog or determine which page is canonical.
Keep the generated comparison as a review note. It is not a complete replacement for the head already managed by your site.
Repair the existing template and preserve navigation
Find the canonical provider in your CMS, SEO plugin or template. Update its pagination handling so each numbered page uses the correct address for that page. Test pages one, two and three to catch a shared setting that accidentally assigns the same value everywhere.
For manually maintained HTML, place the intended link in a valid <head>. Use absolute addresses and keep one consistent preference across your implementation, following Google’s canonical implementation guidance. A canonical expresses a preference; it does not guarantee the URL Google selects.
Keep the visible sequence navigable too. For example, a link from page two to the next list can be:
<a href="https://example.com/model-kits/?page=3">Next page</a>Google’s crawlable-link guidance recommends an anchor with an href containing a usable URL. A canonical in the head does not replace the link visitors use to reach page three.
Verify the saved sequence rather than only the preview
- Load pages one, two and three directly while logged out. Compare their product lists and requested URLs with your review notes.
- Inspect each delivered head for the intended canonical. Check for a conflicting second tag or a response header produced by another component.
- Follow the visible next-page links and confirm that each destination contains the expected next set of products.
- For a property you manage, review the declared and Google-selected canonicals in Search Console URL Inspection when indexed information is available.
Record any disagreement with the exact affected URL. Finish by checking another collection that shares the template, since a successful edit to one page does not establish that the pagination logic works across the site.