PageScale

PageScale replaces the default WordPress list screen with an admin interface built to stay fast on sites that have tens of thousands (or millions) of entries. The stock list table slows down at that scale because it relies on OFFSET pagination and unindexed queries. PageScale takes a different approach at every layer.

As of 1.6.0, PageScale is no longer limited to Pages. You choose which post types it manages from a settings screen. Hierarchical types (like Pages) keep the lazy parent/child tree; non-hierarchical types (like Posts or a Products CPT) get the fast flat list. Pages behaviour is unchanged by default, so existing sites are unaffected until you opt additional types in.

How it stays fast

• Keyset (cursor) pagination instead of OFFSET, so the cost of loading any page of results is constant whether you have 10,000 rows or 1,000,000.
• Lazy hierarchy: only the children of a node you actually expand are queried. The tree never loads the whole site at once.
• Tiered search: numeric input goes straight to the primary key, slugs use an indexed equality/prefix lookup, and title/content/custom-field search uses InnoDB FULLTEXT (MATCH … AGAINST) rather than a leading-wildcard LIKE. Content and custom-field search is optional via a UI toggle and runs entirely in MySQL, so post content is never loaded into PHP memory.
• Virtual scrolling keeps the DOM bounded (about 50 rows) at any dataset size.
• Cached aggregates: totals, the parents list and duplicate reports are cached with the Transients API, keyed per post type.

Custom post type support

• Choose which post types to manage from Settings > PageScale.
• Each managed type gets its own Scalable Manager screen under its menu, with a switcher to move between types.
• Hierarchical types show the parent/child tree and a parents panel; non-hierarchical types show a flat list without a Parent column.
• Search, quick edit, bulk actions, duplicate and CSV export all work per type.

Other features

• Elementor-aware quick actions.
• Bulk actions, chunked client-side so large operations don’t time out.
• Duplicate finder for titles, exact slugs and similar slugs.
• CSV export of the current view or a selection.
• WP-CLI command to build the search indexes on demand.

Indexing is safe on large tables

PageScale never runs a long ALTER TABLE during activation. Instead it records that indexes are pending and builds them lazily, one at a time, on later admin loads (or immediately via WP-CLI). The plugin is fully usable while indexing is in progress, and search simply runs in a basic mode until the FULLTEXT indexes exist.