Deliver a page your client can keep using.
Use AI design output as a starting point, not a dead-end deliverable. Import suitable content as blocks for everyday edits; retain trusted styled HTML where the design needs code. Agree on who maintains each part before handoff.
A practical client-page workflow
- Choose one campaign or service page and keep its source design.
- Import a draft on the client's staging site, using the editing format that fits the content.
- Review text, assets, desktop/mobile layout and important interactions with the client.
- Publish the reviewed page through the appropriate WordPress workflow, then check its public output.
- Hand over the original source, editing instructions and a clear maintenance owner.
Repeat the workflow. Don't share the authority.
A repeatable process helps across client sites, but each site's credentials, permissions, configuration, content and license status remain distinct.
- Confirm the intended site and owner before connecting.
- Use a dedicated credential for that site and role.
- Record the installed version, existing theme/builder and SEO owner.
- Back up before a meaningful change and test on staging when compatibility is uncertain.
- Review the specific target and proposed change.
- Verify the signed-out public result and revoke unused credentials.
Multisite is not a fleet dashboard
The release includes Multisite provisioning and network-identity improvements. That does not mean it provides a central console for arbitrary independent websites, a marketplace, or shared administration of every client installation.
Network administration can affect more than one subsite. Treat network activation, updates, shared files and super-administrator actions as wider-scope operations.
Licenses and commercial terms
Use the terms supplied with your license. This documentation does not establish a universal site allowance, support entitlement or price. Do not infer one from an older comparison table or a development README.
Keep hosting separate
WordPress editing access is not authorization to alter hosting, DNS, server configuration or account-wide files. Those operations need a separate scope, appropriate authority and their own recovery plan.