fix(seo): clarify APISIX capabilities and search intent paths

[Yilialinn]

Changes:

• remove the newly added disclosure that tied the homepage figures exclusively to the published four-core benchmark
• replace the unsupported MCP Gateway claim with the documented ai-prompt-template capability
• narrow deployment and API management wording to APISIX's gateway-level capabilities
• preserve the homepage title, description, H1, canonical, hreflang, and API Gateway + AI Gateway positioning
• clarify intent ownership between the homepage, API gateway explainer, open-source comparison, and deployment-model blog
• add English and Chinese regression coverage for metadata, canonical/hreflang, claims, links, and responsive overflow

Validation:

• yarn lint:frontmatter
• yarn remark on both changed Markdown files
• npm run lint
• NODE_OPTIONS=--max-old-space-size=3072 npm run build
• npx playwright test tests/e2e/main-pages.spec.mjs --grep homepage|Chinese routes (4 passed)
• npm run test:sitemap
• git diff --check
• independent release review: no P0/P1/P2 findings, 9.4/10

Notes:

• The restored performance values are pre-existing homepage values and are not attributed solely to the published four-core benchmark.
• No API7 commercial content was introduced.
• This PR does not claim that Apache APISIX provides an MCP Gateway.
• No product pages, release notes, plugin docs, canonical rules, or hreflang behavior were changed.

Screenshots:

• Desktop and mobile layouts were validated locally at 1440x900 and 390x844.

[Copilot]

🟢 Approval recommended

No blocking issues were identified; the remaining wording comment is a minor nit.

Pull request overview

This PR refines APISIX SEO and capability messaging, clarifies search-intent navigation, and adds regression coverage.

Changes:

• Restores existing performance figures and replaces unsupported MCP Gateway wording.
• Narrows gateway and deployment claims.
• Adds English and Chinese metadata, link, claim, and responsive-layout tests.

File summaries

File	Summary
website/learning-center/open-source-api-gateway-comparison.md	Clarifies comparison scope and APISIX links.
next/tests/e2e/main-pages.spec.mjs	Adds homepage and Chinese-route regression tests.
next/src/components/HomePage.astro	Updates homepage claims, statistics, AI capability messaging, and navigation; one minor wording nit remains.
blog/en/blog/2025/02/17/cloud-vs-open-source-vs-commercial-api-gateways.md	Adds deployment-model and comparison cross-links.

Review details

Suppressed comments (1)

next/src/components/HomePage.astro:225

• The new feature lead is narrowed to gateway-level capabilities, but the same section still renders the preceding paragraph as a “scalable platform for all your APIs and microservices” / “可扩展的管理平台” (lines 216–217). That leaves the broad API-management/platform claim this PR says it is removing; please revise that paragraph too or explicitly scope it to runtime gateway traffic so the homepage’s capability messaging is consistent.

          'Apache APISIX provides 100+ open-source plugins and gateway-level capabilities for traffic management, security, observability, and protocol handling.',
          'Apache APISIX 提供 100+ 开源插件，以及面向流量管理、安全、可观测性和协议处理的网关能力。')}</p>

• Files reviewed: 4/4 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.