Connect your publishing destination
Configure WordPress safely and understand the limits of other destinations.
Open Settings → WordPress for the selected clinic. You need the website address, a WordPress username, and credentials for a user allowed to create or publish posts. Ask your webmaster for help if you do not manage WordPress.
Create a WordPress application password
- Sign in to WordPress and open Users → Profile for the publishing user.
- Find Application Passwords.
- Enter a recognizable name such as “ClinGEO” and add a new application password.
- Copy the password shown once and enter it in the ClinGEO connection form.
An application password is separate from your main login password and can be revoked independently. Use a dedicated account with only the permissions required for your workflow. Follow the official WordPress application-password instructions.
Never place passwords in article text, support screenshots, or shared documents.
Verify the connection
Enter the clinic's HTTPS website URL, WordPress username, and application password in Connect WordPress, then connect and verify. After connecting, test the connection and check Where to publish articles.
A successful connection does not prove that the user can publish every type of post. Start with a WordPress draft and inspect it. Some sites use a compatibility connection; publishing and SEO metadata support can differ.
If authentication is blocked, ask your webmaster to check the appropriate authenticated WordPress endpoints and user permissions. Do not disable two-factor authentication or the website firewall globally.
Other CMS cards
Webflow, Shopify, Wix, and Framer settings may appear, but direct article publishing to these destinations is not implemented. A saved connection is not a working publication route.
For these sites, export Markdown from the article editor and hand the content to the person who publishes in your CMS.
Advanced copy delivery
An advanced webhook destination sends a copy to a server endpoint maintained by your developer. Configure its delivery URL and content format, and securely retain the one-time signing key. The receiving server must validate the signed requests and implement whatever happens next.
A successful test or Delivered result does not mean a public page exists. Email delivery may also depend on administrator configuration and is not available in every account.