SEO: free extension scanner positioning + live "extensions scanned" count (ExtensionShield#232)

* Reposition ExtensionShield SEO content

* SEO: free extension scanner positioning + live "extensions scanned" count

Homepage & landing SEO (Phase 1):
- Retitle the homepage to target "free Chrome extension scanner" while keeping
  the security/governance positioning (title, meta, keywords, eyebrow, H1,
  subhead, trust H2).
- Mobile hero now renders the real H1 + a working scan input instead of a
  "check on desktop" stub (mobile-first indexing).
- Add /free-extension-scanner landing page via the SeoLongFormPage template,
  with FAQPage + BreadcrumbList + SoftwareApplication (price 0) JSON-LD and
  internal links only (no competitor backlinks).
- Wire the page into nav (Product), footer, homepage CTA, routes, and sitemap.
- Add "is it free" / "no install" entries to the homepage FAQ schema.
- Remove 10 stray macOS " 2" duplicate files.

Live "extensions scanned" count:
- Homepage stat now reads the real total from /statistics
  (databaseService.getStatistics) instead of a hardcoded 100.
- Supabase get_statistics uses an exact count for total_scans so the number is
  accurate regardless of the default PostgREST row cap.

Also carries the in-progress SEO repositioning of the compare/landing pages and
blog content on this branch.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Stanzin <snorzang65@gmail.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Author: 3 people

frontend/public/sitemap.xml

@@ -570,9 +570,9 @@ body {
 }
 
 .nav-dropdown-menu {
-  position: absolute;
-  top: calc(100% + 0.25rem);
-  left: 0;
+  position: fixed;
+  top: var(--extensionshield-header-offset);
+  left: auto;
   min-width: 280px;
   max-width: calc(100vw - 2rem);
   background: var(--extensionshield-bg-card);
@@ -587,13 +587,13 @@ body {
   display: flex;
   flex-direction: column;
   gap: 0.5rem;
-  margin-top: 0.25rem;
+  margin-top: 0;
 
   /* Categorized dropdown (e.g. Research = Research + Resources) – centered on viewport */
   &--sections {
     position: fixed;
     left: 50%;
-    top: calc(var(--extensionshield-header-height) + 0.5rem);
+    top: var(--extensionshield-header-offset);
     transform: translateX(-50%);
     animation: megamenuEnterCentered 0.2s ease;
     min-width: 320px;

frontend/src/App.scss

@@ -158,7 +158,7 @@
 .app-footer__groups {
   display: grid;
   grid-template-columns: repeat(2, minmax(0, 150px));
-  gap: 0.75rem 1.25rem;
+  gap: 0.75rem 3rem;
 
   @media (max-width: 600px) {
     grid-template-columns: 1fr;

frontend/src/components/Footer.scss

@@ -274,15 +274,6 @@ export default function HowWeProtectYouSection() {
               </div>
             </div>
 
-            <motion.p
-              className="how-protect-footnote"
-              initial={reduced ? false : { opacity: 0 }}
-              whileInView={reduced ? {} : { opacity: 1 }}
-              viewport={{ once: true, amount: 0.5 }}
-              transition={{ duration: 0.35, delay: stagger * 7 }}
-            >
-              Just because it's in the Chrome store doesn't mean it's safe.
-            </motion.p>
           </div>
         </div>
       </div>

frontend/src/components/home/HowWeProtectYouSection.jsx

@@ -4,14 +4,14 @@
 
 .how-protect-section {
   position: relative;
-  padding: var(--landing-section-padding-y-top) var(--landing-section-padding-x) var(--landing-section-padding-y-bottom);
+  padding: var(--hp-section-py) var(--hp-px);
   background: transparent;
 }
 
 .how-protect-container {
-  max-width: var(--landing-section-inner-max);
+  max-width: var(--hp-max);
   margin: 0 auto;
-  padding: 0 4rem;
+  padding: 0;
   box-sizing: border-box;
 }
 

frontend/src/components/home/HowWeProtectYouSection.scss

@@ -446,5 +446,78 @@ export const blogPosts = [
   }
 ];
 
+export const blogStrategyTopics = [
+  {
+    title: "How to Check if a Chrome Extension Is Safe Before Installing",
+    longTailKeyword: "how to check if chrome extension is safe",
+    intent: "Practical pre-install safety checklist for users who are one search away from installing an extension.",
+    featuredSnippetAngle: "Answer with a numbered checklist: permissions, publisher, reviews, privacy policy, update history, and risk score.",
+    internalLinks: ["/scan", "/extension-security", "/extension-risk-score", "/blog"]
+  },
+  {
+    title: "What Permissions Are Dangerous in Chrome Extensions?",
+    longTailKeyword: "dangerous chrome extension permissions",
+    intent: "Explain high-risk permissions and help users understand whether requested access is justified.",
+    featuredSnippetAngle: "List dangerous permissions with one-sentence risk explanations.",
+    internalLinks: ["/extension-permissions", "/scan", "/extension-risk-score", "/blog"]
+  },
+  {
+    title: "Can Chrome Extensions Steal Data?",
+    longTailKeyword: "can chrome extensions steal data",
+    intent: "Answer a security fear directly and show how permissions, page access, and network calls create exposure.",
+    featuredSnippetAngle: "Lead with a direct yes/no answer, then list the main data paths.",
+    internalLinks: ["/extension-security", "/extension-permissions", "/scan", "/blog"]
+  },
+  {
+    title: "How Hackers Use Browser Extensions to Steal Data",
+    longTailKeyword: "how hackers use browser extensions to steal data",
+    intent: "Educate users and security teams on attack chains without hype.",
+    featuredSnippetAngle: "Break the attack into install, permission, collection, exfiltration, and update abuse steps.",
+    internalLinks: ["/extension-security", "/scan", "/extension-risk-score", "/blog"]
+  },
+  {
+    title: "Chrome Extension Scanner vs Extension Governance Platform",
+    longTailKeyword: "chrome extension scanner vs governance platform",
+    intent: "Capture scanner traffic while moving readers toward the larger governance category.",
+    featuredSnippetAngle: "Use a two-column scanner vs governance comparison.",
+    internalLinks: ["/extension-governance", "/extension-security", "/scan", "/blog"]
+  },
+  {
+    title: "Top Risky Chrome Extension Patterns to Watch in 2026",
+    longTailKeyword: "risky chrome extensions 2026",
+    intent: "Rank for annual risk queries without publishing an unsupported blacklist.",
+    featuredSnippetAngle: "List risky patterns such as all-site access, data collection, obfuscation, ownership changes, and suspicious updates.",
+    internalLinks: ["/scan", "/extension-permissions", "/extension-risk-score", "/blog"]
+  },
+  {
+    title: "Spin.ai vs ExtensionShield",
+    longTailKeyword: "Spin.ai alternative",
+    intent: "Capture high-intent comparison traffic from buyers evaluating browser extension security tools.",
+    featuredSnippetAngle: "Neutral best-fit comparison table by workflow.",
+    internalLinks: ["/compare/spin-ai", "/extension-governance", "/scan", "/blog"]
+  },
+  {
+    title: "CRXcavator vs ExtensionShield",
+    longTailKeyword: "CRXcavator alternative",
+    intent: "Capture users looking for a current extension risk scoring and governance workflow.",
+    featuredSnippetAngle: "Compare historical risk scoring criteria with current governance requirements.",
+    internalLinks: ["/compare/crxcavator", "/extension-risk-score", "/scan", "/blog"]
+  },
+  {
+    title: "How to Build a Chrome Extension Allowlist Policy",
+    longTailKeyword: "chrome extension allowlist policy",
+    intent: "Help enterprise security teams create a repeatable governance process.",
+    featuredSnippetAngle: "Give policy tiers: allow, monitor, request fix, block.",
+    internalLinks: ["/extension-governance", "/extension-risk-score", "/scan", "/blog"]
+  },
+  {
+    title: "How to Audit a CRX or ZIP Chrome Extension Before Release",
+    longTailKeyword: "audit CRX ZIP chrome extension before release",
+    intent: "Convert developers who need pre-release extension security checks.",
+    featuredSnippetAngle: "Checklist for manifest, permissions, content scripts, service worker, network access, and privacy disclosures.",
+    internalLinks: ["/scan/upload", "/extension-security", "/extension-permissions", "/blog"]
+  }
+];
+
 export const getBlogPostBySlug = (slug) =>
   blogPosts.find((p) => p.slug === slug) || null;

frontend/src/data/blogPosts.js

@@ -15,8 +15,14 @@ export const topNavItems = [
     category: NAV_CATEGORIES.PRODUCT,
     label: "Scan",
     path: "/scan",
-    matchPaths: ["/scan", "/extension-security", "/extension-risk-score", "/extension-permissions"],
+    matchPaths: ["/scan", "/free-extension-scanner", "/extension-security", "/extension-risk-score", "/extension-permissions"],
     dropdownItems: [
+      {
+        icon: "🔎",
+        label: "Free Extension Scanner",
+        description: "Check any Chrome extension by URL",
+        path: "/free-extension-scanner"
+      },
       {
         icon: "🛡️",
         label: "Security Platform",
@@ -56,7 +62,7 @@ export const topNavItems = [
           { icon: "📋", label: "Case Studies", description: "Real-world analysis", path: "/research/case-studies" },
           { icon: "⚙️", label: "How We Score", description: "How we score risk", path: "/research/methodology" },
           { icon: "benchmarks", label: "Benchmarks", description: "Industry trends & scoring", path: "/research/benchmarks" },
-          { icon: "compare", label: "Compare Scanners", description: "ExtensionShield vs alternatives", path: "/compare" }
+          { icon: "compare", label: "Compare Tools", description: "Security tool comparison", path: "/compare" }
         ]
       },
       {
@@ -157,6 +163,7 @@ export const footerConfig = {
     {
       heading: "Product",
       links: [
+        { label: "Free Extension Scanner", path: "/free-extension-scanner" },
         { label: "Risk Check (Free)", path: "/scan" },
         { label: "Private Build Audit (Pro)", path: "/scan/upload" },
         { label: "Extension Security", path: "/extension-security" },