Title: PageScale
Author: Shahzaib Rasheed
Published: <strong>26. august, 2026</strong>
Last modified: 26. august, 2026

---

Søk i utvidelser

![](https://ps.w.org/pagescale/assets/banner-772x250.png?rev=3676698)

![](https://ps.w.org/pagescale/assets/icon-256x256.png?rev=3676698)

# PageScale

 Av [Shahzaib Rasheed](https://profiles.wordpress.org/shahzeb2u/)

[Last ned](https://downloads.wordpress.org/plugin/pagescale.1.5.1.zip)

 * [Detaljer](https://nb.wordpress.org/plugins/pagescale/#description)
 * [Omtaler](https://nb.wordpress.org/plugins/pagescale/#reviews)
 *  [Installering](https://nb.wordpress.org/plugins/pagescale/#installation)
 * [Utvikling](https://nb.wordpress.org/plugins/pagescale/#developers)

 [Brukerstøtte](https://wordpress.org/support/plugin/pagescale/)

## Beskrivelse

PageScale replaces the default WordPress Pages screen with an admin interface built
to stay fast on sites that have tens of thousands (or millions) of pages. 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.

**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.

**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.

## Skjermbilder

[⌊The scalable Pages screen: virtual-scrolled list, parent-page overview and quick
actions, staying fast at 8,000+ pages.⌉⌊The scalable Pages screen: virtual-scrolled
list, parent-page overview and quick actions, staying fast at 8,000+ pages.⌉[

The scalable Pages screen: virtual-scrolled list, parent-page overview and quick
actions, staying fast at 8,000+ pages.

[⌊Lazy-loading hierarchy: drilling into a parent loads only that node's children,
never the whole tree.⌉⌊Lazy-loading hierarchy: drilling into a parent loads only
that node's children, never the whole tree.⌉[

Lazy-loading hierarchy: drilling into a parent loads only that node’s children, 
never the whole tree.

[⌊Tiered search across titles, slugs, content and ACF custom fields, with live result
counts.⌉⌊Tiered search across titles, slugs, content and ACF custom fields, with
live result counts.⌉[

Tiered search across titles, slugs, content and ACF custom fields, with live result
counts.

[⌊Duplicate finder scanning for same-title pages across the whole site.⌉⌊Duplicate
finder scanning for same-title pages across the whole site.⌉[

Duplicate finder scanning for same-title pages across the whole site.

## Installasjon

 1. Upload the `pagescale` folder to `/wp-content/plugins/`, or install the plugin 
    through the Plugins screen in WordPress.
 2. Activate the plugin through the Plugins screen.
 3. Open **Pages > Scalable Manager** in the admin menu.
 4. On large sites, optionally run `wp pgscl build-indexes` via WP-CLI to build the
    search indexes immediately instead of waiting for them to build in the background.

## Ofte stilte spørsmål

### Does this add database indexes to my site?

Yes. It adds a small number of composite and FULLTEXT indexes to wp_posts and wp_postmeta
to make search and sorting fast. They are created lazily, one per request, so activation
is instant and no request runs long enough to time out.

### Does it work without the indexes?

Yes. Until the indexes finish building, search falls back to a bounded, basic mode.
Everything else works normally.

### Which capability is required?

Managing pages requires the edit_pages capability, checked on every REST route. 
Private pages are only shown to users who can read them, and per-page edit and delete
actions are checked individually.

### Does it modify my content?

No. Read operations never load post content into PHP. Edit and bulk actions use 
standard WordPress functions and respect per-page capabilities.

## Vurderinger

Det er ingen omtaler av denne utvidelsen.

## Bidragsytere og utviklere

«PageScale» er programvare med åpen kildekode. Følgende personer har bidratt til
denne utvidelsen:

Bidragsytere

 *   [ Shahzaib Rasheed ](https://profiles.wordpress.org/shahzeb2u/)

[Oversett «PageScale» til ditt språk.](https://translate.wordpress.org/projects/wp-plugins/pagescale)

### Interessert i utvikling?

[Bla gjennom koden](https://plugins.trac.wordpress.org/browser/pagescale/), sjekk
ut [SVN-repositoriet](https://plugins.svn.wordpress.org/pagescale/), eller abonner
på [utviklingsloggen](https://plugins.trac.wordpress.org/log/pagescale/) med [RSS](https://plugins.trac.wordpress.org/log/pagescale/?limit=100&mode=stop_on_copy&format=rss).

## Endringslogg

#### 1.5.1

 * Security: apply private-page readability filtering to the /parents, /export and/
   default-view REST endpoints so private pages a user cannot read are never exposed,
   including by direct ID.
 * Cache the parents list per user to avoid serving one user’s readable set to another.

#### 1.5.0

 * Initial public release: keyset pagination, lazy tree, tiered FULLTEXT search,
   virtual scrolling.
 * Duplicate finder for titles, exact slugs and similar slugs.
 * CSV export with formula-injection guarding.
 * Lazy, timeout-safe index building with a WP-CLI command.

## Meta

 *  Versjon **1.5.1**
 *  Sist oppdatert **1 uke siden**
 *  Aktive installasjoner **Færre enn 10**
 *  WordPress-versjon ** 6.0 eller nyere **
 *  Testet opp til **7.1**
 *  PHP-versjon ** 7.4 eller nyere **
 *  Språk
 * [English (US)](https://wordpress.org/plugins/pagescale/)
 * Stikkord
 * [admin](https://nb.wordpress.org/plugins/tags/admin/)[page management](https://nb.wordpress.org/plugins/tags/page-management/)
   [pages](https://nb.wordpress.org/plugins/tags/pages/)[performance](https://nb.wordpress.org/plugins/tags/performance/)
   [search](https://nb.wordpress.org/plugins/tags/search/)
 *  [Avansert visning](https://nb.wordpress.org/plugins/pagescale/advanced/)

## Vurderinger

No reviews have been submitted yet.

[Din omtale](https://wordpress.org/support/plugin/pagescale/reviews/#new-post)

[Se alle omtalene](https://wordpress.org/support/plugin/pagescale/reviews/)

## Bidragsytere

 *   [ Shahzaib Rasheed ](https://profiles.wordpress.org/shahzeb2u/)

## Brukerstøtte

Har du noe å si? Trenger du hjelp?

 [Vis brukerstøtteforumet](https://wordpress.org/support/plugin/pagescale/)