azilen.com — AI Site Grade

Analysis

I have a comprehensive picture now. Let me write the audit.

AI crawlers see the full site, but the cold-knowledge gap is stark

Azilen positions itself as an enterprise AI development company building headless agentic systems, yet cold LLM knowledge still describes it as a traditional Indian IT services firm founded in 2005 — a 20-year-old framing that the site itself contradicts (it claims founding in 2009 on the brand page). Every major AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended) receives a 200 with full HTML content — no blocks, no JS shells, no UA-based discrimination. The site runs on a bare nginx/1.18.0 server on AWS (52.211.41.140) with no CDN or WAF layer, meaning crawlers hit origin directly.

Crawler Access

The robots.txt at https://www.azilen.com/robots.txt contains a single catch-all User-agent: * rule that only disallows /wp-admin/, search result pages, and the search endpoint. No AI-specific bot directives exist — no mention of GPTBot, ClaudeBot, Google-Extended, or any other crawler. The compare_bot_access test confirms every AI bot gets the full 672KB page identical to a browser baseline. The site has an llms.txt (rare and positive) generated by All in One SEO Pro v4.9.7.2, containing 264KB of blog post listings and sitemap references — but it is an auto-generated dump of every post URL rather than a curated, high-signal content map for LLMs.

Cold-Knowledge Gap

The LLM prior describes Azilen as "an IT services and product engineering company based in Ahmedabad, India, founded in 2005" with "notable products including Azilen SmartHub" and partnerships with "AWS, Microsoft, and Salesforce." The actual site says founded in 2009 (not 2005), makes zero mention of "Azilen SmartHub," and lists no Microsoft or Salesforce partnerships. The homepage leads with "Enterprise AI Development Company" and "Headless Agentic AI" — a complete repositioning from IT services to AI-first engineering. The cold model knows nothing about the agentic AI pivot, the 100+ AI systems claim, or the 10+ global awards displayed on the awards page.

Schema Posture

The homepage carries LocalBusiness, Organization, WebPage, WebSite, and BreadcrumbList schema — solid structural foundation. The AI agent development services page includes a FAQPage schema with 9 detailed Q&A entries covering agent capabilities, integration, timelines, and costs. Case study pages use Article schema with author and date metadata. Missing: Service schema for the specific AI service offerings, Product schema for the agentic AI platform, and Review schema for the client testimonials displayed on the homepage (which are plain text quotes with no structured markup).

External Signals

The site has near-zero discoverable external footprint from the tools used. No Reddit mentions, no Clutch profile surfaced in search, no press coverage found. The homepage links to a Forbes profile for CEO Naresh Prajapati and lists awards from TITAN Business Awards, Globee, Corporate Vision, and World Business Outlook — but these recognitions are self-published on the site with no corroborating third-party coverage. The DNS records show Atlassian verification (Jira/Confluence), Zoho, Qualtrics, and Freshsales — a fragmented SaaS stack that hints at operational complexity.

Findings

1. Cold LLM knowledge describes Azilen as a traditional IT firm, contradicting its AI-first positioning High

   LLM prior knowledge describes Azilen as an IT services company founded in 2005 with products like Azilen SmartHub and Microsoft/Salesforce partnerships. The actual site claims founding in 2009, makes no mention of SmartHub, and lists no Microsoft or Salesforce partnerships. The homepage leads with 'Enterprise AI Development Company' and 'Headless Agentic AI' — a complete repositioning that cold models do not reflect.

   What to change: Publish a dedicated AI visibility page or update the homepage with structured data that explicitly states the company's AI focus, founding year, and key differentiators. Submit the site to LLM knowledge bases and ensure consistent messaging across all public profiles.

2. llms.txt is an auto-generated dump of blog URLs, not a curated content map Medium

   The site has an llms.txt file generated by All in One SEO Pro, but it contains 264KB of every blog post URL and sitemap reference rather than a curated, high-signal content map for LLMs. This reduces its effectiveness for AI crawlers seeking concise, authoritative information.

   What to change: Replace the auto-generated llms.txt with a manually curated version that includes only the most important pages (homepage, services, about, case studies) and a brief company summary.

3. No Service or Product schema for AI service offerings Medium

   The AI agent development services page and other service pages lack Service or Product schema markup. This limits AI crawlers' ability to understand and surface specific offerings like 'Agentic AI Development' or 'AI-Powered Lending Solution'.

   What to change: Add Service schema to each service page with properties like name, description, provider, and areaServed. Add Product schema for the agentic AI platform if applicable.

4. Client testimonials lack Review schema markup Medium

   The homepage displays client testimonials as plain text quotes with no structured Review schema. This prevents AI crawlers from extracting and citing these social proof signals.

   What to change: Wrap each testimonial in Review schema with itemReviewed pointing to the company (Organization) and properties for reviewRating, author, and reviewBody.

5. Near-zero discoverable external signals from third-party sources High

   Web searches for Azilen on Clutch, Reddit, and general reviews returned zero results. The site's awards and Forbes CEO profile are self-published with no corroborating third-party coverage. This lack of external signals reduces AI crawlers' confidence in the company's claims.

   What to change: Actively build external presence on platforms like Clutch, G2, and industry publications. Encourage clients to leave reviews and ensure awards are covered by third-party news outlets.

6. robots.txt lacks AI-specific bot directives Low

   The robots.txt file contains only a catch-all User-agent: * rule disallowing /wp-admin/ and search pages. No AI-specific bots (GPTBot, ClaudeBot, Google-Extended, etc.) are mentioned, leaving their access to default allow. While currently not blocking, this means the site cannot selectively manage AI crawler traffic or prevent future issues.

   What to change: Add explicit directives for AI crawlers (e.g., GPTBot, ClaudeBot) to allow or disallow specific paths as needed, and consider adding crawl-delay directives to manage load.

7. Fragmented SaaS stack hints at operational complexity Low

   DNS records show verification tokens for Atlassian (Jira/Confluence), Zoho, Qualtrics, and Freshsales. This fragmented tooling may indicate siloed operations that could affect content consistency and AI visibility efforts.

   What to change: Consolidate tools where possible to reduce complexity and ensure consistent content management and analytics.

What's working

• All major AI crawlers receive full HTML content with no blocks — Every tested AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended) receives a 200 response with the full HTML page, identical to a browser baseline. No UA-based discrimination or JS shell issues.
• Homepage includes LocalBusiness, Organization, WebPage, WebSite, and BreadcrumbList schema — The homepage carries multiple schema types providing a solid structural foundation for AI crawlers to understand the business identity, website structure, and navigation.
• AI agent services page includes FAQPage schema with 9 detailed Q&A entries — The AI agent development services page uses FAQPage schema with detailed questions and answers covering agent capabilities, integration, timelines, and costs, helping AI crawlers extract specific service information.
• Case study pages use Article schema with author and date metadata — Case study pages like the AI-Powered Lending Solution include Article schema with author and date metadata, providing structured context for AI crawlers.
• Site has an llms.txt file, a rare and positive signal — The site publishes an llms.txt file, which is a rare and positive signal for AI crawlers. It provides a machine-readable summary of available content, even though it is auto-generated.
• Awards page lists recognitions with structured data — The awards page displays multiple awards (TITAN, Globee, Corporate Vision, World Business Outlook) with structured data, providing social proof that AI crawlers can index.
• Blog contains substantial content on software product engineering — The blog page has over 1300 words of content on software product engineering, providing a source of authoritative content for AI crawlers to reference.