Company Profile
In June 2025, a Trivandrum-based IT company — referred to as "TechCo Kerala" at their request — was completely invisible in AI-generated answers. When potential clients typed queries like "cloud consulting companies in Kerala" into ChatGPT, or asked Gemini about IT firms operating out of Technopark, TechCo's name never appeared. Twelve months later, the same company appears in AI-generated answers to 23 of their 40 most important target queries. This is a detailed account of how that transformation happened.
TechCo Kerala is an 80-person IT services company operating out of Technopark Phase II, established in 2015. Their primary service lines are AWS cloud consulting, custom software development, and mobile application development. Their revenue splits roughly between two markets: UK and Australian SMEs who engage them for technology outsourcing (export revenue) and Kerala government digital transformation projects (domestic revenue).
Before the AEO engagement began, TechCo had a custom-built website with respectable technical SEO — clean URLs, reasonable page speed, mobile responsive. But zero AEO optimization had ever been considered. The site had been built by an internal developer in 2022 and had received only minor updates since. It ranked page 2 for some local IT service queries but was invisible in AI-generated answers.
Starting Point: The June 2025 Audit
The initial audit in June 2025 identified six major gaps that explained TechCo's complete absence from AI answers:
- Zero featured snippets across all tracked queries. No content on the site was structured to answer specific questions directly.
- Not appearing in any manual AI test — across 40 queries tested in ChatGPT (GPT-4o), Gemini Advanced, and Perplexity.ai, TechCo's name was never returned. Not once.
- Minimal Google Business Profile — 18 photos (most stock images), 22 reviews with no responses, no Q&A section, no regular posts. GBP was ranking on page 2 for "IT company Thiruvananthapuram."
- No Organization schema on the website — AI systems and Google's entity recognition could not confirm TechCo's identity, location, or connections to other web entities (LinkedIn, industry databases).
- No author schema on any page — the three existing blog posts had no authorship markup, making it impossible for AI systems to attribute expertise to named individuals.
- Only 3 blog posts, all under 600 words, with no FAQ sections — thin content with no question-answering structure, the opposite of what AI systems prefer to cite.
The audit produced a clear diagnosis: TechCo was structurally invisible to AI systems. Not because they lacked credibility or expertise — they clearly had both — but because nothing on their digital presence was formatted to be ingested and cited by AI answer engines.
Phase 1: Technical AEO Foundation (Months 1-2)
The first two months focused entirely on fixing the structural gaps before investing in content. This sequencing decision — technical foundation before content — turned out to be one of the most important choices of the engagement.
Schema Markup Implementation
An Organization schema was added to the homepage and sitewide header with full entity data: company name, founding year, number of employees, services offered, address, and — critically — sameAs links to TechCo's LinkedIn company page, Crunchbase profile (newly created), and Google Business Profile URL. These sameAs links give AI systems and Google's Knowledge Graph confirmation that these different web entities all refer to the same real-world organization.
Person schemas were added for the Managing Director and CTO, each including their names, job titles, educational credentials, and LinkedIn profile URLs. This created named, credentialed individuals behind the company — a signal AI systems use to evaluate whether an organization has genuine human expertise.
Content Restructuring
All three existing blog posts were rewritten — not replaced — to add an AEO intro paragraph, a FAQ section with 3-5 specific Q&As, and FAQPage schema. Speakable schema was added to all key content pages. The existing content was not discarded; it was layered with the structural elements that make content citable.
GBP Optimization
The Google Business Profile received intensive attention: 45 new photos uploaded (actual office photos, team photos, project screenshots — not stock imagery), responses written for all 22 existing reviews, a Q&A section enabled with 8 pre-answered questions covering common service enquiries, and a weekly posting schedule started. By the end of month two, the GBP local ranking had improved from page 2 to position 4 for "IT company Thiruvananthapuram" — a measurable early win that validated the effort.
The phase 1 result was modest but meaningful: 2 featured snippets acquired for specific long-tail AWS-related queries. No AI chatbot citations yet — that would take longer — but the structural groundwork was in place.
Phase 2: Content Depth Investment (Months 3-6)
With the technical foundation secure, phase 2 shifted to content. The brief was specific: write about things TechCo's engineers actually know, at a depth that would genuinely help their ideal client make a decision.
Eight New Blog Posts
Eight posts were published over four months, each between 1,800 and 2,500 words, on topics chosen because they matched specific queries TechCo's potential clients actually typed into search engines and AI tools during vendor evaluation:
- AWS migration cost for India SMEs: what to budget and what to watch out for
- How Kerala government cloud procurement works: a vendor's guide to the process
- React Native versus Flutter for Indian startups: a practical comparison with real project data
- Cybersecurity compliance requirements for Kerala IT companies exporting to UK clients
- Building a mobile app on a ₹15 lakh budget: what is and is not achievable
- AWS Well-Architected Framework: what it means for Kerala IT projects
- Custom software versus SaaS for Kerala manufacturing companies: decision framework
- IT project management challenges specific to Kerala government digital projects
Each post included: a direct-answer intro paragraph, a FAQ section with 3-5 Q&As marked up with FAQPage schema, an author bio for the TechCo engineer who wrote it (with their name, title, and LinkedIn link), and internal links to related service pages and other posts. The author attribution was deliberate: AI systems increasingly weight named expert authorship as a credibility signal for citation decisions.
Service Page Enrichment
The cloud consulting, software development, and mobile app development service pages were each rewritten to include comprehensive FAQ sections — 5-6 specific Q&As covering the questions potential clients ask during vendor shortlisting. These were the highest-impact changes of the entire engagement (as detailed in the FAQ section below).
Phase 2 results: the featured snippet portfolio grew from 2 to 9. The first AI Overview appearance in Google Search Console came in month 4 for "cloud consulting Trivandrum" — a genuine milestone. Three editorial citations appeared in YourStory and Inc42 as journalists covering Kerala's tech sector began to find TechCo's content when researching articles. Those editorial citations were unprompted and unpaid — a direct result of publishing genuinely useful, expert content.
Phase 3: Entity Authority Building (Months 7-12)
Phase 3 addressed the deepest layer of AEO: entity recognition. AI systems do not just cite web pages — they cite entities (organizations, people, products) that they have confirmed exist and have a known identity. Without entity recognition, an AI system might use TechCo's content to answer a question without ever mentioning TechCo by name. With entity recognition, the company name becomes a known, citable entity in its own right.
Crunchbase and Industry Database Listings
TechCo's Crunchbase profile was expanded with full company details: founding year, headquarters location, headcount range, service categories, and technology stack. NASSCOM membership was applied for and approved, adding TechCo to India's most authoritative IT industry registry. These listings create structured data about the company in databases that AI training pipelines actively ingest.
Editorial Coverage
TechCo's Managing Director was pitched to YourStory as a subject matter expert on Kerala's IT export opportunity. The resulting article — focused on how Technopark companies can win UK and Australian SME clients — included a direct quote and company mention. A guest post was contributed to the NASSCOM blog on IT export opportunities from tier-2 Indian cities, establishing TechCo's voice in a national industry publication.
Wikipedia Reference
A freelance Wikipedia editor (hired through a reputable agency, following Wikipedia's paid editing disclosure requirements) updated the existing Wikipedia article about Technopark's IT ecosystem to include a reference to TechCo as an example of a mid-size company operating in the campus. The reference was supported by the YourStory article as a citation — it was not invented or unsupported. This is a legitimate practice when the company genuinely merits mention and the reference is properly cited.
The Wikipedia reference triggered an automatic Wikidata entity creation for TechCo. Within six weeks, a Google Knowledge Panel appeared for searches on the company name — the clearest possible signal that Google now recognizes TechCo as a confirmed, known entity.
Final Results and Key Lessons
At the 12-month mark, TechCo Kerala's AI visibility had changed dramatically across every measured dimension:
- 23 of 40 target queries now return a TechCo citation in at least one AI system (ChatGPT, Gemini, Perplexity, or Google AI Overviews) — up from zero at engagement start.
- 9 featured snippets maintained across the target query set.
- ~15 AI Overview appearances per month per Google Search Console data.
- Organic search traffic up 67% — the AEO content programme produced substantial conventional SEO benefits as a side effect.
- 4 direct inbound inquiries per month citing ChatGPT or AI search as the initial discovery channel — up from zero.
- 2 UK client contracts (combined value £85,000) where the client's first contact with TechCo came through an AI-generated answer. Both clients mentioned asking an AI tool to recommend cloud consulting companies in India before reaching TechCo's website.
Four lessons stand out from this engagement:
Technical foundation before content investment. Schema markup and GBP optimization produced faster, more reliable AEO impact than the blog content programme in the first 90 days. Getting the structural signals right first meant that new content launched into a more receptive environment.
FAQ sections on service pages are underrated. The rewritten service pages with FAQPage schema had a higher effort-to-citation ratio than any other single tactic. Service page FAQs answer the exact evaluative questions potential clients ask AI tools during vendor research — which is why they get cited so readily.
Entity recognition unlocks a different class of citation. Content-based AEO gets your information cited. Entity recognition gets your name cited. The two are different outcomes with different business value — and entity building is what makes the difference.
Measurement discipline makes the investment defensible. Without the monthly manual testing protocol established in month one, the improvements would have been invisible to TechCo's leadership. The quarterly scorecard format allowed the engagement to demonstrate clear, quantified progress throughout — which maintained stakeholder confidence during the slow early months.
For the measurement framework used throughout this engagement, see AEO Reporting Metrics: How to Track AI Citations. For the pre-engagement audit process, the AEO Audit Checklist covers all the structural checks that preceded phase 1. And for a parallel SEO case study from a manufacturing context, see the Trivandrum Manufacturer SEO Case Study.