Docs / for Shopify / Every screen
AEO Ultimate for Shopify
Every screen, and when you’d open it
The app has around twenty screens. You will use four of them regularly and the rest when something specific needs fixing. This page says which is which.
Start here
Home is the state of the store at a glance — what is publishing, what is missing, what changed. Learn explains the concepts if answer-engine optimisation is new to you; it is worth ten minutes before you start changing settings.
Settings holds your API keys and connections. Plans shows which tier you are on and what each unlocks.
Finding what is wrong
Audit is the screen you will use most. Paste a product page’s source and it reports what an answer engine can and cannot read from it. Use View Page Source, not Inspect Element — see Troubleshooting for why that distinction decides whether the audit works.
Health looks across the store rather than at one page. Results keeps what previous runs found so you can see whether a change helped.
Uniqueness checks whether your product copy says anything a thousand other stores selling the same item do not. This matters more for AI answers than for classic SEO: an engine choosing one merchant to name has no reason to pick the store whose description is the manufacturer’s boilerplate.
What gets published
Schema is the core: connected structured data for products, collections and pages. Meta generates titles and descriptions; Social handles Open Graph and card metadata.
Organization is your store’s identity — who you are, as an entity an engine can resolve rather than a name in a footer. E-E-A-T covers the experience and expertise signals that make a claim credible. Trust covers the signals a shopper checks before buying: policies, contact routes, returns.
FAQs and Reviews publish question-and-answer content and rating data as structured markup. Blog generates posts grounded in real citations rather than invented filler.
Worth knowing
Schema has to be in the HTML Shopify delivers. Anything injected later by JavaScript — including through a tag manager — is invisible to crawlers that do not run scripts, which includes several AI crawlers.
Getting found and staying found
IndexNow tells search engines a page changed rather than waiting for a recrawl. It reports failures by status code — 400, 403, 422 and 429 each mean something different and each has its own fix.
Redirects sends dead URLs somewhere useful instead of a 404. Search Console and Google Merchant Center connect your existing Google accounts so the app can compare what you publish against what Google actually has.
Crawlers controls which bots may read the store and how often, and edits the robots.txt template in your published theme. If you have no published theme, that control cannot work — Shopify generates robots.txt from the live theme, so there has to be one.
Measuring whether it worked
Visibility asks the answer engines your customers’ questions and records whether you were cited, named or absent.
This is the only screen that measures the actual goal. A crawler log proves a bot fetched your pages; it cannot prove any of them were used in an answer. Asking the engine directly is the difference between activity and outcome.
Blueprint turns all of the above into an ordered plan, so you are not deciding what to fix first from a list of everything.
A sensible first week
01
Fill in Organization and Trust. Everything downstream refers back to your identity, so getting it wrong once costs you twice.
02
Run Audit on your best-selling product. Fix what it finds there before touching the whole catalogue.
03
Connect Search Console and Merchant Center. Several screens can only tell you useful things once they can see real data.
04
Run Visibility once now, before changing much else. Without a baseline you cannot tell later whether anything improved.
Still stuck?
Message me directly — free tier included. Most replies land within the hour during Tampa working hours. Get support →