If you have a ReactJS 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 ReactJS 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 ReactJS 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 ReactJS 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 a ReactJS site, the nameserver steps depend on where the domain was purchased.
How to Update Nameservers for a ReactJS Site
Step 1: Identify where the React site is hosted
Common ReactJS hosting options include:
Vercel
Netlify
AWS Amplify
Cloudflare Pages
Firebase Hosting
Hostinger / cPanel
Custom VPS
S3 + CloudFront
The hosting platform will give you the DNS records needed to connect your domain.
Step 2: Add the domain to Cloudflare
If you are using Cloudflare for an Edge integration or AI Visibility Engine setup:
Log in to Cloudflare.
Add the domain.
Let Cloudflare scan existing DNS records.
Confirm all important records are copied over, including email and verification records.
Step 3: Add the correct DNS records for your React host
In Cloudflare, go to:
DNS → Records
Then add the records required by your hosting provider.
Common examples:
Hosting Platform | Common DNS Setup |
Vercel | CNAME for www, A record or CNAME for root |
Netlify | CNAME for www, A record or ALIAS-style setup for root |
Cloudflare Pages | CNAME to the Cloudflare Pages target |
AWS CloudFront | CNAME to the CloudFront distribution |
Firebase Hosting | A records and TXT verification records |
cPanel hosting | A record pointing to the server IP |
Do not guess these records. Use the exact records provided by the hosting platform.
Step 4: Update nameservers at the domain registrar
Log in to the account where the domain was purchased.
Go to:
Domain Settings → Nameservers
Then:
Choose Custom Nameservers
Remove the current nameservers
Add the two Cloudflare nameservers
Save changes
Cloudflare will give you the exact nameservers to use.
They usually look like:
name.ns.cloudflare.com
name.ns.cloudflare.com
Step 5: Wait for propagation
Nameserver changes can take a few hours, but sometimes up to 48 hours.
After the update, test:
yourdomain.com
Both should load the ReactJS site.
Step 6: Verify everything still works
Check:
Website loads correctly
HTTPS/SSL works
Email still works
Contact forms still work
Google Search Console verification still works
Any subdomains still work
Important Note
For a ReactJS site, the nameserver change happens at the domain registrar, while the DNS records must point to the hosting provider.
For an Edge or AI Visibility Engine integration, the usual setup is:
Domain Registrar → Cloudflare Nameservers → DNS records point to React hosting provider
This allows Cloudflare to manage the DNS and Edge layer while the React site remains hosted wherever it currently lives.