You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "moonming (via GitHub)" <gi...@apache.org> on 2026/04/14 02:25:20 UTC
[PR] feat(seo): add 5 Learning Center articles and SEO contributing guide (P3) [apisix-website]
moonming opened a new pull request, #2027:
URL: https://github.com/apache/apisix-website/pull/2027
## Summary
P3 SEO improvements: 5 new Learning Center articles targeting strategic keywords + SEO contributing guide for the project.
### Learning Center Articles (5 new pages)
| Article | Target Keywords | Strategic Value |
|---------|----------------|----------------|
| API Gateway Security | `secure api gateway`, `api security gateway` (310+/mo) | OWASP-aligned security content |
| Apache APISIX vs Kong | `apisix vs kong` (emerging) | Direct competitor comparison — GEO high value |
| MCP Protocol & AI Gateways | `mcp protocol`, `ai agent gateway` (emerging) | Blue ocean — very low competition |
| API Gateway Observability | `api gateway observability`, `datadog api gateway` (110+/mo) | Observability stack integrations |
| What is Cloud Native | `cloud native`, `cloud gateway` (680+/mo) | Reinforce APISIX's cloud-native positioning |
### SEO Contributing Guide
`CONTRIBUTING-SEO.md` provides guidelines for all content contributors:
- Title tag rules (50-60 chars, primary keyword first, human-readable plugin names)
- Meta description rules (120-160 chars)
- Answer-first content structure for AI search optimization
- Heading hierarchy (single H1, logical H2/H3)
- Statistics policy and internal linking requirements
- Image alt text requirements
- Pre-PR checklist
### Quality Assurance
All articles have been reviewed for factual accuracy:
- Removed unverifiable statistics attributed to named reports/surveys
- Maintained neutral, objective tone (especially in comparison articles)
- Kept only facts verifiable from official project documentation
- No service mesh references (deprecated APISIX project)
## Test plan
- [ ] `yarn build` succeeds
- [ ] Articles render correctly at `/learning-center/` (requires P0 PR merged first)
- [ ] CONTRIBUTING-SEO.md is accessible in repo root
> **Note**: This PR depends on #2024 (P0) for the Learning Center plugin configuration.
--
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 Learning Center articles and SEO contributing guide (P3) [apisix-website]
Posted by "Baoyuantop (via GitHub)" <gi...@apache.org>.
Baoyuantop merged PR #2027:
URL: https://github.com/apache/apisix-website/pull/2027
--
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 Learning Center articles and SEO contributing guide (P3) [apisix-website]
Posted by "Copilot (via GitHub)" <gi...@apache.org>.
Copilot commented on code in PR #2027:
URL: https://github.com/apache/apisix-website/pull/2027#discussion_r3076813455
##########
website/learning-center/apisix-vs-kong.md:
##########
@@ -0,0 +1,131 @@
+---
+title: "Apache APISIX vs Kong: Feature Comparison & Performance Benchmarks"
Review Comment:
Per the new CONTRIBUTING-SEO guidelines added in this PR (50–60 chars for titles), this title is ~65 characters and will likely be truncated in SERPs. Consider shortening/rephrasing the title to fit the stated range while keeping the primary keyword near the front.
```suggestion
title: "Apache APISIX vs Kong: Features and Performance"
```
##########
website/learning-center/apisix-vs-kong.md:
##########
@@ -0,0 +1,131 @@
+---
+title: "Apache APISIX vs Kong: Feature Comparison & Performance Benchmarks"
+description: "Detailed comparison of Apache APISIX and Kong API Gateway. Covers architecture, performance, plugin ecosystem, Kubernetes support, and when to choose each."
+slug: apisix-vs-kong
+date: 2026-04-14
+tags: [comparison, apisix, kong, api-gateway]
+hide_table_of_contents: false
+---
+
+Apache APISIX and Kong are the two most widely adopted open-source API gateways, both built on NGINX and Lua. APISIX differentiates itself with a fully dynamic architecture powered by etcd, higher single-core throughput, and a broader protocol support matrix, while Kong offers a mature enterprise ecosystem with extensive third-party integrations and a large plugin marketplace.
+
+## Overview
+
+Both projects serve as high-performance, extensible API gateways for microservices architectures. Kong was open-sourced in 2015 and has built a substantial commercial ecosystem around Kong Gateway Enterprise, Kong Konnect, and the Kong Plugin Hub. Apache APISIX entered the Apache Software Foundation incubator in 2019 and graduated as a top-level project in 2020, with rapid community growth.
+
+Both projects are recognized as production-grade gateways and see active production deployments worldwide.
Review Comment:
The article contains no internal links at all. This conflicts with the new SEO guide in this PR (“Every page should include at least 2 internal links”), and it also reduces crawlability/context for readers. Add a couple of relevant internal links (e.g., to APISIX plugins, docs, or other Learning Center pages).
##########
website/learning-center/api-gateway-security.md:
##########
@@ -0,0 +1,131 @@
+---
+title: "API Gateway Security: Threats, Best Practices & Implementation"
Review Comment:
Per the new CONTRIBUTING-SEO guidelines added in this PR (50–60 chars for titles), this title is ~62 characters and will likely be truncated in SERPs. Consider shortening/rephrasing it to fit the stated range while keeping the primary keyword near the front.
```suggestion
title: "API Gateway Security: Threats, Best Practices"
```
##########
CONTRIBUTING-SEO.md:
##########
@@ -0,0 +1,139 @@
+# SEO Guidelines for Apache APISIX Website Contributors
+
+This document provides SEO best practices for anyone contributing content to the Apache APISIX website, documentation, or blog. Following these guidelines ensures that our content ranks well in both traditional search engines and AI-powered search (Google AI Overviews, ChatGPT, Perplexity).
+
+## Frontmatter Requirements
+
+Every Markdown page (blog post, doc page, learning center article) **must** include:
+
+```yaml
+---
+title: "Human-Readable Title - Primary Keyword | Apache APISIX"
+description: "120-160 character description that accurately summarizes the page content and includes the primary keyword naturally."
+---
+```
+
+### Title Rules
+
+- **Length**: 50-60 characters (Google truncates longer titles in SERPs)
+- **Format**: `Primary Topic - Modifier | Apache APISIX`
+- **Keyword placement**: Put the primary keyword near the front
+- **Human-readable**: Write for humans, not bots. No keyword stuffing.
+- **Plugin pages**: Use the human-readable name, not just the code identifier
+ - Good: `Rate Limiting Plugin (limit-req) | Apache APISIX`
+ - Bad: `limit-req | Apache APISIX`
+
+### Description Rules
+
+- **Length**: 120-160 characters
+- **Content**: Describe the page honestly and include the main topic naturally
+- **Action-oriented**: Start with a verb when possible ("Learn how to...", "Configure...", "Compare...")
+
+## Content Structure
+
+### Answer-First Writing
+
+Place the primary answer or definition in the **first 40-60 words** of the page. AI search engines preferentially extract opening paragraphs.
+
+```markdown
+## What is an API Gateway?
+
+An API gateway is a server that sits between clients and backend
+services, acting as the single entry point for all API traffic.
+It handles authentication, rate limiting, and routing so that
+individual services don't need to implement these concerns.
+
+[Rest of the detailed content follows...]
+```
+
+### Heading Hierarchy
+
+- **One H1 per page** (the `title` in frontmatter)
+- Use H2 for major sections, H3 for subsections
+- Headings should match developer search queries when possible
+ - Good: `## How to Configure Rate Limiting in APISIX`
+ - Bad: `## Configuration`
+- Never skip heading levels (H1 → H3 without H2)
+
+### Statistics and Data
+
+Include **at least one statistic or data point every 150-200 words**. Concrete numbers make content more authoritative and more likely to be cited by AI engines.
+
+Examples:
+- "Apache APISIX processes 18,000 requests per second per core with 0.2ms latency"
+- "Over 147,000 deployments across 5,200+ companies"
+- "100+ built-in plugins covering authentication, security, and traffic control"
+
+Always cite the source when referencing external statistics.
Review Comment:
The guideline “Include at least one statistic or data point every 150–200 words” is very strict and conflicts with the PR’s stated QA goal of removing unverifiable statistics. It also increases the risk that contributors add low-quality or uncited numbers to satisfy the quota. Consider changing this to a softer recommendation (e.g., add concrete metrics when they can be cited) and making the examples explicitly placeholders that must include a citation.
--
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