Shipit SEO
DocumentationUninstall Shipit SEO
Documentation

Uninstall Shipit SEO

Remove the native integration while retaining the site and plugin data.

On this page

Plan the replacement output

Test removal on a copy first. Decide how the remaining theme or plugins will supply the metadata and indexing policy the site needs.

Disabling Shipit stops its metadata, JSON-LD and public-file contributions, including its noindex rules. Transfer any required indexing restrictions before disabling it.

Content, media, redirects and native EmDash SEO remain with the host. Saved native values are not removed with the Shipit package.

Pause work and disable Shipit SEO

Turning IndexNow Off pauses delivery but retains its key, queue and history. Disabling the plugin stops its own routes and panels; independently owned files and routes can remain.

Disable Shipit while it is still installed. Removing the wrapper or package first does not perform the Disable step, and disabling cannot recall a request already sent to a provider.

  1. Pause the current analysis run and choose Pause automatic & bulk. Turn off IndexNow delivery and automatic submission without sending pending URLs.
  2. Finish or resolve pending saves, imports and deliveries. Let running requests finish before removing the package.
  3. Choose Disable for Shipit SEO in EmDash and confirm it is inactive while the package and configuration are still present.

Keep a restorable copy

Stop application writers and take a consistent database/uploads backup with the current configuration, package manifest and lockfile. With SQLite, preserve committed WAL data too.

Keep the plugin's settings, schemas, templates, analysis results and IndexNow records, along with all content and uploads. Do not reset storage or delete plugin records as part of removal.

Remove the integration and package

In Astro, replace shipitSeo(emdash, options) with the original emdash(options). Keep the complete options object, adapter and other integrations; register EmDash once.

Remove Shipit-specific imports and any taxonomyArchivePage wrapper. Keep the underlying archive context, route and content, plus EmDashHead, body hooks and the theme's title integration.

Use the npm command below, or pnpm remove @shipitseo/emdash-plugin-seo if this site uses pnpm. Update the existing lockfile with the same package manager.

Keep independently owned public files and routes unless you intend to replace them. Do not use a registry plugin's Delete data flow for this native package.

npm uninstall @shipitseo/emdash-plugin-seo

Build and check the site

  • Run the production build and restart. Confirm Shipit is absent from the admin and its package imports are gone.
  • Check the title, description, canonical, sharing tags and JSON-LD supplied by the remaining theme or plugins.
  • Open sitemap.xml and its child files. Confirm private or noindex URLs remain excluded as intended.
  • Check robots.txt, llms.txt and indexnow-key.txt against the routes or files that still serve them. Verify native SEO and redirects.
  • Keep the retained records and backup available for recovery, and clear the site caches using the normal hosting procedure.

Reinstall or restore

Pause analysis and turn off delivery and automatic submission before disabling. Reinstallation retains data and can retain the inactive state. Enable can immediately resume work left on; check the controls and queue promptly after enabling, before deliberately restoring optional work.

If removal fails, keep the site stopped while restoring its matching configuration, package files and, when needed, database/uploads backup. Restore SQLite files together and account for changes made after the backup.