A connected site is only ready when four things work: the CMS connection, the website record in Accounts, the crawl into AI Memory and an actual publish. Run through this checklist for every new client site, and again after any change to the website or its credentials.
1. The CMS connection
In the Connect a Site form, Test Connection must pass before Connect becomes clickable. A passed test shows the CMS's success message, followed by "You can now connect your site to the app."
CMS | Success message |
|---|---|
WordPress | "Test connection successful! Credentials are valid." |
Webflow | "Test connection successful! Credentials are valid." |
Craft CMS | "Test connection successful! Token has required permissions." |
Odoo | "Test connection successful! Credentials are valid and have blog access." |
Drupal | The form may not show a message, but Connect becomes clickable. |
The WordPress, Drupal and Craft CMS tests create a test item and delete it again. WordPress keeps deleted posts in the Trash, so you may find a "Test Post" there.
2. The website in Accounts
Go to Companies > open the company > Websites tab.
Check that the new site is listed. Open it to reach its Members, Team Access, Approval and Social tabs.
Set the reviewers on the Approval tab if the client approves posts. See Setting approvers per website.
If the site does not appear after you clicked Connect, don't connect it again. Contact the UP-TO-DATE support team.
3. The crawl and AI Memory
In Accounts, go to Companies and find the company's Memory column.
Status | What it means |
|---|---|
Not started | No crawl yet. A Crawl button is shown. |
In progress | The crawl is running. |
To verify | The crawl finished. Click it to open the Sitemap tab and approve the result. |
Ready | Crawled and approved. |
The info icon next to the status explains why the company is in that state, and lets you resume a crawl that stalled.
The person who clicked Crawl receives a crawl-complete email. If it arrives, the pipeline worked end to end.
Approve the crawl on the Sitemap tab. See Approving a website crawl.
In the AI App, select the site and ask AI Chat a question about the client's services. An answer that uses real content from the site shows that memory retrieval works.
4. Publish end to end
In the AI App, select the connected site and create a short test post.
Publish it, or schedule it a few minutes ahead.
In the CMS, check the title, body, images, slug and category. For WordPress, also check the post type and any ACF fields. For multilingual sites, check that the translations are linked.
Delete the test post in the CMS.
Common failures
What you see | Likely cause | What to do |
|---|---|---|
"The provided URL does not seem to be a valid WordPress site." |
| Open |
"Authentication failed. Please check your credentials." (WordPress) | Wrong username or Application Password, a revoked password, or a security plugin blocking Application Passwords. | Create a new Application Password and test again. |
"Error: Request failed with status code 403" | The CMS or a firewall refused the request, or the user may not create posts. | Check the user's role and any firewall or security plugin rules. |
Drupal "Error: Request failed with status code 404" | Wrong API Prefix, or JSON:API isn't enabled. | Open |
"Authentication failed. Please check your API key." (Webflow) | The token is wrong or revoked. | Generate a new site API token. |
"Unexpected response from Webflow. Status: 404" | The Collection ID is wrong. | Copy the Collection ID again. |
"GraphQL token has insufficient permissions for content creation." (Craft CMS) | The token's schema can read but not save entries. | Allow saving and deleting entries in the section. |
"Authentication successful but user does not have access to blog posts..." (Odoo) | The Odoo user lacks Website blog rights. | Give the user access to blog posts. |
"No pages found" on the Sitemap tab | No sitemap could be read. | |
The crawl-complete email says many pages couldn't be reached | Bot protection or a consent wall blocks automated visitors. | Allow automated access to public pages. |
The Not approved yet warning | No Product or Service pages were found, usually because only part of the sitemap was read. | Click Look for more sitemaps or correct the page types. |
For more symptoms, see Troubleshooting: website connections and crawls.