FAQ The four questions an independent jeweller actually asks.
If any of these answers needs a follow-up call, reply with two or three 20-minute slots in the next ten days and we will do it on video. No commitment, no upsell.
Why move off WordPress and WooCommerce? The current cart works. +
The shopping cart continues to work. The proposed build is a static Astro frontend (faster, sub-second mobile load, structured-data-first) that hands the cart and checkout back to WooCommerce via the headless WooCommerce API. Nothing the staff currently use in WordPress admin (product listings, stock, orders) changes. The visible site, the SEO, the schema and the speed change. The cart, the orders and the payment flow stay on the WooCommerce engine you already know.
The Cloudflare email obfuscation was meant to stop spam. If you replace it with plain text, will the inbox flood? +
In practice no. The Cloudflare cf_email cipher was an effective spam reducer in 2014 when most spam came from naive crawlers. Modern spam-bot scrapers either run real Chromium and decode the cipher anyway, or hit your contact form directly. The proposed build uses a plain `mailto:` link, a honey-pot field on the contact form (a hidden input only bots fill in), and the Vercel-side rate-limiter on form submits. Net result: the inbox is no noisier than it is today, AI search and directory crawlers can now read the address, and customers without JavaScript see a working email link instead of the literal string "[email protected]".
How do you handle the Daisy Collection page without spoiling the in-person discovery moment? +
The page does not aim to replace the in-store experience. It explains where the Daisy Collection is designed and made (Bath), shows the current range with prices, and gives the customer enough confidence to order online with bicycle delivery within Bath, or to walk in knowing what they want to see. A "bespoke commission" enquiry form on the page invites longer conversations for engagement-style or anniversary pieces. The in-store discovery moment is for visitors who walk Union Passage; the online page is for everyone else.
I have heard "schema markup" pitched before by SEO consultants and it sounded like vapourware. What is the concrete difference? +
Schema markup is a small block of structured JSON in the HTML of each page that tells Google, Bing and AI assistants what kind of business this is, where it sits on a map, what hours it keeps, and how it is rated. Without it Google has to guess from prose. With it Google can confidently show the shop's opening hours, address, phone and review stars directly in the search result, and AI assistants can quote the founding year (1952) and the address (25 Union Passage) without paraphrasing. The proposed JewelryStore + Service + FAQPage + AggregateRating block is roughly 60 lines of JSON, generated automatically at build time, and validates clean against schema.org and Google's Rich Results test. The concrete result is the shop appearing on AI search and the Google business card with the data the chain shops cannot fake.