On Webflow, paste your QualityHive script into Site settings, under the Custom code tab, in Head code, then publish. You need a plan that includes custom code. Without one, use the Chrome, Firefox or Edge browser extension, which needs no site changes.
Check your plan first
Custom code is a paid feature on Webflow. At the time of writing (November 2026), Webflow's pricing page shows:
Your setup | Custom code? |
Starter Site plan on a Starter Workspace | No |
Paid Site plan on that site, such as Basic or CMS | Yes |
Core, Growth, Freelancer or Agency Workspace | Yes |
Confirm it against your own billing page before you buy. The same pricing page limits Starter Workspaces to 2 pages per staged site, which is too few for a meaningful review.
Add the script
In QualityHive, copy the script from your project's widget setup. The tracking code guide shows where.
In Webflow, open Site settings and go to the Custom code tab.
Paste the script into Head code and click Save changes.
Publish to your webflow.io subdomain. Custom code only takes effect when the site is published, so saving alone changes nothing.
Open the webflow.io address while signed in to QualityHive and check the widget appears.
Guest links and webflow.io
Review on your webflow.io address while the build is in progress, but do not plan on guest links there. The guest link loads your site in a frame from app.qualityhive.com. The webflow.io domains we checked in November 2026 sent a frame-ancestors policy allowing only Webflow's own domains, and the Webflow-hosted custom domains we checked sent X-Frame-Options: SAMEORIGIN. Webflow lists custom security headers as an Enterprise feature, so sites on other plans cannot change this.
Each reviewer on the script or the extension signs in as a project member and takes a seat, so count reviewers before choosing from the pricing page.
For design sign-off, where a client only needs to comment on layout, Webflow's own comment-only links let people without a Webflow account review and comment. They will not give you a bug list with browser details and video, but they may be all you need at that stage.
Webflow QA list
Breakpoints
Styles set on the base breakpoint cascade down, so a desktop fix can change tablet and mobile without anyone noticing. Recheck the smaller sizes after every desktop change.
Breakpoint | What to check |
Base (desktop) | Layout holds at the widest screen you support, plus any larger breakpoints in use |
Tablet, 991px and below | Navigation opens and closes, and grids wrap cleanly |
Mobile landscape, 767px and below | Hero text still fits and tap targets stay usable |
Mobile portrait, the narrowest | Long words and buttons do not overflow |
Repeat the check on a real phone, because a resized browser can hide touch problems. Our guide to testing on real devices covers how.
Interactions
Elements with a hidden initial state stay hidden if the trigger never fires, so test on a throttled connection.
Hover interactions have no equivalent on touch screens, so check the content is reachable without them.
Reload halfway down a page, since scroll-into-view animations can look finished or broken depending on where you land.
Record these on video, because a screenshot cannot show timing.
CMS collection states
Empty lists: a Collection list only shows its empty state on the live site when it has no items or all are filtered out, so replace the default "No items found" text.
Items with a very long title, or with an optional image or summary left blank.
Conditional visibility rules on each Collection template.
Reference and multi-reference fields with no items, one item and several.
Rich text styling on a Collection template page, including headings, lists and embedded images.
For everything outside Webflow's own quirks, our website QA checklist covers forms, redirects and metadata before launch.
