AJAX Loading

By default the plugin finds your theme's main content area automatically (for example #content, main or .site-main) and replaces only that. If two pages use different layouts, the second page simply loads normally. To see what is detected, go to Settings → AJAX Loading → Tools & Diagnostics and click Check content selectors. If the wrong area is found, either add the attribute data-ajax-loading-container to your theme's content wrapper, or choose Custom selectors under General → Content regions and enter the selector of the area to replace.

Scripts that set things up when a page first loads have to run again after an AJAX navigation. Try these in order:

1. If it belongs to a plugin listed on SEO & Integrations, make sure that integration is set to Auto.
2. If only some pages are affected, set the integration to Exclude, or add those pages to your exclusions, so they load normally.
3. Re-initialise it from your own code after each navigation (example below).
4. As a last resort, turn on General → Advanced → Fire page-load events again (some scripts may then start twice).

• For one link or a whole area in your templates: add the attribute data-no-ajax or the class no-ajaxy (also no-ajax) to the link or to a parent element.
• For URLs: add patterns under Exclusions → Excluded URLs, one per line. For example /members/ excludes that page and everything below it, /shop/* excludes everything under /shop/, and download= excludes any URL containing that text.
• For links matched by CSS: add selectors under Exclusions → Excluded links.
• For a whole content type: tick it under Exclusions → Excluded post types.

Yes. Shop, category and product pages load with AJAX and the WooCommerce integration re-initialises galleries, variation forms, tabs and sorting. With the default Exclusions → Protect WooCommerce pages option, cart, checkout, My Account and order pages load normally, so payments, sessions and nonces behave exactly as without the plugin. Add-to-cart, remove-from-cart, coupon and logout links are not intercepted either, and WooCommerce's own AJAX add-to-cart buttons keep working. Keep this option on unless you have tested those pages with AJAX navigation.

No. Every URL remains a real page rendered by WordPress, links stay normal links, and the plugin does not show search engines anything different from what visitors get (no cloaking, no #! URLs). It only adds a small <meta name="ajax-loading"> tag, its script and its stylesheet to your pages (and, by default, turns off WordPress's speculative loading rules on those pages). For visitors, the title, meta tags, canonical URL, hreflang links and structured data are updated on every navigation, so share buttons, browser extensions and analytics see the right values.

Yes. The plugin requests pages exactly as a browser does, without special headers, so your page cache serves them as usual. Two things to keep in mind:

• Purge the page cache after activating or updating the plugin and after changing its settings. Cached copies from before can make navigations fall back to normal page loads. When the plugin detects a page cache, its notices remind you after each change.
• If an optimisation plugin delays, combines or defers JavaScript and navigation stops working, exclude the AJAX Loading script (assets/dist/frontend.min.js, handle ajax-loading-WPajaxLoad) and its inline configuration from those features.

By default (Automatic), the plugin sends nothing itself. Google Analytics 4 with Enhanced Measurement ("Page changes based on browser history events") or a Google Tag Manager History Change trigger counts each navigation. You can instead let the plugin send a GA4 page_view event or push a Tag Manager dataLayer event (SEO & Integrations → Analytics). Use only one method; if you choose the GA4 option, turn off the history-based page views in GA4, otherwise every navigation is counted twice.

On the Overview tab you can Turn off AJAX navigation, Pause it for 1 or 24 hours, switch to Test mode (administrators only), or turn on safe mode. All of these keep your settings.

Yes. A global function named wp_ajax_load_complete is still called once after every successful AJAX navigation (never on the first page load). It now runs as soon as the navigation has finished instead of about one second later, and it receives the navigation details as its first argument. New code should listen for the wp_ajax_load_complete event instead, which allows several listeners.

No. The new script has no dependencies. Sites upgraded from 1.x keep loading jQuery (setting General → Advanced → Load jQuery for custom callbacks) because old custom callbacks often use it; turn it off if your own code does not need it.

The readable source is in assets/src/, and an unminified build is shipped as assets/dist/frontend.js (loaded automatically when SCRIPT_DEBUG is on). The build tools are in package.json and tools/build.mjs: run npm install, then npm run build.