nakisa.com — AI Site Grade

Analysis

Nakisa.com: A JS-Rendered Shell Invisible to AI Crawlers

Every page on nakisa.com — homepage, product pages, blog posts, case studies, resource guides — returns exactly 11 words of visible text ("Hear from our clients why they love using Nakisa Learn more") to any HTTP client, including all major AI crawlers. The site is a single-page application shell with no server-side rendering, no prerendering, and no static fallback. AI bots receive the same empty JavaScript bootstrap as browsers but cannot execute it.

Crawler Access

All AI bots — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Applebot-Extended, Bytespider, anthropic-ai, ChatGPT-User, Perplexity-User — receive HTTP 200 responses with ~1.9 MB of HTML that contains zero substantive content. The robots.txt at /robots.txt is a bare Yoast-generated file with User-agent: * Disallow: (no restrictions) and a sitemap reference. No AI-specific directives exist. The /llms.txt URL produces a redirect loop error. The site runs on nginx (hosted at IP 45.79.178.79, likely Linode) with no Cloudflare or WAF layer — the blocking is architectural, not security-driven.

Content & Schema Posture

The homepage <title> and <meta description> are well-written ("AI-Driven Enterprise Solutions for HR, Finance, and Real Estate"), and every page has proper Organization, BreadcrumbList, and SiteNavigationElement JSON-LD schema. Case study pages (/case-studies/sanimax/) embed rich VideoObject schema with full transcripts of customer testimonials — this is the only machine-readable content on the site. However, the visible DOM is empty. The heading structure is a flat wall of ~80 identical H2: Products / H2: Integrations / H2: Solutions / H2: Services entries (the navigation menu rendered as headings), with no H1 on any page. FAQ schema appears on product pages but the actual FAQ content is invisible.

Cold-Knowledge Gap

The LLM prior knows Nakisa as "cloud-based organizational design, workforce planning, and lease accounting software" with products named "Hanelly" and "Lease Administration," and notes SAP partnership and Gartner recognition. The current site never mentions "Hanelly" — that product line has been rebranded under "Workforce Planning Software" and "Decision Intelligence Platform." The site now leads with "AI-driven," "Agentic Decision Intelligence," and "Nakisa AI" — terminology absent from the model's cold knowledge. The model also knows nothing about Nakisa's CCCS Protected B authorization (a Canadian government security certification prominently featured on every page's footer) or the new Nakisa Decision Intelligence (NDI) platform.

External Signals

External search results for Nakisa are conspicuously sparse. Searches for "Nakisa lease accounting software reviews," "Nakisa Hanelly," and "site:nakisa.com" returned zero results from DuckDuckGo. The DNS TXT records reveal integrations with Anthropic (domain verification), Atlassian, DocuSign, HubSpot, Intacct, Rippling, and Microsoft — indicating a complex enterprise SaaS stack. The site has a YouTube channel and LinkedIn presence, but no indexed reviews, Gartner mentions, or press coverage surfaced in search.

Surprising Finding

The about/ page is set to noindex, follow — the company's own about page is deliberately excluded from search engine indexes. The blog contains posts dating back to 2018 (e.g., "The Top 5 Ways Tech Is Improving HR"), but none of their text content is accessible to crawlers. The site has a sitemap index with 20 sub-sitemaps and 320+ URLs, yet every indexed page is a JS shell. This creates a situation where Google may index the URLs but cannot extract content, and AI crawlers receive empty pages despite being technically allowed.

Findings

1. All pages render as empty JavaScript shells with no server-side rendering High

   Every page on nakisa.com returns only 11 words of visible text to HTTP clients, including AI crawlers. The site is a single-page application with no SSR, prerendering, or static fallback, so AI bots receive a bootstrap HTML with no substantive content.

   What to change: Implement server-side rendering (SSR) or static site generation (SSG) for all pages, or use a prerendering service to deliver fully rendered HTML to crawlers.

2. llms.txt file is missing and produces a redirect loop Medium

   The /llms.txt URL returns an error due to excessive redirects, preventing AI crawlers from discovering a structured summary of the site's content.

   What to change: Create a valid /llms.txt file that provides a plain-text overview of the site's key pages and content for AI crawlers.

3. About page is set to noindex, excluding it from search engines Medium

   The /about/ page has a noindex meta tag, preventing search engines from indexing the company's own about page. This reduces the site's discoverability.

   What to change: Remove the noindex directive from the about page to allow search engines to index it.

4. All pages have no H1 and a flat wall of identical H2 headings from navigation Medium

   Every page lacks a proper H1 heading and instead has approximately 80 identical H2 entries (e.g., 'Products', 'Integrations') that are just the navigation menu rendered as headings. This harms semantic structure and accessibility.

   What to change: Add a unique H1 heading to each page and use a proper heading hierarchy (H1, H2, H3) that reflects the page's content structure.

5. LLM cold knowledge is outdated: product rebranding and new AI platform are missing Medium

   The LLM prior knows Nakisa for products like 'Hanelly' and 'Lease Administration', but the current site has rebranded to 'Workforce Planning Software' and 'Decision Intelligence Platform'. The new 'Nakisa AI' and 'Agentic Decision Intelligence' terminology is absent from the model's knowledge.

   What to change: Ensure that AI crawlers can access the full text of product pages so that LLMs can update their knowledge with the current product names and descriptions.

6. CCCS Protected B certification is not captured by LLMs Medium

   The site prominently displays a Canadian government security certification (CCCS Protected B) in the footer, but this information is not accessible to AI crawlers and is absent from the LLM's cold knowledge.

   What to change: Include the certification text in the visible HTML (not just images) and ensure it is crawlable.

7. No external reviews or press coverage appear in search results Low

   Searches for Nakisa reviews, Gartner mentions, and site-specific queries returned zero results from DuckDuckGo, indicating low external signal presence.

   What to change: Encourage customer reviews on third-party platforms and improve SEO to increase indexed external content.

8. Blog content is invisible to crawlers despite being technically allowed High

   The blog contains posts dating back to 2018, but none of the text content is accessible to crawlers because the pages are JS shells. AI crawlers receive empty pages even though robots.txt allows them.

   What to change: Implement SSR or prerendering for blog pages to deliver the full article text to crawlers.

9. FAQ schema exists but FAQ content is invisible to crawlers Medium

   Product pages include FAQ JSON-LD schema, but the actual FAQ questions and answers are not rendered in the HTML, so crawlers cannot extract them.

   What to change: Ensure FAQ content is present in the initial HTML (server-side rendered) so that schema matches visible content.

10. Robots.txt lacks AI-specific directives Low

    The robots.txt file is a bare Yoast-generated file with no AI-specific user-agent rules. While this technically allows all bots, it also means no guidance is provided for AI crawlers.

    What to change: Add explicit directives for AI crawlers (e.g., GPTBot, ClaudeBot) to control access and provide hints.

What's working

• Robots.txt allows all crawlers with no restrictions — The robots.txt file has no disallow rules for any user-agent, meaning all AI crawlers are technically permitted to access the site.
• All pages include Organization, BreadcrumbList, and SiteNavigationElement JSON-LD schema — Every page has proper structured data markup for organization, breadcrumbs, and navigation, which helps search engines understand site structure.
• Case study pages embed VideoObject schema with full transcripts — The Sanimax case study page includes VideoObject JSON-LD with a complete transcript of the customer testimonial, providing machine-readable content.
• Homepage has well-written title and meta description — The homepage title and meta description are descriptive and keyword-rich, which helps with search engine ranking and click-through rates.
• Sitemap index with 20 sub-sitemaps and 320+ URLs is available — The sitemap index at /sitemap_index.xml contains 20 sub-sitemaps and over 320 URLs, providing a comprehensive list of pages for crawlers.
• DNS TXT records show integration with Anthropic for domain verification — The DNS records include an Anthropic domain verification TXT record, indicating proactive engagement with AI platforms.