The 8-Week AI SEO Starter Plan for Shopify Stores

← Back to the AI SEO Guide

The biggest mistake Shopify merchants make with AI SEO is trying to do everything at once. Schema, llms.txt, FAQ rewrites, comparison pages, entity SEO, robots.txt, citable snippets — the full list is overwhelming if you approach it as a single project.

This plan sequences the work correctly. Each phase builds on the last. By week 8 you have a measurable AI SEO foundation; by week 16 (if you run a second cycle) you have a compounding system.

The 8-week overview

Week	Phase	Core deliverable	Est. hours
1	Schema audit	Identify schema gaps across top 10 pages	3–4 h
2	Schema + robots.txt install	FAQPage, Product, Article schema live; robots.txt verified	4–6 h
3	FAQ pages	3 FAQ pages on top product pages with FAQPage schema	4–5 h
4	Comparison page	One “X vs Y” comparison page, fully structured	3–4 h
5	llms.txt	llms.txt file live at domain root	2–3 h
6	Entity signals	Wikidata + Crunchbase entries; author schema on blog posts	3–4 h
7	Measurement setup	AI source attribution dashboard live	2–3 h
8	Iterate	Prioritize next cycle based on citation data	2–3 h

Total time investment: approximately 23–32 hours over 8 weeks, roughly 3–4 hours per week. This is a realistic scope for a solo merchant or a small team without a dedicated SEO.

Weeks 1–2: Schema and robots.txt foundation

Week 1: audit

Before writing a line of schema, audit what you have. Many Shopify themes ship with partial schema — usually Product schema but not FAQPage or Article. Overlapping or conflicting schema is worse than no schema.

The week 1 audit checklist:

1. Run 3 pages through Google’s Rich Results Test: your top product page, top blog post, and homepage.
2. Check each result: is Product schema present and complete (price, availability, reviews)? Is Article schema on blog posts? Is FAQPage schema anywhere?
3. Check robots.txt at yourdomain.com/robots.txt. Confirm GPTBot, PerplexityBot, ClaudeBot, and Google-Extended are allowed (no Disallow: / rule that catches them).
4. List every page type that is missing schema: product pages, blog posts, collection pages, comparison pages.

The output of week 1 is a simple gap list: which schema types are missing on which page templates. That drives all of week 2.

Week 2: install

Install schema in priority order:

Schema type	Page template	Priority	Why
FAQPage	Product pages + top blog posts	Highest	Single highest-citation-rate schema type
Product	All product pages	High	Required for commerce citations in ChatGPT Shopping + Perplexity
Article	All blog posts + guides	High	Establishes authorship and dateModified — required for long-form citations
ItemList	Collection pages, comparison pages	Medium	Drives “best of” citations

On Shopify: JSON-LD is the recommended format. Inject it via the content_for_header hook in theme.liquid, or use a metafield-based approach. Avoid Microdata (inline HTML attributes) — it’s harder to maintain and doesn’t give AI engines cleaner signals than JSON-LD.

Validate every template after installation, not just one sample page. A schema bug in a template will affect every page built from it.

Fix robots.txt: add explicit Allow: / lines for all four AI crawlers (GPTBot, PerplexityBot, ClaudeBot, Google-Extended) if they’re not already present.

Inxy note: Inxy automates the entire week 1–2 workflow — it audits schema gaps across your full catalog, installs FAQPage + Product + Article + ItemList schema via the Shopify Admin API (no theme editing), and verifies robots.txt allows all major AI crawlers. What takes a solo merchant 7–10 hours manually takes about 20 minutes with Inxy.

Weeks 3–4: FAQ pages and first comparison page

Week 3: FAQ pages

Three FAQ pages done well produce more AI citations than most other content investments of the same time. The goal is not to stuff FAQs onto existing pages — it’s to build standalone, schema-rich FAQ sections that answer the real questions your customers ask.

Finding the right questions:

Source	What you get
Google Search Console	Actual queries that landed customers on your site
Google “People Also Ask” boxes	Exact user phrasing for your top queries
Customer support tickets	Post-purchase questions and pre-purchase objections
Product page reviews	What customers actually cared about
ChatGPT prompt	”What are the 10 most common questions about [your product category]?”

The FAQ structure AI engines reward:

• Question is exactly what a real user would type
• First sentence of the answer is the direct answer — no preamble
• Answer includes at least one specific fact, number, or comparison
• Answer length: 60–100 words
• Visible content matches the FAQPage schema exactly

Week 3 deliverable: FAQPage schema live on your top 3 product pages, with 4–6 questions each. Validate with Google’s Rich Results Test before moving on.

Week 4: first comparison page

Comparison pages are the highest-ROI single content asset in AI SEO. The “X vs Y” structure is pre-extracted by design — AI engines copy the comparison table directly into their answers. One well-built comparison page can generate more citations than 10 standard blog posts.

The seven elements every comparison page needs:

1. <h1> containing both names and the word “vs”
2. A 60-word TL;DR verdict at the top (this is the citable snippet AI engines lift)
3. Side-by-side table with at least 5 criteria
4. One image per option with descriptive alt text
5. A “Best for” verdict for each option
6. FAQ block with FAQPage schema (4–6 questions)
7. Internal links to relevant product pages

Which comparison to build first: pick the comparison your customers actually make. If you sell standing desks, that’s probably “standing desk vs traditional desk.” If you sell moissanite jewelry, that’s “moissanite vs diamond.” The right comparison is the one where customers already ask the question — not the one you want to win.

Important: balanced framing. AI engines downweight comparison pages that read as marketing pitches. Include honest assessments of both options — including legitimate strengths of the competitor. Balanced pages get cited more often because the engine trusts they are informational.

Weeks 5–6: llms.txt and entity signals

Week 5: publish llms.txt

llms.txt is the new robots.txt for AI crawlers — a structured plain-text file at yourdomain.com/llms.txt that gives AI engines a curated summary of your site and its priority pages.

Why it matters: AI crawlers have a token budget. A 200-line llms.txt is more useful to them than a 50,000-URL sitemap because it tells them which pages matter and why, in plain language they can act on.

A minimal llms.txt structure:

# [Your Brand Name]

[One paragraph brand description: what you sell, who you serve, what makes you different.]

## Priority pages

### Products
- /products/[top-product-1]: [one-sentence description]
- /products/[top-product-2]: [one-sentence description]

### Guides
- /blogs/guides/[top-guide-1]: [one-sentence description]
- /blogs/guides/[top-guide-2]: [one-sentence description]

### About
- /pages/about: [one-sentence description]

Keep it under 200 lines. Update it whenever you add a new cornerstone product page or guide. The llms.txt Complete Guide has vertical-specific templates.

Week 6: entity signals

Entity signals are what make AI engines refer to your brand by name rather than just by URL. The goal is getting your brand recognized as a named entity in Wikidata and Crunchbase — the two sources AI engines use most heavily for entity resolution.

The entity signal checklist:

1. Wikidata — check if your brand has an entry at wikidata.org. If not, create one (it’s a public wiki, anyone can add entries). Include: official website, founding date, founder names, product category.
2. Crunchbase — claim or create your company profile at crunchbase.com. Add funding, team members, website, product description.
3. Author schema — add author and @id fields to your Article schema so AI engines can resolve the author as a named entity, not just a string.

Inxy note: Entity SEO is a slow signal — Wikidata and Crunchbase entries typically take 30–60 days to propagate into AI engine knowledge bases. Week 6 is the right time to start because the compounding begins while you build everything else. Wikipedia is harder (requires independent press coverage for notability) and is a later-stage play for most Shopify merchants.

Weeks 7–8: measure and iterate

Week 7: set up AI source attribution

You cannot optimize what you cannot measure. By week 7, you should have enough schema and content live to start seeing first AI citations. Set up the measurement system now so you can track what’s working.

The three metrics that matter:

Metric	What it measures	Where to find it
AI source revenue	Dollar share of monthly revenue from AI referrers	Shopify Analytics → Referrers filter
Citation referrer volume	Sessions from chat.openai.com, perplexity.ai, claude.ai, gemini.google.com	Google Analytics → Acquisition → Traffic acquisition
AI Overviews impressions	How often your pages appear in AI Overviews	Google Search Console → Search results → Filter by “AI Overviews”

For a full measurement setup guide, see AI Search Attribution.

Week 8: prioritize the next cycle

By week 8 you have 6 weeks of citation data from the schema and content work. Use it to prioritize:

• Which pages are getting cited? — expand that pattern to similar pages
• Which pages rank in Google’s top 10 but have zero AI citations? — those pages likely have schema or snippet issues
• Which AI platforms are sending traffic? — double down on the platform already working
• Which comparison or FAQ pages got cited? — build more like them

The second 8-week cycle should be faster than the first. The audit and foundation work (weeks 1–2) doesn’t need to be repeated — only maintained. Weeks 3–8 can be replaced with higher-volume content and entity work.

What to skip if you’re short on time

If 8 weeks is too long, compress to the highest-ROI subset:

Minimum viable AI SEO (4 days):

1. Fix robots.txt (1 hour)
2. Install FAQPage schema on top 5 product pages (3–4 hours)
3. Add one citable snippet (60–80 words, stat-anchored) as the first paragraph under every H2 on top 5 pages (2–3 hours)
4. Publish one comparison page (3–4 hours)

This four-day version gets you to first citations without the full 8-week commitment. Add llms.txt and entity signals later.

FAQ

Can I do this without a developer?

Weeks 3–4 (content) and week 5 (llms.txt) require no developer. Weeks 1–2 (schema installation) typically require either a developer or a tool that handles Shopify schema injection. Inxy’s Admin API installer handles weeks 1–2 without touching theme code. Weeks 6–7 (entity signals and analytics) require no developer.

What if my store is brand new (< 6 months old)?

Run the plan in the same order, but expect slower results from AI Overviews (which is heavily dependent on Google organic ranking). New stores often see first citations from Perplexity and ChatGPT before Google AI Overviews, because those platforms have weaker organic-rank dependencies. See The 2026 AI Search Landscape for platform-specific timelines.

How many FAQ pages should I have by week 8?

At minimum: 3 FAQ-enriched product pages and 1 FAQ-enriched comparison page. A realistic target after 8 weeks is 5–8 pages with FAQPage schema installed and validated. Quality matters more than quantity — 5 well-structured FAQ pages outperform 20 poorly structured ones.

Should I update old blog posts or write new ones?

Both, but updating outperforms creating for AI SEO purposes. An existing page that already ranks in Google’s top 20 and gets FAQPage schema plus citable snippets added will generate citations faster than a new page starting from zero ranking authority. Prioritize updating your top-ranking content before writing new articles.

How do I know if my FAQPage schema is working?

Two signals: (1) Google’s Rich Results Test shows a valid FAQ result for the page, and (2) within 2–4 weeks of publication, you see citation referrer traffic from AI engines for queries that match the FAQ questions. If you see valid schema but no citations after 4 weeks, the FAQ questions may not match real user queries — revisit the question sourcing step.

What’s next

This plan is the implementation layer. For the underlying concepts:

• What Is AI SEO? — the definition and why it differs from traditional SEO
• AEO Explained: The 7 Levers — the full operational breakdown of every tactic in this plan
• The 2026 AI Search Landscape — which platforms to prioritize for your store

Inxy.ai automates weeks 1–2 of this plan — schema audit, schema installation across your full catalog, and robots.txt verification — without touching your theme. It also runs the week 7 measurement setup automatically and tracks AI citation share weekly. Connect Shopify + GSC + GA4 and see your first AI revenue report in 5 minutes. Start free →