🕸️ Spider: [SEO improvement] Replace CTA buttons with semantic links#159
🕸️ Spider: [SEO improvement] Replace CTA buttons with semantic links#159kourdroid wants to merge 1 commit into
Conversation
…t.js Link elements Replaced meaningless `<button>` elements in `IntroBlock` and `AboutBlock` with semantic Next.js `<Link>` elements. Because CTA URLs are not always defined via CMS props for these blocks, the links fallback to `href="/"` to ensure the components remain reusable without risking 404s, while dramatically improving crawlability for search engines. Co-authored-by: kourdroid <36898160+kourdroid@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 participant
💡 What: Replaced meaningless
<button>elements lackingonClickfunctionality with semantic Next.js<Link href="/">elements insrc/blocks/Intro/Component.tsxandsrc/blocks/About/Component.tsx.🎯 Why: Buttons that act as links but are not semantic anchor (
<a>) elements cannot be crawled by search engines, preventing bots from discovering and following important Call-To-Action (CTA) paths.📊 Impact: Ensures search engines can successfully crawl CTA elements, improving internal linking structure and the discoverability of related content. Using
/as a fallback ensures we do not introduce hardcoded 404s in generic, CMS-driven UI components.PR created automatically by Jules for task 14597359019981112299 started by @kourdroid