Ariy&Co

Sites / Preparation

Prepare your website for Ariy Sites

Gather the site details, editable content and approval decisions needed for a useful website-management conversation.

Last reviewed October 8, 2026

Early access

Editorial perspective: Ariy&Co · Product guidance

Start with your existing website

You may already have a website you like. The question is which parts you need to keep current and whether its structure supports a controlled content workflow. Ariy Sites early access covers supported Ariy-managed sites; another CMS may need separately scoped integration or migration.

Make a short content inventory

  • Website URL and the person who owns or manages it.
  • Hosting and CMS details, if known. “Not sure” is a useful answer too.
  • Pages that change regularly: services, hours, team, contact or announcements.
  • Images, logos and written content you have permission to use.
  • SEO titles and descriptions you want reviewed.
  • Areas that should stay controlled, such as layouts, custom code and integrations.
Website URL:
Site owner or manager:
Hosting / CMS (or “not sure”):
Pages that need regular updates:
Images and content we have permission to use:
SEO titles or descriptions to review:
Areas that should stay controlled:
One example change:
Who can request a change:
Who can approve publication:
Who handles problems after release:

Do not include passwords, access tokens or other credentials. Agree a secure setup process separately.
This worksheet prepares a scope discussion; it does not confirm CMS compatibility, activate a subscription or authorize publication.

Download this template (.txt)

Bring one real change

Instead of “we want AI to manage everything,” try a request such as “Our service hours change seasonally, and I want to review the new hours before they go live.” That gives us a concrete path to assess.

Separate the content update from any new design requirement. Changing a paragraph and redesigning its section can have very different scopes.

Agree access and review responsibilities

Name who can request changes, who can approve publication and who handles a problem after release. Share credentials only through the agreed secure setup process, never in a public help request.

The agreed scope should distinguish the initial website build, any integration work, ongoing management and hosting. A preparation conversation is not a subscription or a promise that every CMS is supported.

Need a hand?

Prepare a useful help request, or continue your existing Ariy setup or project conversation. For Nia configuration, open your Front Desk settings.