Re: [PR] fix(seo): optimize titles and descriptions for 50 blog posts (batch 2) [apisix-website]
Baoyuantop merged PR #2021: URL: https://github.com/apache/apisix-website/pull/2021 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] fix(seo): optimize titles and descriptions for 50 blog posts (batch 2) [apisix-website]
Yilialinn commented on code in PR #2021: URL: https://github.com/apache/apisix-website/pull/2021#discussion_r3070768650 ## blog/en/blog/2020/12/16/another-way-to-implement-envoy-filter.md: ## @@ -9,7 +9,7 @@ keywords: - Apache APISIX - Envoy - Envoy filter -description: This article describes extending Envoy with new functionality and concrete examples using the base library of the cloud-native API gateway Apache APISIX. +description: Run APISIX Lua plugins as Envoy filters using apisix-seed. Extend Envoy with dynamic capabilities without writing C++ code. Review Comment: fixed @Baoyuantop -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] fix(seo): optimize titles and descriptions for 50 blog posts (batch 2) [apisix-website]
Yilialinn commented on code in PR #2021: URL: https://github.com/apache/apisix-website/pull/2021#discussion_r3069493268 ## blog/en/blog/2020/12/16/another-way-to-implement-envoy-filter.md: ## @@ -9,7 +9,7 @@ keywords: - Apache APISIX - Envoy - Envoy filter -description: This article describes extending Envoy with new functionality and concrete examples using the base library of the cloud-native API gateway Apache APISIX. +description: Run APISIX Lua plugins as Envoy filters using apisix-seed. Extend Envoy with dynamic capabilities without writing C++ code. Review Comment: @copilot fix it -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] fix(seo): optimize titles and descriptions for 50 blog posts (batch 2) [apisix-website]
Yilialinn commented on code in PR #2021: URL: https://github.com/apache/apisix-website/pull/2021#discussion_r3069493268 ## blog/en/blog/2020/12/16/another-way-to-implement-envoy-filter.md: ## @@ -9,7 +9,7 @@ keywords: - Apache APISIX - Envoy - Envoy filter -description: This article describes extending Envoy with new functionality and concrete examples using the base library of the cloud-native API gateway Apache APISIX. +description: Run APISIX Lua plugins as Envoy filters using apisix-seed. Extend Envoy with dynamic capabilities without writing C++ code. Review Comment: @copilot fix it -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] fix(seo): optimize titles and descriptions for 50 blog posts (batch 2) [apisix-website]
Copilot commented on code in PR #2021: URL: https://github.com/apache/apisix-website/pull/2021#discussion_r3069498627 ## blog/en/blog/2022/02/25/consul-api-gateway.md: ## @@ -13,8 +13,8 @@ keywords: - API Gateway - Consul - Service Discovery -- Servici Register -description: Apache APISIX supports the Consul KV-based service discovery registry. This article will walk you through the process of implementing service discovery and service registry in APISIX. +- Service Register +description: Integrate Consul KV with APISIX for service discovery and registration. Configure upstream resolution with health checks. Review Comment: The new meta description mentions "health checks", but this article doesn’t appear to cover health checks anywhere else (only occurrence is in this frontmatter). This makes the description inaccurate; consider removing the health-checks claim or updating the article content to match. ```suggestion description: Integrate Consul KV with APISIX for service discovery and registration. ``` ## blog/en/blog/2020/12/16/another-way-to-implement-envoy-filter.md: ## @@ -9,7 +9,7 @@ keywords: - Apache APISIX - Envoy - Envoy filter -description: This article describes extending Envoy with new functionality and concrete examples using the base library of the cloud-native API gateway Apache APISIX. +description: Run APISIX Lua plugins as Envoy filters using apisix-seed. Extend Envoy with dynamic capabilities without writing C++ code. Review Comment: Frontmatter description references "apisix-seed", but the post body links to and discusses the `api7/envoy-apisix` repo and doesn’t mention apisix-seed elsewhere. This makes the description misleading; align it with the actual project name used in the article. ```suggestion description: Run APISIX Lua plugins as Envoy filters using envoy-apisix. Extend Envoy with dynamic capabilities without writing C++ code. ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] fix(seo): optimize titles and descriptions for 50 blog posts (batch 2) [apisix-website]
Baoyuantop commented on code in PR #2021: URL: https://github.com/apache/apisix-website/pull/2021#discussion_r3063317281 ## blog/en/blog/2020/12/16/another-way-to-implement-envoy-filter.md: ## @@ -9,7 +9,7 @@ keywords: - Apache APISIX - Envoy - Envoy filter -description: This article describes extending Envoy with new functionality and concrete examples using the base library of the cloud-native API gateway Apache APISIX. +description: Run APISIX Lua plugins as Envoy filters using apisix-seed. Extend Envoy with dynamic capabilities without writing C++ code. Review Comment: The article did not mention apisix-seed. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] fix(seo): optimize titles and descriptions for 50 blog posts (batch 2) [apisix-website]
Copilot commented on code in PR #2021:
URL: https://github.com/apache/apisix-website/pull/2021#discussion_r3061463771
##
blog/en/blog/2021/11/30/use-apisix-ingress-in-kubesphere.md:
##
@@ -10,7 +10,7 @@ keywords:
- Kubenetes
Review Comment:
The keywords include a misspelling ("Kubenetes"). This should be corrected
to "Kubernetes" to avoid SEO/tagging issues.
```suggestion
- Kubernetes
```
##
blog/en/blog/2022/02/25/consul-api-gateway.md:
##
@@ -14,7 +14,7 @@ keywords:
- Consul
- Service Discovery
- Servici Register
Review Comment:
The keyword list contains a typo: "Servici Register". Since this PR is
already editing frontmatter for SEO, it’s worth correcting this to "Service
Register" (or the intended phrasing) to avoid indexing the misspelling.
```suggestion
- Service Register
```
##
blog/en/blog/2021/01/11/interview-Apache-APISIX-contributor-Wang-Pengcheng-Senior-Security-Advisor-of-PwC-South-China-Data-Security-and-Privacy-Protection-Team.md:
##
@@ -1,5 +1,5 @@
---
-title: Apache APISIX Contributor Interview | Pengcheng Wang from
PricewaterhouseCoopers
+title: "APISIX CVE-2020-13945: Admin API Token Flaw"
Review Comment:
The updated title reads like a CVE advisory, but the article content is
primarily an interview (the slug also includes "interview"). Consider revising
the title to reflect the interview format while still including the CVE ID, to
avoid a mismatch between title and page content/search intent.
```suggestion
title: "Interview: Pengcheng Wang on APISIX CVE-2020-13945"
```
##
blog/en/blog/2021/07/14/the-road-to-customization-of-Sina-Weibo-API-gateway-based-on-Apache-APISIX.md:
##
@@ -8,7 +8,7 @@ keywords:
- Weibo
- Usser Case
Review Comment:
The keywords include a misspelling ("Usser Case"). Since the frontmatter is
being updated here, please correct it (e.g., "User Case" or "Use Case",
whichever is intended) so the tag/keyword is consistent and searchable.
```suggestion
- Use Case
```
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
[PR] fix(seo): optimize titles and descriptions for 50 blog posts (batch 2) [apisix-website]
moonming opened a new pull request, #2021: URL: https://github.com/apache/apisix-website/pull/2021 ## Summary SEO title and meta description optimization for 50 blog articles ranked 31-80 by SEO impact score. This is the second batch following PR #2020 (batch 1: top 30 articles). ## Changes Rewrites frontmatter `title` and `description` fields across 50 blog posts to: - **Shorten titles to ≤55 characters** — prevents truncation in Google SERPs (with ` | APISIX` suffix added by Docusaurus, total stays ≤64 chars) - **Compress descriptions to ≤155 characters** — ensures full display in search snippets - **Place primary keywords early** in titles for better ranking signals - **Replace vague "this article describes..." phrasing** with clear value propositions - **Align with search intent** — action-oriented titles that match what users actually search for ## Examples | File | Before Title | After Title | |--|-|| | `beeto-with-apache-apisix.md` | Practice of localized application with API gateway in the Middle East (69c) | How Beeto Uses APISIX for API Management (41c) | | `cve-2022-29266.md` | The Vulnerability of Leaking Information in Error Response from jwt-auth Plugin（CVE-2022-29266） (88c) | CVE-2022-29266: jwt-auth Secret Leak Fix (40c) | | `why-we-need-apache-apisix.md` | Why do you need Apache APISIX when you have NGINX and Kong? (59c) | Why Choose APISIX Over NGINX and Kong? (39c) | | `file-logger-api-gateway.md` | How to develop plugin in API Gateway (36c, keyword-missing) | Build an APISIX Plugin: file-logger Tutorial (45c) | | `apisix-owasp-coraza-core-ruleset.md` | Hardening Apache APISIX with the OWASP's Coraza and Core Ruleset (63c) | Protect APIs with OWASP Coraza WAF in APISIX (46c) | ## SEO Rules Applied 1. Titles ≤55 chars with primary keyword in first 30 chars 2. Descriptions ≤155 chars with clear value proposition 3. Use "APISIX" (not "Apache APISIX") in titles to save space — brand suffix handles the full name 4. Search-intent framing over narrative framing 5. CVE titles include CVE ID + short impact summary ## Files Changed 50 blog post markdown files under `blog/en/blog/` ## Related PRs - PR #2020 — Batch 1: top 30 articles (ranks 1-30) - PR #2015 — External canonical URL removal (57 files) - PR #2017 — Title tag optimization (brand suffix) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
