The second page of a catalog has different products, but its canonical points to the first page. A canonical is an indication to search engines of the preferred main URL. Sometimes the cause is shared code that removes all URL parameters at once. It removes advertising tags along with the page number, making different product lists look like a single URL.
Do not fix this by adding another canonical. First find the current source of the tag, determine the page number, and agree on the main URL for each list. The instructions below apply to a Bitrix catalog with pagination; infinite scrolling requires separate accessible list URLs first.
What to check on the first and second pages
Open the section and go to the next page using its actual link. Save both full URLs. Find the canonical in each page's source HTML and write down its value. Then compare the products: does the second page show the next set, rather than repeating the first?
If the browser changes the content after navigation without changing the URL, investigate the navigation first. A canonical will not create a missing route. If the URL changes but opening the second page directly returns the first set, the problem may be with how the parameter is handled or with list caching.
According to Google's pagination recommendations individual pages in a sequence should have their own URLs and canonicals. The first page should not become the preferred URL for all the others just because they belong to the same section.
Tutorial example with PAGEN_1
Imagine the section /catalog/fans/, where products 1–20 are on the first page, and 21–40 are on the second. This is a fictional example. In a specific setup, the second-page link looks like /catalog/fans/?PAGEN_1=2. The number after PAGEN depends on the current navigation; get it from an actual site link.
With the chosen rule, the expected HTML for the second page looks like this:
<link rel="canonical"
href="https://example.com/catalog/fans/?PAGEN_1=2">The first page uses /catalog/fans/. A version of the second-page URL with an advertising tag should point to the main URL of the second page, preserving its page number. The URL example.com is for illustration: replace it with the actual primary domain in the production document.
If the page has two independent lists with different paginators, do not copy PAGEN_1 from the example. The developer must determine which parameter controls the main catalog and what changes the second list. Otherwise, the canonical could accidentally include the reviews page number instead of the product page number.
Where to find the canonical source in Bitrix
Ask the developer to check the catalog component parameters, the site template, the SEO module, and custom code. Find out what creates the tag and where it gets its value. Sometimes the standard mechanism runs alongside a manually added string in the header; in that case, fixing one source leaves the other incorrect tag in place.
The CMain::SetPageProperty method sets a property for the current page. Assigning a property named canonical is not, by itself, a universal way to output a link. For it to appear in the head, the active theme or component must use this property accordingly.
The developer's task should show the entire chain: how the main URL is calculated, where the value is stored, and where the tag is output. A custom template may require other integration methods. The site owner does not need to insert a call into a random PHP file: what matters is getting a verified public result without duplicates.
How to separate the page number from extra parameters
Create a table of parameters: the page number changes the product set, an advertising tag does not, and sorting changes the order. Define a rule for each one. Do not remove all GET parameters in a single operation or automatically keep them all. Both extremes create unexpected main URLs.
Common differences between filters, sorting, and advertising tags are covered in the guide to URL parameters.
If the selected sort order shows the same set and should not be indexed separately, agree on its rule separately. A filter that changes the product set requires a decision about whether it should have its own landing page. The canonical for the second page should reflect the page's meaning, not just the presence of a question mark in the URL.
Check a page with multiple parameters in different orders. If the content is the same, it should point to one chosen main URL. Form the full URL with the correct protocol and domain; do not use an unverified hostname from an arbitrary request and end up with a canonical pointing to another domain.
For the first page, decide whether the URL uses the number 1. Internal links and the canonical should consistently follow the chosen format. If the first page is accessible both with and without the parameter, handle both versions according to the agreed rule while preserving access to subsequent pages.
How to check navigation after the fix
Go from the first page to the second and third, then back. At each step, compare the URL, products, and canonical. Open the second URL in a new window without the previous session. The result should match what you see when navigating from the catalog.
Check the source HTML: pagination links should lead to accessible URLs, not just trigger a client-side function. Then check the public response without being logged in. If the page number is preserved but the products repeat, the task is not complete: the canonical correctly describes a URL with incorrect content.
Add checks for the last existing page and a clearly out-of-range number. Behavior beyond the list depends on the implementation, but it must be agreed upon. Returning the first set for any arbitrarily large number creates new duplicates and makes it difficult to tell where the catalog ends.
How to check after adding a neighboring block
If the page template contains several lists, check the catalog on a site copy after adding a new neighboring block. Do not assume the main navigation parameter name is fixed without checking it. Open the actual link to the second page and compare it with the calculated canonical. Changing the number in a secondary paginator should not unexpectedly change the catalog's main URL or return the first page of products.
How to write the task and acceptance criteria
Give the developer three actual URLs, the canonical values before the fix, and a list of the products to check on each page. Specify the main navigation and exceptions: the first page, filter, sorting, advertising tag, and nonexistent page number. Record the versions of the component and modules involved in outputting the tags.
The work is accepted when each existing page shows its own set, the canonical matches the chosen main URL, extra parameters are handled according to the table, and the tag is output from a single source. Include a separate example for the third page: two successful URLs do not prove that a shared function works for any page number.
Additional pages can be checked with a technical site audit, and useful filter pages are covered in the guide to the Bitrix smart filter. Assess Google and Yandex responses separately using up-to-date data. Acceptance of the PHP change confirms the site structure, but does not guarantee that a search engine has already selected all the specified main URLs.