Get every page of your lists found
Pagination SEO helps search engines reach and index the numbered pages of an archive or other long list. We inspect how your site generates those pages, including their addresses, links and canonical tags. Our engineers deliver the corrections to the list templates as pull requests in your repo.
What is pagination SEO?
On a growing blog, the newest posts occupy page one and the older entries move onto later pages. That is pagination: dividing a list across numbered pages. Guide libraries and changelogs often use it too. Each part of the list needs an address and a way for crawlers to reach it, because the entries it contains may still answer a buyer's search long after they leave the first page.
Google's rules concern the addresses and links the template produces. Give each page a unique URL, point its canonical tag to that address, and link to the next page with <a href>. A page number after a # fragment does not create a separate address for Google. Titles and descriptions may repeat across the sequence. The rel="next" and rel="prev" tags no longer play a part in how Google handles pagination.
An engineer may check the list templates manually when product work allows. A crawler can supply a list of faults for someone to correct. We take on the inspection and the code changes, starting with the lists containing buyer guides and comparisons. Whichever way you handle it, the correction needs to reach the template the live site uses. Changing that source addresses the tag wherever the template repeats it.
- Set a canonical per page. Each numbered page should name its own address as the preferred URL.
- Connect the sequence. Put a crawlable HTML link on each page leading to the next.
- Assign distinct addresses. Keep page numbers in the URL itself, outside any fragment.
Lists pointing at page one drop pages from Google
A canonical tag repeats across a list template, and every numbered page points back to page one as its preferred address.
- Older posts become harder to find. The later pages listing them tell Google to prefer the first page.
- Archive paths break. A script button without a crawlable link can leave later entries beyond a crawler's reach.
- Pages share one address. Numbering after a
#leaves Google with a single URL for the collection.
A crawl gives us faults to investigate in the templates that generate the archive.
We correct the templates behind your paged lists
We find where the lists begin and follow their numbered pages. Their URLs and tags tell our engineers which parts of the template to change.
Locate the archives
Our audit reads up to 100 public pages per run; we use that crawl to find the blog, guide and changelog lists.
Examine the page tags
We compare the URLs, canonicals and next-page links with Google's rules, then identify where their templates produce the wrong value.
Change the shared code
We correct the template generating the list and prepare a pull request containing the change that applies across its numbered pages.
Align sitemap entries
We update the sitemap to reflect the paged addresses intended for indexing, checking that those entries agree with the URLs the template produces.
We crawl your lists before changing one tag
We separate the initial inspection from changes to the site. Once the corrected template is deployed, we return to the later URLs in Search Console.
First
Read the public pages
We run the read-only audit and retain the evidence behind its findings, giving the inspection a record without changing the site.
Then
Review the findings
Our people identify which affected lists contain buyer guides and comparison pages, then use those destinations to set the order of the work.
Next
Submit the code change
The template correction arrives in your repository as a pull request, where your team can review the work and merge it.
After deployment
Inspect the deployed URLs
We look up the later pages in Search Console and bring that evidence to the weekly decision on what to continue, change or stop.
Example: checking each page of a blog archive
This sample shows the fields we examine in a blog archive. Each numbered page gets a row with its URL, declared canonical, next-page link and sitemap status. A wrong tag or missing link can then be traced to a particular page. We save the findings and their evidence together in the project files.
Buyer searches decide which lists come first
A guide buried in an archive matters when it answers something your buyers search for. We use the keyword plan to find those pages and judge which searches the site can compete for today. The lists containing that content come first when we decide where to spend engineering time.
- Assess the search opportunity. We consider what the site can compete for before selecting the pages to support.
- Follow the buyer pages. We give attention to archives containing the guides and comparisons chosen for those searches.
- Retain the work. The fixes to your list pages, your accounts and the workflows behind them stay with you.
It fits startups whose content outgrew page one
Startups building a library
We help pre-seed to Series A B2B companies whose guides fill several pages and whose founders lack an experienced marketing lead.
AI-enabled service companies
We work on the guide libraries buyers read as they learn about the service and consider whether to talk.
Companies rebuilding their site
We examine paged-list templates during a relaunch, when changes to the site can also change the route to older content.
Talk to Tin
Let's discuss which lists hold your buyer pages and what a crawl would check first. Our work on your search opportunities comes with no long-term commitment.
FAQ
Does Google still use rel="next" and rel="prev"?
No. Google says it no longer uses those tags. For a paginated list, we check the parts its guidance calls for today: a crawlable link to the next page, a separate URL for each numbered page and a canonical that points to that same URL.
Should every page in a list have its own title?
The sequence can use the same title and description, according to Google. Its general advice favors distinct titles, but the pagination guidance permits repetition here. The canonical rule still applies independently: each numbered page identifies its own URL, even when the archive title stays the same.
Can our own engineers make these fixes?
Yes, the work is in the list templates your engineers already maintain. They can run Tin's open-source audit and investigate the pages it reads. We can take on both that inspection and the corrections, with our engineers sending the template changes to your repository.
How do we know the later pages are indexed?
Search Console reports the index status of those URLs. We inspect them after the template change is deployed, because a corrected tag and an indexed page are different things to check. The status of the later pages tells us where more investigation is needed.
Talk through the lists on your site
Talk with the founders and engineers who run the experiments about your archives and the buyer pages inside them. We can discuss how those lists work today and where a closer check would help.