Choose one primary product surface
Decide whether the WordPress page or the Shopify product page should be the main version before enabling index controls. In Fy2Press, this choice applies to every synchronized product at once.
Search surface control center
Control the search surface before it controls the story
Fy2Press publishes Shopify records as native WordPress content. Search results still depend on how you set primary URLs, archives and rendered signals.
Implementation boundary
Fy2Press 1.0.0 offers a partial SEO baseline: essential canonical, robots, sitemap and schema behavior. Treat every control as something to configure and verify, never as an automatic ranking promise.
Decision guide
Shopify or WordPress: which product URL should be canonical?
Decide which of your Shopify and WordPress product pages to declare as the main version, then check the served result with a fillable checklist.
01 · In three steps
Make three decisions in the right order.
The search architecture starts with ownership. Only then should you expose URLs or tune individual signals.
- 01
Choose the main product page before enabling index controls.
- 02
Keep thin tag archives disabled unless they are intentionally curated.
- 03
Inspect canonicals, robots, XML sitemap inclusion and rendered schema on the public URL.
02 · SEO
Four controls, one coherent surface.
Use these controls together. A canonical tag cannot repair a confused publishing model by itself.
Build crawlable editorial paths
Connect native WordPress products and collections to useful guides, comparisons and curated category pages.
Publish archives deliberately
Keep thin tag and filter combinations out of the index until they contain a distinct, maintained search experience.
Verify the rendered evidence
Inspect canonicals, robots directives, sitemap membership and schema on the public URL, not only in plugin settings.
03 · Keep the system boundary visible
One boundary. Zero confusion.
Fy2Press connects the catalog surface. It does not replace Shopify, copy your store, or pretend WordPress is the commerce engine.
Owns commerce
- Product and collection records
- Cart and checkout
- Payments and inventory
Carries the catalog
- Manual, reviewable sync
- Display templates
- Blocks and shortcodes
Owns presentation
- Pages and templates
- Editorial context
- Pages you optimize for search
04 · Fy2Press 1.0.0
The operating map
Each task points to its owning surface and the version-bound guide that supplies the verification path.
Control
Primary surface
Verification guide
Connect one Shopify store safely
Shopify + Fy2Press
Create a public Storefront API token in Shopify's Headless channel, enter it with your store address and test the connection. →
Review and synchronize the catalog
Fy2Press
Discover your Shopify catalog, review the summary and start a manual synchronization, then check a first product. →
Publish with blocks and shortcodes
WordPress
Show synchronized products in WordPress pages with the included designs, 17 blocks and 27 shortcodes, while buying stays on Shopify. →
Shape products and collections
WordPress
Use the included visual workshop, default templates and delivered Pro controls without confusing preview locks with active engines. →
Choose the canonical catalog surface
Fy2Press + WordPress
Decide whether WordPress or Shopify is primary, then align indexing, archives, sitemaps and structured output. →
Handle tokens, packages and optional telemetry
All three systems
Keep public and private credentials distinct, limit administrator access and understand optional Freemius data flow. →
Diagnose connection and rendering failures
All three systems
Separate Shopify access, WordPress HTTP, synchronization data and theme rendering before changing credentials or templates. →
Understand data, credentials and external services
Fy2Press
Trace what becomes WordPress content, what remains with Shopify and when Freemius receives optional licensing data. →
05 · Guide index
Follow the evidence, not a checklist.
What you can do for search depends on connection quality, synchronization, publication, design, data handling and diagnostics. The supporting guides form the actual content cluster.
02
03
03
05
06 · Dual Web
Readable by people, retrieval systems and agents.
A strong catalog surface makes identity, source hierarchy and evidence easy to recover without pretending that machine-readable files can force an interpretation.
- 01
Keep product, collection and publisher identities stable across visible content and structured data.
- 02
State the source hierarchy explicitly: Shopify supplies commerce records, WordPress publishes the catalog surface, Shopify retains checkout.
- 03
Bind claims to rendered pages, exact versions and observable behavior instead of generic SEO promises.
07 · Implementation boundary
What this hub does not claim
- No automatic ranking, indexing or citation outcome.
- No scheduled background synchronization in Fy2Press 1.0.0.
- No complete SEO implementation claim until every rendered signal has been verified.
In three steps
Turn the model into a verified publishing workflow.
Use the canonical-surface guide for the control sequence, then look at the plugin screens and what Free and Pro include.