[PR] feat(seo): add 5 head-to-head API gateway comparison articles (AWS, NGINX, Envoy, Traefik, Apigee) [apisix-website]

["moonming (via GitHub)" <gi...@apache.org>]

moonming opened a new pull request, #2059:
URL: https://github.com/apache/apisix-website/pull/2059

   ## Summary
   
   Adds **five head-to-head comparison articles** to the Learning Center. Comparison content was the biggest gap for the stated goal — *ranking on "API gateway" queries ahead of Kong and the cloud vendors*. Today only `apisix-vs-kong` and the open-source roundup exist, while the SERP for high-intent "X vs Y" terms is dominated by third-party aggregators. APISIX's existing comparisons already rank on page one, so more should follow.
   
   > ⚠️ **Stacked on #2058.** Base is `feat/seo-article-structured-data` so the new articles pick up the `Article`/`FAQPage`/`BreadcrumbList` wrapper from that PR (and this PR shows only the new content). Merge #2058 first; GitHub will retarget this to `master`.
   
   ## New articles
   
   | Article | Framing |
   |---|---|
   | `apisix-vs-aws-api-gateway` | Self-hosted open source vs managed cloud service — cost at scale, lock-in, performance |
   | `apisix-vs-nginx` | APISIX is *built on* NGINX — what a purpose-built gateway adds over raw NGINX / NGINX Plus |
   | `apisix-vs-envoy` | Turnkey API gateway vs a proxy that needs a separate control plane; north-south vs service mesh |
   | `apisix-vs-traefik` | Throughput + plugin breadth vs container-native auto-discovery + automatic TLS |
   | `apisix-vs-apigee` | Open-source gateway vs a full enterprise API management platform — scope and cost |
   
   Each follows the existing `apisix-vs-kong` structure (intro → overview → architecture → feature table → when-to-choose-each → FAQ) and carries an FAQ section + matching `faq` front matter, so it emits FAQPage structured data.
   
   ## Also in this PR
   - **`apisix-vs-kong` FAQ backfill** — its FAQ heading is `## FAQ`, which #2058's grep (looking for "Frequently Asked Questions") missed, so it had no `faq` front matter. Added it (answers copied verbatim from its body) so it now emits FAQPage too.
   - **`/comparisons/` hub** — expanded from 4 to 9 cards, head-to-head comparisons grouped first.
   - **`llms.txt`** — added the 5 new articles for GEO/LLM discoverability.
   
   ## Content approach
   - **Balanced and credible**, matching the `apisix-vs-kong` tone — favorable to APISIX on its genuine strengths (performance, open-source completeness, dynamic config, no lock-in/cost) while fairly stating when each competitor fits. Credible content ranks better and suits Apache's vendor-neutral posture.
   - **No fabricated benchmarks** — like `apisix-vs-kong`, performance is discussed qualitatively with a recommendation to benchmark your own workload, rather than inventing head-to-head numbers.
   - **Honest scope framing** — e.g. NGINX is the foundation APISIX builds on; Apigee is a full platform, not just a gateway (APISIX OSS doesn't bundle a dev portal/monetization).
   - **Vendor-neutral** — no promotion of any commercial vendor on the Apache site.
   
   ## Verification — production (SSR) build
   
   Built (`yarn workspace website build`, green) and grepped the output HTML:
   
   | Article | Article | Breadcrumb | FAQPage | FAQ answer = body? |
   |---|---|---|---|---|
   | apisix-vs-kong | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch |
   | apisix-vs-aws-api-gateway | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch |
   | apisix-vs-nginx | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch |
   | apisix-vs-envoy | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch |
   | apisix-vs-traefik | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch |
   | apisix-vs-apigee | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch |
   
   All 9 `/comparisons/` hub links resolve to built pages.
   
   ## Test plan
   - [x] Production build green; SSR schema verified per the table (incl. FAQ answer ⊆ body check)
   - [x] `/comparisons/` hub renders 9 cards, all links resolve
   - [ ] CI deploy build green
   - [ ] Post-merge: spot-check a couple URLs in Google Rich Results Test
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] feat(seo): add 5 head-to-head API gateway comparison articles (AWS, NGINX, Envoy, Traefik, Apigee) [apisix-website]

["moonming (via GitHub)" <gi...@apache.org>]

moonming commented on PR #2059:
URL: https://github.com/apache/apisix-website/pull/2059#issuecomment-4789307900

   ## Independent audit (resolved)
   
   An independent adversarial review (no shared context, isolated worktree) checked factual accuracy, fairness/vendor-neutrality, schema/front-matter, SEO consistency, and house style. **No HIGH findings and no blocking factual errors** — every technical claim was verified against primary sources (APISIX, AWS, Traefik docs), all 24 FAQ answers match their body verbatim, and there was no em-dash regression. Findings and resolution:
   
   | Sev | Finding | Resolution |
   |-----|---------|------------|
   | **MEDIUM** | `llms.txt` trailing-slash inconsistency (new entries had slashes, existing ones didn't) | **Fixed** (`c388f9b9e`) — normalized all Learning Center URLs to the canonical trailing-slash form (also restored the 5 new entries, which had been lost to a build race) |
   | **LOW** | 5 article meta descriptions > ~160 chars (SERP truncation) | **Fixed** — trimmed all five to ~140–150 chars |
   | **LOW** | `apisix-vs-apigee` title 71 chars | **Fixed** — shortened to 59 chars |
   | **LOW** | existing `apisix-vs-kong` says "80+ plugins" vs the new articles' "100+" | **Deferred** — the auditor scoped this as a change to the kong article's body, out of scope here; the new articles correctly say 100+ |
   | **LOW** | no inter-article "see also" links | **Deferred** — this is the P1 internal-linking roadmap item; the `/comparisons/` hub already cross-links all 9 |
   
   Accuracy, fairness, schema, and house-style lenses came back clean. These were text-only front-matter / `llms.txt` changes; the structured-data mechanism (Article / BreadcrumbList / FAQPage, with FAQ answer ⊆ body) was verified in the prior SSR build.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] feat(seo): add 5 head-to-head API gateway comparison articles (AWS, NGINX, Envoy, Traefik, Apigee) [apisix-website]

["guoqqqi (via GitHub)" <gi...@apache.org>]

guoqqqi merged PR #2059:
URL: https://github.com/apache/apisix-website/pull/2059


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org