Evaluate SEO, Answer Engine Optimization (AEO), and Artificial Intelligence Optimization (AIO)

[xmulligan]

We can improve how cilium.io content is discovered and surfaced by search engines and AI tools by addressing the following:

✅ SEO Improvements
Add meta descriptions and targeted titles to docs, blog, and product pages

Use structured heading hierarchy (H1 > H2 > H3) with relevant keywords

Improve internal linking between related docs and pages

🤖 Answer Engine Optimization (AEO)
Add TL;DR summaries or short definitions at the top of key pages

Use FAQ schema / Q&A structured data where appropriate

Restructure content to clearly answer "what is", "how to", and "why" questions

🧠 Artificial Intelligence Optimization (AIO)
Break out reusable concepts into standalone, deep-linkable pages (e.g., /concepts/kube-proxy-replacement)

Add authorship and last-updated metadata to build trust

Ensure docs are citation- and chunk-friendly for LLMs

[naman9271]

Hi @xmulligan .....
I have a idea for upcoming LFX or include in this one that we can also add the migrtation of website to typescript from JS for type safety and better developer experience.
Ehat are you thoughts on this.??

[xmulligan]

@naman9271 I don't have the background or experience in that so can't be a mentor so I don't think we will focus on it for now

[xmulligan]

While I can't comment on anyone's application specifically as it wouldn't be fair to other applicants, I do have some general advice. Being able to write clearly and communicate effectively is critical for this project. I've used enough AI to recognize what it sounds like, if you don't use your own analysis, knowledge, and insight you will not have a successful application. Please don't send me something that was just generated and you don't understand, you will not be chosen.

Applications will open soon

[1308harshit]

Hey @xmulligan,
Hope you're doing well!

I’ve been diving into the Cilium.io website Current SEO & Content Setup and look into the issues you raised
While digging into the Cilium.io codebase recently, I took a closer look at how the site is handling SEO, content structure, and LLM (AI) optimization. I noticed a lot of potential for improvement—especially for contributors who enjoy working on web performance, developer experience, or even technical writing.

Here’s a breakdown of what’s currently in place and where help is needed:

--> SEO – The Basics Are There, But It’s Just the Start
-Basic Setup in Place: There’s an existing SEO component (seo.jsx) that takes care of standard things like meta descriptions, Open Graph tags, and Twitter Cards.

-Static Metadata: Site-wide metadata like title and description are defined statically in gatsby-config.js, but they're quite generic.

-No Page-Specific Descriptions: Most individual pages just fall back to a default site description. That’s a big missed opportunity for improving how each page ranks and shows up in search.

-No Structured Data: Currently, there’s no schema.org markup—so search engines aren’t getting any rich content like FAQs, breadcrumbs, or article metadata.

--> Content Structure – Room for a Much Better Developer Experience
-Blog Posts Need More Metadata: Right now, blog frontmatter is pretty minimal (mostly title and date). Adding things like targeted summaries or tags could really help both SEO and discoverability.

-No TL;DR Sections: Articles can be long, but there’s no summary section or quick takeaways for readers to grasp the key idea fast.

-Very Limited Internal Linking: There’s no consistent way of linking between related posts or concepts, which hurts navigation and content discoverability.

-Missing Concept Pages: Important ideas—like how Cilium replaces kube-proxy—don’t have dedicated pages. This would be super helpful for newcomers and great for search rankings.

--> AI / LLM Optimization – A Big Opportunity Here
-No Author or Update Info: Articles are missing metadata like author attribution or last updated timestamps, which are super useful for both readers and AI tools.

-FAQ Component Exists, But Unused: There’s a component for FAQs, but it’s filled with placeholder text and doesn’t use structured data—so it’s not really helping much.

-Not Optimized for AI Chunking: Right now, the content isn’t structured in a way that would help LLMs (like ChatGPT or Bard) understand and cite it properly.

I’d love to start contributing in any of these areas.
Let me know what you think or if there’s a specific part you'd like me to pick up first.

Looking forward to collaborating!

• Harshit

[yugalkaushik]

Hi, I'm pretty interested in this issue. To know more, could you share any insights on the tools or strategies Cilium has previously used for SEO or content optimization? This would help me align my approach with the project’s goals. Thanks.

[xmulligan]

@1308harshit that's an example of exactly what I asked you not to do. I'm locking this issue until the mentee is chosen by LFX.