Investigate why my collection pages don't have canonical tags. Find the cause and fix it.
Want more control? See the expanded prompt ›
Investigate why my collection pages don't have canonical tags. Look in theme.liquid, collection.liquid, and related snippets. Explain what's missing and write the fix.
- Reads your actual theme code (not assumptions).
- Identifies root cause, not symptoms.
- Writes the fix as a queued change.
- Documents the explanation for your team.
What you're trying to do
Most theme issues are symptoms of a root cause buried in the theme code — a missing snippet, a misconfigured section, an app that injected breaking code. Generic theme fixes don't help; you need someone (or something) to read the actual code and explain. That's what this is for.
Things to watch out for
- Code reading: Fudge reads your actual Liquid, JS, and CSS. Not generic guidance.
- Root cause: not 'add this line' but 'here's why this was missing'.
- Fix queue: changes are queued for your approval, not auto-deployed.
- Documentation: Fudge writes notes your developer can reference later.
How Fudge does it
Fudge duplicates your live theme into a draft, makes the targeted edit (Liquid logic, JS event, conditional rendering) your prompt requires, and tests it on the draft preview. Everything starts in draft — review the diff, verify the behavior, and publish when you're ready. Your live store stays untouched.
When a theme code investigation makes sense
Theme code investigations diagnose specific functional problems — “why don’t my collection pages have canonical tags,” “why is the cart drawer broken on mobile,” “what’s making the hero load slowly.” Fudge reads the actual theme code, traces the cause, and writes the fix.
When to run this investigation
Run the investigation when you have a specific symptom you can’t explain. Generic “audit my theme” doesn’t have an outcome; specific problems have specific causes.
The investigation is also the right call when developers told you it would be a multi-day project. Often the actual fix is a one-line change Fudge can identify and draft for you.
What makes a great investigation
- Specific problem statement — “Collection pages missing canonical tags” or “Cart drawer doesn’t open on iPhone 14 Pro.” Specific, observable, reproducible.
- Reads actual theme code — theme.liquid, snippets, sections. Traces the cause across files.
- Explains what’s missing or broken — the cause, not just the symptom.
- Writes the fix — actual patch, ready to apply.
- Tests the fix on draft theme — before recommending you ship.
Common mistakes to avoid
The biggest mistake is investigating without a clear question. “Look at my theme” doesn’t have an answer; “Why don’t my collection pages have canonical tags” does.
The second mistake is fixing without testing. Theme changes can have unexpected side effects. Always test on the draft theme first.
Pair this with canonical tag audit and fix and core web vitals audit — three complementary tools for technical theme work.
Fudge does this work with its store editor.