<!doctype html>
<html lang="en">
  <head>
<!--SEO-->
<title>Buy a Franchise | Franchise Businesses for Sale | Franchise Grade</title>
<meta name="title" content="Buy a Franchise | Franchise Businesses for Sale | Franchise Grade">
<meta name="description" content="Find franchise opportunities by industry, location, or brand. Compare franchise businesses for sale and discover the right investment with data-driven insights.">
<link rel="preload" as="image" href="https://mvp.franchisegrade.com/hs-fs/hubfs/Website/Home/4.png?width=1000&name=4.png" imagesrcset="https://mvp.franchisegrade.com/hs-fs/hubfs/Website/Home/4.png?width=400&name=4.png 400w, https://mvp.franchisegrade.com/hs-fs/hubfs/Website/Home/4.png?width=800&name=4.png 800w, https://mvp.franchisegrade.com/hs-fs/hubfs/Website/Home/4.png?width=1000&name=4.png 1000w" imagesizes="(max-width: 768px) 100vw, 1000px" fetchpriority="high">
<link rel="canonical" href="https://www.franchisegrade.com/">
<meta property="og:title" content="Buy a Franchise | Franchise Businesses for Sale | Franchise Grade">
<meta property="og:description" content="Find franchise opportunities by industry, location, or brand. Compare franchise businesses for sale and discover the right investment with data-driven insights.">
<meta property="og:url" content="https://www.franchisegrade.com/">
<meta property="og:type" content="website">
<meta property="og:site_name" content="Franchise Grade">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Buy a Franchise | Franchise Businesses for Sale | Franchise Grade">
<meta name="twitter:description" content="Find franchise opportunities by industry, location, or brand. Compare franchise businesses for sale and discover the right investment with data-driven insights.">
<script type="application/ld+json">{"@context":"https://schema.org","@type":"WebSite","name":"10,000+ franchise buyers chose their business with confidence, trusting us","description":"Find franchise opportunities by industry, location, or brand. Compare franchise businesses for sale and discover the right investment with data-driven insights.","url":"https://www.franchisegrade.com/","publisher":{"@type":"Organization","name":"Franchise Grade","url":"https://www.franchisegrade.com"}}</script>
<!--/SEO-->

<!--
  Google Consent Mode v2 — REQUIRED for GDPR/CCPA compliance (2026-05-21).
  Sets default consent state to DENIED before any tags fire. GTM tags
  configured with consent gating will then only execute if the user
  explicitly grants consent via the CookieBanner component.

  Why this matters: without Consent Mode, GTM and GA fire on first page
  load BEFORE the user can accept/reject cookies — a violation of
  GDPR (EU), CCPA/CPRA (California), and similar regional laws. Past
  exposure: every visit prior to consent was an un-consented data event.

  After this default is set, CookieBanner.tsx will call
  `gtag('consent', 'update', {...})` when the user accepts or rejects,
  flipping the relevant categories to 'granted'.

  Reference: https://developers.google.com/tag-platform/security/guides/consent
-->
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){ dataLayer.push(arguments); }
  // Consent Mode v2 defaults (laura/restore-ga-tracking).
  //
  // Previously analytics_storage defaulted to "denied" → GA4 dropped EVERY
  // pageview unless the user clicked Accept All on the cookie banner. Since
  // most US/CA visitors bounce without interacting with banners, GA + Search
  // Console showed near-zero traffic. Fix: split the consent categories by
  // jurisdiction:
  //
  //   - analytics_storage  → GRANTED by default. CCPA (California) and PIPEDA
  //     (Canada) are opt-OUT regimes — analytics doesn't require prior opt-in.
  //     The cookie banner's "Reject All" still flips this to denied, honoring
  //     opt-out requests.
  //   - ad_storage / ad_user_data / ad_personalization → DENIED. Ads remain
  //     gated behind explicit user accept (GDPR-safer, future-proof for any
  //     EU traffic, and matches Google Ads' own consent requirements).
  //   - functionality / security → granted (necessary cookies, never gated).
  //   - personalization_storage → denied.
  //
  // Net effect: GA4 + GTM analytics fire immediately for every visitor;
  // Google Ads conversions still wait for explicit consent. CookieBanner's
  // saveConsent already calls gtag('consent','update',{...}) which correctly
  // updates whichever categories the user accepts/rejects.
  gtag('consent', 'default', {
    'ad_storage': 'denied',
    'ad_user_data': 'denied',
    'ad_personalization': 'denied',
    'analytics_storage': 'granted',
    'functionality_storage': 'granted',
    'personalization_storage': 'denied',
    'security_storage': 'granted',
    'wait_for_update': 500
  });
</script>

<!--
  Google Tag Manager — load-event-deferred (laura/restore-tracking).
  An earlier interaction-gated load (laura/core-web-vitals-v2) hurt
  tracking too much: bouncers who left in <7s without scrolling/clicking
  were never tracked → GA + Search Console showed traffic collapsed.

  New strategy: load GTM AFTER the `window.load` event fires (page is
  fully painted + LCP is done) using requestIdleCallback to spread the
  ~600 KB of GTM CPU work across idle frames. Hard fallback at 5s in
  case `load` is delayed by polling/slow images. Result:
    - LCP/FCP/CLS unaffected (GTM doesn't run until after load)
    - TBT lightly affected (GTM ~600 ms CPU happens after paint)
    - page_view fires for every real visitor that waits for load
    - dataLayer.push({'gtm.start'}) still fires SYNCHRONOUSLY at parse,
      so any auto-events queued before GTM loads are preserved.
  Consent Mode v2 (set above) still gates ad/analytics tags inside GTM
  behind CookieBanner accept.
-->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
  new Date().getTime(),event:'gtm.js'});
  var loaded=false;
  function loadGtm(){if(loaded)return;loaded=true;
    var f=d.getElementsByTagName(s)[0],
    j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
    'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);}
  function scheduleLoad(){
    if('requestIdleCallback' in w){w.requestIdleCallback(loadGtm,{timeout:2000});}
    else{setTimeout(loadGtm,100);}
  }
  if(d.readyState==='complete'){scheduleLoad();}
  else{w.addEventListener('load',scheduleLoad,{once:true});}
  setTimeout(loadGtm,5000); // hard fallback if load event is delayed
  })(window,document,'script','dataLayer','GTM-5H685J');</script>
  <!-- End Google Tag Manager -->

  <meta name="google-site-verification" content="mnKX4_22jG_3eBlB5q-UJ4i6oBAtzfa-d6lZzWjnWKM" />

    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=5.0" />
    <!--
      Robots directive is intentionally NOT hardcoded here. It is emitted
      per-page by:
        • Static build (per-page prerender)  — scripts/generate-seo-pages.mjs
          emits `<meta name="robots" content="noindex, follow">` only for
          thin-content brand pages (see src/utils/seoIndexability.ts).
        • Runtime React                       — src/components/seo/DynamicHead.tsx
          emits the same directive once Helmet hydrates.
      Hardcoding `<meta name="robots" content="index, follow">` here caused
      a duplicate-meta-robots bug: the prerender's `noindex` for thin pages
      sat next to a default `index, follow`, sending Google conflicting
      signals (GSC: "No: 'noindex' detected" but validators warned of
      duplicate robots). Removed 2026-05-15.
    -->
    <meta name="theme-color" content="#203D57" />
    <meta name="author" content="Franchise Grade" />

    <!--
      systems.json preload removed 2026-06-24 (laura/core-web-vitals-v2).
      It was preloading 1.3MB on every page, but only Browse/Dashboard/
      AddFranchiseSheet actually consume it via ensureSystemCardsLoaded().
      Brand, sector, learn, and home pages were paying ~1MB of mobile
      bandwidth for nothing — contributing to the Lighthouse mobile timeout
      on SystemDetail. The 3 pages that DO use it can preload via their
      route component, or just fetch on demand (already does via
      systems-list service).
    -->

    <!--
      <title> is intentionally NOT hardcoded here (same reason as <meta robots>
      above). The hardcoded title used to ship with every served HTML response,
      causing HubSpot's SEO scanner + Google's pre-JS index pass to see the
      homepage title on every non-prerendered page → "duplicate title" + "multiple
      canonical links" flags (HubSpot audit 2026-05-18, 118 pages affected).
      Title is now emitted per-page by:
        • Static build  — scripts/generate-seo-pages.mjs adds <title> to each
                          prerendered SEO snippet (injected by inject-seo.mjs).
        • Runtime React — src/components/seo/DynamicHead.tsx via react-helmet-async.
      Removed 2026-05-19.
    -->
    <!--
      <meta name="description"> is intentionally NOT hardcoded here (same
      reason as <title> and <meta robots> above).
      The hardcoded description shipped in EVERY served HTML response,
      causing every page to end up with TWO <meta name="description"> tags:
      (1) this generic fallback + (2) the page-specific description injected
      by scripts/generate-seo-pages.mjs → scripts/inject-seo.mjs.
      Google Lighthouse + HubSpot SEO Grader + Screaming Frog all flagged
      "duplicate meta description" on 1,282 indexed pages. Google picks one
      arbitrarily → sometimes the weaker generic one shows in SERPs.
      Description is now emitted per-page by:
        • Static build   — scripts/generate-seo-pages.mjs
        • Runtime React  — src/components/seo/DynamicHead.tsx
      Removed 2026-06-25 (laura/seo-audit-2026-06).
    -->

    <!-- Open Graph -->
    <meta property="og:title" content="Franchise Grade - Find Your Perfect Franchise Match" />
    <meta property="og:description" content="Investor-first franchise matchmaking. Build your profile, get smart matches, compare franchises, and connect with advisors." />
    <meta property="og:type" content="website" />
    <meta property="og:locale" content="en_US" />
    <meta property="og:site_name" content="Franchise Grade" />
    <meta property="og:image" content="https://www.franchisegrade.com/og-image.png" />
    <meta property="og:image:width" content="1200" />
    <meta property="og:image:height" content="630" />
    <meta property="og:image:type" content="image/png" />

    <!-- Twitter Card -->
    <meta name="twitter:card" content="summary_large_image" />
    <meta name="twitter:site" content="@FranchiseGrade" />
    <meta name="twitter:image" content="https://www.franchisegrade.com/og-image.png" />

    <!-- Favicon + Icons -->
    <link rel="icon" type="image/png" href="/favicon.png" />
    <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" />

    <!--
      Preconnect strategy (laura/core-web-vitals-v2):
      PSI's "Unused preconnect" warnings appear when an origin's connection
      isn't reused inside the ~10s LCP-observation window. We keep
      preconnects ONLY for origins guaranteed to be hit during the critical
      path on every page (fonts + Font Awesome CDN). Image / chat / system-
      logo origins get dns-prefetch only — same DNS resolution benefit,
      no "unused" warning when they're not hit immediately.

      Specifically:
      - mvp.franchisegrade.com: home LCP image is preloaded statically; the
        preload opens its own connection so the extra preconnect was
        redundant. Kept as dns-prefetch for non-LCP images.
      - assets.franchisegrade.com: only system pages load logos from here
        (home/learn never touch it). dns-prefetch only.
      - js.usemessages.com: HubSpot chat is interaction-gated → never hit
        during first-paint critical path. dns-prefetch only.
    -->
    <link rel="preconnect" href="https://cdnjs.cloudflare.com" crossorigin />
    <link rel="preconnect" href="https://fonts.googleapis.com" />
    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
    <link rel="dns-prefetch" href="https://mvp.franchisegrade.com" />
    <link rel="dns-prefetch" href="https://assets.franchisegrade.com" />
    <link rel="dns-prefetch" href="https://cdnjs.cloudflare.com" />
    <link rel="dns-prefetch" href="https://js.usemessages.com" />

    <!--
      Manrope — non-blocking stylesheet load.
      PERF fix (laura/core-web-vitals-v2, agent2): the old pattern was a
      preload + stylesheet pair, but the preload was missing the JS swap
      handler so the &lt;link rel="stylesheet"&gt; on the next line was still
      render-blocking. PageSpeed mobile showed 750ms blocked. The
      media="print" onload="this.media='all'" pattern fetches the CSS
      asynchronously, then applies it once loaded. Manrope already has
      &display=swap so the brief system-font fallback is unnoticeable.
      The &lt;noscript&gt; fallback ensures users with JS disabled still get
      the font (sync, blocking — acceptable for that audience).
    -->
    <link rel="stylesheet" media="print" onload="this.media='all'"
          href="https://fonts.googleapis.com/css2?family=Manrope:wght@400;500;600;700&display=swap" />
    <noscript><link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Manrope:wght@400;500;600;700&display=swap" /></noscript>

    <!--
      Font Awesome — non-blocking stylesheet load (same pattern as Manrope).
      PERF fix (laura/core-web-vitals-v2, agent2): previously
      render-blocking ~1,050ms on mobile per PageSpeed. Above-the-fold
      icons (Navbar bookmark, HeroSection) briefly render as empty boxes
      for ~50-100ms before the FA CSS arrives; this FOIT is acceptable
      for decorative iconography and reclaims ~1s of LCP.
      &lt;noscript&gt; fallback keeps icons usable for JS-disabled users.
    -->
    <link rel="stylesheet" media="print" onload="this.media='all'"
          href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css"
          integrity="sha512-DTOQO9RWCH3ppGqcWaEA1BIZOC6xxalwEsw9c2QQeAIftl+Vegovlnee1c9QX4TctnWMn13TZye+giMm8e2LwA=="
          crossOrigin="anonymous" referrerPolicy="no-referrer" />
    <noscript><link rel="stylesheet"
          href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css"
          integrity="sha512-DTOQO9RWCH3ppGqcWaEA1BIZOC6xxalwEsw9c2QQeAIftl+Vegovlnee1c9QX4TctnWMn13TZye+giMm8e2LwA=="
          crossOrigin="anonymous" referrerPolicy="no-referrer" /></noscript>

    <!--
      HubSpot Tracking Code — load-event-deferred (laura/restore-tracking).
      Mirrors the GTM pattern above. Previous interaction-gated load was
      too aggressive (lost tracking on pure bouncers → HubSpot reports
      went blank). New strategy: load HubSpot AFTER `window.load` using
      requestIdleCallback. Captures every real visitor that completes
      the initial page load. HubSpot then handles its own page_view,
      forms, and chat — they're queued via `_hsq` if pushed before the
      script loads, so any code that calls window._hsq.push(...) early
      still works.
    -->
    <script>
      (function () {
        /*
          Chat widget deferral (laura/perf-quick-wins): the conversations
          widget is BY FAR the heaviest thing HubSpot loads — visitor.js
          (~360 KB), whisper-core, AND Google reCAPTCHA enterprise
          (~1.1 MB, its spam protection) — together ~1.5s of mobile CPU in
          Lighthouse. `loadImmediately:false` keeps all of that out of the
          initial load; the widget loads on the visitor's FIRST interaction
          (scroll/tap/key), which real users produce within seconds, so the
          chat bubble appears effectively as before.

          IMPORTANT: tracking is NOT interaction-gated — that was tried
          before (laura/restore-tracking) and bouncer page views vanished
          from HubSpot reports. The tracker itself still loads on idle
          below; only the chat UI defers.
        */
        window.hsConversationsSettings = { loadImmediately: false };
        var chatWanted = false;
        /*
          No HubSpot chat on MOBILE (Laura 2026-07-11). The chat widget's
          visitor.js (~360 KB) + reCAPTCHA enterprise (~1.1 MB) are the single
          heaviest mobile payload, and the bubble crowds small screens. Gate the
          load behind the md breakpoint (≤767px = the site's mobile cutoff, same
          as MobileBottomNav / chat-clearance CSS) so phones never load OR show
          it; desktop is unchanged. Evaluated at interaction time, so a
          resize/rotate up to desktop width still gets chat. If matchMedia is
          unavailable (ancient browsers), default to allowing chat (safe).
        */
        function chatAllowed() {
          return !window.matchMedia || !window.matchMedia('(max-width: 767px)').matches;
        }
        function loadChat() {
          if (!chatAllowed()) return;
          chatWanted = true;
          if (window.HubSpotConversations) {
            window.HubSpotConversations.widget.load();
          }
        }
        window.hsConversationsOnReady = [function () {
          if (chatWanted) window.HubSpotConversations.widget.load();
        }];
        ['scroll', 'pointerdown', 'touchstart', 'keydown'].forEach(function (evt) {
          window.addEventListener(evt, loadChat, { once: true, passive: true });
        });

        var loaded = false;
        function loadHubSpot() {
          if (loaded) return;
          loaded = true;
          if (document.getElementById('hs-script-loader')) return;
          var s = document.createElement('script');
          s.type = 'text/javascript';
          s.id = 'hs-script-loader';
          s.async = true;
          s.defer = true;
          s.src = 'https://js.hs-scripts.com/3867240.js';
          document.head.appendChild(s);
        }
        function scheduleLoad() {
          if ('requestIdleCallback' in window) {
            window.requestIdleCallback(loadHubSpot, { timeout: 2000 });
          } else {
            setTimeout(loadHubSpot, 100);
          }
        }
        if (document.readyState === 'complete') {
          scheduleLoad();
        } else {
          window.addEventListener('load', scheduleLoad, { once: true });
        }
        setTimeout(loadHubSpot, 5000); // hard fallback
      })();
    </script>
    <script type="module" crossorigin src="/assets/index-DC9vnlC-.js"></script>
    <link rel="stylesheet" crossorigin href="/assets/index-YX7F_GKK.css">
  </head>

  <body>

<!-- Google Tag Manager (noscript) -->
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-5H685J"
  height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
  <!-- End Google Tag Manager (noscript) -->



    <div id="root"></div>
  </body>
</html>
