NextNet AI: Technical Setup & Troubleshooting Guide

For your Web Developer / IT Administrator: You/Your client are implementing NextNet AI, a next-generation AI-powered SEO and visibility platform. The platform transforms client content into structured vector representations—the same format AI models use to retrieve information. To complete the onboarding process, a few technical warnings on the domain need to be resolved.

Please review the following requirements and implement the necessary fixes to ensure the client's site can be properly crawled, vectorized, and cryptographically verified by AI systems.

1. Indexability Warning (robots.txt Block)

The Issue: The NextNet AI platform is detecting that the site's robots.txt file is disallowing crawling. The Consequence: The client's site must be crawlable very quickly and efficiently to optimize for LLMs. If the platform cannot crawl the site to create fresh, semantically rich vectors every single night, the site will be AI-invisible.

The Fix: * Please review the domain's robots.txt file.

• Ensure there are no blanket Disallow: / directives under a wildcard User-agent: *.
• Remove any specific blocks on standard HTTP libraries (like Python-urllib or httplib) that might inadvertently block our validation agents from reading the core content.

2. JWKS Endpoint & Content Signing Warnings

The Issue: The platform cannot locate the JSON Web Key Set (JWKS) endpoint or active signing keys. The Consequence: JWKS is a standardized JSON file that acts as a public repository for cryptographic public keys. This creates cryptographically verifiable metadata to signal authority and proven trust to AI. AI agents default to signed vectors, and content without them is treated as "legacy crawl only". While this is optional for basic domains, resolving it is highly recommended to maximize AI trust and visibility.

The Fix (Choose Option A or Option B):

Option A: Custom Subdomain (DNS Setup) You can use a canonical subdomain to host these resources. This requires adding three records into the DNS.

1. CNAME Record (Traffic): Point vectors-nextnet to the target vectors.nextnet.ai.
2. TXT Record 1 (Hostname ownership verification): Add a TXT record for _cf-custom-hostname.vectors-nextnet with the unique value provided in the client's NextNet AI dashboard.
3. TXT Record 2 (SSL certificate validation): Add a TXT record for _acme-challenge.vectors-nextnet with the unique value provided in the client's NextNet AI dashboard.

Option B: WordPress Integration (If applicable) If the site is hosted on WordPress, you can resolve this by installing our integration.

1. Generate the API key inside the NextNet AI platform.
2. Download the nextnet-ai-wordpress-plugin.zip file.
3. Install and activate the plugin on the WordPress site.
4. Configure the plugin using the API key generated in step 1.

Need Help? If you have any questions on where these updates should be made, please reach out to our support team at support@app.nextnet.ai, and we would be happy to help!