# Leave WordPress behind without treating years of authority as disposable.

> Intakit rebuilds the public site on a separately deployed public-only runtime, preserves the governed web estate, adds native SEO and AI-readable authority, and connects visitors to the protected firm workspace.

**Operating promise:** Keep every authority signal accountable. Remove the fragile stack.

**Availability:** Native Sites is in controlled release with Albaugh as the first proof migration. The isolated runtime and evidence system are proven on the QA domain; a customer-domain launch is accepted only when that customer’s route, security, analytics, and rollback packet is green.

## Intakit Sites pages

- [Intakit Sites](https://intakit.com/sites)
- [Intakit Sites Connected](https://intakit.com/sites/connected)
- [Intakit Sites Native](https://intakit.com/sites/native)
- [Aegis Authority Migration](https://intakit.com/sites/migration)
- [The Intakit Preservation Covenant](https://intakit.com/sites/preservation)

## Public by design. Separate by design.
Move the public website to a separately deployed public-only Intakit runtime that preserves the governed web estate, removes the public WordPress/plugin stack, adds machine-readable authority, and hands visitors securely to the protected firm workspace.

    The Sites runtime has no Intakit app sessions and no broad client, case, or document access. Only approved public publications cross the boundary.

    Controlled-release status: the isolated runtime and compiled Albaugh publication are proven in staging. A customer domain is not accepted for launch until approval, activation, rollback, and export controls pass that customer’s evidence gate.

    
### Production public surface and launch standard

      - Custom domain, TLS, CDN caching, managed public assets, pages, posts, search, archives, RSS, redirects, and sitemap.

      - Metadata, structured data, llms.txt, public AI-discovery surfaces, attribution, and secure application handoff.

      - Draft, attorney review, preview, activation, rollback, audit evidence, export, and publication monitoring.

    
## Keep what earned trust. Remove what creates drag. Gain what the old stack cannot provide.

    The point is not React instead of WordPress. It is moving the firm’s public authority onto an isolated, measurable foundation without disconnecting it from intake and firm intelligence.

    - **Keep:** The firm’s domain, approved brand and content, valuable URLs, canonical signals, analytics ownership, backlinks, and export rights.
- **Remove:** The public WordPress runtime, plugin and patch treadmill, fragile templates, disconnected forms, duplicate hosting tools, and opaque vendor handoffs.
- **Gain:** A public-only runtime, direct protected Intakit journeys, governed publishing, stronger machine-readable authority, measurable attribution, and evidence-led releases.

  
## Confidence comes from what happens before DNS

    The current website stays live while Intakit builds and proves the replacement beside it. An unexplained route difference, broken protected journey, analytics failure, or unrehearsed rollback keeps launch blocked.

    - **Inventory what the firm has earned:** Combine crawl, sitemaps, CMS data, redirects, analytics landing pages, backlinks, and available logs into one governed URL denominator.
- **Rebuild beside the live site:** Create the Native publication on an isolated, non-indexable host while the existing website and customer DNS remain unchanged.
- **Compare what users and crawlers receive:** Check status, redirect destination, canonical, metadata, heading, authoritative content, links, assets, schema, and indexability after browser rendering.
- **Prove the operational seams:** Verify protected inquiry and portal journeys, attribution, analytics, TLS, CSP, accessibility, performance, publication identity, and rollback readiness.
- **Cut over only the approved release:** Change public web DNS only after named customer and Intakit owners accept the evidence packet, then monitor through 30-day hypercare.

  
## The first proof is measured, not hypothetical

    Albaugh staging proof · July 10, 2026

    - 292 content routes
- 111 archive routes
- 80 governed redirects
- 0 parity blockers

    The exact QA-host browser gate found zero failed redirects, unresolved internal links, or failed public assets and measured 100% minimum normalized coverage of the imported governed body corpus. This is staging evidence for the governed corpus—not a ranking guarantee or the final customer-domain launch certificate.

  
    
## Pricing

    Controlled early access: Native Sites is in controlled release with Albaugh as the first proof migration. The isolated runtime and evidence system are proven on the QA domain; a customer-domain launch is accepted only when that customer’s route, security, analytics, and rollback packet is green.

    - Connected Foundation: Included — Included with Starter, Professional, and Enterprise: protected journey links, attribution receipt, and endpoint monitoring. Authority Review, remediation, and automatic connectors are separate and verified per CMS.
- Native Professional: $499/mo — $4,990/year for one public site. Recurring billing begins at customer-domain launch; migration is separate.
- Native Enterprise: Included — One Native public site is included with Enterprise after launch approval. Migration is separate.
- Authority Review: $750 — Delivered within two business days after complete access. Credited to an accepted Authority Migration within 90 days.

    
### Authority Migration tiers

    - Focused: $8,000 — Up to 75 canonical content routes, one brand/CMS/theme, two offices, ten biographies, one protected journey mapping, two consolidated review rounds, and 30-day hypercare. Preview: Working preview in 1–2 business days after Review approval. Launch-ready: Launch-ready within 5 business days after Review approval.
- Content-rich: $12,000 — Up to 300 canonical content routes, one brand/CMS/theme, five offices, 25 biographies, blog/archive/search/RSS, three protected journey mappings, two consolidated review rounds, and 30-day hypercare. Preview: Working preview in 2–3 business days after Review approval. Launch-ready: Launch-ready within 10 business days after Review approval.
- Custom: Custom SOW — More than 300 routes, multiple brands or CMSs, custom applications, ecommerce, rescue work, or unusual workflows. Preview: Preview target defined in the approved SOW. Launch-ready: Launch-ready target defined in the approved SOW.

    Migration pricing is based on canonical content routes, not generated archives or governed redirects. The signed Authority Review locks the tier, evidence sources, exclusions, review rounds, and custom requirements.

[Book an Intakit Sites consultation](https://intakit.com/sites?consultation=1)