Publish to Webflow
Install the ProjectHQ App for Webflow, pick an authorized site, map your blog's CMS collection once, and publish each article as a live CMS item with its images.
The ProjectHQ App for Webflow publishes each article as a live item in your blog's CMS collection, with its images uploaded to your Webflow site. You authorize Webflow, pick a site and match the collection's fields once; after that, Publish in the editor is all it takes.
Before you start
- A ProjectHQ account. If you don't have one yet, you create it during installation.
- A ProjectHQ subscription for the site. Publishing to Webflow needs an active paid subscription ($99/month per website). A new site gets a 14-day free trial (card required, nothing charged for 14 days), and Webflow publishing is included in it. Connecting Webflow is not a separate charge. See Plans, trial and limits and pricing.
- A Webflow site with a CMS collection for your blog, and a Rich text field in it to hold the article body.
- A site that has been published at least once in the Webflow Designer — Webflow can't create live CMS items on a site that has never been published.
- Permission to install Apps. Your Webflow role needs the Install/uninstall Apps permission for the site. This is not limited to Workspace Admins — several Workspace and site roles can have it.
Install from Webflow
This is the path when you start from the ProjectHQ listing in the Webflow Marketplace. You never type your website's address: ProjectHQ reads it from Webflow.
- Click Install on the listing. ProjectHQ opens; sign in, or sign up if you're new.
- Click Continue to Webflow. On Webflow's consent screen, choose which sites ProjectHQ may use and approve. (If you decline, you come back to ProjectHQ and can start again.)
- Back in ProjectHQ, choose one of the sites you authorized. ProjectHQ creates a project from the site's name and domains as Webflow reports them — or, if you already have a project for that domain, you can pick it instead. Nothing on your site is crawled.
- Click Finish installation. If the site doesn't have a ProjectHQ subscription yet, start it on the next screen (Start free trial opens Stripe's secure checkout).
- You land on your blog's Webflow connection. Continue with Step 2 below.
Connect from ProjectHQ
If you already use ProjectHQ for this site:
- In ProjectHQ, open your blog's Settings → Publishing and choose Webflow (see Publish to your website).
- Click Connect Webflow.
- On Webflow's screen, choose which sites ProjectHQ may use and approve. You come back to the same place in ProjectHQ.
You can connect more than one Webflow account: Add account signs in again. To add a site you didn't grant at first, connect again and choose it.
What ProjectHQ asks Webflow for, and why
| Permission | What it's used for |
|---|---|
| Sites — read | List the sites you authorized so you can pick one, and read their name and domains. |
| CMS — read and write | Read your collections and their fields to build the mapping; create and update the live items your articles become. |
| Assets — read and write | Upload article images to your site's assets, so nothing is hosted off-site. Webflow grants asset access as read and write together; ProjectHQ only uploads images and never lists or downloads the assets already on your site. |
| Authorized user — read | Your Webflow email address, shown so you can tell connected accounts apart. |
Nothing else is requested. The App can't see or change your Designer content, site settings, forms or site users.
Step 2: pick the collection
Under Destination, choose the Account, Site and Collection. ProjectHQ picks the likely blog collection for you (one called "Posts", "Blog", "Articles" and so on). Collections without a Rich text field are marked and can't be chosen.
Step 3: map the fields
Under Field mapping, tell ProjectHQ which collection field gets what. It suggests a mapping as soon as the collection loads:
- The article body → a Rich text field (required).
- The featured image → an Image field (optional).
- The meta description → a plain text field (optional). Webflow has no built-in SEO field on CMS items, so do this once in Webflow: open the collection page in the Designer, then Page settings → SEO, and bind the meta description to this field. Otherwise the text is stored but never shown.
The article's title and slug always go into the collection's Name and Slug.
Other required fields of your collection (an intro, a category, an author…) are listed too, with a counter of how many still need an answer. For each one, choose what to send — The article's title, The article's meta description, The article's slug, The publication name or The article's featured image — or The same value every time… and enter or pick the value. If you choose something an article might not have, such as the meta description, also fill in Articles without one use: — Webflow rejects an item with a required field left empty. Optional reference fields such as a category can be given a fixed value too, so every article lands in the same category.
When everything required has an answer, click Connect & verify. ProjectHQ checks the collection and the mapping and connects.
What gets published
- A live CMS item in your collection when you click Publish (or on the article's scheduled date). ProjectHQ only publishes live — there is no draft mode and no choice between draft and live, so review the article in ProjectHQ first.
- Images — the featured image and the images inside the article — are uploaded to your site's assets. Images over Webflow's 4 MB limit are made smaller first.
- Updates: after you edit a live article in ProjectHQ, click Push update to Webflow in the editor. The same item is updated, not duplicated.
- Unpublishing in ProjectHQ does not remove the item from Webflow. Archive or delete it in Webflow yourself.
Where readers see your articles
Webflow tells ProjectHQ the collection, not the page that shows it, so ProjectHQ guesses the address from your site and the collection's slug. If your posts live somewhere else (say /blog instead of /posts), enter the right address under Where readers see it — ProjectHQ then links to your articles as that-address/article-slug.
Other ProjectHQ features on a Webflow site
ProjectHQ reads a Webflow site only through Webflow's official API and never crawls or scrapes its pages. For a site connected to Webflow, that means:
- Site Audit and Webpages are switched off and can't be turned on, because both crawl the site.
- Knowledge Base doesn't import pages from the site's addresses. Add text or upload files instead.
- The tracking script (for Analytics and Live Chat) is confirmed by the first visit it reports — ProjectHQ doesn't fetch your pages to look for it.
- Insights don't re-read your pages; they work from Search Console and search data.
- Rank Tracker and competitor comparisons use search-data providers, not your site or your Webflow CMS.
Troubleshooting
Webflow's consent screen lists no sites
Webflow only offers sites you're allowed to install Apps on. Check that you signed in to the right Webflow account and that your role has the Install/uninstall Apps permission for the site.
"CMS write access is required to publish articles"
The authorization went through without the permission publishing depends on. Start again and approve all the requested permissions.
"The Webflow authorization link expired"
Each authorization link works once, only in the browser that started it, and has to be finished within 15 minutes. If you opened it in another browser, came back to an old tab, or used the link twice, start again from Continue to Webflow.
A publish failed on an image
If any image can't be uploaded, the whole attempt fails and is retried, rather than publishing an article whose images point elsewhere. The article's delivery log shows which image and why.
Disconnect or revoke access
- Disconnect (in the Publishing section) stops publishing this blog to Webflow.
- Revoke (next to Add account in the connect form) deletes the Webflow access token ProjectHQ stored, so publishing to that account stops until you connect again.
- To cut access from Webflow's side as well, uninstall the App from your Webflow dashboard.
- If you revoke the App's access or uninstall it in Webflow, ProjectHQ notices at its next request, deletes the stored access token and stops contacting Webflow for that account. The account is shown as access revoked until you connect it again.
Articles already published stay on your site, along with their images. ProjectHQ keeps the site's identifier and domains with your project after you disconnect, so that the site is never crawled later; deleting the project or your account removes them. See the Privacy Policy for what is stored and for how long.