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

   ## Summary
   
   Improve CTR-oriented metadata, introductory summaries, FAQ/schema content, 
and internal APISIX links for high-impression Apache APISIX website pages.
   
   This PR updates 42 tracked pages across:
   
   - APISIX Learning Center pages
   - APISIX AI Gateway page metadata/schema
   - English blog posts
   - Chinese blog posts
   - Plugins and downloads pages
   
   The changes keep the Apache APISIX website focused on APISIX docs, Learning 
Center content, and community resources. They do not add API7 conversion CTAs.
   
   ## Why
   
   Recent GSC analysis identified high-impression / low-CTR APISIX pages where 
search snippets and page intros could better match user intent around:
   
   - open-source API Gateway
   - AI Gateway / LLM Gateway / MCP
   - API authentication and security
   - Kubernetes / Ingress / microservices
   - APISIX plugins and downloads
   
   ## What Changed
   
   - Updated page descriptions for stronger search intent alignment.
   - Added short `Quick Overview` sections to clarify page relevance near the 
top of the content.
   - Added related APISIX resource blocks to improve internal linking.
   - Added FAQ sections where appropriate.
   - Updated AI Gateway metadata and FAQ schema for LLM, MCP, and AI agent 
intent.
   - Added concise SEO intro copy to plugins and downloads pages.
   
   ## Validation
   
   - Built website preview successfully.
   - Built English blog preview successfully.
   - Verified representative preview URLs returned `200 OK`.
   - Checked newly added diff lines for forbidden API7 conversion terms.
   
   Note: the temporary worktree was missing the Husky helper script, so the 
commit was created with `--no-verify` after the manual validation above.
   


-- 
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]

Reply via email to