# Questions and straight answers

URL: https://wpexit.io/faq/
Description: What breaks when a WordPress site goes static, how edits work by chat, domains, email, going back, WCAG checks, timing, page counts, the plugin, and hosting.
Site: WPExit (Bit Source, Pikeville, Kentucky)

Everything we get asked before someone signs up, in one place. The short versions of the first six are on the home page.

## All questions

### What does agent-ready actually mean?

Three concrete things on every Rebuild. Machines can read the site: each page has a Markdown twin, an llms.txt index and schema.org data. Machines can act through it: a hosted MCP server lets an AI assistant list and read pages, search, and submit your forms as tools, so a person can say "ask this company for a quote" and it happens through your real form. And machines can trust it: every build is signed, with a manifest of page hashes and a public key anyone can check. You also pick an AI access policy, open, attribution or closed, which is published where crawlers look.

### Can I keep AI companies from using my content?

You choose. Closed disallows the known AI crawlers in robots.txt and says so in llms.txt and the agent manifest. Attribution lets them in on the stated condition that answers link to your page. Open is open. Search engines are always allowed. Like any robots policy it relies on crawlers honoring it; the well-known ones do, and the policy is also the record of what you permitted.

### What breaks when the site goes static?

Anything that ran PHP on each visit. Forms are the common one, and they keep working: we point them at our forms endpoint and email you each submission. Site search is replaced with a static index built at publish time, so it keeps working without a server. Comments become read-only; new comments are a server feature and we tell you up front if you depend on them. Stores, memberships, courses, forums, and directories do not fit; we flag those at the preview stage and you pay nothing.

### How do I make changes without WordPress?

On the Rebuild plan you ask for the change in chat: fix a phone number, swap a photo, add a paragraph, post a notice. Low-risk text edits apply right away with an undo. Larger changes wait for your approval before they go live. Every change is versioned, so any version can be restored. Freeze is for a site that does not change; when it needs to, move to Rebuild and the editor works from the same snapshot.

### What about my domain?

You keep it, at any registrar. The portal walks you through a verification record, then an A or CNAME record. If your DNS is on Cloudflare, it is one click. TLS certificates are issued automatically when the first request arrives.

### What about email?

WPExit does not host mailboxes, and your existing email is not affected by moving the website. The only mail we send is form notifications: each submission goes to the addresses your form plugin used, or ones you choose. You can add DNS records so those notifications come from your own domain.

### Can I go back?

Yes. Your WordPress install is yours and untouched. Once your domain points at us, your WordPress install is no longer reachable at that name. We suggest leaving it up for 14 days as a fallback, then cancelling the hosting. If you keep it running for editing on the Freeze plan, put it behind a private hostname and HTTP authentication; we will help you set that up. Going back means pointing your DNS at it again. Every snapshot we build is also kept, and you can download the files at any time.

### Is this ADA compliant?

We do not make legal claims about compliance. What we do: every Rebuild runs WCAG 2.2 AA checks (axe-core) at build time, serious and critical issues block publishing, and we remediate what the checks find in the templates and content. The measured violation count is in each site's build report.

### How long does it take?

A preview is usually ready the same day. Going live takes as long as your DNS change: minutes on Cloudflare, up to a day elsewhere.

### What counts as a page?

A public URL that returns HTML: pages, posts, category and tag archives, and so on. Images, PDFs, and the one-image attachment pages WordPress makes for every upload do not count; we keep those addresses working by redirecting them to the file. Page count sets expectations for the crawl, not the price: the migration fee is the same for every site.

### Do I have to install the plugin?

Not for the preview; we crawl what the public can see. For the migration itself, yes. The plugin gives the crawler a complete list of your URLs and redirects, lets it bypass caching so the copy is clean, and tells us which forms notify which addresses. It sends nothing until you click Connect.

### Where is the site hosted?

On servers we run in a US data center, behind Caddy with HTTP/3 and automatic TLS. There is no PHP, no database, and no admin login on the host. The security page lists exactly what we store.

### Freeze or Rebuild: which should I pick?

Freeze if you want the site exactly as it looks today and you still edit in WordPress. Rebuild if you want the speed and accessibility gains, and you would rather make changes by chat than keep a WordPress install around. You can start with Freeze and move to Rebuild later; both are built from the same crawl.

Something not covered? Use the form on the [pricing page](https://wpexit.io/pricing/).