# Apex Sentinel — Jungle Kingdom Flower Monthly Audit **URL:** https://junglekingdomflower.com/ **Platform:** unknown **Archetype:** fun **Run ID:** 2026-04-19T06-18-18-831Z **Scanned:** 2026-04-19T06:56:42.127Z **Duration:** 792s This is a **monthly deep audit**. The crawler performed a full-site scan including Lighthouse performance, axe-core accessibility (WCAG 2.2 AA), cross-browser compatibility, security headers, schema markup validation, and SEO best-practice checks. Because this site is not a repository we control, Apex Sentinel **cannot automatically apply fixes** — instead, each finding below includes an AI-generated plain-English explanation + step-by-step recommended fix you can hand to a developer or execute in your CMS directly. --- ## Executive Summary **Overall grade:** **F** | Dimension | Count | Meaning | |---|---|---| | Pages crawled | 21 | Full sitemap + linked pages | | P0 (critical) | 4 | Site-down or compliance-breaking | | P1 (urgent) | 35 | Significant revenue / SEO / UX impact | | P2 (high) | 37 | Quality / ranking / trust degradation | | P3 (medium) | 35 | Polish + optimization | | "Do first" items | 30 | AI-flagged top priorities | | Quick wins (< 30 min) | 29 | Fastest ROI items | --- ## Top 10 Actions (Ranked) If you only have time for ten things this month, do these — in this order. 1. **[P0] 🔴 DO FIRST Sensitive artifact exposed: /.git/config** — _Exposing development files puts your site at immediate risk of being hacked, which could compromise customer data, disrupt sales, violate cannabis licensing compliance requirements, and damage your reputation._ Page: https://junglekingdomflower.com/.git/config Effort: Moderate (1-3 hours) 2. **[P0] 🔴 DO FIRST Sensitive artifact exposed: /.git/HEAD** — _This is a direct security vulnerability that could expose your codebase, customer data handling logic, or payment processing details to attackers, risking compliance violations (cannabis licensing boards require secure systems) and potential data breaches._ Page: https://junglekingdomflower.com/.git/HEAD Effort: Moderate (1-3 hours) 3. **[P0] 🔴 DO FIRST Sensitive artifact exposed: /wp-login.php** — _Exposing your login page increases the risk of account takeover, which could lead to your site being defaced, malware injection, or unauthorized access to customer data and compliance records._ Page: https://junglekingdomflower.com/wp-login.php Effort: Moderate (1-3 hours) 4. **[P0] Sensitive artifact exposed: /.env** Page: https://junglekingdomflower.com/.env 5. **[P1] 🔴 DO FIRST Page returns 404: https://junglekingdomflower.com/about-us/** — _Customers looking for your "About Us" page will hit a dead end, and Google will gradually stop trusting your sitemap, which hurts your visibility in search results for cannabis dispensary queries._ Page: https://junglekingdomflower.com/about-us/ Effort: Quick win (< 30 min) 6. **[P1] 🔴 DO FIRST Page returns 404: https://junglekingdomflower.com/contact-us/** — _Lost customer inquiries and compliance violations: cannabis retailers must provide a working contact method to answer age-verification questions and license inquiries; a broken contact page damages trust and may trigger compliance audits._ Page: https://junglekingdomflower.com/contact-us/ Effort: Quick win (< 30 min) 7. **[P1] 🔴 DO FIRST Page returns 404: https://junglekingdomflower.com/weed-delivery-williamsburg/** — _You're losing potential sales from customers searching for 'weed delivery Williamsburg' — Google will stop showing this page in results, and any traffic sent to this URL bounces immediately._ Page: https://junglekingdomflower.com/weed-delivery-williamsburg/ Effort: Quick win (< 30 min) 8. **[P1] 🔴 DO FIRST Page returns 404: https://junglekingdomflower.com/weed-delivery-bed-stuy/** — _Customers searching for 'weed delivery Bed-Stuy' may click a Google result pointing to this URL and land on an error page instead of a product page, causing lost sales and damaging trust._ Page: https://junglekingdomflower.com/weed-delivery-bed-stuy/ Effort: Moderate (1-3 hours) 9. **[P1] 🔴 DO FIRST Page returns 404: https://junglekingdomflower.com/terms-conditions/** — _Broken links harm your search rankings, frustrate customers looking for legal terms, and may trigger compliance issues if regulators expect a Terms & Conditions page to be publicly available._ Page: https://junglekingdomflower.com/terms-conditions/ Effort: Quick win (< 30 min) 10. **[P1] 🔴 DO FIRST Page returns 404: https://junglekingdomflower.com/blog/** — _You're losing potential organic search traffic from blog-related keywords, and customers who click blog links from search results or social media will hit a dead end instead of engaging with your content._ Page: https://junglekingdomflower.com/blog/ Effort: Quick win (< 30 min) --- ## Findings by Severity ### P0 — 4 findings ### 1. Sensitive artifact exposed: /.git/config - **Severity:** P0 | **Priority:** 🔴 DO FIRST - **Effort:** Moderate (1-3 hours) - **Business category:** security - **Page URL:** https://junglekingdomflower.com/.git/config - **Rule:** `tier5.exposed.artifact` **What it means (plain English)** Your website is exposing a Git configuration file (a developer tool file) that contains sensitive information about your codebase and deployment setup. This file should never be publicly accessible on the internet—it's like leaving your house blueprints and security codes on your front lawn. An attacker can use this to find vulnerabilities or understand your system architecture. **Why it matters for your business:** Exposing development files puts your site at immediate risk of being hacked, which could compromise customer data, disrupt sales, violate cannabis licensing compliance requirements, and damage your reputation. **Technical root cause:** Your website's source code was deployed to production with the .git directory (a hidden developer folder) still present and accessible. Most web servers should block access to hidden directories, but this one isn't configured to do so. **Recommended fix — step by step** 1. Contact your hosting provider or server admin and ask them to add a firewall rule blocking all requests to /.git/* and other hidden directories (/.hg/*, /.svn/*, /.env, etc.) at the edge (before traffic reaches your application). 2. If you have server access: add a .htaccess rule (Apache) or nginx config block to deny access: 'location ~ /\.git { deny all; }' and restart the server. 3. Remove the .git directory from your production server entirely: SSH into your server, navigate to your root directory, and run 'rm -rf .git' (ask your host for help if unsure). 4. Add a .gitignore file to your repository so .git never gets deployed again in future updates. 5. Scan https://junglekingdomflower.com/.git/config, /.env, /.htaccess, and /web.config with a free tool like GitHunter or manually verify they no longer return HTTP 200. ### 2. Sensitive artifact exposed: /.git/HEAD - **Severity:** P0 | **Priority:** 🔴 DO FIRST - **Effort:** Moderate (1-3 hours) - **Business category:** security - **Page URL:** https://junglekingdomflower.com/.git/HEAD - **Rule:** `tier5.exposed.artifact` **What it means (plain English)** Your website is exposing Git version control files (internal developer files) to the public internet. When someone visits `/.git/HEAD`, they can see it exists and potentially access other Git files, which may contain sensitive information like code history, credentials, or file paths that attackers could exploit. **Why it matters for your business:** This is a direct security vulnerability that could expose your codebase, customer data handling logic, or payment processing details to attackers, risking compliance violations (cannabis licensing boards require secure systems) and potential data breaches. **Technical root cause:** The `.git/` directory from local development was deployed to production and is not being blocked by the web server or CDN. Most hosting platforms don't automatically hide these directories. **Recommended fix — step by step** 1. Add a `.htaccess` file to your root directory with ` Deny from all ` (if Apache) or equivalent `location ~ /\.git` block in nginx.conf (if Nginx) — ask your host which you use 2. Contact your hosting provider and ask them to block `/.git/`, `/.env`, `/.svn/`, and other hidden version-control directories at the server level 3. Remove the `.git/` directory entirely from your production server: SSH into your host and run `rm -rf .git/` in your website's root folder, or redeploy without it 4. Test the fix by visiting `https://junglekingdomflower.com/.git/HEAD` in your browser — it should return a 403 Forbidden or 404, not 200 5. Scan for other exposed files: visit `/.env`, `/.git/config`, and `/web.config` to ensure they also return 403/404 ### 3. Sensitive artifact exposed: /wp-login.php - **Severity:** P0 | **Priority:** 🔴 DO FIRST - **Effort:** Moderate (1-3 hours) - **Business category:** security - **Page URL:** https://junglekingdomflower.com/wp-login.php - **Rule:** `tier5.exposed.artifact` **What it means (plain English)** Your WordPress admin login page (/wp-login.php) is publicly accessible and returns a successful response. This is a common entry point for attackers trying to break into websites. While WordPress login pages exist by default, exposing them without protection makes your site a target for automated attacks that guess passwords. **Why it matters for your business:** Exposing your login page increases the risk of account takeover, which could lead to your site being defaced, malware injection, or unauthorized access to customer data and compliance records. **Technical root cause:** WordPress installations ship with /wp-login.php exposed by default. No server-level protection (IP whitelist, WAF rule, or HTTP 403 block) has been configured to restrict access to this sensitive administrative path. **Recommended fix — step by step** 1. Log into your hosting control panel (cPanel, Plesk, or your host's dashboard) and locate the Web Application Firewall (WAF) or ModSecurity settings. 2. Create a rule to return HTTP 403 (Forbidden) for requests to /wp-login.php from all IP addresses except those you explicitly whitelist (e.g., your office IP). 3. Alternatively, install the WordPress plugin 'Wordfence Security' (free tier) → Firewall tab → set 'Block all login attempts' or 'Restrict login to specific IP addresses'. 4. If you use Cloudflare for DNS, enable 'WAF Rules' and create a custom rule: (cf.uri_path contains '/wp-login.php') → Block. 5. Test the fix by visiting https://junglekingdomflower.com/wp-login.php in an incognito window; you should see a 403 error or blank page, not a login form. 6. Optional: rename /wp-login.php to a custom path using a plugin like 'WPS Hide Login' if you want to avoid lockouts. ### 4. Sensitive artifact exposed: /.env - **Severity:** P0 - **Page URL:** https://junglekingdomflower.com/.env - **Rule:** `tier5.exposed.artifact` **Detail** https://junglekingdomflower.com/.env returned 200. Sensitive paths must be blocked at edge. --- ### P1 — 35 findings ### 1. Page returns 404: https://junglekingdomflower.com/about-us/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/about-us/ - **Rule:** `tier2.page.404` **What it means (plain English)** Your sitemap (the file that tells Google which pages exist on your site) lists a page at /about-us/, but when we visit that URL, the server returns a 404 error — meaning the page doesn't exist or has been deleted. This breaks both user experience and search engine crawling. **Why it matters for your business:** Customers looking for your "About Us" page will hit a dead end, and Google will gradually stop trusting your sitemap, which hurts your visibility in search results for cannabis dispensary queries. **Technical root cause:** Either the page was deleted without updating the sitemap, the page URL was changed without a redirect, or the page exists but is misconfigured on the server. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/about-us/ directly and confirm whether the page should exist — check your site structure and navigation menu. 2. If the page should exist, check your CMS (WordPress, Shopify, custom platform) to see if it's published and publicly visible; if using WordPress, go to Pages → All Pages, search "about", and verify the post status is "Published" and URL slug is exactly "about-us". 3. If the page exists but is returning 404, ask your hosting provider to check server logs or test from a different network (the page might be geofenced or IP-blocked due to cannabis restrictions). 4. If the page was intentionally removed, remove it from your sitemap: use your SEO plugin (e.g., Yoast SEO: SEO → Sitemaps → view XML sitemap, or manually edit the sitemap.xml file) or contact your hosting provider to regenerate the sitemap. 5. Once resolved, submit the updated sitemap to Google Search Console (Google Search Console → Sitemaps → Request indexing of the correct URL). ### 2. Page returns 404: https://junglekingdomflower.com/contact-us/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** compliance - **Page URL:** https://junglekingdomflower.com/contact-us/ - **Rule:** `tier2.page.404` **What it means (plain English)** Your sitemap (the file search engines use to discover all your pages) lists a contact page at /contact-us/, but when we visit it, the server returns a 404 error—meaning the page doesn't exist or is misconfigured. Customers clicking 'Contact Us' will hit a dead end, and Google will gradually stop trusting your sitemap. **Why it matters for your business:** Lost customer inquiries and compliance violations: cannabis retailers must provide a working contact method to answer age-verification questions and license inquiries; a broken contact page damages trust and may trigger compliance audits. **Technical root cause:** The page URL is listed in your sitemap but either (a) the page was deleted without updating the sitemap, (b) the URL routing is misconfigured, or (c) the page exists but isn't being served due to a redirect or permission issue. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/contact-us/ directly in your browser and confirm the 404 error. 2. Log in to your site's admin panel and check if a contact page exists in the Page or Post list; if not, recreate it with a contact form or contact information. 3. If the page exists but returns 404, check your site's Settings → Permalinks (or URL routing in non-WordPress platforms) to ensure clean URLs are enabled. 4. Update or regenerate your XML sitemap via your site builder's SEO tool or plugin (e.g., Yoast SEO → XML Sitemaps → Regenerate) to remove the dead link. 5. Test the contact page again and confirm it loads with a 200 status code; use Google's URL Inspection tool (search.google.com → URL Inspection → paste link) to verify. ### 3. Page returns 404: https://junglekingdomflower.com/weed-delivery-williamsburg/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** revenue - **Page URL:** https://junglekingdomflower.com/weed-delivery-williamsburg/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your sitemap (the file search engines use to discover your content) is returning a 404 error, meaning it no longer exists or was deleted. When customers click links to this page or search engines try to index it, they hit a dead end instead of finding product information. **Why it matters for your business:** You're losing potential sales from customers searching for 'weed delivery Williamsburg' — Google will stop showing this page in results, and any traffic sent to this URL bounces immediately. **Technical root cause:** The page was either deleted, moved to a different URL, or the permalink structure changed without setting up a redirect. The sitemap wasn't updated to match. **Recommended fix — step by step** 1. Check if /weed-delivery-williamsburg/ was intentionally deleted or if the content moved to a new URL by searching your site's admin history or checking similar delivery pages (e.g., /weed-delivery-brooklyn/) to understand the current URL pattern. 2. If the page still should exist, restore it or recreate it with current inventory and delivery details. 3. If the page was moved, set up a 301 redirect from the old URL to the new one using your hosting control panel (typically .htaccess for Apache servers or your CMS redirect tool). 4. Remove https://junglekingdomflower.com/weed-delivery-williamsburg/ from your sitemap by editing sitemap.xml and resubmitting via Google Search Console. 5. In Google Search Console, check 'Coverage' to confirm the 404 is resolved, then request re-indexing of the corrected page if it was restored. ### 4. Page returns 404: https://junglekingdomflower.com/weed-delivery-bed-stuy/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Moderate (1-3 hours) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/weed-delivery-bed-stuy/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your website's sitemap (the file that tells search engines what pages exist on your site) is actually returning a 404 error, meaning the page is not found. This confuses both visitors and search engine robots, who expect that page to exist based on the sitemap. **Why it matters for your business:** Customers searching for 'weed delivery Bed-Stuy' may click a Google result pointing to this URL and land on an error page instead of a product page, causing lost sales and damaging trust. **Technical root cause:** Either the page was deleted or moved without updating the sitemap, or the URL slug (weed-delivery-bed-stuy) no longer maps to a published page in the CMS. **Recommended fix — step by step** 1. Check your CMS (WordPress, Shopify, custom platform) to confirm whether a 'Bed-Stuy delivery' or location-specific page actually exists; search for 'bed-stuy' in your page/post listings 2. If the page should exist, restore it from a backup or republish it; if it was intentionally deleted, proceed to step 3 3. Remove the dead URL from your sitemap: locate sitemap.xml in your admin panel or root directory and delete or comment out the line containing '/weed-delivery-bed-stuy/' 4. If this is a location page that was consolidated into another page, set up a 301 redirect (permanent redirect) from /weed-delivery-bed-stuy/ to the correct URL using your CMS plugin (e.g., Redirection for WordPress) or server config 5. Resubmit your updated sitemap to Google Search Console (Search Console → Sitemaps → click your sitemap URL → Request indexing) 6. Use Google Search Console's 'Removed URLs' report to check if this 404 is still being crawled; if yes, request removal ### 5. Page returns 404: https://junglekingdomflower.com/terms-conditions/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** compliance - **Page URL:** https://junglekingdomflower.com/terms-conditions/ - **Rule:** `tier2.page.404` **What it means (plain English)** Your sitemap (the file that tells Google which pages exist on your site) lists a Terms & Conditions page at /terms-conditions/, but when visitors or search engines try to load it, they get a 404 error—meaning the page doesn't actually exist or has been moved. This creates a bad user experience and signals to Google that your sitemap is out of date. **Why it matters for your business:** Broken links harm your search rankings, frustrate customers looking for legal terms, and may trigger compliance issues if regulators expect a Terms & Conditions page to be publicly available. **Technical root cause:** The page URL was either deleted, moved to a different path, or never created—but the sitemap.xml file was not updated to remove it. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/sitemap.xml in your browser and download or view it to confirm the /terms-conditions/ URL is listed 2. Check your site's navigation and admin panel to find where your Terms & Conditions page actually lives (or confirm it doesn't exist) 3. If the page exists at a different URL, update the sitemap entry to point to the correct path 4. If the page does not exist, remove the /terms-conditions/ entry from sitemap.xml 5. After updating the sitemap, go to Google Search Console (search.google.com) → Sitemaps → re-submit your sitemap 6. Wait 24–48 hours for Google to re-crawl and verify the error is resolved ### 6. Page returns 404: https://junglekingdomflower.com/blog/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/blog/ - **Rule:** `tier2.page.404` **What it means (plain English)** Your sitemap lists a /blog/ page, but when Google (or customers) try to visit it, the server returns a 404 error — meaning 'page not found.' This breaks the user experience and signals to search engines that your sitemap is out of sync with your actual site. **Why it matters for your business:** You're losing potential organic search traffic from blog-related keywords, and customers who click blog links from search results or social media will hit a dead end instead of engaging with your content. **Technical root cause:** The /blog/ URL is referenced in your XML sitemap but the page either does not exist on the server, has been deleted, or is misconfigured. This mismatch between the sitemap and live content confuses both crawlers and visitors. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/blog/ directly in your browser and confirm the 404 error. 2. Check your sitemap file (usually at /sitemap.xml) and remove the /blog/ entry if the page is intentionally gone, or note the correct URL if it has been moved. 3. If you want a blog, restore the /blog/ page or create it with at least one published post; if not, delete the /blog/ entry from sitemap.xml and submit the updated sitemap to Google Search Console. 4. After fixing, go to Google Search Console → Coverage → resubmit the sitemap to expedite re-crawl. 5. Check your URL structure in your CMS settings to ensure all sitemap entries map to real, published pages going forward. ### 7. Page returns 404: https://junglekingdomflower.com/blog/best-cannabis-brands-brooklyn/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/blog/best-cannabis-brands-brooklyn/ - **Rule:** `tier2.page.404` **What it means (plain English)** A blog post URL is listed in your sitemap (the file search engines use to discover pages) but returns a 404 error, meaning the page no longer exists or was deleted. Customers clicking from search results or old links will land on a dead end, and Google will waste crawl budget trying to index a broken page. **Why it matters for your business:** Lost SEO ranking power for cannabis-related keywords, wasted search traffic, and damage to your site's credibility if users encounter dead links—especially harmful for a niche market where every qualified visitor counts. **Technical root cause:** The blog post was either deleted, moved to a different URL, or the sitemap was not updated after content removal. Search engines indexed the URL and will keep checking it until told otherwise. **Recommended fix — step by step** 1. Verify the post still exists: visit the blog section and search for 'best cannabis brands brooklyn' or similar keywords to confirm it's truly deleted. 2. If the post exists under a different URL, note that new URL. 3. If the post is genuinely deleted: either restore it from backup, or create a 301 redirect from the old URL to a related post (e.g., your general cannabis brands page). 4. Update your sitemap (usually at /sitemap.xml or /sitemap.xml.gz) to remove the dead URL—if using WordPress, install Yoast SEO, go to Crawl Settings > Sitemaps, and regenerate. 5. Submit the updated sitemap to Google Search Console: go to Google Search Console > Sitemaps, paste the sitemap URL, and click Submit. 6. Monitor Search Console for 404 errors in the next 2–4 weeks to confirm the page is no longer reported as broken. ### 8. Page returns 404: https://junglekingdomflower.com/blog/best-pre-rolls-brooklyn/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/blog/best-pre-rolls-brooklyn/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your site's sitemap (the index search engines use to crawl your content) is returning a 404 error, meaning it's gone or inaccessible. This creates friction: customers who click a link from Google or social media land on an error page instead of the content they expected, and search engines mark the page as broken, which hurts your ranking. **Why it matters for your business:** You're losing potential customers at the moment they're most interested (mid-research phase), and Google is interpreting broken links as poor site maintenance, which lowers your visibility in local search results for cannabis dispensaries. **Technical root cause:** The page URL was likely deleted, moved, or renamed without setting up a redirect. The sitemap still references the old URL, creating a mismatch between what search engines expect to find and what actually exists. **Recommended fix — step by step** 1. Check if the blog post 'best-pre-rolls-brooklyn' still exists at a different URL by searching your site admin or CMS for 'pre-rolls' or 'brooklyn'; if found, note the new URL. 2. If the post no longer exists and was valuable, restore it from a backup or rebuild it — blog content about local product guides drives consistent cannabis discovery traffic. 3. If the post is genuinely deleted and won't be recreated, add a 301 redirect from /blog/best-pre-rolls-brooklyn/ to your main /blog/ page or a relevant category page (e.g., /products/pre-rolls/). 4. Regenerate your sitemap to remove the dead URL — in most CMS platforms (WordPress, Shopify, etc.), this is automatic after you delete/redirect; manually ping Google Search Console > Sitemaps to force a re-crawl. 5. Search Google Search Console for 'best-pre-rolls-brooklyn' to confirm it's no longer indexed; if it still shows, click 'Request indexing' on the new destination URL. ### 9. Page returns 404: https://junglekingdomflower.com/blog/weed-delivery-bed-stuy-guide/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Moderate (1-3 hours) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/blog/weed-delivery-bed-stuy-guide/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your site's sitemap (the file that tells Google which pages exist) is returning a 404 error, meaning it no longer exists or was moved without a redirect. Customers clicking links and search engines crawling your site will hit a dead end, wasting their time and signaling to Google that your site has quality issues. **Why it matters for your business:** This broken page wastes SEO equity—Google invested crawl budget here, and any backlinks pointing to it are now worthless; it also frustrates customers looking for delivery info in Bed-Stuy, potentially pushing them to competitors. **Technical root cause:** The page was either deleted, the URL slug changed, or the page was moved to a new location without setting up a 301 redirect (a permanent forwarding rule). The sitemap was not updated to match. **Recommended fix — step by step** 1. Check your content management system (WordPress, Shopify, custom CMS, etc.) to see if the blog post 'weed-delivery-bed-stuy-guide' still exists in draft or trash; if it's live, verify the URL is correct. 2. If the page no longer serves a purpose, remove it from your sitemap: access your sitemap file (usually at /sitemap.xml or /sitemap-index.xml) and delete the entry for this URL. 3. If the page should exist, restore it from backup or republish it with the correct URL; then test the URL in your browser to confirm it returns a 200 status (success). 4. If the URL changed (e.g., from /blog/weed-delivery-bed-stuy/ to /delivery-guides/bed-stuy/), set up a 301 redirect from the old URL to the new one using your platform's redirect tool or .htaccess file. 5. Re-submit your updated sitemap to Google Search Console (at https://search.google.com/search-console/sitemaps) to notify Google of the fix. 6. Monitor this URL weekly in Search Console under 'Coverage' to ensure it no longer reports errors. ### 10. Page returns 404: https://junglekingdomflower.com/blog/cannabis-concentrates-guide/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Moderate (1-3 hours) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/blog/cannabis-concentrates-guide/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page that's listed in your sitemap (the file that tells search engines what pages exist on your site) is returning a 404 error, meaning it no longer exists or is broken. This breaks the user experience when someone clicks a link to that page, and it wastes search engine crawl time looking for content that isn't there. **Why it matters for your business:** Broken links hurt your SEO rankings for cannabis-related keywords, reduce customer trust when they land on error pages, and waste search engine crawlers' time that could be indexing working pages—directly impacting your ability to be found for high-intent 'cannabis concentrates' searches. **Technical root cause:** The page either was deleted without setting up a redirect, the URL path changed without updating the sitemap, or the content was moved to a different location. The sitemap still references the old URL, creating a mismatch. **Recommended fix — step by step** 1. Check if the page exists at a different URL (e.g., /concentrates-guide/ instead of /cannabis-concentrates-guide/) and note the correct path. 2. If the page exists elsewhere, go to your site's .htaccess file (or redirect settings in your hosting panel) and add a 301 redirect from the broken URL to the correct one. 3. If the page content is truly gone and you don't plan to recreate it, remove the URL from your sitemap (usually at /sitemap.xml or via your CMS). 4. Regenerate and resubmit your sitemap to Google Search Console (search.google.com) to notify Google of the change. 5. Set up a monitoring alert (e.g., using Screaming Frog or Google Search Console 'Coverage' reports) to catch future 404s in the sitemap weekly. ### 11. Page returns 404: https://junglekingdomflower.com/brands/jeeter/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Moderate (1-3 hours) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/brands/jeeter/ - **Rule:** `tier2.page.404` **What it means (plain English)** Your sitemap (the map search engines use to find all your pages) lists a page at /brands/jeeter/, but when Google or a customer tries to visit it, they get a 404 error (page not found). This tells search engines the page is broken and tells customers the product no longer exists. **Why it matters for your business:** Broken product pages harm SEO rankings, waste crawl budget that Google could use on live pages, and confuse customers who land on the missing page from external links or ads. **Technical root cause:** The page was either deleted or moved without updating the sitemap, or the URL slug in the sitemap doesn't match the actual URL structure on your site. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/brands/jeeter/ directly and confirm it returns 404. 2. Check if Jeeter products exist under a different URL path (e.g., /products/jeeter/ or /shop/jeeter/) using your site search or navigation. 3. If the product page is permanently gone, remove the /brands/jeeter/ URL from your sitemap file (usually sitemap.xml in your root directory or via an SEO plugin). 4. If the page should exist, restore the page content or redirect /brands/jeeter/ to the correct URL using a 301 redirect. 5. Regenerate and resubmit your sitemap to Google Search Console to notify Google of the change. 6. Check for any other dead links in your sitemap by running a crawl tool (e.g., Screaming Frog free tier) to catch similar issues. ### 12. Page returns 404: https://junglekingdomflower.com/brands/runtz/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/brands/runtz/ - **Rule:** `tier2.page.404` **What it means (plain English)** Your sitemap (the file that tells Google where your pages are) lists a page about Runtz brand products, but when visitors or search engines try to visit that URL, they get a 404 error — meaning the page doesn't exist or has been deleted. This creates a broken experience and wastes search engine crawling time. **Why it matters for your business:** Potential customers searching for Runtz products won't find your page in Google, and if they click a link to that page, they leave your site frustrated — hurting both sales and your search ranking. **Technical root cause:** The page either was deleted without updating the sitemap, or the URL path changed but the sitemap wasn't refreshed. Sitemaps are cached by search engines, so stale entries persist. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/brands/runtz/ directly to confirm it returns 404 2. Check your content management system (CMS) or product database to see if a Runtz brand page exists under a different URL path 3. If the page should exist, restore it from backup or recreate it with product listings 4. If Runtz is no longer carried, delete the URL from your sitemap file (typically at /sitemap.xml or /sitemap-index.xml) and resubmit via Google Search Console 5. After fixing, go to Google Search Console → Coverage → and request re-indexing of the corrected or removed URL 6. Set up monthly sitemap audits to catch future mismatches (or enable automated sitemap generation if your CMS supports it) ### 13. Page returns 404: https://junglekingdomflower.com/brands/ayrloom/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Moderate (1-3 hours) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/brands/ayrloom/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your sitemap (the file that tells Google which pages exist on your site) is returning a 404 error, meaning it no longer exists or is broken. This confuses both search engines and customers who click links to that brand page. **Why it matters for your business:** Search engines waste crawl budget on dead pages, and customers cannot browse the Ayrloom brand—losing potential sales and damaging trust in your site reliability. **Technical root cause:** The /brands/ayrloom/ page either was deleted without updating the sitemap, the brand inventory was removed from the database, or a URL structure change was made without redirects. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/sitemap.xml and verify whether /brands/ayrloom/ is still listed; if yes, remove it and resubmit the sitemap to Google Search Console. 2. Check your site's brand management system or CMS to confirm Ayrloom is no longer an active brand; if it should exist, restore the page content or database entry. 3. If Ayrloom was moved or renamed, set up a 301 redirect from /brands/ayrloom/ to the new URL (e.g., /brands/ayrloom-cannabis/) so old links and search results point to the correct page. 4. In Google Search Console, go to Coverage report and verify the 404 disappears after fixes; resubmit the sitemap. 5. Audit other /brands/* URLs in the sitemap to ensure no similar dead pages exist. ### 14. Page returns 404: https://junglekingdomflower.com/brands/grassroots-cannabis/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/brands/grassroots-cannabis/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page that's listed in your sitemap (the file that tells Google which pages exist on your site) is actually returning a 404 error — meaning it doesn't exist. This sends conflicting signals to search engines and breaks user experience if someone clicks a link to that page. **Why it matters for your business:** Customers searching for 'Grassroots Cannabis' brands won't find your product page, and Google will gradually trust your sitemap less, hurting your overall search visibility for other product pages. **Technical root cause:** The URL /brands/grassroots-cannabis/ is listed in your sitemap but the page has been deleted, moved, or never existed. The web server is configured to return HTTP 404 (not found) when accessed. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/brands/grassroots-cannabis/ directly to confirm it's broken. 2. Check your sitemap at https://junglekingdomflower.com/sitemap.xml or /sitemap-index.xml and remove the /brands/grassroots-cannabis/ entry. 3. If this product page should still exist, restore it from a backup or recreate it in your CMS. 4. If the page was intentionally removed, set up a 301 redirect from /brands/grassroots-cannabis/ to a related page (e.g., /brands/ or the correct Grassroots product page) so bookmarks and search results preserve traffic. 5. Regenerate and resubmit your sitemap via Google Search Console (Google > Search Console > Sitemaps > Resubmit). 6. Monitor Google Search Console > Coverage for any remaining 404 errors in the next 2–3 weeks. ### 15. Page returns 404: https://junglekingdomflower.com/brands/tyson-20/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/brands/tyson-20/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your website's sitemap (the file that tells Google which pages to crawl) is returning a 404 error, meaning it no longer exists. When customers click links to this product or brand page, or when Google's crawler tries to index it, they hit a dead end. This wastes crawl budget and frustrates visitors. **Why it matters for your business:** Lost sales opportunity: customers searching for Tyson products cannot reach that brand page, and search engines will gradually stop showing your site for brand-related queries. **Technical root cause:** The /brands/tyson-20/ URL was either deleted, renamed, or moved without setting up a redirect. The sitemap file was not updated to remove the dead link. **Recommended fix — step by step** 1. Verify whether the Tyson brand page should still exist: check your product inventory or content calendar to confirm if this brand is still carried. 2. If the page should exist, restore it or check your hosting file manager / CMS for a deleted or moved file. 3. If the page should NOT exist, log into your CMS admin or server and remove /brands/tyson-20/ from the sitemap.xml file. 4. If the URL was renamed or moved, set up a 301 redirect from /brands/tyson-20/ to the correct new URL (e.g., via .htaccess on Apache servers or CMS redirect plugins). 5. After fixing, submit the updated sitemap to Google Search Console (search.google.com > your property > Sitemaps) to re-crawl. ### 16. Page returns 404: https://junglekingdomflower.com/brands/jaunty/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/brands/jaunty/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your sitemap (the file that tells Google what pages exist on your site) is returning a 404 error, meaning it no longer exists or is broken. When customers or search engines try to visit https://junglekingdomflower.com/brands/jaunty/, they hit a dead end instead of seeing product or brand information. **Why it matters for your business:** This wastes crawl budget (the limited time Google spends indexing your site), breaks any backlinks or internal links pointing to that brand page, and damages user experience if customers are directed there via email, social, or search results. **Technical root cause:** The page either was deleted without updating the sitemap, the URL path changed without a redirect, or the brand content is unpublished but still referenced in the sitemap file. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/brands/jaunty/ directly and confirm it returns 404. 2. Log into your CMS admin panel and search for 'Jaunty' brand or any archived/unpublished content — restore it if it should be live, or delete it if it's obsolete. 3. If the brand page was intentionally removed, access your sitemap file (usually at /sitemap.xml or /sitemap-index.xml) and remove the dead URL from the list. 4. If the URL structure changed (e.g., brand page is now at /brands/jaunty-flower/), set up a 301 redirect from the old URL to the new one at the server level (via .htaccess for Apache, or your CMS redirect tool). 5. Resubmit your sitemap to Google Search Console (Settings → Sitemaps → paste sitemap URL and click 'Submit'). 6. Run a site crawl again in 48–72 hours to confirm the error is gone. ### 17. Page returns 404: https://junglekingdomflower.com/brands/platinum-reserve/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** revenue - **Page URL:** https://junglekingdomflower.com/brands/platinum-reserve/ - **Rule:** `tier2.page.404` **What it means (plain English)** A product page listed in your sitemap (the file that tells Google where your pages are) is returning a 404 error, meaning it no longer exists or is broken. When customers click links to this page or Google tries to index it, they'll hit a dead end instead of seeing product information. **Why it matters for your business:** Lost sales from customers trying to find Platinum Reserve products, and lost SEO ranking power because Google can't crawl and index this page—which also hurts visibility for related searches. **Technical root cause:** The page either was deleted without updating the sitemap, the URL structure changed (e.g., slug renamed), or the product was removed from inventory but the sitemap wasn't refreshed. The web server is correctly returning a 404 status code, but the sitemap still points to it. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/brands/platinum-reserve/ directly to confirm it's broken. 2. Check if the Platinum Reserve product still exists in your inventory system or CMS—if it does, restore the page; if not, proceed to step 3. 3. Remove the dead URL from your sitemap file (usually /sitemap.xml or generated via a CMS plugin) or regenerate the sitemap to exclude it. 4. If the product was renamed or moved, update any internal links pointing to the old URL to point to the new one. 5. Resubmit your updated sitemap to Google Search Console (search.google.com → your property → Sitemaps → re-upload or click 'Refresh'). 6. Check Google Search Console for other 404 errors in the 'Coverage' report to catch similar issues. ### 18. Page returns 404: https://junglekingdomflower.com/order-east-williamsburg/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/order-east-williamsburg/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your sitemap (the file that tells Google which pages exist on your site) is returning a 404 error, meaning it no longer exists or is misconfigured. This breaks the user experience for anyone trying to access that page and signals to search engines that your site structure is broken. **Why it matters for your business:** Customers searching for the East Williamsburg location may land on a dead page, lose trust, and order elsewhere; Google also penalizes sites with broken sitemap links, hurting your search visibility for dispensary keywords. **Technical root cause:** The URL /order-east-williamsburg/ is listed in your sitemap.xml but either the page was deleted without updating the sitemap, or a server redirect is missing. Search engines crawl the sitemap first and expect all listed URLs to return 200 OK responses. **Recommended fix — step by step** 1. Check if this page should still exist: visit https://junglekingdomflower.com/order-east-williamsburg/ in your browser and confirm it's truly a 404. 2. If the East Williamsburg location still exists, restore the page or check the CMS (WordPress, Shopify, etc.) to ensure it's published and not in draft mode. 3. If the location/page was intentionally removed, access your sitemap.xml file (usually at /sitemap.xml) and remove the line containing '/order-east-williamsburg/'. 4. After editing the sitemap, resubmit it to Google Search Console: go to google.com/search/console → select your property → Sitemaps → paste https://junglekingdomflower.com/sitemap.xml → click Submit. 5. Wait 24–48 hours, then re-check the URL in Search Console's URL Inspection tool to confirm it's no longer flagged as an error. ### 19. Page returns 404: https://junglekingdomflower.com/dispensary/east-williamsburg/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** revenue - **Page URL:** https://junglekingdomflower.com/dispensary/east-williamsburg/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your sitemap (the file search engines use to discover all your content) is returning a 404 error — meaning it no longer exists or is broken. When customers click links to this page from search results or your own site, they'll hit a dead end. Search engines will also waste crawl time on a page that doesn't exist, which harms your search visibility. **Why it matters for your business:** You're losing potential customers who find your East Williamsburg location in Google Search and land on an error page instead of your menu, hours, or ordering info — and search engines will gradually deprioritize your site if 404s accumulate. **Technical root cause:** The page URL is registered in your sitemap.xml but either the page has been deleted, moved to a different URL path, or the server is misconfigured to return 404 instead of serving the actual content. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/dispensary/east-williamsburg/ directly in your browser and confirm it shows 404; take a screenshot for documentation. 2. Check your CMS (WordPress, Shopify, custom platform) to see if this location page exists—search admin for 'east-williamsburg' or browse your Dispensary/Locations section. 3. If the page should exist: restore it from backup, republish it, or verify the URL slug matches exactly (including hyphens and spelling). 4. If the page was intentionally removed or relocated: update your sitemap.xml to remove the dead URL, or redirect it to the correct new URL (301 redirect in your hosting control panel or WordPress plugin like Redirection). 5. After fixing, resubmit your sitemap to Google Search Console (Property Settings → Sitemaps → click 'Add/Test Sitemap') to signal the fix. 6. Monitor Google Search Console for 404 errors in the Coverage report weekly for the next month to confirm no new dead links. ### 20. Page returns 404: https://junglekingdomflower.com/dispensary/williamsburg/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/dispensary/williamsburg/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page that you listed in your sitemap (the map search engines use to find your content) is returning a 404 error—meaning it doesn't exist or is broken. When customers click a link or Google tries to crawl it, they hit a dead end. This wastes crawl budget and frustrates both users and search engines. **Why it matters for your business:** Broken location pages in your sitemap directly harm local SEO visibility for Williamsburg and similar searches, reducing foot traffic and online discovery for that area. **Technical root cause:** Either the /dispensary/williamsburg/ page was deleted but not removed from the sitemap.xml file, or it's misconfigured on the server and returning 404 instead of 200 OK. **Recommended fix — step by step** 1. Go to https://junglekingdomflower.com/sitemap.xml and download or view the full sitemap; search for 'williamsburg' to confirm it's listed 2. Visit https://junglekingdomflower.com/dispensary/williamsburg/ directly in a browser and verify it returns 404 3. Decide: either restore/republish the Williamsburg location page, or remove that URL from sitemap.xml 4. If removing from sitemap: access your site's root directory (via FTP, cPanel, or content management admin panel) and edit sitemap.xml to delete the https://junglekingdomflower.com/dispensary/williamsburg/ block 5. If restoring the page: recreate the location content, ensure it's published/live on your server, then test the URL again in a browser 6. After fix, go to Google Search Console → Sitemaps → Resubmit your sitemap to notify Google of changes 7. Monitor Google Search Console → Coverage report over the next 48–72 hours to confirm the 404 errors disappear ### 21. Page returns 404: https://junglekingdomflower.com/dispensary/flatbush/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/dispensary/flatbush/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your sitemap (the file that tells search engines what pages exist on your site) is returning a 404 error, meaning it no longer exists or is not accessible. When customers click a link or search engines crawl that URL, they hit a dead end instead of finding dispensary information. **Why it matters for your business:** This breaks customer journeys to a specific dispensary location, wastes search engine crawl budget on non-existent pages, and signals to Google that your site structure is broken—hurting your search rankings for dispensary location pages. **Technical root cause:** The page URL exists in your sitemap but the actual page has been deleted, moved without a redirect, or the server is misconfigured. Search engines indexed it (hence the sitemap reference) but can no longer reach it. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/dispensary/flatbush/ in a browser and confirm it shows a 404 error. 2. Check if this dispensary location still exists—if it closed or moved, the page deletion was correct; if it should still exist, restore it from backup or recreate it. 3. If the page was intentionally removed, delete it from your sitemap: log into your website admin, find Sitemap settings (often under SEO or XML Sitemap plugins), and remove the flatbush URL. 4. If the page should exist but was moved to a new URL, set up a 301 redirect from /dispensary/flatbush/ to the new URL using your hosting control panel or a redirect plugin (e.g., Redirection for WordPress). 5. Regenerate and resubmit your sitemap to Google Search Console: go to google.com/webmasters, select your property, navigate to Sitemaps, and click 'Resubmit Sitemap'. 6. Check Google Search Console for other 404 errors in the 'Coverage' report under the 'Excluded' tab and repeat this process for any other broken dispensary location pages. ### 22. Page returns 404: https://junglekingdomflower.com/dispensary/crown-heights/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Moderate (1-3 hours) - **Business category:** revenue - **Page URL:** https://junglekingdomflower.com/dispensary/crown-heights/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your sitemap (the file that tells Google where your content lives) is returning a 404 error, meaning it no longer exists or is broken. This prevents both customers and search engines from accessing it, damaging discoverability and user trust. **Why it matters for your business:** Potential customers searching for your Crown Heights location won't find it in search results, and anyone clicking a saved link or social media reference will hit a dead end—losing foot traffic and sales. **Technical root cause:** The page URL exists in your sitemap.xml but the actual page has been deleted, moved without a redirect, or the site structure doesn't support that path. The server is configured to return HTTP 404 instead of forwarding traffic or restoring content. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/sitemap.xml and confirm whether /dispensary/crown-heights/ is still listed; if it is, remove it from the sitemap. 2. Check if the Crown Heights location page exists at a different URL (e.g., /locations/crown-heights/ or /crown-heights-dispensary/); if so, set up a 301 redirect from the old URL to the new one. 3. If the Crown Heights location is no longer in service, create a simple page at that URL explaining the closure and directing visitors to your active locations, or implement a 301 redirect to your main locations page. 4. Submit an updated sitemap to Google Search Console (https://search.google.com/search-console/) to remove the dead URL. 5. Check your server logs or hosting control panel for other 404 errors in the /dispensary/ path to identify additional broken location pages. ### 23. Page returns 404: https://junglekingdomflower.com/cannabis-101/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/cannabis-101/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your sitemap (the file search engines use to discover your content) is returning a 404 error, meaning it no longer exists or is unreachable. Customers clicking links expecting educational content will hit a dead end, and Google will waste crawl budget on a page that isn't there. **Why it matters for your business:** This damages your SEO rankings because search engines see broken links as a sign of poor site maintenance, and it frustrates customers seeking 'Cannabis 101' educational content that might convert them into buyers. **Technical root cause:** The page /cannabis-101/ was either deleted, moved to a new URL without a redirect, or the sitemap wasn't updated after the page was removed. **Recommended fix — step by step** 1. Visit https://junglekingdomflower.com/cannabis-101/ directly and confirm it is indeed returning a 404 error. 2. Check your CMS or hosting control panel (e.g., WordPress admin → Pages, or your site builder's page list) to see if the page still exists; if it does, republish it. 3. If the page was intentionally removed, access your sitemap file (usually at /sitemap.xml or /sitemap_index.xml) and remove the /cannabis-101/ URL entry. 4. If the page was moved to a new URL, set up a permanent 301 redirect from /cannabis-101/ to the new location using your CMS (WordPress: Redirection plugin, or hosting control panel > Redirects). 5. Resubmit your sitemap to Google Search Console: log in → your property → Sitemaps → click 'Add/test sitemap' and paste the sitemap URL. ### 24. Page returns 404: https://junglekingdomflower.com/cannabis-101/how-to-buy-legal-weed-nyc/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/cannabis-101/how-to-buy-legal-weed-nyc/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page listed in your sitemap (the file that tells Google what pages exist on your site) is returning a 404 error, meaning it's not found. This happens when either the page was deleted without redirecting traffic elsewhere, or the URL in your sitemap is wrong. Both Google and customers who click links will hit a dead end. **Why it matters for your business:** You're losing potential customers searching for 'how to buy legal weed in NYC'—a high-intent search query—and Google is wasting crawl budget on a broken page instead of indexing content that converts. **Technical root cause:** The URL exists in your sitemap.xml but the actual page has either been deleted, moved to a different URL without a redirect, or never existed. Web servers and search engines follow what the sitemap says should be there. **Recommended fix — step by step** 1. Check your live site: visit https://junglekingdomflower.com/cannabis-101/how-to-buy-legal-weed-nyc/ in a browser and confirm it's truly gone or if it loads. 2. If the page exists but shows 404: check your web server logs or CMS for why the page isn't rendering (contact your hosting provider or admin). 3. If the page was intentionally deleted: remove the URL from your sitemap.xml file and add a 301 redirect (permanent redirect) from the old URL to the most relevant replacement page (e.g., a general 'How to Buy' guide). 4. If the page should exist: restore it from backup or republish it through your CMS (WordPress, Shopify, custom platform, etc.). 5. After fixing, re-submit your updated sitemap to Google Search Console (Google → Search Console → Sitemaps → Re-submit). 6. Monitor Search Console for crawl errors over the next 2 weeks to confirm Google recrawls successfully. ### 25. Page returns 404: https://junglekingdomflower.com/cannabis-101/indica-vs-sativa-vs-hybrid/ - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/cannabis-101/indica-vs-sativa-vs-hybrid/ - **Rule:** `tier2.page.404` **What it means (plain English)** A page that your sitemap promises to search engines (cannabis-101/indica-vs-sativa-vs-hybrid/) is returning a 404 error, which means it doesn't exist. This sends conflicting signals to Google and Bing: your sitemap says 'this page is here,' but the server says 'nope, it's gone.' Both search engines and customers who click links will hit a dead end. **Why it matters for your business:** You're losing potential customers searching for educational cannabis content (a common entry point for new dispensary shoppers), and Google will gradually trust your sitemap less, reducing visibility for your other pages. **Technical root cause:** The page has been deleted, moved, or never published, but the sitemap was not updated to remove it. This creates a mismatch between what your site promises and what actually exists. **Recommended fix — step by step** 1. Log into your site admin or CMS dashboard and search for any page with 'indica-vs-sativa-vs-hybrid' in the URL; if it exists in draft or archived state, either publish it or delete it permanently 2. If the page was intentionally deleted, regenerate your XML sitemap (most platforms have a 'Regenerate Sitemap' button in SEO settings) to remove the dead URL 3. Visit https://junglekingdomflower.com/cannabis-101/indica-vs-sativa-vs-hybrid/ directly to confirm it now returns 200 (success) or a proper 301 redirect to a live page 4. Submit the updated sitemap to Google Search Console (search.google.com → your site → Sitemaps → Resubmit), and request a crawl of the affected URL 5. Check your analytics or backlink tools for any external links pointing to this URL and redirect them to the correct educational content page if one exists, or to your main cannabis education hub ### 26. 25 broken internal link(s) - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Moderate (1-3 hours) - **Business category:** seo - **Page URL:** https://junglekingdomflower.com/ - **Rule:** `tier2.links.broken` **What it means (plain English)** Your site has 25 internal links pointing to pages that no longer exist (returning HTTP 404 errors). Visitors clicking these links land on error pages instead of useful content, creating frustration. Search engines also waste crawl budget following dead links, which signals poor site maintenance and hurts your search ranking. **Why it matters for your business:** Broken links kill conversions—customers trying to learn about your products, read your blog, or contact you hit dead ends and may buy elsewhere. Search engines penalize sites with broken internal links, pushing you lower in results for local cannabis searches. **Technical root cause:** Pages were likely deleted, renamed, or moved without updating the links pointing to them. This commonly happens during site redesigns, CMS migrations, or when content is consolidated. **Recommended fix — step by step** 1. Run a full internal link audit: use a free tool like Screaming Frog SEO Spider (download, point at your domain) or Ahrefs Site Audit to identify all 404s and the pages linking to them. 2. For each broken link, decide: does the page still exist at a new URL (redirect needed), or was it genuinely deleted (remove the link)? 3. If pages were renamed/moved, set up 301 redirects from old URLs to new ones. In most CMS platforms (WordPress, Shopify, etc.), use a redirect plugin; for custom sites, ask your hosting provider to configure server-level redirects. 4. If pages were deleted, edit the linking pages and remove or update the dead links—prioritize high-traffic pages like your homepage, /order/, and /blog/. 5. After fixes are live, resubmit your sitemap to Google Search Console (follow Google's instructions for your CMS) to trigger a fresh crawl. 6. Set a quarterly reminder to re-run the audit and fix any new broken links. ### 27. A11y: Elements must only use permitted ARIA attributes (×3) - **Severity:** P1 | **Priority:** 🔴 DO FIRST - **Effort:** Quick win (< 30 min) - **Business category:** accessibility - **Page URL:** https://junglekingdomflower.com/ - **Rule:** `tier9.a11y.aria-prohibited-attr` **What it means (plain English)** Your site has star rating displays (showing "5 out of 5 stars") that use an ARIA label—a special HTML attribute meant to help screen readers—but the elements don't have a proper ARIA role assigned. This is like labeling a box without saying what kind of box it is. Screen readers get confused and may ignore or misread the label entirely. **Why it matters for your business:** Customers using screen readers cannot understand your product ratings, degrading their shopping experience and potentially violating accessibility law (ADA), which could expose you to legal risk or complaints. **Technical root cause:** The `.rstars` div elements have `aria-label` attributes but lack a `role` attribute. ARIA labels are only valid on elements with explicit roles (e.g., `role="img"`, `role="button"`); bare divs cannot use them. **Recommended fix — step by step** 1. Open your site's HTML source (View > View Page Source in Chrome/Firefox), search for 'rstars' and 'aria-label' to locate the star rating markup. 2. Add `role="img"` to each `.rstars` div element, e.g. `