From c875d2dea98018f71bcf6c04609215eb581a74a8 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Wed, 10 Jun 2026 22:11:31 +0000
Subject: [PATCH] =?UTF-8?q?=F0=9F=95=B8=EF=B8=8F=20Spider:=20Convert=20CTA?=
 =?UTF-8?q?=20button=20to=20Next.js=20Link=20in=20KineticBlades?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Replaced a meaningless `<button>` element with a semantic Next.js `<Link>` component for the "Découvrir la solution" CTA in `KineticBlades.tsx`. This improves search engine crawlability by providing an explicit `href` that bots can follow.

Co-authored-by: kourdroid <36898160+kourdroid@users.noreply.github.com>
---
 .jules/spider.md                           | 3 +++
 src/components/expertise/KineticBlades.tsx | 6 ++++--
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/.jules/spider.md b/.jules/spider.md
index 572ac48..8f0e4cc 100644
--- a/.jules/spider.md
+++ b/.jules/spider.md
@@ -10,3 +10,6 @@
 ## 2024-05-19 - Typechecking JSON-LD Date Properties
 **Learning:** When passing potentially null date fields (like `publishedAt`, `updatedAt`) from Payload CMS to jsonLd generator functions, using the fields directly can cause strict TypeScript compilation failures since the schemas explicitly expect `string | undefined` and not `null`.
 **Action:** Always use the logical OR operator with `undefined` (e.g., `datePublished: post.publishedAt || undefined`) when passing date properties to JSON-LD generator functions to satisfy strict type requirements and prevent build regressions.
+## 2024-06-10 - Replace meaningless <button> wrappers with semantic <Link> tags
+**Learning:** In sections with Call to Actions (CTAs) acting as navigation but using `<button>` wrappers without explicit `href` or `onClick` (such as in `KineticBlades.tsx`), search engine crawlers are unable to follow the pseudo-links, severely impacting indexability of the deeper content like `/solutions`.
+**Action:** Always use semantic `<Link>` components with an explicit `href` instead of `<button>` tags for interactive elements that trigger navigation, in order to maximize crawlability.
diff --git a/src/components/expertise/KineticBlades.tsx b/src/components/expertise/KineticBlades.tsx
index 8f00877..330e28c 100644
--- a/src/components/expertise/KineticBlades.tsx
+++ b/src/components/expertise/KineticBlades.tsx
@@ -3,6 +3,7 @@
 import React, { useRef, useState } from 'react'
 import { Plant, Bed, UsersThree, ArrowRight } from '@phosphor-icons/react/dist/ssr'
 import clsx from 'clsx'
+import Link from 'next/link'
 import gsap from 'gsap'
 import { useGSAP } from '@gsap/react'
 
@@ -247,10 +248,11 @@ export function KineticBlades() {
                                     </div>
 
                                     {/* CTA */}
-                                    <button className="group mt-8 flex items-center gap-2 font-mono text-xs font-bold uppercase tracking-widest text-white transition-colors hover:text-[#FFAA00]">
+                                    {/* SEO: Using Next.js <Link> with href instead of meaningless <button> improves crawlability for search engines */}
+                                    <Link href="/solutions" className="group mt-8 flex items-center gap-2 font-mono text-xs font-bold uppercase tracking-widest text-white transition-colors hover:text-[#FFAA00]">
                                         Découvrir la solution
                                         <ArrowRight className="transition-transform group-hover:translate-x-1" />
-                                    </button>
+                                    </Link>
                                 </div>
                             </div>