Automated SEO fixes: resolve multiple H1 on /api and trim SSH meta description#258
Draft
petradonka wants to merge 1 commit into
Draft
Automated SEO fixes: resolve multiple H1 on /api and trim SSH meta description#258petradonka wants to merge 1 commit into
petradonka wants to merge 1 commit into
Conversation
…tion
- src/pages/api.astro: demote the server-rendered endpoint-index spec
title from <h1> to <h2> (and per-endpoint headings <h2> to <h3>) so
the page has a single H1 ("Warp & Oz HTTP API reference"), fixing the
multiple_h1 SEO warning while keeping a clean h1 > h2 > h3 outline.
- src/content/docs/terminal/warpify/ssh.mdx: trim the meta description
from 162 to 159 chars ("to get a" -> "for a") so it is no longer
truncated in search results.
Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Ran the
docs-seo-auditskill against the livedocs.warp.devsitemap (338 pages scanned, 9 issues found: 8 warnings, 1 info, 0 errors). This PR fixes the two clear, low-risk issues. The remaining warnings are intentionally-short titles already documented as exceptions in the skill, plus one borderline title flagged for human review (see below).Changes
src/pages/api.astro<h1>to<h2>, and the per-endpoint headings from<h2>to<h3>./apipage now has a single<h1>(Warp & Oz HTTP API reference), resolving themultiple_h1warning while preserving a cleanh1 > h2 > h3outline. This is a semantic-only change to a visually-hidden, crawler-facing section.src/content/docs/terminal/warpify/ssh.mdxto get a→for a) so it is no longer truncated in search results. Wording and keywords are unchanged otherwise.Not changed (intentional)
title_too_shortwarnings are allowlisted exceptions per the skill (intentionally short titles where sidebar/section context disambiguates):changelog/index.mdx,guides/index.mdx,reference/cli/artifacts.mdx,terminal/windows/tab-configs.mdx,terminal/windows/tabs.mdx,terminal/windows/split-panes.mdx.agent-platform/cloud-agents/agents.mdx(Cloud agents | Warp, 19/20 chars) — flagged for human review rather than auto-renamed. It's a proper feature name only 1 char under the soft threshold, has sidebar context (Oz Cloud Agents & Orchestration>Agents), and any rename risks colliding with the siblingCloud agents overviewpage. Per the skill's caution against over-eager prefixing, it was left as-is.Validation
/apipage now has exactly one<h1>and balancedh1 > h2 > h3heading tags.npm run buildwas not run because dependencies are not installed in this environment; changes are syntactically trivial (a YAML string trim and balanced heading-tag swaps).Conversation: https://app.warp.dev/conversation/cfa2469b-c80c-41c8-b6c9-1cc38cd76535
Run: https://oz.warp.dev/runs/019f02ba-77d2-764f-99c4-caf605380dd3
This PR was generated with Oz.