Choose the canonical catalog surface

This guide applies to the ShopiPress version identified in the page header, officially published on Freemius. Confirm the installed version before applying the procedure. Later versions may change screens, defaults or service boundaries.

Expected result

A documented canonical, robots, sitemap and schema policy is verified on rendered Shopify and WordPress URLs. The policy reflects one chosen primary product surface and makes no ranking promise.

Decide whether WordPress or Shopify is primary, then align indexing, archives, sitemaps and structured output.

Before you begin

• Published test URLs for a product, collection, archive and any relevant taxonomy.
• A decision about whether Shopify or WordPress is canonical for product pages.
• Knowledge of the active SEO plugin: core WordPress, Yoast, Rank Math, AIOSEO or SEOPress.
• Access to the rendered HTTP response and generated sitemap indexes.

Prepare a rollback point and identify the authoritative Shopify record and the WordPress URL or administration surface that will prove the result. The test should be small enough to repeat without creating ambiguous catalog state.

Scope and current limits

The SEO baseline is partial. ShopiPress can align supported canonical, robots, sitemap and minimal schema behavior, but it cannot guarantee crawling, indexation, ranking or the behavior of every theme and SEO-plugin version.

Keep the responsibility model visible throughout the task: Shopify remains the commercial source and checkout system; ShopiPress connects, synchronizes and renders the catalog according to delivered contracts; WordPress owns the publishing context. A successful WordPress result must not be interpreted as a transfer of orders, customers, payments or inventory authority.

Procedure

1. Choose the canonical source for products and document why that surface best answers the target intent.
2. Render a published product and inspect the final canonical in core and the active SEO integration.
3. Verify robots directives for products, collections, tags and internal builder templates.
4. Inspect sitemap indexes and child maps so non-primary or disabled ShopiPress surfaces are absent where required.
5. Compare schema URLs and action targets with the canonical and verify meaningful internal links from guides and collections.

Do not skip the review step between an administrative action and public publication. A successful control response is only one layer of evidence; the stored WordPress record, rendered page and Shopify commerce path must agree.

Verify the result

• The canonical is absolute, valid and stable for the intended primary surface.
• Builder templates are noindex and excluded from sitemaps.
• A surface canonicalized to Shopify is not silently promoted through a conflicting WordPress product sitemap.

Verify the result in the rendered WordPress page and in the authoritative Shopify surface, not only inside the ShopiPress administration screen. Use a representative product with price, availability, variant and collection data. Repeat the smallest safe operation when idempotence matters, and record any difference before broadening the test.

Common mistakes

• Settings and HTML disagree: trust the rendered response, then identify the filter or integration overriding it.
• Duplicate sitemap nodes remain: inspect the active SEO integration and clear only the relevant generated caches.
• Schema points at a different URL: align the WebPage or product URL and action targets with the canonical decision.

When a result is unexpected, stop broad actions and reduce the case to one record, one URL and one renderer. Preserve the failing response before changing settings or clearing caches so the diagnosis remains reproducible.

Troubleshooting

1. Confirm the package version and edition.
2. Reproduce the smallest safe case with controlled data.
3. Identify whether Shopify, ShopiPress or WordPress owns the failing step.
4. Compare the observed result with the delivered, partial or absent capability state.
5. Restore the test environment, repeat once and record whether the result is stable.

Security and data

SEO inspection needs public-like URLs, not production customer data. Use fictional or controlled catalog fixtures and avoid exposing tokens in rendered source, logs or test artifacts.

Record the installed version, edition, WordPress and PHP versions, active builder or SEO integration, exact URL, viewport and the ordered actions that produced the result. Capture only controlled catalog data. Redact the Storefront token, customer data, order information, private domains and any environment secret before an artifact leaves the validation workspace.

SEO consequences

Measure crawl and indexation after release as observations, not guarantees. Record the exact URL, response, canonical, robots, sitemap membership, schema and internal-link path for each test case.

Evidence to record

Record the installed version, edition, WordPress and PHP versions, active builder or SEO integration, exact URL, viewport and the ordered actions that produced the result. Capture only controlled catalog data. Redact the Storefront token, customer data, order information, private domains and any environment secret before an artifact leaves the validation workspace.

Related guides

• Installation
• Publish with WordPress
• Google and SEO
• Security and data

Version and product state

ShopiPress is officially published on Freemius. This guide describes the documented version. Purchase and download links will be added to this site once their destinations are configured.