Skip to content

๐Ÿ•ธ๏ธ Spider: [SEO] Convert CTA buttons to semantic Links in Intro and About blocks#155

Open
kourdroid wants to merge 1 commit into
mainfrom
spider/seo-link-crawlability-12415644462159812495
Open

๐Ÿ•ธ๏ธ Spider: [SEO] Convert CTA buttons to semantic Links in Intro and About blocks#155
kourdroid wants to merge 1 commit into
mainfrom
spider/seo-link-crawlability-12415644462159812495

Conversation

@kourdroid

Copy link
Copy Markdown
Owner

๐Ÿ’ก What: Replaced the inert, non-semantic <button> wrappers used for CTAs in src/blocks/Intro/Component.tsx and src/blocks/About/Component.tsx with Next.js <Link> components pointing to a safe relative path (/).
๐ŸŽฏ Why: Search engine crawlers (like Googlebot) do not interact with <button> elements or execute click handlers to discover content. They rely on standard <a> tags with href attributes to map out site architecture and follow links.
๐Ÿ“Š Impact: Improves crawlability by allowing search engines to discover and parse the intended navigation paths, converting what were previously SEO "dead ends" into functional internal links.


PR created automatically by Jules for task 12415644462159812495 started by @kourdroid

โ€ฆbout blocks

๐Ÿ’ก What: Replaced the inert, non-semantic `<button>` wrappers used for CTAs in `src/blocks/Intro/Component.tsx` and `src/blocks/About/Component.tsx` with Next.js `<Link>` components pointing to a safe relative path (`/`).
๐ŸŽฏ Why: Search engine crawlers (like Googlebot) do not interact with `<button>` elements or execute click handlers to discover content. They rely on standard `<a>` tags with `href` attributes to map out site architecture and follow links.
๐Ÿ“Š Impact: Improves crawlability by allowing search engines to discover and parse the intended navigation paths, converting what were previously SEO "dead ends" into functional internal links.

Co-authored-by: kourdroid <36898160+kourdroid@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

๐Ÿ‘‹ 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel

vercel Bot commented Jun 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
smatch Ready Ready Preview, Comment Jun 28, 2026 9:43pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant