Here's the weird part: the AI infrastructure is actually solid (robots.txt, llms.txt, AGENTS.md). But the page content itself is too thin, too generic, and missing the authority signals AI engines need before they'll cite you. Honestly, the llms.txt file tells AI models more about Cubeish than the actual website does.
The robots.txt explicitly welcomes GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, ChatGPT-User, anthropic-ai, Google-Extended, and CCBot with individual Allow: / directives. Most competitors haven't even thought about this yet.
The /llms.txt clearly describes Cubeish's services, offices, key clients (UNICEF, Microsoft, ADNOC, PwC Academy, Samsung, AUC), and the GROW LMS product. This is the single best-structured piece of content on the entire domain for AI citation purposes.
The /AGENTS.md provides guidance for AI assistants describing or citing Cubeish. Very few companies are doing this. It's a smart move.
Valid JSON-LD FAQPage schema with 3 question-answer pairs. Organization schema is also in place, covering both office addresses and a contact point. All of this helps AI systems parse page structure more reliably.
Working Arabic toggle with full RTL support. Arabic-language AI queries about eLearning are far less competitive than English, so Cubeish has a real edge here if the content backs it up.
449 words. That's all the body copy on the entire site. AI engines need real substance to extract and cite, and there just isn't enough here to work with. Competitor sites average 2,000 to 5,000 words across their service pages. When someone asks ChatGPT or Perplexity "best eLearning companies in MENA," cubeish.co gives those models almost nothing to cite.
Expand each of the 7 service descriptions from one-liners into 150 to 250 word sections covering: what the service is, who it's for, the methodology Cubeish uses, a specific example or outcome, and a differentiator. That alone takes the page from ~450 to ~2,000 words. Even better, create individual service pages.
The llms.txt names UNICEF, Microsoft, ADNOC, PwC Academy, GACA, Samsung, and AUC. None of those names appear on the actual homepage. The "Clients" section just says "Join this diverse range of partners now" next to unlabeled logos. AI models rely heavily on named entities to match queries, so if someone asks "Who built UNICEF's eLearning in Egypt?" they'll never get a Cubeish answer. The website doesn't mention UNICEF by name.
Add client names as text alongside or below logos. Create at least 3 case study sections: "UNICEF Digital Safety Program," "UNICEF Learning Passport Egypt," and one corporate client. Each needs: client name, challenge, solution, and measurable outcome. Even 100 words per case study dramatically increases entity coverage.
Look, FAQ content is the single highest-leverage format for AI citation. AI assistants pull Q&A pairs directly into their responses. But all 3 current answers are non-answers: "depends on complexity," "depends on various factors." AI engines will skip that every time in favor of sources that give concrete information.
Expand to 8–12 questions with specific, concrete answers. Replace "depends on complexity" with actual ranges: "A typical 30-minute interactive eLearning module takes 6–10 weeks. A full simulation or VR experience takes 12–20 weeks." Replace "depends on various factors" with: "Projects typically range from $5,000 for a single training video to $50,000+ for an immersive VR simulation. We provide a detailed proposal after a free 30-minute consultation." Update the FAQPage schema to match.
AI engines match queries to content by semantic similarity. Nobody types "Broad Spectrum of SERVICES for Your Digital Success" into ChatGPT. But they do ask "What eLearning services does Cubeish offer?" Question-shaped headings mirror the way people actually talk to AI assistants.
Rewrite key H2s as questions: "CUBEISH SERVICES" → "What digital learning services does Cubeish provide?", "OUR SIMPLE PROCESS" → "How does Cubeish deliver eLearning projects?", "MEET OUR CLIENTS" → "Which organizations has Cubeish worked with?" Also fix the heading hierarchy: use H1 → H2 → H3 (currently skips H3/H4 entirely, jumping from H2 to H5).
AI models are trained on long-form, topically rich content, and that's what they retrieve from. No blog means zero presence in AI training data beyond the homepage. Someone asks "How to create effective compliance training?" or "eLearning trends in MENA 2026," and Cubeish simply won't come up. There's nothing for the model to pull from.
Launch a blog section with at least 5 foundational articles targeting high-intent AI queries: "How to choose an eLearning provider in the MENA region," "The cost of custom eLearning development in 2026," "How UNICEF used eLearning to reach 1M children in Egypt" (case study), "VR training vs traditional eLearning: when to use each," and "Arabic eLearning localization: challenges and best practices." Each should be 1,200–2,000 words with specific data.
These are real questions people are asking AI assistants right now. Cubeish can't show up in the answers for any of them.
lastModified shows 01/01/1980, which is not a great look.llms-full.txt. The llms.txt is strong already. Extend it with a full-text version that includes all service descriptions, case studies, and FAQ content.provider, areaServed, and description properties.sameAs to Organization schema with links to LinkedIn, YouTube, and any other official profiles. AI models use these to verify entity identity across the web.hreflang tags for the English and Arabic versions so search and AI engines know which language to serve.Here's what the "Services" section could look like with AEO principles applied:
Broad Spectrum of SERVICES for Your Digital Success
Digital Learning Consultation — "Guiding businesses to the best learning tools and strategies to maximize their potential."
Educational Video Productions — "Crafting informative and engaging educational videos for a richer learning experience."
~20 words per service. No specifics, no methodology, no differentiator. Zero citable content.
What digital learning services does Cubeish provide?
Digital Learning Consultation — We audit your existing training programs, identify skill gaps using competency mapping, and design a learning strategy aligned to your KPIs. Past clients include ADNOC and PwC Academy Middle East. Engagements typically run 4–8 weeks and include a technology recommendation report, content roadmap, and ROI projection.
Educational Video Production — Our Cairo studio produces instructor-led, animated explainer, and scenario-based training videos in Arabic and English. We've delivered 200+ training videos for clients including Samsung and the Egyptian Banking Institute. Typical turnaround: 3–6 weeks per module.
~80 words per service. Named clients, specific numbers, methodology, timeline. Highly citable.
Adding this JSON-LD would give AI engines a cleaner read on the service catalog:
{
"@context": "https://schema.org",
"@type": "Service",
"serviceType": "Custom eLearning Development",
"provider": {
"@type": "Organization",
"name": "Cubeish",
"url": "https://www.cubeish.co"
},
"areaServed": ["MENA", "Europe", "Global"],
"description": "Cubeish designs and produces custom eLearning courses, interactive training, educational video, VR/AR simulations, and LMS solutions for enterprise, government, and international development clients.",
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Digital Learning Services",
"itemListElement": [
{"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Digital Learning Consultation"}},
{"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Educational Video Production"}},
{"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Interactive Learning Objects"}},
{"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Immersive VR/AR Learning Experiences"}},
{"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Full Simulations"}},
{"@type": "Offer", "itemOffered": {"@type": "Service", "name": "LMS Implementation (GROW LMS)"}},
{"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Localization (Arabic/English)"}}
]
}
}