External Website implementation package
Prepare, hand off and verify changes when Aetherion cannot edit the website directly.
When to use manual implementation
Use External Website · manual implementation when the SEO Site has a public URL but Aetherion has no connected Aetherion Project or writable source. It works with any CMS or agency workflow because Aetherion prepares the change and verifies the public result without pretending it modified the site.
No connector required
WordPress, Shopify, Wix, Webflow and custom CMS sites can use the same package. Publication still happens through the site's own administrator, developer or agency.
Prepare and hand off the package
Open the Content Brief
Choose the measured task and confirm the target route and required content changes.
Prepare implementation package
Aetherion captures a fresh public before snapshot and creates the next version linked to this task and page.
Choose the correct view
Content editor explains the answer and structure, Developer provides head HTML, visible HTML and JSON-LD, and Client / agency provides scope and acceptance criteria.
Copy or Download ZIP
Copy one code block, copy the current view or download the complete versioned package for handoff.
Publish outside Aetherion
Implement the approved content, metadata, canonical and schema through the site's normal workflow, then publish the target page.
Approve every first-party fact
Bracketed factual slots are intentional. Replace them with verified organization-owned facts before publication. Never invent credentials, dates, people, statistics or product claims to complete the package.
Declare publication and check the live page
Complete the checklist
Mark the implemented items and confirm Page published. The checklist guides the handoff but cannot verify the website by itself.
Choose I’ve published · check live
This records the manual implementation checkpoint and immediately crawls the target page against the latest package version.
Read every public check
Repair missing content, old metadata, incorrect canonical, absent schema, blocked indexing or an unchanged public fingerprint, then choose Check live again.
Continue at Ready to retest
Only a complete public pass unlocks the provider retest. Earlier package versions remain in history but cannot validate the newest task iteration.
Package preparation, checklist updates, ZIP download and public verification are plan-included and make no AI request. The later Provider retest remains a separately confirmed billed action.
Need project-specific help?
Open the private Help Center or create a support ticket with the affected project, route and request ID.