Architecture before apps
If a Shopify SEO problem can be fixed through collections, product data, internal links, redirects, theme output or reporting, the app is not the first answer. If structure is wrong, apps will make it worse.
Methodology
This page defines how advice is allowed onto Storefront Field Guide.
If a guide, checklist or tool recommendation does not meet this standard, it should not be published.
Why a methodology page matters
Shopify advice is easy to publish and expensive to follow.
Most ecommerce SEO damage comes from advice that sounded reasonable at the time.
A bad migration checklist can lose search equity. A lazy app recommendation can add bloat. A generic SEO audit can bury the page types that actually drive revenue. Storefront Field Guide exists because growing ecommerce teams need more than tips — they need a way to decide what matters, what can wait and what should not be touched without evidence.
These editorial rules govern the guides, reviews, resources and tool recommendations before new advice goes live.
Editorial rules
The four rules that protect the reader.
These are not guidelines. They are constraints.
Evidence before opinion
Migration, audit and tool advice should start from URLs, Search Console, analytics, crawl exports, Shopify settings, product data and observable page behaviour. If it cannot be observed, it should not be recommended.
Commercial honesty before conversion
Affiliate or partner status must be visible, but it should not push a tool ahead of the reader’s actual problem or the site’s evidence level. If the recommendation changes because of commission, it should not be made.
Page-type judgement before generic SEO advice
A collection page, product page, migration guide, app review and reporting dashboard do different jobs. The advice should reflect that difference. If page types are ignored, advice becomes generic and less useful.
Evidence labels
Not every page has the same evidence level — and it should say so.
Evidence level should be visible before trust is required.
| Label | What it means |
|---|---|
| Tested on live store | Used only where a process or tool has been checked in a real store environment with observable behaviour. |
| Tested on demo store | Used where the setup was tested in a development or controlled Shopify environment. |
| Process-tested | Used where the steps have been worked through as an audit, migration, reporting or spreadsheet review. |
| Source-backed guide | Used where the advice is built from official documentation, reputable search guidance and editorial judgement. |
| Editorial reference | Used when a tool or platform is mentioned to explain context, not as a recommendation. |
Source-backed guidance can still be useful. The important point is not to overclaim. If a tool review is based on public documentation and a structured test plan, it should say that. If a process has been used in a real store, it can say that too.
Tool reviews
A tool is judged by the problem it solves and the risk it adds.
A useful tool recommendation reduces uncertainty. A bad one adds another layer to manage.
A Shopify app is not judged only by features. It is judged by the job it does, whether Shopify already offers a native control, whether it changes theme output, whether it can be reversed, whether it duplicates another app, and what a store should measure after installing it.
This is why reviews and recommended-tool pages should not sound like adverts. A tool can be useful and still be wrong for a store that has not fixed collections, product evidence, redirects, internal links or tracking first.
Commercial standard
Commercial links are allowed. Commercial pressure is not.
If a recommendation needs commission to make sense, it is not a valid recommendation.
Storefront Field Guide can earn commission from some links. That support does not decide whether a tool appears, where it is placed or what the verdict says. A recommendation should still make sense if the commission disappeared tomorrow.
Practical checks
What an editor should check before publishing or updating a page.
Each page needs to pass these checks before it is published or updated.
Execution quality
The advice needs to tell a store operator what to do next, what tools are needed, what breaks in real projects and which edge cases change the recommendation.
Evidence honesty
Testing status, commercial links, native Shopify alternatives and limits of the advice should be obvious before the reader is asked to trust a recommendation.
Page-type fit
A migration checklist should behave like a migration checklist. A tools page should help with selection. A resource page should explain when the worksheet is worth opening.
Link logic
Each guide points to the next practical step, whether that is a guide, a worksheet, a tools page or a paid audit review.
What this methodology is designed to prevent
- migrations that lose search equity
- tools being added without solving the problem
- audits that create task lists without priorities
- content that sounds correct but cannot be applied
- decisions based on incomplete evidence
Method in practice
Pages that show the standard working properly.
audit evidence
Shopify SEO audit support with Semrush
This shows how a commercial tool can be useful without pretending the export replaces Shopify-specific judgement.
desk researched
Best Shopify SEO app for image-heavy stores
Use this as the app-governance example: clear fit criteria, native alternatives, and no unsupported performance claims.
tracking
Shopify AI visibility tracking
This is the model for adding a new topic area without inflating the claims beyond what the evidence can actually prove.
If a page does not meet this standard
It should be updated or removed.