oleo.ie today is a Shopify storefront with GSAP animations, Cloudflare CDN, Weglot translation, Judge.me reviews, HSTS, HTTP/3. That's a thoughtful stack. Most agencies would say "rip it out and start over". We don't think that. The case for a rebuild is narrow but real: AI-readiness, prescriber-vs-patient navigation, schema-everywhere, and an embedded chat-commerce surface that the current setup can't carry cleanly.
Detected on the live site:
That's a stack someone cared about. The Shopify checkout primitives, payment infrastructure, inventory, app ecosystem (Judge.me, Weglot) all work. We are not pitching against any of that. We are pitching adding a layer on top, with the option to migrate the static surfaces only if the case is clear.
Realistic numbers for content pages (home, conditions, about, MCAP hub). Not for commerce pages, where Shopify checkout is best left alone.
Numbers are realistic ranges based on Astro static sites on Cloudflare Pages vs a typical Shopify Hydrogen build. Actual delta depends on chosen images, fonts, and any third-party scripts retained.
The right shape is not "rebuild everything". It is:
The biggest single argument for the new build is the chatbot Tony has built for ecom: it qualifies, educates, routes prescribers into Module 1, drafts referral messages for patients, and sells the advertisable surfaces (Panacea device, OleoCare onboarding, CPD modules) where legally permitted. Compliant by design. Two-track logic baked in. Available 24/7. Works on the current Shopify too, but it shines when paired with the new architecture and clean schema.
A preview build of the patient-vs-prescriber two-track structure, with condition pillars, MCAP hub, prescriber resources, schema everywhere, founder surfaced, NAP block. Built on Astro principles, embedded below.
Open the file directly: site-preview.html. All placeholders for real photos, NAP, and Panacea regulatory status are clearly marked.
| Path | Built on | Schema |
|---|---|---|
| / | Astro static | Organization + MedicalBusiness + Person |
| /conditions/ms-spasticity, /chemo-induced-nausea, /refractory-epilepsy | Astro static + named clinician review | MedicalWebPage + MedicalCondition |
| /mcap/* (eligibility, application, reimbursement, FAQs) | Astro static + FAQ schema | FAQPage + MedicalProgram |
| /oleocare/for-patients, /for-prescribers | Astro static | MobileApplication + HealthApplication |
| /products/panacea, /panacea-flo, /waterpipe-adaptor | Shopify Storefront API + Astro shell | Product + MedicalDevice (conditional on MDR) |
| /cart, /checkout, /account | Shopify (untouched) | Shopify defaults |
| /for-prescribers | Astro static + gated content | WebPage + Article |
| /for-pharmacies | Astro static (links to Module 5 portal) | WebPage |
| /insights | Astro static + content collection | Blog + Article |
| Site-wide chat | Tony's AI Chat Commerce | n/a |
Skip the static rebuild if: the current Shopify Hydrogen pages pass Lighthouse 80+, schema can be patched in via a Shopify metafield app, and the chatbot can be added as a script tag. That's a defensible "don't fix what isn't broken" call.
Do the static rebuild if: you want full control over schema (you do, for AI citation), the prescriber-vs-patient nav split needs deeper page architecture than the theme allows (it does), and the speed lift from <2s LCP feels worth it for the patient-research demographic (it should). Phased migration so checkout never moves.