Download the PHP package automattic/jetpack-seo without Composer
On this page you can find all versions of the php package automattic/jetpack-seo. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download automattic/jetpack-seo
More information about automattic/jetpack-seo
Files in automattic/jetpack-seo
Package jetpack-seo
Short Description Jetpack SEO — the visibility command center for WordPress sites in the agentic web.
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package 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 and Site verification cards, each deep-linking into the matching Settings section.
- Settings — a tab to configure search-engine indexing, the XML sitemap, post title structure, the front-page description, and site verification codes.
The Per-post SEO (Content) and AI (llms.txt / AI crawlers) tabs land in follow-up PRs.
Architecture
Built as a @wordpress/build (wp-build) dashboard, the pattern shared by recently-shipped Jetpack admin pages (Podcast, Scan, Forms, Newsletter):
- PHP:
Automattic\Jetpack\SEO\Initializerregisters the admin menu viaAdmin_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 oncurrent_screenso wp-build's auto-generated enqueue callback fires. - React: an ES-module bundle. Routing uses
@wordpress/route; the Overview and Settings tabs are?tab=-driven panels._inc/app.tsxwraps them in theAdminPagechrome from@automattic/jetpack-components. UI uses@wordpress/components,@wordpress/ui, and@wordpress/icons. - Data: read-only initial state for both tabs is bootstrapped server-side onto
window.JetpackScriptData.seo.{overview,settings}via thejetpack_admin_js_script_datafilter (Initializer::inject_script_data()) and read synchronously on the client through@automattic/jetpack-script-data. wp-build pages load as ES modules, sowp_localize_scriptcan't bootstrap them — the script-data layer is the supported channel. The package registers no REST controller of its own: Settings writes reuse the existing/jetpack/v4/settingsendpoint (and core/wp/v2/settingsfor theblog_publicsearch-engine-visibility option).
Development
The built JS/CSS lives in build/ and is included in the vendored Jetpack plugin distribution via .gitattributes (/build/** production-include).
All versions of jetpack-seo with dependencies
automattic/jetpack-admin-ui Version ^0.9.1
automattic/jetpack-status Version ^6.1.7
automattic/jetpack-wp-build-polyfills Version ^0.1.12