The Edge Protocol

Enterprise Deployment Guide

A step-by-step masterclass on securely launching your Footprint-Free Satellite networks. From raw HTML export to bypassing AI firewalls and forcing Google indexation.

archive Phase 1: Pre-Flight Export

Before your site hits the internet, Threadweb compiles your dynamic project into a pristine, crawler-optimized static package. This is the foundation of your SEO security.

1. Automated CSS Consolidation
Threadweb automatically extracts all inline styles and compiles them into a single style.css file, linking it cleanly in the <head>.

Why it's important: Serving the same CSS block repeatedly across 50 pages destroys your Crawl Budget. A single, cached stylesheet makes your site lightning-fast for Google's Web Rendering Service (WRS).
2. Class Obfuscation & Sitemap Generation
During export, CSS class names are mutated with unique prefixes, and a dynamic sitemap.xml & robots.txt are instantly generated.

Why it's important: Class obfuscation destroys the "Agency Template" footprint. Automated sitemaps ensure Googlebot maps your hierarchy on Day 1.

dns Phase 2: Edge Hosting & Version Control

You can use Threadweb's 1-click Netlify deploy, but for Enterprise-grade security and rollbacks, we recommend linking a private GitHub repository.

The Git-to-Netlify Pipeline

Export your project ZIP from Threadweb and extract it to a local folder.
Initialize Git and push it to a Private GitHub repository.
Log into Netlify or Vercel, select "Import from Git", and link your repo.
Leave the Build Command blank, and set Publish Directory to . (root).

Why it's important (IP Isolation): By pushing to Netlify/Vercel, your static HTML files are instantly served on globally redundant Edge nodes. You completely bypass the "Shared Hosting Trap" (matching C-Block IPs and Nginx headers) that gets PBNs penalized.

security Phase 3: The WAF Bypass (Crucial)

If you route your custom domain through Cloudflare to secure it, the default Web Application Firewall (WAF) will block automated scrapers. This will silently kill your generative AI traffic.

Whitelist AI Retrieval Bots

You must manually audit your firewall and create an exception for AI agents fetching live answers.

Go to Cloudflare Dashboard > Security > WAF.
Click Create Rule. Name it Allow Real-Time AI Crawlers.
Use this exact Expression Builder logic:

                    (http.user_agent contains "OAI-SearchBot") or (http.user_agent contains "ChatGPT-User") or (http.user_agent contains "ClaudeBot") or (http.user_agent contains "PerplexityBot")
                

Set the Action to: Skip (WAF Managed Rules).

Why it's important: `OAI-SearchBot` retrieves live data to answer user queries on ChatGPT. If your WAF returns a 403 Forbidden error, OpenAI abandons your site immediately. You lose the citation and the zero-click traffic.

troubleshoot Phase 4: GSC & Indexation

You cannot just publish and pray. You must force Google's hand to claim your indexing territory.

1. HTML Tag Verification
In Google Search Console, choose URL Prefix. Do not use DNS verification for temporary Netlify subdomains. Select HTML Tag, copy the provided <meta name="google-site-verification"> code, paste it into your index.html, and re-deploy.
2. Submit the Map & Nudge the Bot
Navigate to Sitemaps in GSC and submit sitemap.xml. Immediately after, paste your homepage URL into the top inspection bar and click Request Indexing.

Why it's important: The "Nudge" prioritizes your domain in Google's queue. By serving obfuscated, perfectly semantical HTML with a pre-mapped sitemap, you manipulate the Web Rendering Service into granting you full crawl budget.

query_stats Phase 5: Telemetry & Analytics

Measuring the success of your satellite network requires precision. Doing it improperly will expose your entire network to Google's spam team.

1. Privacy-First Tracking (No Shared G-IDs)

NEVER place the exact same Google Analytics 4 (GA4) tracking ID across multiple satellite domains. This creates an immediate, mathematically undeniable link-graph footprint. Use cookieless, privacy-first alternatives like Plausible or Fathom, or create entirely independent GA4 properties per satellite.

2. The "New Tab" Dwell Time Hack

Every link pointing from your Satellite to your Main Hub MUST open in a new tab and be configured securely.

                    <a href="https://your-main-hub.com" target="_blank" rel="noopener">
                

Why it's important (Dwell Time & Attribution): Opening in a new tab keeps the satellite site open in the background, maximizing "Time on Page" and lowering "Bounce Rate" (massive SEO signals). Using rel="noopener" instead of noreferrer ensures your Main Hub's analytics correctly attribute the incoming traffic to the satellite, rather than marking it as "Direct" traffic.