Choose the route your website supports
WordPress uses a site connection and application password. Framer needs a project API key, article collection and field mappings. For a custom or AI-built website, a developer or coding assistant installs an API-backed blog that renders article HTML on your own site.
A managed blog is an alternative for website builders where you prefer a separate blog subdomain. That route needs domain setup and a navigation link; it does not mean articles are inserted into the builder's native CMS.
Verify the complete public page
After connecting, complete the installation check and inspect a delivered article. Its title, body, summary, images and links should appear in the listing and detail template. Existing blogs also need their original content source and URLs preserved.
For API installations, the public article needs useful initial HTML, stable URLs and the required metadata. A page that only loads its text after a browser script runs is not the installation contract described in the developer guide.
Follow delivery after approval
An approved article can still encounter a connection problem. Check the status and resolve the specific destination issue before retrying. For example, Framer delivery can wait while unrelated project changes are unpublished.
Search Console access is a separate connection for search data. Neither a publishing success nor a sitemap entry confirms indexing or rankings. Monitor the public page and search data as separate parts of the process.
Common questions
- Can I keep an existing blog?
- Yes, but preserve its address and original content source. Follow the existing-blog instructions for your platform before changing its connection or publishing new articles.
- Is publishing completely automatic?
- You can choose automatic publishing after setup. Article checks and a verified connection are still required, and held articles or delivery failures can need attention.