Add-ons /

Next Page

Developer documentation for the Ajax Load More Next Page add-on.

Filter Hooks

The following filter hooks are available when using this add-on:


The alm_nextpage_break filter will automatically split content of the post into pages without requiring the Page Break block or <!–-nextpage–-> quicktag inserted into the content.

The following code snippet will dynamically page the content of each post wherever an <h2/> element is found – view example.


The alm_nextpage_the_content filter provides a method to modify the content of the current page.

The following code snippet will prepend an <h3/> with the current page number to the content of each page.


Do not load previous pages when a user enters via deep link URL. e.g.


Add a leading slash / before the page number in the URL.

Note: This is useful when permalink URLs do not have trailing slashes.


Removes the trailing slash / from the end of the URL.


Used to render content before a page is displayed. In this example, a Google Adsense advertisement will be displayed at the opening of each page load.


Used to render content after a page is displayed. In this example, text copy will be displayed after each page.

Frequently Asked Questions

Below are common questions regarding the Next Page add-on. If you have a question and don’t see an answer here, please visit the support page and submit your request.

No, the Next Page add-on uses the_content() for display – repeater templates are not used with this add-on.

Ajax Load More will not hide the paging navigation generated by wp_link_pages(), it will be up to you to modify your template to remove the function or use CSS to hide it.

Yes, the Gutenberg Editor is fully supported by the Next Page add-on. In Gutenberg you will use the Page Break block to split your content into multiple page.

No, Elementor does not currently support the multi-paged WordPress content so this add-on cannot be used.

« Back to Add-ons