Skip to content

🕸️ Spider: Fix invalid nested <main> tags in Actualités detail page#146

Open
kourdroid wants to merge 1 commit into
mainfrom
spider/fix-nested-main-actualites-3607392899607932353
Open

🕸️ Spider: Fix invalid nested <main> tags in Actualités detail page#146
kourdroid wants to merge 1 commit into
mainfrom
spider/fix-nested-main-actualites-3607392899607932353

Conversation

@kourdroid

Copy link
Copy Markdown
Owner

💡 What: Replaced a nested <main> element with a semantically correct <div> within the actualites/[slug]/page.tsx template, preserving all existing CSS classes and functionality. Added an explanatory SEO comment.

🎯 Why: The HTML5 specification dictates that a document should have only one visible <main> tag. The outer page structure in this repository already utilizes a global or layout-level <main> wrapper. Nesting an additional <main> tag for the content column creates invalid semantic HTML, which can confuse screen readers and search engine crawlers regarding the primary content structure.

📊 Impact: Restores valid HTML5 structure, ensuring Googlebot and other crawlers correctly identify the primary content area, improving indexation accuracy and accessibility for screen reader users.


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

Replaced the nested `<main>` element wrapping the article body with a `<div>` inside `src/app/(frontend)/[locale]/actualites/[slug]/page.tsx` to ensure valid HTML5 semantics and improve search engine crawlability. Also added an explanatory comment for the SEO benefit.

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

vercel Bot commented Jun 16, 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 16, 2026 10:12pm

@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.

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