Jane SEO is live in the Shopify App Store. She is my first AI SEO app, built alone, and she got there through three rejections. If you are reading this because a Shopify app review rejection just landed in your inbox, this is the post I wanted three weeks ago and could not find. Not the polished version. What the process actually feels like from the inside, what nobody tells you before you submit, and the working method that got me from rejected to approved.

Table of Contents

• The Part Nobody Prepares You For
• Rejection Is Information, Not Judgment
• Three Things I Wish Someone Had Told Me
• Being Crafty Beats Being Clever
• The Bug in the Address Bar
• What Actually Solved Every Problem
• What Jane Does Now
• Summary
• Frequently Asked Questions
• Related Reading

The Part Nobody Prepares You For

Everybody writes about building the app. Almost nobody writes about the weeks after you hit submit, which is where the Shopify app review process actually lives.

Here is the shape of it. You submit. Days pass. A message arrives saying your app does not meet requirement such and such, with a rule number and two sentences. Sometimes a short screen recording. Then nothing, until you fix it and submit again.

I expected a dialogue. I got a verdict. That is not a complaint about the reviewers, who were accurate every single time, on every single rejection. It is a description of the system, and the sooner you understand the system the sooner you stop spending energy fighting its shape. The reviewer's job is to check whether your app does what you claim, safely, without errors. Their job is not to work out why it does not. That part is yours.

I learned this properly when I sent a long, careful technical write-up into the review thread and waited for a reply. Nothing came back. What I eventually understood is that in my case the thread only moved when I resubmitted the app. The queue runs on submissions, not on messages. So a question sent into that thread and left to sit is a question that sits. If you genuinely need an answer before you can move, you may have to resubmit to get one, which is an expensive way to ask. Never send a question you could have answered yourself with an hour of proper investigation.

Rejection Is Information, Not Judgment

The first rejection landed and I read it as a failure. That is the wrong reading, and it costs you days.

A Shopify app store rejection is a very expensive, very slow test result. Somebody sat down with your app, did a specific thing, and it broke. The rule number tells you which promise you failed. The two sentences tell you where they were standing when it broke. That is real information about your product, gathered by a stranger with no context, which is exactly the condition every future customer will be in.

My three rejections landed in different places. One was about the app being free from errors. One was about the billing flow. One was about the billing flow again, from a completely different angle. Read as failures, that is three punches in three weeks. Read as information, that is a stranger telling me three separate places where a real merchant would have hit a wall and uninstalled without ever telling me why.

The second rejection was actually progress and I nearly missed it, because I was too busy being deflated to notice that the rule number had changed. A different rule number means they got past the first problem. You moved forward. Notice that, because morale is a real resource when you are the only person on the project and there is nobody else in the room to point it out.

Three Things I Wish Someone Had Told Me

One. Reviewers verify, they do not diagnose. Assume nobody is coming to help. Build your own reproduction, your own logging, your own way of seeing what is actually happening inside your app. If your only picture of the problem is the reviewer's two sentences, you are working blind on purpose. Roll your sleeves up before you submit, not after.

Two. The Shopify app reviewer test account setting is hidden. Reviewers need a way into your app that does not charge them money. That setting is not on the submission form where you would go looking for it. It sits in the settings page you reach while adding your pricing plans, in a section you have no reason to open unless you already know it is there. I found it late. Go and find it now, before you submit, because a reviewer who cannot get into your app is a rejection you never needed to take.

Three. Your demo video does more work than your app does. The reviewer watches it, and it frames everything they see afterward. Record the real flow, slowly, with nothing broken and nothing skipped. Then record it again after every fix, so it always shows the current truth rather than the version you wish were true.

Being Crafty Beats Being Clever

There is a difference between clever and crafty, and as a solo Shopify app developer the whole month came down to it.

Clever is the elaborate theory. Clever is deciding, on the strength of a symptom, that the fault must be in a system you cannot see, and then building a careful case for it. I did exactly this. I wrote a long technical document arguing that a platform component was broken, with evidence, ready to send to support and wait however long it took. Every fact in that document was true. The conclusion was wrong.

Crafty is smaller and much less satisfying. Crafty is asking what you can check in the next sixty seconds. Crafty is noticing that a value you assumed was correct has never actually been verified by anyone. Crafty is opening the thing in a plain browser tab instead of inside the app, because that removes half the variables at no cost. Crafty is reading what is in front of you before you construct what might be behind it.

Every hour I lost that month, I lost to clever. Every problem I actually solved, I solved by being crafty.

The pattern repeated until it stopped being funny. A feature that did nothing at all, no error, no warning, which turned out to be two halves of my own system disagreeing about what yes meant. An app that died on every request, which I was certain meant I had broken something deep, and which turned out to be an account somewhere that had quietly run out of credit. A cosmetic label I fought for an entire evening before discovering it blocked absolutely nothing. Every one of those looked like a deep problem and was a shallow one. Every one of them had announced itself plainly in a log or a message I had not bothered to read yet.

The Bug in the Address Bar

The last one is the story I will be telling for years, because it is the one that stood between me and Shopify app store approval.

Near the end, the billing flow failed in a way that looked exactly like a platform fault. A page would appear, hold for about a second, then throw the merchant straight back out. It happened to me. It happened to the reviewer. It happened when I opened the page directly in a clean browser tab, with none of my own code anywhere in the path, which is normally decisive proof that the fault is not yours.

I had verified everything on my side. Settings, plans, permissions, all of it. I was confident enough to write the escalation, and confident enough to be completely wrong.

Then I opened my own app inside the store admin and looked at the address bar. Sitting there, in plain text, was the identifier Shopify uses for my app. It was not the identifier I had configured. It was close enough that nobody would notice at a glance, and different enough that every single test I had run for weeks had been aimed at the wrong place.

I had taken a version number and used it where an app name belonged. The two look nearly identical. The system had been telling me the correct value, in the address bar, every time I opened my own app, for weeks.

I changed one setting. The page worked. The escalation went in the bin. Days later the app was approved.

There is no clever lesson in that. The lesson is that the answer was in plain sight and I was busy looking somewhere more interesting.

What Actually Solved Every Problem

Looking back across the whole run, the method that worked never changed. If you want to know how to pass Shopify app review as a solo builder, it is less about knowing the rules and more about how you behave when something breaks.

Read the evidence before you build the theory. Logs, error messages, the address bar, the actual response. The system usually knows what is wrong and will tell you if you let it. Every mystery I had dissolved the moment I stopped guessing and started reading.

Verify the thing you are most sure about. The bugs did not hide in the complicated parts. They hid in the parts I had decided were already correct and never checked again. If you have eliminated everything and you are still stuck, the fault is in something you never put on the list.

Reduce the variables before you reason. Open it outside the app. Try it in a clean window. Take the pieces apart. Half of a hard problem is usually a variable you could have removed for free.

Never send a theory when you can send a fact. I came close to filing a formal complaint about a platform I depend on, based on a conclusion I had not tested hard enough. Being wrong in private is survivable. Being wrong in a support queue costs you weeks and some credibility.

Sleep on it. Every problem I forced at night went worse. Every one of them fell in minutes the next morning. This is not a productivity tip. It is the single most reliable debugging technique I own.

See what Jane does for your store

What Jane Does Now

Now the part I have earned the right to write. Jane is an AI SEO app for Shopify that lives inside your admin and does the work, rather than handing you a report and wishing you luck.

You talk to her. Plain language. Ask what is hurting your rankings, which products to fix first, or what your rivals are winning on, and she answers from your real store data. You can discuss strategy with her, not just trigger actions.

She sees your products. Not just the title and the tags. She looks at the actual product image and writes from what is there.

She writes the whole page. Meta title, meta description, on-page copy, an FAQ where it helps, image alt text, and structured schema. Products and collection pages both, so the category pages carrying your biggest terms get the same treatment as the products under them.

She reads real demand. Live Search Console data where you have it, and she keeps up with your catalog as you add to it. She works out what your store actually sells and builds from there.

She talks to the other AI engines. This is the part I am proudest of. Jane queries ChatGPT and Perplexity directly to pull keyword strings, competitor intelligence, top-ranking products, and the leading blogs in your niche. She mines the live web for what is rising. Then she checks what those assistants cite when a buyer asks a question in your category, which tells you exactly what you need to become in order to be the cited answer. That is answer engine optimization done by reading the answers, not by guessing at them.

She shows her working. A demand-ranked queue of what to fix next, trends, blog ideas, market intelligence, and a full activity log with before and after on every single change.

Nothing happens without your yes. She proposes the work and the cost. You approve. Every change reverts in one click. Reading, advising and browsing cost nothing at all. Only acting spends credits, and only when you say so.

Three plans from $39 a month, sized by how much work she does rather than by which features are held hostage, and every plan gets the whole product with a 14-day free trial.

And she is not finished. Jane shipped as version one on purpose, with features deliberately cut to get her into merchants' hands sooner. Those features are coming back, and more with them, through the rest of this year.

Frequently Asked Questions

How long does Shopify app review take?

For me it was three weeks from first submission to approval, across three rejections. Each cycle is a few days of waiting followed by a short message. The clock only moves when you submit, so the real length of your review is mostly the length of your own fixes.

Does Shopify help you fix problems during app review?

No. Reviewers verify that your app does what you claim and that it runs without errors. They will tell you what failed and often show you a recording of it failing. Working out why is entirely your job. Plan for that before you submit rather than after.

Can you ask questions in the Shopify app review thread?

You can write in it. In my case nothing came back until I resubmitted the app. Treat the thread as the place to file your answer, not as a place to ask a question and wait for a reply.

How do Shopify reviewers test a paid app without paying?

There is a setting that gives reviewers a free way in, and it is not on the submission form. It lives in the settings page you reach while adding your pricing plans. Set it up before you submit, or a reviewer may not be able to get into your app at all.

What is the most common mistake solo Shopify app developers make?

Building a theory before reading the evidence. Nearly every hour I lost went to an elaborate explanation of something a log line, an error message, or the browser address bar would have told me in seconds.

What is Jane SEO?

Jane is an AI SEO app for Shopify that lives inside your admin. You ask her what you want in plain language, she proposes the work and its cost, you approve, and she rewrites your product and collection pages. She reads your real search demand, queries ChatGPT and Perplexity for keywords and competitor intelligence in your niche, and every change she makes reverts in one click.

Where can I get Jane?

Jane SEO is live in the Shopify App Store with three plans from $39 a month and a 14-day free trial on all of them. Details at the Jane SEO page.

Related Reading

• I Built a Shopify App Alone in Four Weeks. The Idea Took Three Months.
• AI Agents Just Went Mainstream. What It Means for Your Store.
• AI Commerce Is Live on Shopify. 33% of Stores Haven't Even Started.