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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to