Moving from WordPress or WooCommerce to Shopify
Best matched to search equity, redirects, old URLs, content migration, launch QA, analytics continuity or a post-launch traffic drop.
Open migration guidanceContact
Contact should be the last step, not the first.
Most questions are answered faster by starting with the right guide. Contact is for focused gaps that remain after the guides, checklists or diagnostics have narrowed the problem.
Before you write
Start with the ecommerce risk, not the tactic.
The quality of the message determines the usefulness of the reply.
A useful message explains what could go wrong. A WooCommerce to Shopify migration needs a different answer from a live Shopify collection issue, a TinyIMG question, an analytics problem, or a Field Notes resource request. Use the guides below when they solve the problem faster than a general email.
If the problem is unclear, start with a guide before contacting. If the message is vague, the reply will be generic. If context is missing, the answer may not apply to your store. If the issue is urgent, avoid making changes before diagnosis.
For urgent live-store issues, keep your own evidence log and avoid making rushed changes to URLs, redirects, noindex rules, canonicals, theme files, analytics settings or apps until the issue has been diagnosed properly.
Before you send a message
Filter the request first.
- Have you used the most relevant guide or resource?
- Do you know what problem you are trying to solve?
- Can you describe the risk, not just the tactic?
If not, start there first.
Start with the right guide
Most questions fit one of these four starting points.
Most problems are solved faster by opening the guide that matches the risk.
Improving a live Shopify store
Best matched to collections, products, filters, URL structure, crawl/index signals, internal links, schema, images or reporting.
Open Shopify SEO guidanceChoosing tools without adding bloat
Best matched to decisions about Semrush, TinyIMG, SEO apps, crawlers, GA4, Search Console or operating templates.
Open tool guidanceDownloads, templates and email library questions
Best matched to resource links, signups, workbooks, checklists or Field Notes email issues.
Open resourcesChoose the contact path
General contact and paid review are not the same thing.
General contact
Use this for editorial corrections, resource questions, affiliate/disclosure queries and focused gaps after you have used the right guide.
- Best when the question is specific
- Good for one or two example URLs
- Useful when a page, resource or explanation needs clarifying
Paid audit enquiry
Use the paid audit path when migration, tracking, traffic loss, app conflicts or technical SEO risk needs store-specific review.
- Best when a wrong decision would be expensive
- Use the audit brief before sending the first message
- Better for launch risk, measurement issues and diagnostic work
What to include
Better context means a better first reply.
Include enough detail to make the first reply useful.
You do not need a full audit pack. A few precise details are enough to avoid a generic reply.
- The store URL and current platform, if the question is about a live ecommerce site.
- Whether the store is pre-migration, in staging, newly launched, or already live on Shopify.
- The specific risk you are trying to reduce: traffic loss, redirect mapping, collection SEO, tracking, tool choice, app bloat, or content quality.
- One or two example URLs if the issue is about redirects, collections, products, filters, page templates or tracking.
- What has already been checked, such as Search Console, GA4, crawl exports, redirect tests, Shopify settings or app/theme changes.
Contact form
Use the form when the gap is specific.
Keep the message focused. Longer messages without structure are harder to answer.
The form uses a mail fallback so the message opens in your email client. You can also email info@storefrontfieldguide.com directly.
If the question is really a paid diagnostic review, the cleaner starting point is the paid Shopify SEO audit page. It shows the scope, the evidence to prepare and what the review is for.
Do not include passwords, payment details, customer records, private analytics exports or confidential data in a general enquiry.
Useful enquiries
What a useful message looks like
- Describes the risk, not just the tool or tactic.
- Includes one or two example URLs.
- Explains what has already been checked.
- Identifies whether the store is pre-migration, staging or live.
Enquiry types
Use the right label so the first reply is useful.
| Type | Use it for |
|---|---|
| Editorial correction | Broken links, unclear wording, factual corrections, source updates or a page that needs stronger evidence. |
| Migration or Shopify SEO enquiry | A store that needs a checklist, audit direction or practical next step. Include context rather than a one-line request. |
| Tool, app or affiliate query | Questions about recommended tools, partner links, product changes or review evidence. |
| Privacy, terms or data request | Privacy questions, unsubscribe problems, data requests, disclosure queries or terms-related questions. |
Important notes
Contact can clarify the gap. It cannot diagnose the whole store.
Storefront Field Guide can help clarify corrections, resources and possible next steps, but a complex migration, traffic drop, app conflict or analytics problem still needs store-specific checks before action is taken.
Contact does not replace diagnosis. It helps clarify it.
- Storefront Field Guide is an editorial resource, so messages that include useful context are easier to answer than vague requests.
- Do not send passwords, private customer records, payment information, full analytics exports or confidential commercial documents through a general contact form.
- If a request relates to a live migration, keep a separate evidence log and avoid making risky URL, redirect, indexing, theme or tracking changes while waiting for a reply.
- A message sent through this page does not create a consulting, legal, technical-support or implementation agreement unless a separate agreement is made later.
Trust pages
Commercial, privacy and editorial questions have supporting pages.
For how recommendations are judged, read the methodology. For partner links, read the affiliate disclosure. For forms, analytics and tracking, read the privacy policy. For website-use limits, read the terms.
After the guide
Use contact after the guide
Start with the guide.
Then send the gap.