Install and configure

1. Use the matching nopCommerce 4.80 package and install eStoreware Core first.
2. Back up the database and plugin files. Update an existing installation in place; do not uninstall it as an upgrade step.
3. Restart the application, complete the normal plugin update process, validate licensing, and confirm version 2.51.
4. Select the intended store in SEO settings. Enable the SEO Manager widget when using its structured-data output.
5. Review scheduled tasks and configure only the external connections your store needs.

Version 2.51 creates the current schema on fresh installation and repairs missing phase tables on update. Confirm migration and page access on staging.

Start in the Command Center

Review the prioritized work list, regression alerts, and stored audit/search/performance signals. Use store filters and check data timestamps before acting. Alert thresholds are configurable. Client reports support CSV export and print/Save as PDF.

1. Run an audit in the intended store scope.
2. Review high-priority issues and the affected records.
3. Connect and refresh Search Console/PageSpeed data when those reports are needed.
4. Choose a small set of fixes, preview changes, apply them, and rerun the relevant audit.

Metadata, content, and duplicates

Metadata Manager edits native product, category, and manufacturer fields. Templates, CSV tools, Quick Shorten, and the Duplicate Resolver help with larger catalogs. Content Manager supports fill-empty, replace, append, and prepend modes with previews and history.

For duplicate groups, choose the primary record to retain, review suggestions, then apply the intended records. Ignore deliberate duplicates only after review. Back up/export current values before broad replacement. History includes guarded rollback; a rollback should not overwrite a newer edit.

Structured data, crawling, redirects, and images

• Review Organization/WebSite, Product, BreadcrumbList, and collection markup previews against the actual storefront.
• The store-aware sitemap is /estoreware-sitemap.xml. Verify published URLs and robots diagnostics before submission.
• Publishing robots.additions.txt affects every store in the same application; review shared-store implications. A robots.custom.txt override can prevent additions from taking effect.
• Use the Redirects & 404 tools to review missing paths, proposed replacements, exact-path 301/302 rules, and loop/chain diagnostics.
• Image SEO edits native picture ALT/TITLE/SEO filename values. Review shared-picture safeguards and test a small selection first.

Internal links and specification landing pages

Create rules for natural existing phrases and use Opportunities to preview links before applying them. Page Support identifies weakly supported targets and existing mentions. Bulk recommendations create preview rules; they do not immediately rewrite storefront content.

Auto Apply is optional and should be enabled only for reviewed rules. Specification landing pages use native product specification mappings at /compatibility/{slug}; publish only accurate, useful matches.

Search Console and performance monitoring

Search Console uses a read-only OAuth connection for performance snapshots, page/query comparisons, opportunity signals, and URL Inspection. Configure the authorized connection/property and scheduled synchronization in the plugin. Performance tools combine PageSpeed Insights, Lighthouse opportunities, and available CrUX field data.

Missing or sparse field data is not a passed performance test. Reports are snapshots; refresh them and compare like-for-like dates and URLs. Review provider setup on your installed configuration page.

Review and apply AI SEO drafts

1. Configure the OpenAI connection/model in SEO Manager and select the target records.
2. Request metadata, content, or primary-image ALT drafts.
3. Review factual accuracy, compatibility, tone, field lengths, and the selected store/entity.
4. Explicitly apply only approved drafts and verify the native field and storefront result.

AI drafting in SEO Manager is separate from the storefront AI Assistant plugin. It does not automatically publish drafts. Provider usage fees are separate; request limits are not a guaranteed dollar cap.

Verify results and troubleshoot

After changing page names, test the old and new URLs and their redirects. Check sitemap output, robots behavior, JSON-LD, images, and internal links. Rerun audits and inspect change history. If a screen fails after an upgrade, review migration and plugin-load logs rather than uninstalling the plugin.

Search rankings and traffic depend on many factors. No audit score or AI draft guarantees a ranking improvement.