Quick Answer
Place pagination outside the repeated element and target the collection it should control. Then verify the first, middle and final result sets. A visible “Next” link is only useful if it advances the intended query without skipping, duplicating or replacing the wrong content.
Define one collection before connecting navigation
Record the post type, filters, order and items per page. Use enough published records to produce several result pages on a controlled test copy. Give the repeated element a clear admin label so it is distinguishable from other loops.
Connect the card’s title, image and link to its current record. Keep the collection heading and pagination outside that repeated element. Our portfolio grid guide covers the item-level fields.
Select the intended target explicitly
The August 24, 2025 publisher tutorial connects a Pagination module to a custom loop. The current module help distinguishes Main Query and Looped Element targets. Choose the looped element for the specific collection described here, then verify which element is selected.
If the page contains a featured collection and a full archive, label them differently and decide which needs navigation. Do not assume the nearest module is the correct target. For a category or search template, also check whether the collection should follow the current page’s query context.
Compare the result sets, not only the animation
Write down the item URLs on the first page, advance, and compare the next set. Check that the order is intentional and the result count agrees with the query. Continue to the final page, including a final page with fewer items.
Check previous navigation, refresh and browser Back. Copy the resulting URL into another test visit to see whether it represents the expected collection state. Verify the actual implementation rather than promising that navigation always avoids a full reload.
Investigate skipped or repeated content
| Symptom | Investigation |
|---|---|
| Another feed changes | Inspect the selected target and any shared selector. |
| Items repeat or disappear | Review ordering, offsets, exclusions and records changing between requests. |
| Every card opens one URL | Check the per-record link binding. |
| Navigation leads nowhere | Check the final result state, generated URL and query configuration. |
Test keyboard access and visible focus for each control. Label direction in terms people can understand from the collection’s order. Our feed selection guide helps decide whether a custom loop is needed. For implementation help, see our WordPress design service.
Key Takeaways
- Keep pagination outside the repeated item and select its target.
- Compare actual record URLs across result pages.
- Test the final page, refresh, Back and multiple-loop behavior.
Frequently Asked Questions
Should every loop have pagination?
A small curated selection may intentionally end after a few items. A browsable collection needs a clear route to the rest.
Does pagination guarantee faster loading?
No. It limits the displayed result set, but query work, images, scripts and caching still affect the actual page.
Can I offset the query?
Review how the offset interacts with paging and exclusions on your actual collection. Check continuity rather than assuming the settings combine correctly.

