Leafology 420 Landing

Your website's homepage is returning a 404 error, meaning visitors and search engines can't access it. This blocks all traffic and revenue.

Action: Immediately check your Netlify deployment: verify the build succeeded, confirm the correct branch is deployed, and check for missing index.html or routing misconfigurations. Contact Netlify support if the deployment itself failed.

Your site's core customer journey is breaking: visitors can reach your homepage and age gate, but when they try to view your menu, a resource fails to load (404 error). This blocks customers from browsing products and placing orders.

Action: Investigate which asset is missing on the menu page (check Network tab in browser DevTools, look for red 404 responses). Common culprits: broken Dutchie iframe URL, missing CSS/JS file, or misconfigured CDN path. Fix the broken URL or re-upload the missing file, then re-test the full journey.

Your website's main landing page is returning a 404 error, meaning it's not accessible to customers or search engines. This breaks the entire user journey and damages your search rankings.

Action: Immediately check your Netlify deployment logs and verify the root index.html file exists and is deployed. If recently migrated, confirm DNS and build settings are correct. Test the URL directly in a browser and check Netlify's deployment history for failed builds.

Search engines can't find instructions on which pages to crawl on your site, which may hurt your search visibility. A missing robots.txt file means Google has to guess what's important, potentially wasting crawl budget on low-value pages.

Action: Deploy a robots.txt file to your root domain. For a Netlify-hosted cannabis dispensary landing page, allow all major search engines to crawl your content (except any age-gate or admin sections). Use the auto-fix plan (write-default-robots) to generate a standard compliant file immediately.

Search engines can't find a map of your website's pages, which hurts discoverability. Without a sitemap, Google may miss pages or index you more slowly.

Action: Generate and publish a sitemap.xml file listing all public pages. For Netlify, use a plugin like netlify-plugin-sitemap or manually create one and commit to your repo.

Your website is missing a content security policy (CSP) header, which is a security safeguard that tells browsers which sources of content are trusted. This increases vulnerability to injection attacks and lowers your site's security score.

Action: Enable the auto-fix to add a standard CSP header via Netlify configuration. Ensure the policy allows the Dutchie iframe domain and any third-party scripts your menu uses.

Your website is missing a security header that prevents attackers from embedding your site inside malicious frames. This is a standard security practice that protects both your business and your visitors.

Action: Add the x-frame-options header (set to DENY or SAMEORIGIN) to your Netlify site configuration. This is a one-line fix in your _headers file or Netlify settings.

Your website is completely inaccessible to people using screen readers and keyboard navigation. This blocks users with disabilities from browsing your menu, hurts SEO rankings, and exposes you to legal liability under accessibility laws.

Action: Review the Lighthouse HTML report immediately. Check for missing alt text on images, broken heading hierarchy, color contrast issues, and keyboard navigation problems. Start by fixing critical issues in the Dutchie iframe embed and main navigation.

Your mobile website is completely inaccessible to people with disabilities and fails basic web standards. This means visitors using screen readers, keyboard navigation, or assistive devices can't use your site at all, and search engines can't properly index it. It's also a legal compliance risk under accessibility laws.

Action: Download the Lighthouse HTML report from the evidence path and audit the critical failures (likely missing alt text, broken heading structure, poor color contrast, form labels). Prioritize fixing semantic HTML, image descriptions, and navigation keyboard support. Consider hiring an accessibility specialist for a full remediation if in-house expertise is limited.

Your website is failing Google's best practices audit across the board (0/100 score), which means it likely has serious technical issues like unpatched vulnerabilities, outdated libraries, broken HTTPS, or unsafe third-party code. This damages trust and can trigger browser warnings for visitors.

Action: Open the Lighthouse HTML report immediately and prioritize fixing critical vulnerabilities and HTTPS/security warnings first, then address deprecated APIs and unsafe dependencies. Re-run Lighthouse after each fix to track progress toward 90+.

Your mobile site is failing Lighthouse best practices checks across the board (0/100 score). This likely means broken dependencies, outdated libraries, unsafe code patterns, or missing security headers—things that slow down your site, frustrate visitors, and hurt your search ranking.

Action: Open the Lighthouse HTML report at the evidence path and fix the top 5 failing audits. Prioritize: HTTPS/security headers, deprecated APIs, missing viewport meta tag, and unminified JavaScript. Re-run Lighthouse after each fix.

Your website is loading extremely slowly on desktop browsers, scoring zero on Google's performance test. This means visitors are experiencing long load times, which drives away customers and hurts search rankings.

Action: Open the Lighthouse HTML report at the evidence path and fix the top 3 blocking issues (usually unoptimized images, render-blocking scripts, or oversized bundles). Start with image compression and lazy loading.

Your mobile site is essentially non-functional—Lighthouse detected it scores 0/100 on performance, accessibility, and SEO. This means the page likely isn't loading properly, has critical rendering issues, or is completely broken on mobile devices. Since most cannabis customers browse on phones, this is killing conversions and search visibility.

Action: Open the Lighthouse HTML report immediately to identify what's blocking page load (likely a JavaScript error, failed asset, or blocking resource). Check browser console on a mobile device. If Dutchie iframe is involved, verify it's loading and not causing a hard block. Escalate to dev for urgent triage.

Your landing page is scoring 0/100 on Google's SEO audit, meaning search engines can't properly read your site's structure, metadata, or content. This kills organic visibility and traffic from search results.

Action: Open the Lighthouse HTML report (/Users/markwallace/BKH/apex-sentinel/runs/2026-04-20T11-30-05-807Z/lighthouse/leafology-worldcup-420/lighthouse-desktop.html) and fix critical SEO blockers: add a proper title tag, meta description, heading hierarchy (h1 for main topic), and ensure all text content is crawlable (not hidden in images or JS-only). Retest after each fix.

Your mobile site is failing Google's SEO quality checks entirely (0/100 score). This means search engines can't properly index your pages, read your content, or rank you for cannabis dispensary searches. This is a major blocker for organic traffic.

Action: Download the Lighthouse HTML report and fix critical issues in order: ensure mobile viewport is set, add meta descriptions to all pages, fix heading hierarchy (H1 should appear once per page), and verify internal links are crawlable. Retest after each fix.

Your landing page is missing a `<main>` landmark tag, which helps screen readers and assistive devices understand the page structure. This doesn't block functionality but makes the site harder to navigate for users with disabilities.

Action: Wrap your primary content (below header/nav) in a `<main>` tag. This is a quick HTML fix: add `<main>` around the central content area and close it before the footer.

Some content on your landing page isn't wrapped in proper structural landmarks (like <main>, <nav>, <header>). Screen reader users and assistive tech miss this content. It's a accessibility issue that could expose you to complaints or ADA concerns.

Action: Wrap the `.main` div content in a semantic <main> landmark tag, or add role="main" to the existing div. This is a quick fix—your dev team can do it in minutes.

Your website's homepage is returning a 404 error, meaning visitors see a 'page not found' message instead of your actual site. This completely blocks customer access to your menu, ordering system, and business information.

Action: Immediately verify the Netlify deployment is live and the build succeeded. Check that the correct build output folder is configured in Netlify settings. If recently deployed, wait 2–3 minutes for propagation, then test again. Contact Netlify support if the site remains unreachable.

A critical resource failed to load (404 error) while testing the customer journey from homepage through age gate to the menu. This breaks the path customers take to view products and place orders.

Action: Check server logs and Netlify deploy status to identify which asset returned 404. Verify the Dutchie iframe URL, menu assets, and any external dependencies are correctly configured and deployed. Re-run the journey test after fixes.

Your site's main landing page (listed in your sitemap) is returning a 404 error, meaning it doesn't exist or is misconfigured. Visitors and search engines trying to reach your site will hit a dead end, breaking your entire traffic flow.

Action: Check Netlify deployment: verify the build succeeded, confirm index.html exists in the publish directory, and test the root URL directly. If recently deployed, rollback to the last working version and redeploy.

Search engines can't find your site rules. Without a robots.txt file, Google and other search engines don't know which pages to crawl or avoid, which can hurt your visibility in search results and may cause indexing delays.

Action: Create and deploy a robots.txt file at the root of your site. For a dispensary landing page, allow all major search engines and block only sensitive admin paths. Use the auto-fix plan 'write-default-robots' to generate a standard template.

Search engines can't find a map of your pages, which hurts how quickly Google discovers and ranks your content. This is particularly important for dispensaries competing in local search.

Action: Generate and deploy a sitemap.xml file listing all public pages, then submit it to Google Search Console. Netlify can auto-generate this—check your build settings or use a static sitemap plugin.

Your website is missing a security header (Content-Security-Policy) that tells browsers which external resources are safe to load. This reduces your security posture and could allow malicious scripts to execute if your site is compromised.

Action: Add a Content-Security-Policy header to your Netlify configuration. Start with a restrictive policy that allows your Dutchie iframe and essential third-party services, then loosen as needed. Use Netlify's _headers file or netlify.toml to deploy this.

Your website is missing a security header that tells browsers whether your pages can be embedded inside other websites' frames. This is a basic security control that protects against clickjacking attacks where bad actors could trick visitors into clicking hidden elements.

Action: Add the x-frame-options header set to SAMEORIGIN or DENY to your Netlify site configuration. Since this is a landing page (not an embedded storefront), DENY is safest unless you intentionally embed this page elsewhere.

Your website's homepage is returning a 404 error, meaning visitors see a 'page not found' message instead of your business. This blocks all traffic and kills revenue potential.

Action: Check Netlify deployment status immediately—verify the build succeeded, correct branch is deployed, and index.html exists in the root. If recently deployed, rollback to the last known working version.

A critical visitor journey is failing: customers see a 404 error when trying to proceed from the age gate to view your menu. This blocks the path to sales and suggests a broken link or missing resource on your site.

Action: Check your age-gate redirect logic and verify the menu page URL is correct and accessible. Review server logs and test the full flow manually (homepage → age gate → menu) to identify which resource is missing.

Your main landing page is returning a 404 error, meaning visitors and search engines can't access it. This is a critical blocker—potential customers will hit a dead end and leave.

Action: Immediately verify the Netlify deployment is live and the root index.html file exists. Check deployment logs for build failures. If recently deployed, trigger a rebuild. If using a custom domain, verify DNS and domain settings point to the correct Netlify site.