Skip to main content

AI Visibility Engine Integration for Angular Sites

Written by Sebastiaan Jooste

If you have an Angular site, there is a chance your site may not be fully visible to AI bots like ChatGPT, Perplexity, Gemini, and Claude.

This often happens because many Angular sites rely heavily on JavaScript-rendered content. If important content on your site is loaded through JavaScript, some AI crawlers may struggle to read, understand, and index it properly. As a result, your products, collections, blogs, and key site content may not be fully consumed or cited by large language models.

This can negatively affect your performance across AEO, GEO, SEO, and AI visibility.

Alli AI has developed an AI Visibility Engine that helps solve this problem by prerendering your website and serving an HTML version of your site to AI bots when they crawl it. This makes your content easier for LLM crawlers to access, understand, and cite.

By providing a clean, crawlable HTML version of your Angular site, the AI Visibility Engine can also help speed up the crawling process, allowing AI bots to discover and consume more pages across your site.

To integrate your Angular site with Alli AI’s AI Visibility Engine, we recommend using the Edge integration method. This setup uses Cloudflare or AWS CloudFront service workers to deliver the prerendered HTML version of your site to AI crawlers.

The final step usually involves switching your nameservers to Cloudflare to complete the integration.

Here is an Article on how to complete the AI Visibility Edge Integration: https://help.alliai.com/en/articles/15787799-ai-visibility-engine-edge-integration-using-cloudflare-workers

Once the Cloudflare setup is complete, the nameservers need to be updated.

For an Angular site, the nameserver steps depend on where the domain was purchased.

Updating Nameservers for an Angular Site

An Angular site does not have nameservers inside Angular. Nameservers are updated where the domain was purchased, such as GoDaddy, Namecheap, Hostinger, Porkbun, Cloudflare, or another registrar.

Step 1: Confirm Where the Site Is Hosted

First, identify where the Angular site is hosted, such as:

  • Netlify

  • Firebase Hosting

  • AWS Amplify

  • Cloudflare Pages

  • Vercel

  • cPanel

  • Custom server

The hosting provider will give you the DNS records needed to connect the domain.

Step 2: Add the Domain to Cloudflare

If using Cloudflare for an Edge integration:

  1. Log in to Cloudflare.

  2. Add the domain.

  3. Let Cloudflare scan the current DNS records.

  4. Confirm important records were copied over, including email, TXT records, and subdomains.

Step 3: Add the Hosting DNS Records

In Cloudflare, go to:

DNS → Records

Add the DNS records provided by the Angular hosting provider.

These may include:

  • A records

  • CNAME records

  • TXT verification records

Use the exact records from the hosting platform.

Step 4: Update Nameservers at the Registrar

Log in to the account where the domain was purchased.

Go to:

Domain Settings → Nameservers

Then:

  1. Choose Custom Nameservers

  2. Remove the current nameservers

  3. Add the two Cloudflare nameservers

  4. Save changes

Step 5: Verify the Site

After propagation, test:

Also confirm:

  • HTTPS works

  • Email still works

  • Contact forms work

  • Subdomains still work

Summary

For an Angular site, update nameservers at the domain registrar, point them to Cloudflare, and make sure Cloudflare DNS records point to the Angular hosting provider.

Did this answer your question?