PHPackages automattic/jetpack-seo - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. automattic/jetpack-seo ActiveJetpack-library[Utility & Helpers](/categories/utility) automattic/jetpack-seo ====================== Jetpack SEO — the visibility command center for WordPress sites in the agentic web. v0.5.0(1w ago)0571↓32.1%21GPL-2.0-or-laterPHPPHP >=7.2CI passing Since Jun 8Pushed 3d agoCompare [ Source](https://github.com/Automattic/jetpack-seo)[ Packagist](https://packagist.org/packages/automattic/jetpack-seo)[ RSS](/packages/automattic-jetpack-seo/feed)WikiDiscussions trunk Synced 1w ago READMEChangelogDependencies (20)Versions (9)Used By (1) Jetpack SEO =========== [](#jetpack-seo) The visibility command center for WordPress sites in the agentic web — a unified wp-admin screen that consolidates SEO, sitemaps, AI discoverability, and site verification settings across all site types (self-hosted, Atomic/WoW, Simple). This package is built up across a stacked series of PRs (see #48154 for the split plan). It currently provides, on a wp-admin page registered at `admin.php?page=jetpack-seo` (gated on the `seo-tools` module being active): - **Overview** — a dashboard with **Site visibility**, **Site verification**, and **Content SEO** cards. The visibility/verification cards deep-link into the matching Settings sections; Content SEO shows factual coverage rings (custom description, schema type set) with literal counts. - **Settings** — search-engine indexing, the XML sitemap (with a "View sitemap" link once it's generated; the toggle is disabled while indexing is blocked, since a sitemap can't be served then), canonical URLs, the title structure for all page types (front page, posts, pages, tags, archives), the front-page description, site verification codes, and site-level Organization, LocalBusiness, and BreadcrumbList schema controls, plus read-only search & social previews of the home page (Google / Facebook / X). - **Content** — a DataViews list of published posts and pages showing each post's SEO state (schema type, meta description set, search visibility). Rows link to the Gutenberg editor and open a per-post **SEO inspector** (custom title, description, schema type, noindex, SERP preview) in the dashboard sidebar. Filters for post type, schema type, description state, and search visibility run client-side over the merged set. The Schema type control and SEO columns also appear in the block editor and `edit.php` post-list tables respectively. JSON-LD (Article / FAQ) is emitted on `wp_head`. - **AI** — the AI SEO Enhancer toggle. (llms.txt and AI-crawler management land in separate Phase 1 projects.) Architecture ------------ [](#architecture) Built as a [`@wordpress/build`](https://www.npmjs.com/package/@wordpress/build) (wp-build) dashboard, the pattern shared by recently-shipped Jetpack admin pages (Podcast, Scan, Forms, Newsletter): - **PHP:** `Automattic\Jetpack\SEO\Initializer` registers the admin menu via `Admin_Menu::add_menu()`, loads wp-build's generated bundle (`build/build.php` + `WP_Build_Polyfills::register()`), and bootstraps the app's initial state. Because the user-facing slug (`jetpack-seo`) differs from wp-build's page slug (`jetpack-seo-dashboard`), the screen id is aliased on `current_screen` so wp-build's auto-generated enqueue callback fires. - **React:** an ES-module bundle. Each top-level view (Overview, Settings, Content, AI) is its own [`@wordpress/route`](https://www.npmjs.com/package/@wordpress/route) route under `routes/`, exporting a `stage` — the per-route pattern shared with Forms. The Content route also exports an `inspector` (the per-post SEO editor), rendered in wp-build's native Stage/Inspector sidebar when a post is selected (`?postId=`). A shared shell (`_inc/dashboard/dashboard-page` + `dashboard-nav`) renders the `AdminPage` chrome from `@automattic/jetpack-components` and the route-based tab navigation, so every route gets the same header, tabs and footer. UI uses `@wordpress/components`, `@wordpress/ui`, and `@wordpress/icons`. - **Data:** the Overview, Settings, and AI routes are backed by read-only REST routes `GET /jetpack/v4/seo/{overview,settings,ai}` (`Initializer::register_rest_reads()`, `manage_options`-gated), whose responses are **preloaded** into the page server-side via `rest_preload_api_request()` (`Initializer::inject_script_data()`, on the `jetpack_admin_js_script_data` filter — wp-build pages load as ES modules, so `wp_localize_script` can't bootstrap them and the script-data layer is the supported channel). On a normal load each route reads its slice from the preload synchronously through `@automattic/jetpack-script-data` (`_inc/data/get-preloaded.ts`) — instant, no request. When a slice is missing or stale (e.g. a mismatched bundle after an update), the route's stage fetches it from its REST route instead of dead-ending: `_inc/data/use-ensure-tab-data.ts` shows a loading skeleton, retries silently, and surfaces a recoverable "Try again" state only on genuine failure. `google_verify` and `site` stay synchronous on `window.JetpackScriptData.seo`. The Content route fetches posts and pages live from **core `/wp/v2/posts` and `/wp/v2/pages`** (no custom endpoint), with SEO meta returned via registered `show_in_rest` post meta; the inspector writes through the same core post endpoint. Most Settings writes reuse `/jetpack/v4/settings` (and core `/wp/v2/settings` for `blog_public`); nested site-level schema settings use the package-owned `GET/POST /jetpack/v4/seo/schema-settings` route so each schema section can be preserved across partial updates. Development ----------- [](#development) ``` # Build once (from the repo root) jetpack build packages/seo # Watch mode pnpm --filter='@automattic/jetpack-seo' run watch # Typecheck pnpm --filter='@automattic/jetpack-seo' run typecheck # Tests pnpm --filter='@automattic/jetpack-seo' run test ``` The built JS/CSS lives in `build/` and is included in the vendored Jetpack plugin distribution via `.gitattributes` (`/build/** production-include`). ### Health Score 41 — FairBetter than 87% of packages Maintenance99 Actively maintained with recent releases Popularity20 Limited adoption so far Community20 Small or concentrated contributor base Maturity24 Early-stage or recently created project Bus Factor3 3 contributors hold 50%+ of commits How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~5 days Total 7 Last Release 11d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/7c5869ecbb8e0eac7e8b8e0f3cf7bdd8d5fcdc4abc10a72281872c53f8639d44?d=identicon)[automattic](/maintainers/automattic) --- Top Contributors [![anomiex](https://avatars.githubusercontent.com/u/1030580?v=4)](https://github.com/anomiex "anomiex (19 commits)")[![angelablake](https://avatars.githubusercontent.com/u/35241639?v=4)](https://github.com/angelablake "angelablake (16 commits)")[![gmjuhasz](https://avatars.githubusercontent.com/u/36671565?v=4)](https://github.com/gmjuhasz "gmjuhasz (11 commits)")[![dhasilva](https://avatars.githubusercontent.com/u/8486249?v=4)](https://github.com/dhasilva "dhasilva (7 commits)")[![robertsreberski](https://avatars.githubusercontent.com/u/8419292?v=4)](https://github.com/robertsreberski "robertsreberski (5 commits)")[![zaguiini](https://avatars.githubusercontent.com/u/26530524?v=4)](https://github.com/zaguiini "zaguiini (3 commits)")[![CGastrell](https://avatars.githubusercontent.com/u/157240?v=4)](https://github.com/CGastrell "CGastrell (3 commits)")[![tbradsha](https://avatars.githubusercontent.com/u/32492176?v=4)](https://github.com/tbradsha "tbradsha (3 commits)")[![xavier-lc](https://avatars.githubusercontent.com/u/8511199?v=4)](https://github.com/xavier-lc "xavier-lc (3 commits)")[![manzoorwanijk](https://avatars.githubusercontent.com/u/18226415?v=4)](https://github.com/manzoorwanijk "manzoorwanijk (2 commits)")[![enejb](https://avatars.githubusercontent.com/u/115071?v=4)](https://github.com/enejb "enejb (2 commits)")[![chriskmnds](https://avatars.githubusercontent.com/u/1705499?v=4)](https://github.com/chriskmnds "chriskmnds (2 commits)")[![simison](https://avatars.githubusercontent.com/u/87168?v=4)](https://github.com/simison "simison (2 commits)")[![chihsuan](https://avatars.githubusercontent.com/u/4344253?v=4)](https://github.com/chihsuan "chihsuan (2 commits)")[![haqadn](https://avatars.githubusercontent.com/u/3737780?v=4)](https://github.com/haqadn "haqadn (1 commits)")[![vianasw](https://avatars.githubusercontent.com/u/298685?v=4)](https://github.com/vianasw "vianasw (1 commits)")[![LiamSarsfield](https://avatars.githubusercontent.com/u/43409125?v=4)](https://github.com/LiamSarsfield "LiamSarsfield (1 commits)") ### Embed Badge ![Health badge](/badges/automattic-jetpack-seo/health.svg) ``` [![Health](https://phpackages.com/badges/automattic-jetpack-seo/health.svg)](https://phpackages.com/packages/automattic-jetpack-seo) ``` ### Alternatives [automattic/jetpack Jetpack supercharges your self‑hosted WordPress site with the awesome cloud power of WordPress.com 3622.8k](/packages/automattic-jetpack) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)