Skip to content

Automated SEO fixes: resolve multiple H1 headings on open-source-licenses page#39

Closed
petradonka wants to merge 1 commit intomainfrom
automated-seo-fixes/multiple-h1-open-source-licenses
Closed

Automated SEO fixes: resolve multiple H1 headings on open-source-licenses page#39
petradonka wants to merge 1 commit intomainfrom
automated-seo-fixes/multiple-h1-open-source-licenses

Conversation

@petradonka
Copy link
Copy Markdown
Contributor

Summary

Fix multiple_h1 SEO warning on the Open Source Licenses page (/support-and-community/community/open-source-licenses/).

Problem

The page had 10 H1 headings detected by crawlers. The root cause was a blank line between </summary> and <pre> inside a <details> block, which caused the MDX compiler to switch from JSX mode to markdown mode. License text containing Setext-style heading markers (=== underlines) and ATX headings (#) was then parsed as HTML <h1> elements instead of being treated as preformatted text.

Fix

Removed the blank line between </summary> and <pre> so MDX treats the entire <details>/<summary>/<pre> block as a single JSX expression, preventing markdown parsing of the license content.

SEO audit results (314 pages scanned, 7 warnings)

Fixed (1):

  • multiple_h1 on open-source-licenses.mdx — 10 H1 headings → 1

Allowlisted (5):

  • title_too_short: Changelog, Guides, Tabs, Split panes, Tab Configs (intentionally short per exceptions list)

Unfixable (1):

  • missing_h1 on /api/ — auto-generated page, no local source file

Conversation: https://app.warp.dev/conversation/1a48a8ae-1020-4e5e-8188-1b743786bd55
Run: https://oz.warp.dev/runs/019e0662-d27f-74bb-a14c-bb81e85f890c

This PR was generated with Oz.

… leakage

The blank line between </summary> and <pre> caused MDX to switch to
markdown mode and parse license text (Setext === underlines, ATX #
headings) as HTML H1 elements, producing 10 H1 headings on the page.

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label May 8, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented May 8, 2026

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

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment May 8, 2026 7:06am

Request Review

@petradonka petradonka marked this pull request as ready for review May 8, 2026 07:15
@petradonka petradonka requested a review from rachaelrenk May 8, 2026 07:53
@rachaelrenk
Copy link
Copy Markdown
Contributor

Closing this PR — the conflict is because main has since replaced the <details>/<summary>/<pre> HTML block with a markdown code fence (```text`), which also removed the blank line this PR targeted. The fix is no longer needed.

@rachaelrenk rachaelrenk closed this May 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants