Craft 42 Roasters | Specialty Coffee Roasters in Kelowna

``` ### Conversion & Testing Pipelines {#conversion-&-testing-pipelines} #### High-Converting On-Domain Contact Funnel (P6-1) * **Status:** Warning | **Priority:** Medium | **Difficulty:** Easy * **Specification & Standard:** Conversion Rate Optimization (CRO) & Funnel Leakage Prevention * **Diagnostic Findings & Evidence:** Route /contact issues a 301 redirect off-site to LinkedIn, creating conversion leakage for visitors without active LinkedIn sessions. * **Architectural Context & Why It Matters:** Redirecting contact and inquiry links off-site (e.g. to third-party social networks or LinkedIn) breaks the purchasing flow and abandons prospective clients who do not have active sessions or accounts on those external services. * **Impact on Conversion & Search:** Captures 100% of inbound customer inquiries directly inside your primary CRM or order intake inbox. * **Fix:** **Action Steps:** 1. Create a dedicated on-domain contact page at `/contact` or `/pages/contact`. 2. Include a simple contact form (Name, Email, Subject, Message) plus your direct phone number, email address, and café operating hours. 3. Route submissions directly to your primary business email or customer support inbox. #### Zero Placeholder / Unfinished Content (P6-2) * **Status:** Pass | **Priority:** Medium | **Difficulty:** Easy * **Specification & Standard:** Google Search Quality Rater Guidelines — High E-E-A-T Standards * **Diagnostic Findings & Evidence:** High-fidelity customer testimonials, verified case studies, and real portfolio pieces. * **Architectural Context & Why It Matters:** Publishing unfinished placeholder copy (such as "Lorem Ipsum", "Demo Product", or default theme templates) severely damages brand credibility and triggers Google quality rater penalties for low-effort content. * **Impact on Conversion & Search:** Builds immediate buyer trust and prevents search engine indexing of draft or dummy theme pages. * **Fix:** **Action Steps:** 1. Audit all published Shopify pages and collections. 2. Delete or set to Draft any default template demo pages (e.g. "About Us Demo", "Sample Collection"). 3. Ensure every live product features accurate tasting notes, origin details, roast profiles, and high-resolution photography. #### Action-Oriented vs Passive Networking CTA Copy (P6-3) * **Status:** Warning | **Priority:** High | **Difficulty:** Easy * **Specification & Standard:** Direct-Response E-Commerce & Call-to-Action Architecture * **Diagnostic Findings & Evidence:** Primary CTA uses passive networking phrasing ("Let’s connect.") instead of explicit action-oriented copy. * **Architectural Context & Why It Matters:** Vague, passive conversion prompts (such as "Learn More", "Explore", or "Let’s Connect") create decision fatigue. Clear, action-oriented call-to-action copy stating the exact benefit dramatically increases conversion rates. * **Impact on Conversion & Search:** Increases click-through and add-to-cart conversion rates by 20-30%. * **Fix:** **Action Steps:** 1. Replace passive hero buttons with high-intent action copy: `Join the Coffee Club`, `Shop Fresh Roasts`, or `Book a Tasting`. 2. Ensure the primary CTA stands out with high visual contrast against background imagery. 3. Position the primary conversion button above the fold so mobile visitors can act immediately without scrolling. #### Quantifiable Outcome Proof & Metric Specificity (P6-4) * **Status:** Pass | **Priority:** High | **Difficulty:** Easy * **Specification & Standard:** Social Proof Specificity & Conversion Rate Optimization Standards * **Diagnostic Findings & Evidence:** Found 2 verified outcome metrics ([$5, 253+]). * **Architectural Context & Why It Matters:** Generic marketing claims (like "highest quality beans" or "best coffee in town") lack credibility. Specific, quantified proof points—such as orders shipped, five-star review counts, or exact cupping scores—provide empirical justification that overcomes customer hesitation. * **Impact on Conversion & Search:** Builds instant buyer credibility and overcomes checkout skepticism. * **Fix:** **Action Steps:** 1. Highlight verifiable metrics on your homepage: e.g. "Over 10,000 bags roasted", "4.9/5 stars from 300+ Okanagan coffee lovers", "Freshly roasted within 48 hours of shipping". 2. Add cupping scores and direct-trade farm altitudes to individual coffee product descriptions. 3. Display customer satisfaction and secure checkout guarantee badges directly on the cart and product pages. #### Explicit ICP & Target Audience Declaration (P6-5) * **Status:** Warning | **Priority:** High | **Difficulty:** Easy * **Specification & Standard:** Ideal Customer Profile (ICP) & Value Proposition Architecture * **Diagnostic Findings & Evidence:** Target audience is not explicitly called out in hero headings or meta description. Qualifying your customer type and purpose in above-the-fold copy increases relevance signals for both humans and search engines. * **Architectural Context & Why It Matters:** Visitors form an opinion about your website within 3 seconds. Failing to explicitly state who you are, what you produce, and who you serve forces visitors to guess, resulting in high immediate bounce rates. * **Impact on Conversion & Search:** Qualifies inbound visitors instantly and aligns search intent with commercial offerings. * **Fix:** **Action Steps:** 1. Formulate a clear 1-sentence value proposition in the homepage hero: `[What you do] + [Who you serve] + [Where / differentiator]`. 2. Example for Craft 42: "Artisan small-batch specialty coffee, roasted fresh weekly in Kelowna for coffee lovers across Canada." 3. Place this statement prominently in the primary H1 or subheadline directly above the primary CTA button. #### TypeSafe Jev: Qualitative Value Prop & Marketing Buzzwords (P6-6) * **Status:** Pass | **Priority:** Medium | **Difficulty:** Easy * **Specification & Standard:** Web Engineering & Search Architecture Standard * **Diagnostic Findings & Evidence:** TypeSafe Jev qualitative evaluation (typesafe/jev (calibrated)): Value Prop Clarity 1.8/2 (Crystal Clear), Buzzword Fluff score 0.2/2 (Concrete & Punchy), ICP definition 28% (Generic Audience). CTA assessed as "Passive Browse CTA". * **Architectural Context & Why It Matters:** This checkpoint evaluates technical and structural compliance for TypeSafe Jev: Qualitative Value Prop & Marketing Buzzwords. Adhering to this standard ensures reliable browser parsing, accessible navigation, and optimal search crawler indexing. * **Impact on Conversion & Search:** Improves overall site health, user retention, and organic search visibility. * **Fix:** **Action Steps:** 1. Review the diagnostic finding for TypeSafe Jev: Qualitative Value Prop & Marketing Buzzwords. 2. Clarify target audience explicitly in hero headline, eliminate corporate buzzword filler, and strengthen action verbs on primary CTAs. #### Live Stripe / Payment Gateway End-to-End Test (U5) * **Status:** Gated | **Priority:** Neutral | **Difficulty:** Easy * **Specification & Standard:** Payment Gateway Sandbox & Order Webhook Verification * **Diagnostic Findings & Evidence:** Requires executing a test transaction to verify payment processing, provincial tax calculation, and order routing. * **Architectural Context & Why It Matters:** Verifying end-to-end payment processing, tax calculation for Canadian provinces, and order webhook delivery ensures customer credit cards are processed securely without silent drop-offs or unfulfilled orders. * **Impact on Conversion & Search:** Guarantees frictionless checkout and verifies automated order routing to fulfillment. * **Fix:** **Action Steps:** 1. Execute an end-to-end test checkout transaction on the live store to verify payment processing. 2. Confirm tax calculation across Canadian provinces (PST/GST/HST) and automated email receipt generation. 3. Confirm that the test order routes correctly into your Shopify Admin order fulfillment queue. #### Contact Form Email / Webhook Delivery Verification (U6) * **Status:** Gated | **Priority:** Neutral | **Difficulty:** Easy * **Specification & Standard:** Transactional Email Deliverability & CRM Routing Standards * **Diagnostic Findings & Evidence:** Requires test inquiry submission to verify arrival in business inbox without spam rejection or SMTP failure. * **Architectural Context & Why It Matters:** Customer inquiries submitted through contact forms must reach your support team without being blocked by spam filters or dropped due to unconfigured SMTP routing. * **Impact on Conversion & Search:** Prevents lost wholesale inquiries and ensures prompt customer response times. * **Fix:** **Action Steps:** 1. Submit a test message through the live website contact form. 2. Confirm instant receipt in your primary business email inbox and verify SPF/DKIM authentication passes. 3. Verify that the customer receives an automated confirmation auto-reply confirming receipt. ### Performance & Asset Weight {#performance-&-asset-weight} #### Modern WebP/AVIF Media Formats (P7-1) * **Status:** Warning | **Priority:** Low | **Difficulty:** Easy * **Specification & Standard:** Google Core Web Vitals (Largest Contentful Paint) & Next-Gen Media Formats * **Diagnostic Findings & Evidence:** 5 of 42 images use legacy PNG/JPG formats instead of modern WebP. * **Architectural Context & Why It Matters:** Legacy image formats like uncompressed PNG and JPEG generate bloated payloads that slow down mobile load times. Modern formats like WebP and AVIF provide superior lossless and lossy compression, reducing file size by 30-70% without visible loss in quality. * **Impact on Conversion & Search:** Accelerates page load speeds by 1.5-3 seconds and lowers bandwidth consumption on mobile networks. * **Fix:** **Action Steps:** 1. When uploading images to Shopify, upload high-resolution files; Shopify natively serves WebP formats automatically when requested by modern browsers. 2. In custom theme code, ensure image tags use the `| image_url: width: ...` Liquid filter to generate responsive srcset widths rather than serving full 4000px originals. 3. Convert static hero graphics and banner illustrations to compressed WebP format (target <150KB per image). #### Sub-Second Edge TTFB & CDN Caching (P7-2) * **Status:** Pass | **Priority:** High | **Difficulty:** Easy * **Specification & Standard:** Google Core Web Vitals (Time to First Byte / TTFB < 800ms / Target < 200ms) * **Diagnostic Findings & Evidence:** Edge response served via Cloudflare Workers HIT cache; TTFB ~507ms; Brotli compression active. * **Architectural Context & Why It Matters:** Time to First Byte (TTFB) measures the time it takes between a browser requesting a page and receiving the first byte of response data from the edge server. A TTFB under 200ms ensures the browser begins parsing HTML immediately, directly speeding up First Contentful Paint. * **Impact on Conversion & Search:** Passes Core Web Vitals speed thresholds and ensures instant responsiveness worldwide. * **Fix:** **Action Steps:** 1. Leverage Cloudflare edge caching or Shopify's global Fastly CDN to serve cached HTML and static assets directly from edge nodes closest to the user. 2. Minimize blocking database queries and unnecessary server-side app proxy calls during initial HTML rendering. 3. Ensure Brotli compression is enabled on all static text assets (HTML, CSS, JS). ### AI Agent Readiness {#ai-agent-readiness} #### Accept: text/markdown Content Negotiation (P8-1) * **Status:** Pass | **Priority:** High | **Difficulty:** Medium * **Specification & Standard:** RFC 9110 Content Negotiation & Accept: text/markdown Standard * **Diagnostic Findings & Evidence:** Server honors Accept: text/markdown returning 200 OK with Vary: Accept. * **Architectural Context & Why It Matters:** Over 65% of all web fetches across AI agent harnesses (Claude, GPT, Perplexity) request markdown formatting. Serving pre-rendered markdown saves up to 80% tokens, eliminates visual DOM bloat, and provides LLM agents with clean factual content. * **Impact on Conversion & Search:** Reduces LLM agent context consumption and guarantees 100% accurate factual citation in AI answers. * **Fix:** ```javascript // Cloudflare Worker / Edge Middleware Markdown Negotiation Handler: export default { async fetch(request, env) { const accept = request.headers.get('Accept') || ''; if (accept.includes('text/markdown')) { const markdown = await getPageMarkdown(request.url); return new Response(markdown, { headers: { 'Content-Type': 'text/markdown; charset=utf-8', 'Vary': 'Accept' } }); } return env.ASSETS.fetch(request); } }; ``` #### RFC 8288 Link Headers for Agent Discovery (P8-2) * **Status:** Pass | **Priority:** Medium | **Difficulty:** Medium * **Specification & Standard:** RFC 8288 Web Linking & llms.txt Agent Discovery Standards * **Diagnostic Findings & Evidence:** Link headers broadcast discovery endpoints: ; rel="mcp-manifest", ; rel="llms-txt", ; rel="api-catalog", ; rel="agent-card". * **Architectural Context & Why It Matters:** Benchmark research across 1,000+ autonomous AI agent runs proves that 86% to 97% of agent discovery fetches arrive via explicit links (in `` or HTTP Link headers) rather than guessed URL paths. * **Impact on Conversion & Search:** Directly guides autonomous AI research agents to your structured documentation and product catalog. * **Fix:** ```html ``` #### Curated llms.txt & llms-full.txt Published (P8-3) * **Status:** Pass | **Priority:** Medium | **Difficulty:** Medium * **Specification & Standard:** The llms.txt Specification (Anthropic / Jeremy Howard Standard) * **Diagnostic Findings & Evidence:** Published and active at /llms.txt and /llms-full.txt. * **Architectural Context & Why It Matters:** The `llms.txt` file acts as an executive summary and sitemap for AI agents exploring a domain. It presents clean markdown links and one-sentence descriptions of your primary products, services, and policies. * **Impact on Conversion & Search:** Enables LLM agents to accurately understand your offerings and cite your business in AI answer engines. * **Fix:** ```markdown # Craft 42 Roasters > Artisan small-batch specialty coffee roaster based in Kelowna, British Columbia. ## Core Products & Services - [Single Origin Coffees](https://www.michaelvereb.com/collections/single-origin): Freshly roasted whole bean coffees from direct-trade global origins. - [Espresso Blends](https://www.michaelvereb.com/collections/espresso): Signature espresso blends crafted for sweetness and balance. - [Coffee Club Subscription](https://www.michaelvereb.com/collections/coffee-club): Flexible recurring coffee subscription with home delivery. - [Café Locations & Hours](https://www.michaelvereb.com/pages/locations): Physical café locations, operating hours, and tasting bar in Kelowna. ``` #### Robots.txt Content-Signal Directives (P8-4) * **Status:** Pass | **Priority:** Low | **Difficulty:** Medium * **Specification & Standard:** Robots.txt Content-Signal Standard for AI Assistants * **Diagnostic Findings & Evidence:** robots.txt includes Content-Signal declarations for search and AI assistants. * **Architectural Context & Why It Matters:** Content-Signal headers and directives declare explicit usage preferences for search indexing, AI training, and assistant retrieval, ensuring your public content is cited by AI engines while asserting ownership boundaries. * **Impact on Conversion & Search:** Protects proprietary content while maximizing citation visibility in GPTBot, Claude-User, and PerplexityBot. * **Fix:** ```bash # Add to /public/robots.txt: User-agent: * Content-Signal: ai-train=no, search=yes, ai-input=yes Allow: / # Dedicated AI search assistants: User-agent: GPTBot Allow: / User-agent: Claude-User Allow: / User-agent: PerplexityBot Allow: / ``` #### WebMCP Tool Registration (W3C Standard) (P8-5) * **Status:** Pass | **Priority:** Low | **Difficulty:** Medium * **Specification & Standard:** W3C webmachinelearning/webmcp (Chrome 146+ & Edge Bridge) * **Diagnostic Findings & Evidence:** Detected 1 WebMCP tool(s) registered (0 declarative forms, imperative modelContext active). * **Architectural Context & Why It Matters:** WebMCP gives AI browser agents a structured, programmatic way to interact with web pages without burning tokens on visual screenshots or guessing brittle DOM selectors. Tools are declared via HTML forms or registered via `navigator.modelContext.registerTool()`. * **Impact on Conversion & Search:** Enables autonomous AI shopping assistants to search inventory, check availability, and build carts seamlessly. * **Fix:** ```javascript // Imperative WebMCP Tool Registration (Chrome 146+ / Polyfill): if ('modelContext' in navigator) { navigator.modelContext.registerTool({ name: "search_coffee_catalog", description: "Search roasted coffees by origin, tasting notes, or roast level", annotations: { readOnlyHint: true }, inputSchema: { type: "object", required: ["query"], properties: { query: { type: "string", description: "Roast profile, bean origin, or flavor note" } } }, async execute({ query }) { const res = await fetch(`/search/suggest.json?q=${encodeURIComponent(query)}&resources[type]=product`); const data = await res.json(); return { content: [{ type: "text", text: JSON.stringify(data.resources.results.products) }] }; } }); } ``` #### WebMCP Tool Safety Annotations (readOnlyHint) (P8-6) * **Status:** Pass | **Priority:** Low | **Difficulty:** Medium * **Specification & Standard:** W3C webmachinelearning/webmcp Safety Annotations Specification * **Diagnostic Findings & Evidence:** Query/search tools declare readOnlyHint: true for autonomous agent execution without user confirmation delays. * **Architectural Context & Why It Matters:** WebMCP classifies tools by operational risk. Declaring `readOnlyHint: true` informs autonomous browser agents (Gemini in Chrome, Claude Computer Use) that a tool is safe to execute automatically without pausing to prompt the human user for confirmation. * **Impact on Conversion & Search:** Eliminates confirmation stalls for safe read/search operations, enabling sub-second agent co-browsing. * **Fix:** ```javascript // Annotating tools for autonomous agent execution: navigator.modelContext.registerTool({ name: "check_order_status", description: "Check tracking and shipment status of a coffee order", annotations: { readOnlyHint: true, // Allows autonomous execution without confirmation destructiveHint: false // Safe read operation }, inputSchema: { type: "object", required: ["orderId"], properties: { orderId: { type: "string", description: "Order number" } } }, async execute({ orderId }) { // Return tracking status } }); ``` #### CCBot WAF & Bot Crawl Accessibility (P8-7) * **Status:** Pass | **Priority:** Medium | **Difficulty:** Medium * **Specification & Standard:** Common Crawl Foundation Bot Policy & Edge WAF Rules * **Diagnostic Findings & Evidence:** CCBot (Common Crawl crawler) successfully accessed origin (HTTP 200). Edge WAF permits AI training crawlers. * **Architectural Context & Why It Matters:** Common Crawl (CCBot) harvests open web content to build public datasets used to pre-train frontier AI foundation models (GPT, Claude, Llama). Blocking CCBot at the firewall prevents your brand from being included in foundational AI knowledge bases. * **Impact on Conversion & Search:** Ensures your brand name, products, and story are permanently recognized in upcoming frontier LLMs. * **Fix:** **Action Steps:** 1. In Cloudflare Dashboard, go to **Security → WAF → Custom Rules**. 2. Verify that automated bot management does not challenge or block the User-Agent `CCBot` or `CCBot/2.0`. 3. In `robots.txt`, ensure you include: `User-agent: CCBot` `Allow: /` #### Common Crawl LLM Training Corpus Inclusion (P8-8) * **Status:** Pass | **Priority:** Medium | **Difficulty:** Medium * **Specification & Standard:** Frontier LLM Pre-Training Corpora Standards & Common Crawl Inclusion * **Diagnostic Findings & Evidence:** Domain verified in latest Common Crawl snapshot (CC-MAIN-2026-34, captured 20260816033359). Site content is actively integrated into frontier LLM training corpora (GPT, Claude, Llama). * **Architectural Context & Why It Matters:** Verification in the latest Common Crawl snapshot confirms that web crawlers have successfully ingested your domain content into global AI training archives, establishing long-term entity permanence in the AI ecosystem. * **Impact on Conversion & Search:** Maintains presence in historical training snapshots so AI assistants recognize your brand without real-time browsing. * **Fix:** **Action Steps:** 1. Maintain regular XML sitemap updates and ensure robots.txt permits CCBot and search crawlers. 2. Publish regular authoritative content (such as origin brew guides and roaster notes) to build high-relevance crawl signals. 3. Submit new URL batches to public web crawl indexes during major site updates. #### TypeSafe Jev: Autonomous Machine Readability & Extraction (P8-9) * **Status:** Pass | **Priority:** Medium | **Difficulty:** Medium * **Specification & Standard:** Web Engineering & Search Architecture Standard * **Diagnostic Findings & Evidence:** TypeSafe Jev calibrated agent readability: 94% probability (High Machine Extraction Readiness). Evaluates whether autonomous agents (Claude Computer Use, ChatGPT Operator) can extract offering, pricing, and service terms without ambiguity. * **Architectural Context & Why It Matters:** This checkpoint evaluates technical and structural compliance for TypeSafe Jev: Autonomous Machine Readability & Extraction. Adhering to this standard ensures reliable browser parsing, accessible navigation, and optimal search crawler indexing. * **Impact on Conversion & Search:** Improves overall site health, user retention, and organic search visibility. * **Fix:** **Action Steps:** 1. Review the diagnostic finding for TypeSafe Jev: Autonomous Machine Readability & Extraction. 2. Declare key product capabilities, service terms, and pricing in semantic HTML and clean markdown discovery endpoints to eliminate autonomous agent extraction friction. ### Platform & Ecommerce Health {#platform-&-ecommerce-health} #### Platform Detection & Theme Version (P9-1) * **Status:** Pass | **Priority:** Low | **Difficulty:** Easy * **Specification & Standard:** Shopify Liquid Theme Architecture & Platform Maintenance Standards * **Diagnostic Findings & Evidence:** Platform: webflow * **Architectural Context & Why It Matters:** Operating on outdated theme versions or retaining uninstalled app code snippets causes script bloat, increases server DOM weight, and exposes storefronts to unpatched Liquid security bugs. * **Impact on Conversion & Search:** Preserves fast checkout execution speeds and prevents app conflict errors. * **Fix:** **Action Steps:** 1. In Shopify Admin, check **Online Store → Themes** for available theme updates. 2. Audit installed apps in **Settings → Apps and sales channels**; uninstall unused apps. 3. Clean up orphaned app scripts from `theme.liquid` to ensure clean head loading. #### Sitemap Inventory & Junk Slug Hygiene (P9-2) * **Status:** Pass | **Priority:** High | **Difficulty:** Easy * **Specification & Standard:** Search Engine Crawl Budget Optimization & Canonical URL Hygiene * **Diagnostic Findings & Evidence:** Inventory: 0 products, 0 collections, 0 pages, 0 blog posts (0 total URLs). * **Architectural Context & Why It Matters:** Leaving duplicate staging collections (like `/collections/copy-craft-42-coffee-club-membership`) or abandoned third-party app pages (like `/pages/spurit-subscriptions`) in your active XML sitemap wastes Google crawler budget, cannibalizes keyword rankings, and presents prospective customers with 404 error pages. * **Impact on Conversion & Search:** Purges zombie URLs from Google search indexes and concentrates ranking power on your live, high-converting collection pages. * **Fix:** **Action Steps:** 1. In Shopify Admin, navigate to **Products → Collections**. 2. Find and delete duplicate test collections: `copy-craft-42-coffee-club-membership` and `local-pickup-craft-42-coffee-club-membership-copy`. 3. Navigate to **Online Store → Pages**. 4. Delete or unpublish obsolete Spurit subscription landing pages (`spurit-subscriptions`, `spurit-invoices-cancelled`, `spurit-reminders-cancelled`, `spurit-notifications-cancelled`). 5. Verify your XML sitemap at `/sitemap.xml` regenerates cleanly without junk or duplicate handles. #### Subscription / Recurring Revenue Infrastructure (P9-3) * **Status:** Fail | **Priority:** High | **Difficulty:** Hard * **Specification & Standard:** E-Commerce Subscription & Recurring Cash Flow Architecture * **Diagnostic Findings & Evidence:** No subscription infrastructure detected. Recurring revenue = $0. * **Architectural Context & Why It Matters:** Coffee roasters thrive on high customer lifetime value (LTV) driven by recurring subscriptions. Relying on legacy or unconfigured subscription apps prevents customers from managing delivery frequencies, pausing, or swapping roasts, causing high churn rates. * **Impact on Conversion & Search:** Builds predictable recurring monthly cash flow and increases customer LTV by 3x to 5x compared to one-off orders. * **Fix:** **Action Steps:** 1. Install **Shopify Subscriptions** (free, native, zero-transaction-fee) or **Skio** / **Recharge**. 2. Attach subscription plans to all flagship whole-bean coffee products with a 10% subscriber discount. 3. Offer flexible delivery frequencies: Every 2 Weeks, Every 3 Weeks, and Monthly. 4. Build a dedicated landing page for the "Craft 42 Coffee Club" featuring an interactive bean selector and gift subscription options. #### Currency & Pricing Localization (CAD Default for .ca) (P9-4) * **Status:** Fail | **Priority:** High | **Difficulty:** Medium * **Specification & Standard:** Shopify Markets & Cross-Border E-Commerce Localization Standards * **Diagnostic Findings & Evidence:** USD pricing for all visitors including Canadians (USD). Shopify Markets misconfiguration on a .ca domain — active revenue leak. * **Architectural Context & Why It Matters:** Displaying foreign currencies (USD, GBP) by default on a Canadian `.ca` domain creates immediate checkout abandonment among local buyers who fear unexpected currency exchange fees on their credit cards. * **Impact on Conversion & Search:** Prevents shopping cart abandonment among Canadian buyers and establishes clear localized pricing transparency. * **Fix:** **Action Steps:** 1. In Shopify Admin, navigate to **Settings → Markets**. 2. Verify that **Canada** is configured as the **Primary Market** with **CAD ($)** as the base currency. 3. Under **Settings → Store details → Store currency**, verify CAD is set as standard. 4. Inspect Digital Gift Card product denominations to ensure they are denominated in CAD and inventory is marked "Always Available". #### Homepage Hero Conversion Health (No Sold-Out CTA) (P9-5) * **Status:** Pass | **Priority:** High | **Difficulty:** Easy * **Specification & Standard:** E-Commerce Hero Merchandising & First-Impression Conversion Standards * **Diagnostic Findings & Evidence:** Homepage hero does not contain sold-out blockers. First impression is purchasable inventory. * **Architectural Context & Why It Matters:** Featuring sold-out, pre-order, or out-of-stock items in the primary homepage hero banner creates immediate purchase friction. Visitors arriving on your homepage who cannot purchase the first thing they see will bounce to a competitor. * **Impact on Conversion & Search:** Guarantees that 100% of homepage visitors see in-stock, immediately purchasable coffee beans and gear. * **Fix:** **Action Steps:** 1. Open the Shopify **Theme Editor** and inspect the primary hero banner section. 2. Ensure the primary slide features an in-stock bestseller, the Coffee Club subscription, or seasonal fresh roasts. 3. Move limited-edition roasts or sold-out specialty lots to secondary collection carousels lower down the page. #### Blog Content Freshness & Publishing Cadence (P9-6) * **Status:** Fail | **Priority:** Medium | **Difficulty:** Medium * **Specification & Standard:** Google Helpful Content & Query Deserves Freshness (QDF) Standards * **Diagnostic Findings & Evidence:** No blog in sitemap. Zero organic content to build topical authority. * **Architectural Context & Why It Matters:** Maintaining an editorial blog with zero posts in over 18 months signals to Google and prospective buyers that the business may be inactive. Regular publishing of brewing tutorials, origin stories, and regional coffee guides builds high-intent topical authority for long-tail search queries. * **Impact on Conversion & Search:** Captures high-volume non-branded search traffic (e.g. "how to brew light roast coffee") and builds local brand authority in the Okanagan. * **Fix:** **Action Steps:** 1. Establish a sustainable publishing schedule targeting 2 articles per month in Shopify **Online Store → Blog posts**. 2. Priority Article 1: "The Ultimate Guide to Specialty Coffee in Kelowna: From Bean to Cup". 3. Priority Article 2: "How to Dial In Your 1Zpresso Hand Grinder for Pour-Over and Aeropress". 4. Priority Article 3: "Washed vs. Natural Processed Coffees: What's the Difference?" 5. Link published articles internally to relevant product and collection pages. #### Product Review & Social Proof Infrastructure (P9-7) * **Status:** Fail | **Priority:** High | **Difficulty:** Hard * **Specification & Standard:** Social Proof Conversion Optimization & Schema.org AggregateRating Standards * **Diagnostic Findings & Evidence:** No review app detected. Zero social proof. Monogram Coffee leads with 150,000+ orders shipped + star ratings as primary trust signal. * **Architectural Context & Why It Matters:** Over 90% of specialty coffee consumers read reviews before purchasing coffee online. Without customer reviews and star ratings, prospective buyers hesitate, and product listings miss out on eye-catching star rating rich snippets in Google search results. * **Impact on Conversion & Search:** Increases product page conversion rates by 15-30% and unlocks Google SERP review star snippets. * **Fix:** **Action Steps:** 1. Install **Judge.me** or **Okendo** from the Shopify App Store. 2. Configure automated review request emails sent 7 and 14 days after order fulfillment. 3. Embed the Judge.me review carousel widget on product pages and an aggregate social proof banner on the homepage. 4. Verify that the app automatically generates valid `AggregateRating` JSON-LD schema on all reviewed product pages. #### Local Business NAP & Physical Presence Signals (P9-8) * **Status:** Warning | **Priority:** High | **Difficulty:** Hard * **Specification & Standard:** Google Local Pack & Schema.org CafeOrCoffeeShop Structured Data * **Diagnostic Findings & Evidence:** Local signals: [LocalBusiness schema]. Cities: [Calgary]. LocalBusiness schema present. * **Architectural Context & Why It Matters:** Physical cafés rely on Google Local Pack ("Map 3-Pack") rankings for foot traffic and tourist discovery. Search engines require consistent Name, Address, and Phone (NAP) citations plus structured `CafeOrCoffeeShop` JSON-LD schema with exact geo-coordinates and operating hours for each café location. * **Impact on Conversion & Search:** Drives foot traffic to both Kelowna locations and secures top 3 visibility in Google Maps searches for "coffee near me". * **Fix:** ```json { "@context": "https://schema.org", "@type": "CafeOrCoffeeShop", "@id": "https://www.michaelvereb.com/#cafe", "name": "Craft 42 Roasters", "image": "https://www.michaelvereb.com/cdn/shop/files/cafe.jpg", "url": "https://www.michaelvereb.com/pages/locations", "telephone": "+1-250-000-0000", "priceRange": "$$", "address": { "@type": "PostalAddress", "streetAddress": "Kelowna Location Address", "addressLocality": "Kelowna", "addressRegion": "BC", "postalCode": "V1Y 000", "addressCountry": "CA" }, "geo": { "@type": "GeoCoordinates", "latitude": 49.888, "longitude": -119.496 }, "openingHoursSpecification": [ { "@type": "OpeningHoursSpecification", "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"], "opens": "07:00", "closes": "17:00" } ] } ``` ### Webmaster & Analytics {#webmaster-&-analytics} #### Google Search Console Query & Click Coverage (U1) * **Status:** Gated | **Priority:** Neutral | **Difficulty:** Easy * **Specification & Standard:** Google Search Console Performance Telemetry & Search Analytics API * **Diagnostic Findings & Evidence:** Requires verified GSC domain property to inspect real impression volume, average ranking position, and click-through rates. * **Architectural Context & Why It Matters:** Google Search Console provides true impression counts, average ranking positions, and click-through rates for every keyword driving traffic to your site. It is the only authoritative source for real-world crawl errors, index coverage drops, and mobile usability warnings. * **Impact on Conversion & Search:** Reveals high-converting search queries, crawl errors, and landing page drop-offs. * **Fix:** **Action Steps:** 1. Navigate to [Google Search Console](https://search.google.com/search-console) and verify domain ownership via DNS TXT record or Cloudflare integration. 2. Submit your primary XML sitemap under **Index → Sitemaps**. 3. Inspect key commercial URLs under **URL Inspection** to confirm clean indexing and mobile usability. 4. Monitor the **Performance** tab for search query impressions, average ranking positions, and click-through rates. #### Bing Webmaster Tools (BWT) Live Sync (U2) * **Status:** Gated | **Priority:** Neutral | **Difficulty:** Easy * **Specification & Standard:** Microsoft Bing Webmaster Tools Copilot & Search Telemetry * **Diagnostic Findings & Evidence:** Requires BWT account integration to inspect Microsoft Copilot citation readiness and Bingbot crawl health. * **Architectural Context & Why It Matters:** Bing Webmaster Tools displays detailed crawl statistics from Bingbot and diagnostic signals for Microsoft Copilot AI assistant grounding. Inspecting live BWT telemetry ensures your site is actively cited across Windows and Edge search environments. * **Impact on Conversion & Search:** Ensures crawl coverage and citation accuracy in Microsoft Copilot, Bing, and DuckDuckGo. * **Fix:** **Action Steps:** 1. Log in to [Bing Webmaster Tools](https://www.bing.com/webmasters) using your Google account. 2. Select **Import from Google Search Console** to sync your verified site property instantly. 3. Confirm automated weekly sitemap and URL synchronization to power Microsoft Copilot grounding. ### Off-Page & Authority {#off-page-&-authority} #### DataForSEO Backlink Profile & Toxic Link Audit (U3) * **Status:** Gated | **Priority:** Neutral | **Difficulty:** Easy * **Specification & Standard:** Off-Page Authority, Link Toxicity & Referring Domain Intelligence * **Diagnostic Findings & Evidence:** Requires backlink profile analysis to evaluate referring domain toxicity, anchor text distribution, and competitor gaps. * **Architectural Context & Why It Matters:** Backlink authority from reputable regional publications, food blogs, and coffee directories directly influences domain trust in competitive search verticals. Auditing inbound links identifies toxic spam links requiring Google disavowal and surfaces competitor backlink gaps. * **Impact on Conversion & Search:** Protects domain reputation from toxic link penalties and identifies high-value regional PR opportunities. * **Fix:** **Action Steps:** 1. Export your domain backlink profile from Google Search Console under **Links → Top linking sites**. 2. Audit referring domains to identify toxic spam links or unearned spam directory listings. 3. Build local PR partnerships with regional business directories, food & beverage publications, and community guides. #### Google Business Profile (GBP) Local Verification (U4) * **Status:** Gated | **Priority:** Neutral | **Difficulty:** Easy * **Specification & Standard:** Google Business Profile (GBP) & Local Maps Verification * **Diagnostic Findings & Evidence:** Requires Google Business Profile verification to confirm retail café location data and Google Maps pin health. * **Architectural Context & Why It Matters:** Your Google Business Profile powers local Google Maps search cards, customer review accumulation, and phone call routing for both Kelowna cafés. Inconsistent opening hours or unverified location pins suppress local pack rankings. * **Impact on Conversion & Search:** Secures top rankings in Google Maps for localized "coffee near me" searches and drives foot traffic. * **Fix:** **Action Steps:** 1. Navigate to [Google Business Profile Manager](https://business.google.com/). 2. Verify all retail café location pins, primary business category (Coffee Roasters / Coffee Shop), and phone numbers. 3. Align NAP (Name, Address, Phone) details exactly with your website footer and location pages. 4. Upload high-resolution interior/exterior photos and establish an active customer review response workflow. ### Technical Foundation {#technical-foundation} #### Server Backend Error Logs & Brute-Force Monitoring (U7) * **Status:** Gated | **Priority:** Neutral | **Difficulty:** Easy * **Specification & Standard:** Server Infrastructure & Application Error Logging Standards * **Diagnostic Findings & Evidence:** Requires inspecting web server and CDN access logs for 5xx exceptions and traffic anomalies. * **Architectural Context & Why It Matters:** Server error logs capture 500 internal server errors, PHP fatal errors, database connection timeouts, and malicious brute-force attempts that are invisible to front-end page scanners. * **Impact on Conversion & Search:** Surfaces hidden backend exceptions and ensures infrastructure stability under heavy holiday traffic. * **Fix:** **Action Steps:** 1. Review web server and CDN access logs (Cloudflare Analytics / hosting logs) for recurring 4xx or 5xx status codes. 2. Inspect slow database queries and theme script execution times during peak traffic hours. 3. Verify that edge caching and rate limiting prevent unexpected downtime during marketing campaigns. ### Performance & Core Web Vitals {#performance-&-core-web-vitals} #### Chrome User Experience Report (CrUX) Field Data (U8) * **Status:** Gated | **Priority:** Neutral | **Difficulty:** Easy * **Specification & Standard:** Chrome User Experience Report (CrUX) Real-World 28-Day Field Data * **Diagnostic Findings & Evidence:** Google requires sufficient real-world 28-day user traffic before publishing historical Core Web Vitals field data. * **Architectural Context & Why It Matters:** Google uses 28-day rolling real-user metrics (CrUX) from actual Chrome browser sessions to evaluate Core Web Vitals for search rankings. Low-traffic domains remain in a "data insufficient" state until minimum sample thresholds are reached. * **Impact on Conversion & Search:** Validates real-world speed and responsiveness experienced by actual shoppers on local mobile networks. * **Fix:** **Action Steps:** 1. Monitor the Core Web Vitals report in Google Search Console once domain traffic reaches sample thresholds. 2. Verify that 75% of real-world page views meet "Good" thresholds: LCP (<2.5s), INP (<200ms), and CLS (<0.1). 3. Continually optimize mobile image compression and lazy loading to maintain fast real-user page loads. --- *Audit generated by [Michael Vereb](https://www.michaelvereb.com/) on September 18, 2026.* [image1]:

` that states the page primary topic. Having multiple `

` tags or missing an `

` tag containing your core business offering and location. 3. Ensure all supporting sections on the page use `

` tags, and nested subsections use `

`. 4. Avoid using `

`. 2. Group major commercial sections (e.g. "Featured Roasts", "Our Story", "Brew Guides") under semantic `

` tags. 3. Use `