The site we made together does exactly what it was scoped to do — show forty products beautifully and bring in enquiries. Selling online is a different machine, and search has moved a long way since we built it. Here's what that means, and what we'd build next.
Each one was scoped separately and each one does its job. What's happened naturally is that they've grown into three islands — and the moment you start selling, that becomes the thing worth solving.
"Three sites, three audiences, three separate starts. Connected properly, each one should be making the other two rank."
The current site was scoped to present products and collect enquiries, and it's solid at that — clean heading structure, RankMath in place, Cloudflare in front, sitemaps generating. Selling online asks for a different set of foundations, and search itself has changed since we built it. Here's the gap, and how quickly each part closes.
| The gap | What closing it gives you | Effort | |
|---|---|---|---|
| 01 | Products aren't marked up as products The 40 pages present beautifully, but they're structured as content pages rather than commerce listings. |
Marked up properly, those same 40 pages become 40 entries Google can display as products — with images and detail — and that AI assistants can cite when someone asks for a pastry supplier. The pages already exist; this is structure, not new work. | Quick win |
| 02 | The content engine was never switched on A blog was never part of the original scope. |
This is the biggest untapped surface you own. Every search that isn't your brand name — "wholesale conchas", "guava danish supplier" — needs a page behind it. Starting it is the compounding piece. | Ongoing |
| 03 | Page titles are written for a brochure e.g. "Guava Cheese Danish - Got Pastry" |
Right for a catalogue. For a shop you want category and buying intent in there — "wholesale", "bulk", the format. Rewriting the set is roughly a day. | Quick win |
| 04 | Pack shots are catalogue-weight 145–426 KB PNGs, sized for one product on a page. |
Fine for a product page, heavy for a 12-product shop grid on mobile data. Converting the set to modern formats is mechanical and cuts the weight dramatically. | In the build |
| 05 | Page-builder overhead 35 stylesheets and 21 scripts load on the homepage. |
That's the cost of a builder your team can edit by hand — a fair trade for a brochure. A storefront can't carry it: every hundred milliseconds shows up in conversion. This is the core reason to rebuild the shop on a different footing. | In the build |
| 06 | No Bakery or LocalBusiness markup | Tells Google what kind of company you are, where you ship, and that you supply retailers. Small addition, disproportionate payoff for a food business. | Quick win |
| 07 | Search has moved Structured data and AI-assistant citation weren't ranking factors when this was scoped. |
People increasingly ask an assistant for suppliers and recommendations. Those answers get built from structured, well-written pages. It's new ground for everyone — and it's winnable while your competitors ignore it. | Ongoing |
"Nothing here needs undoing. The catalogue, the photography and the brand are the expensive part, and you already own all three."
We'll go through the new Shopify storefront together on screen: template fit against your brand, product page structure, mobile experience, checkout flow, and what carries over versus what gets rebuilt. Nothing here needs throwing away — the photography and the catalogue are the expensive part, and you already own both.
We'd rebuild the shop on Astro — a modern static framework. Pages are generated ahead of time and served as plain files from a global CDN, so there's no page builder tax, no plugin stack, and nothing to slow down between you and the customer.
Nothing renders on demand and there's no builder overhead to download. Pages arrive pre-built from the edge. Faster sites convert better and rank better — that's the whole trade.
All 40 products ship with proper structured data from day one, so Google and AI assistants can actually read, cite and display your catalogue.
You get a simple admin to add products, edit copy and publish posts. No page builder to fight, no theme to break. Publish, and it's live.
Homepage figures measured live, July 2026. The trade-off is deliberate: a builder buys hand-editing, a static build buys speed. A shop wants speed.
Both are built with your real products and your real photography — nothing here is a placeholder. Click through, then tell us which one feels like Bon Appetit.
Chocolate, cream and butter yellow, with display type set enormous and the pack shots blown up and running off the edge of the page. Warm, confident, a little vintage — the heritage bakery you'd trust on a grocery shelf. Strongest for the wholesale side.
Open concept A →Your existing brand, turned into a shop. Same Windsor headlines in the same red, your real logo, your category colours, the brown band and the cream review cards — all carried straight over from the site you already have, and extended to do the things a storefront needs to do.
Open concept B →"Both share the same shop page — so you can see exactly how the catalogue behaves either way."
A rebuild is a one-off. The reason your competitors show up and you don't is that they've been publishing for years. This is the ongoing piece — and it's where the return actually lives.
Product schema across all 40 SKUs, titles and descriptions rewritten around how buyers actually search, Bakery and Organization markup, and clean internal linking between categories and products. The content already exists — this is structure.
Recipes, pairings, retailer guides, "what is a concha", seasonal features. Every post links back to the products it mentions. This is the surface area you currently don't have.
Dedicated pages for wholesale, foodservice and distribution — the searches that bring a purchase order rather than a single box.
More people are asking assistants for suppliers and recommendations. Those answers are built from structured, well-written pages. Right now there's nothing on the site for them to pull from.
"We're not fixing one storefront — we're connecting three properties into one thing that ranks, and then feeding it every month."
You tell us A or B — or the parts you like from each. We take the winner to a full design of the homepage, shop, product page and wholesale page.
Astro build, all 40 products migrated with proper schema, images converted and compressed, checkout wired up, admin set up so your team can publish without us.
Decide what happens to ba58program.com and the main site, consolidate authority, set up redirects so nothing already ranking gets lost.
Go live, then the search engine starts: content every month, technical upkeep, and a plain-English report showing what moved.
Have a look at both concepts before the call. Whichever way you lean, we'll scope it properly and send a written proposal after we talk.