Not an SEO strategy
It fixes what is wrong on pages you already have. Deciding which pages should exist is a different job — that is content strategy, and it needs a person.
NEW ON THE SHOPIFY APP STORE
Simply SEO Agent scans a Shopify store for missing meta titles, weak descriptions, duplicate content, missing image alt text and Core Web Vitals problems, drafts a fix for each one with Claude, and applies the ones you approve — with an automatic backup and one-click restore on every change. A scheduled agent researches and publishes long-form articles tied to the catalogue.
IN SHORT
Most Shopify SEO problems are not strategic. They are coverage: four hundred products with no alt text, sixty collections sharing a meta title, descriptions that got truncated in a CSV import three years ago. Everyone knows. Nobody is going to spend a fortnight on it.
This app does the two halves of that job that a person is bad at — finding every instance, and drafting a first pass — and leaves the half a person is good at, which is deciding whether the draft is any good. It scans, it proposes, you approve, and the original is kept so you can put it back.
The backup is not a footnote. Bulk-applying four hundred changes to a live catalogue is only reasonable because each one is individually reversible.
Five stages. The fourth is the one that makes the third safe.
A full-store pass over products, collections, pages and the homepage, plus Core Web Vitals. The output is a list of specific issues on specific URLs, not a score out of a hundred.
Each issue gets a proposed fix written by Claude from the page it is on — the actual product, the actual copy — rather than a template with the product name substituted in.
You read the draft against the current value and accept it or you do not. Bulk apply exists for the cases where reading four hundred alt texts individually is not a real option.
The original value is stored before the change lands. One click restores it, per change, which is the difference between a bulk operation and a bulk accident.
The scheduled blog agent researches a topic tied to your catalogue and publishes a long-form article. This is the one part that runs without you in the room, so decide deliberately whether to switch it on.
A monthly allowance plus pay-as-you-go tokens. The higher plans buy a lower per-token rate, not just a bigger bucket.
Free to install
$99/month
$199/month
$399/month
It fixes what is wrong on pages you already have. Deciding which pages should exist is a different job — that is content strategy, and it needs a person.
It reports Core Web Vitals. Improving them means removing third-party scripts and resizing images, which is theme work.
Nothing here earns you a citation from anyone else. On-page coverage is the floor, not the ceiling.
Everything but the blog agent waits for your approval. If you want autonomy, you turn it on knowingly.
Not in the audit-and-fix flow — every drafted fix is previewed and approved before it is applied, and every applied change is backed up and restorable in one click. The exception is the scheduled blog agent, which publishes on a schedule by design. If unattended publishing is not something you want, leave that agent off.
Claude, in two sizes — Sonnet for the work that needs judgement and Haiku for the volume work. The pricing reflects that: token rates are quoted separately for each, and the higher plans buy a lower rate on both.
Each plan includes a monthly token allowance — 100k on Free, 500k on Pro, 1.0M on Business, 2.0M on Scale. Past the allowance you pay per 1,000 tokens, at a rate that falls with the plan: on Free it is $0.0390 for Sonnet and $0.0104 for Haiku, and on Scale it is $0.0156 and $0.0042. The app shows a per-operation token estimate before you run something, which is the number to watch on a large catalogue.
A meta description is not a ranking factor; it is a click-through factor, and a drafted one that is specific beats an empty one or a truncated product description every time. Where the app genuinely earns its keep is the boring coverage problem — the four hundred products with no alt text and the sixty collections sharing one title.
Cautiously, and not instead of anyone. Volume is not the constraint on a blog — a hundred posts nobody reads is a liability. It is a reasonable way to cover the long tail of catalogue-adjacent questions; it is not a way to produce the piece that wins you the customer. We run our own blog on exactly that principle.
It surfaces them. Actually fixing them means removing scripts, resizing images and clearing the critical path, which is theme work rather than a metadata change — see our Shopify speed optimization service.
The app handles the metadata layer. The things it will report and not fix — Core Web Vitals, crawl budget wasted on faceted navigation, a collection architecture that never matched how people search — are the parts that need someone in the theme and in Search Console.
NEXT STEP
The app tells you what is wrong. If the list is longer than a metadata problem — and on most stores it is — a senior engineer will read it with you.