feat(seo): Update Cloud Product Page H2 and meta description#13355
feat(seo): Update Cloud Product Page H2 and meta description#13355balpreetgrowthnatives wants to merge 2 commits into
Conversation
dosubot
Bot
added
the
size:XS
🎭 Playwright: ⏳ Running...🎨 Storybook: 🚧 Building... |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThis PR updates cloud landing page copy by removing a ReasonSection prop, changing the ChangesCloud Landing Page Copy Updates
Estimated code review effort: 2 (Simple) | ~5 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 6✅ Passed checks (6 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
apps/website/src/i18n/translations.ts (1)
903-906: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueRemove the unused
cloud.reason.headingHighlightentry.
apps/website/src/components/product/cloud/ReasonSection.vueno longer passesheading-highlight-key, and there are no remaining code references to this translation key, so it can be dropped to keep the dictionary aligned.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/website/src/i18n/translations.ts` around lines 903 - 906, Remove the unused cloud.reason.headingHighlight translation entry from the translations map in translations.ts. The key is no longer referenced by ReasonSection.vue or anywhere else, so delete that object from the dictionary and keep the remaining translation keys unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/website/src/i18n/translations.ts`:
- Around line 899-902: The heading text for cloud.reason.heading asks about
concurrent job capacity, but the surrounding reason items do not provide any
concurrency limit, so align the copy with the actual content. Either update
cloud.reason.heading to remove the concurrency question, or add a reason entry
that explicitly states the plan-based concurrency limits by referencing the
existing pricing.plan.* feature data so the section answers what it asks.
In `@apps/website/src/pages/cloud/index.astro`:
- Line 15: The meta description in the cloud page is too vague about concurrency
and may conflict with the FAQ; update the description in the Astro
frontmatter/metadata so it either states the exact supported concurrency (for
example, by plan) or removes the concurrency claim entirely. Use the existing
description field in the page metadata and keep the wording aligned with the
FAQ’s job limits so the search-facing copy is unambiguous.
---
Outside diff comments:
In `@apps/website/src/i18n/translations.ts`:
- Around line 903-906: Remove the unused cloud.reason.headingHighlight
translation entry from the translations map in translations.ts. The key is no
longer referenced by ReasonSection.vue or anywhere else, so delete that object
from the dictionary and keep the remaining translation keys unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 0a723df9-7732-49bb-9368-10b7d2a311e5
📒 Files selected for processing (3)
apps/website/src/components/product/cloud/ReasonSection.vueapps/website/src/i18n/translations.tsapps/website/src/pages/cloud/index.astro
💤 Files with no reviewable changes (1)
- apps/website/src/components/product/cloud/ReasonSection.vue
| 'cloud.reason.heading': { | ||
| en: 'Why\nprofessionals\nchoose ', | ||
| 'zh-CN': '专业人士为何\n选择' | ||
| en: 'What is ComfyUI Cloud, and how many concurrent jobs can it run?', | ||
| 'zh-CN': 'ComfyUI Cloud 是什么，它能同时运行多少个任务？' | ||
| }, |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Heading asks a concurrency question the section doesn't answer.
The new heading explicitly asks "What is ComfyUI Cloud, and how many concurrent jobs can it run?", but the reason items rendered under it (GPU/security, models, control, customization) don't state a concurrency number. This creates a mismatch between the question posed and the content that follows, which could hurt both user experience and the "citation opportunity" this change was meant to improve (an LLM/crawler citing this heading would find no direct answer nearby). Consider either adding a reason item that states the actual concurrency limits (which vary by plan per pricing.plan.*.feature* entries), or rephrasing the heading to not over-promise an answer.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/website/src/i18n/translations.ts` around lines 899 - 902, The heading
text for cloud.reason.heading asks about concurrent job capacity, but the
surrounding reason items do not provide any concurrency limit, so align the copy
with the actual content. Either update cloud.reason.heading to remove the
concurrency question, or add a reason entry that explicitly states the
plan-based concurrency limits by referencing the existing pricing.plan.* feature
data so the section answers what it asks.
| <BaseLayout | ||
| title="Comfy Cloud — AI in the Cloud" | ||
| description={t('cloud.hero.subtitle', 'en')} | ||
| description="ComfyUI Cloud runs on Blackwell RTX 6000 Pro GPUs with pre-loaded models and supports concurrent jobs per account." |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Vague/potentially contradictory "concurrent jobs" claim in meta description.
The description states "ComfyUI Cloud runs on Blackwell RTX 6000 Pro GPUs with pre-loaded models and supports concurrent jobs per account." without specifying a number. Elsewhere on the same site, the FAQ states each workflow allows only "one active job at a time" by default, while paid plans support 1/3/5 concurrent workflows depending on tier. As-is, "supports concurrent jobs" is ambiguous and could be read as contradicting the FAQ, which is risky for a search-facing meta description. Per the PR's own review focus, either state a concrete/accurate number (or range, e.g., "up to 5 concurrent jobs depending on plan") or drop the concurrency claim from this description entirely.
Proposed fix
- description="ComfyUI Cloud runs on Blackwell RTX 6000 Pro GPUs with pre-loaded models and supports concurrent jobs per account."
+ description="ComfyUI Cloud runs on Blackwell RTX 6000 Pro GPUs with pre-loaded models and supports up to 5 concurrent jobs per account, depending on your plan."📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| description="ComfyUI Cloud runs on Blackwell RTX 6000 Pro GPUs with pre-loaded models and supports concurrent jobs per account." | |
| description="ComfyUI Cloud runs on Blackwell RTX 6000 Pro GPUs with pre-loaded models and supports up to 5 concurrent jobs per account, depending on your plan." |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/website/src/pages/cloud/index.astro` at line 15, The meta description in
the cloud page is too vague about concurrency and may conflict with the FAQ;
update the description in the Astro frontmatter/metadata so it either states the
exact supported concurrency (for example, by plan) or removes the concurrency
claim entirely. Use the existing description field in the page metadata and keep
the wording aligned with the FAQ’s job limits so the search-facing copy is
unambiguous.
1 participant
Summary
Updated the H2 heading and meta description for the Cloud Product Page to improve SEO structure and citation opportunity.
Changes
ReasonSection.vueheading keys andindex.astrodescription forcomfy.org/cloudto feature structured citation content.Review Focus
Please review the meta description copy, specifically verifying if omitting the concurrent jobs number
[N]is the intended behavior or if a specific number should be inserted before merge.