Prompts for your AI assistant
A connected assistant already has your real feed data and the same optimization playbooks the app follows. What it does not have is your priorities. A good prompt supplies those, and takes about one line more than a vague one.
What a good prompt says
- Name the part of the feed you want worked on. Titles, descriptions, images and identifiers each have their own playbook.
- Ask it to read the app's guide for that part first. The rules the app follows are the rules you want applied, and Google's generic advice is not the same thing.
- Say which data to use. Search Console query data is what turns a title rewrite into a match for real demand.
- Say how many products to change at once. One at a time suits a careful pass, batches suit a large catalog.
- Ask for the reasoning. You approve every change, so make each one easy to judge.
Work through the whole feed
The broadest starting point. The assistant picks the section costing you the most and works down.
For the Google feed, start with whatever is hurting me most, go one product at a time, and show me each change before you make it.Optimize titles with your search data
Titles decide most of your impressions, and every product needs a different one. The guide line matters here. Without it an assistant writes to generic best practice instead of the rules on the Titles page.
Optimize the titles of my Google feed. Read the app's titles optimization guide first, then use my Google Search Console data for each product. Summarize your reasoning for changes so I can review.Fix what Google is rejecting
Disapprovals cost you every impression the product would have had, so they come before any polish.
Show me the Merchant Center issues affecting the most products. Start with the disapprovals, fix the ones that share a cause, and show me each change before you make it.Find the fields you are missing
Short, and useful before you have decided what to work on.
What fields am I missing?Fix a whole field at once
On a large catalog the fastest fix is usually a rule, not a thousand edits. Ask for the rule and you get one change to approve instead of hundreds.
Most of my products have no product type. Look at a page of them, work out a rule that fills the field from my Shopify data, and show me the rule before you apply it.Check a sample, then fix everything
A survey first, then the work. Good when you do not yet know how bad the feed is.
Let's perfect my Google feed. Review a sample of 10 products to see what data exists, where fields are weak, and what fields are missing. Then, start with the product hurting me the most, going one product at a time and optimize all fields.Check one product
The assistant sees the exact output your feed sends, overrides and market rules included.
Show me exactly what my feed sends Google for my best selling product, and tell me what you would change.What not to ask for
- Changes without review. Every edit needs your approval anyway, and a vague request produces a list you cannot check.
- Tool names. The assistant receives the full tool list when it connects, so plain language works better than jargon.
- A new item id. It is how Google identifies each item and it can never be changed.
- Anything outside your feeds. An assistant cannot touch your products in Shopify, your customers or your orders.
Every change follows a preview then confirm flow. The assistant shows you what it proposes and applies nothing until you approve it.
After the changes
Ask the assistant to run the feed when you are done, then check the counts on the Optimization page have dropped. Google picks the changes up on its next fetch.
Related articles
- What connected AI assistants can do
- Connect AI assistants
- Optimize your Google Shopping feed
- Ask Shopify Sidekick about your feed
Was this page helpful?
Still stuck?
Reach us on the support page or use the support form in the app under Settings. Support hours are 9am to 5pm Monday to Friday, Adelaide time.