Shipit SEO
DocumentationUpdate Shipit SEO
Documentation

Update Shipit SEO

Update the package, keep the site settings and check the result.

On this page

Choose the release

Check Compatibility and the release notes before updating Shipit SEO. Record the installed version and choose the exact new version you will test.

Keep the existing EmDash, database and runtime setup during this update. A host upgrade is a separate change.

Back up the site

Finish pending saves and stop analysis, imports and delivery work. Use the site's backup process to save a consistent database and uploads snapshot with the matching configuration, manifest and lockfile.

For SQLite, use a backup procedure that includes committed WAL data; copying the main database file alone can miss saved changes. Test restoration on a copy. A configuration export is not a full site backup.

Update the package

  1. Use the command below for npm. For pnpm, use pnpm add --save-exact @shipitseo/emdash-plugin-seo@0.4.0-beta.55 instead. Keep one lockfile and review the dependency changes.
  2. Keep the shipit-seo plugin ID, stored data, full EmDash options and public template integrations. Do not uninstall the plugin as an update step.
  3. Confirm the saved site-wide indexing choice before restarting. Do not rely on a previous version's unsaved default restriction.
  4. Run the site checks and production build, restart the copy, then repeat the installation checks in the admin and on a published page.
npm install --save-exact @shipitseo/emdash-plugin-seo@0.4.0-beta.55

Check the updated site

Confirm the settings, entry SEO, schemas, sitemap selection and public files you intend to keep. Review optional work before turning it back on; updating does not start a catch-up scan.

Older analysis results remain saved until you check the entries again. Before importing configuration, preview the changes and take a separate backup; an interrupted import can leave only some changes applied.

Restore the previous setup if needed

If the update fails, stop site writers and restore the matching package manifest, lockfile and configuration. Restore the matching database/uploads snapshot too if the update changed data.

For SQLite recovery, move the failed database, -wal and -shm files aside together before restoring. Account for changes made after the backup: restoring it discards those later changes. Reinstalling an older package alone does not undo data changes.