Protect the old site
Use risk, redirect and launch assets before WordPress or WooCommerce evidence disappears.
Start here
Most Shopify mistakes happen because the wrong thing is optimised first. Teams redesign before capturing URLs. They install apps before understanding the problem. They fix metadata while collections and internal links are still broken. This page exists to stop that sequence.
Immediate action
If you are dealing with:
Do not scroll. Choose one.
The real starting point
A Shopify project usually looks simple at the start: choose a theme, move products, tidy titles, install a few apps and launch. The expensive problems appear later, when old URLs lose value, collections do not match search demand, product pages are too thin, filters create crawl noise, or reporting cannot explain what happened.
Stop that sequence by naming the risk first, then open the guide that matches it. Read only the guide that matches the decision in front of you.
The risk defines the starting point. Not the topic.
Do not start here
These are the most common ways stores lose time before the real work begins.
Choose by situation
Pick the situation that matches your store.
The same symptom can have different causes. A traffic drop after migration is not the same problem as a weak collection page. A tool decision is not the same problem as unclear store architecture. Use the table first, then open the matching guide.
| Signal | Area | Use it when | Start |
|---|---|---|---|
| You have not chosen the platform yet | Platform decision | The store is choosing between Shopify, WooCommerce, WordPress or another ecommerce setup and the decision affects operations, content, SEO control, cost or migration risk. | Compare the platform decision |
| You are moving from WooCommerce or WordPress | Migration protection | The store already has URLs, products, categories, blog posts, rankings, analytics data, plugin SEO settings, backlinks or redirects that must survive the move. | Plan the migration |
| Shopify is live, but performance is unclear | Shopify SEO architecture | The store needs clearer collections, stronger product evidence, better internal links, crawl control, cleaner filters, stronger reporting or fewer overlapping apps. | Open the Shopify SEO hub |
| The team is about to buy another tool | Tools and reviews | The store is considering Semrush, TinyIMG, SEO apps, reporting tools or migration tooling and needs to know whether the tool solves a real operational problem. | Choose tools by job |
If more than one row feels true, choose the one with the highest risk first.
For owners deciding whether Shopify is the right operating model before another expensive rebuild.
For stores moving from WordPress or WooCommerce where redirects, metadata and launch QA are the risk.
For live Shopify stores improving collections, products, crawl control, schema and internal links.
For choosing Semrush, TinyIMG and templates after the platform, migration or SEO job is clear.
Fast triage
If you only know the symptom, start here and move quickly.
| Symptom | First move | Next step |
|---|---|---|
| Traffic could drop during a rebuild | Start with migration protection, not design or app setup. | Start here |
| Important collections do not rank | Start with Shopify collection SEO and internal linking. | Start here |
| Products are thin or duplicated | Start with product evidence before metadata polish. | Start here |
| Filters create lots of URLs | Start with faceted navigation and crawl control. | Start here |
| Reporting does not explain performance | Start with the SEO reporting dashboard and analytics QA. | Start here |
| Image-heavy catalogue feels slow or messy | Start with image SEO before testing another app. | Start here |
| The team wants AI visibility without a process | Start with the AI hub, then move into prompt and citation tracking. | Start here |
| You need diagnosis, not another report | Run a Shopify SEO audit checklist first, then use tool evidence to support the audit. | Start here |
How this site thinks
A live store has different page types with different responsibilities. Collections capture commercial demand. Product pages prove the item. Guides answer pre-purchase questions. Tools and resources help the work happen. Migration pages protect what already exists.
When those jobs blur together, teams optimise the wrong pages. Storefront Field Guide keeps the work separated so you can decide whether the next fix is structural, editorial, technical, commercial, analytical or operational.
If the problem is unclear, start with the highest risk, not the easiest fix.
If a page feels important but has no clear job, treat it as a structural issue.
If multiple issues exist, fix the one that affects the most valuable pages first.
If the guide feels wrong after starting, switch early instead of continuing.
First week plan
Reduce uncertainty before changing templates, URLs, apps or reporting.
If you are new to the site, do not turn every page into a task list. Work through this sequence once, then choose the deeper guides only where the evidence shows a real risk or opportunity.
Are you choosing a platform, protecting a migration, repairing a live Shopify store, or choosing a tool? If the answer is unclear, use the situation guide below before reading any detailed guide.
For migrations, that means old URLs, redirects, metadata, analytics and Search Console data. For live Shopify SEO, that means crawls, page types, collection performance, product quality and internal links.
Most ecommerce SEO work becomes clearer when it is split by page type: collections, products, guides, tools, resources, filters, migrated URLs and reporting pages.
Do not jump from redirect mapping to app reviews to AI visibility. Pick the starting point that protects the current risk, then use the supporting pages as needed.
Use the resource library to record owners, URLs, priorities, risk level, status and follow-up actions. If the work is not captured, it will be forgotten during launch or reporting.
Before you leave
Pick the page that matches the current risk.
Then follow it.
Do not open five guides at once.
Best first downloads
Field Notes
Field Notes is the practical library behind the public guides. Join if you want the checklists, templates and operating notes organised around safer Shopify migrations, cleaner Shopify SEO architecture and more restrained tool choices.
Use risk, redirect and launch assets before WordPress or WooCommerce evidence disappears.
Use audit and collection assets to separate structural fixes from app-led busywork.
Use tool notes only after the job is clear, so software supports the work instead of defining it.