Quick answer: HubSpot theme QA should compare the source and converted pages, comparing the source and converted pages, testing desktop and mobile layouts, checking every asset and link, validating forms and scripts, and reviewing SEO and accessibility basics. Do this in a test page before publishing.
Why previewing is not optional
A preview helps identify visible differences early, but it cannot prove that every HubSpot page, form or external integration will work in production. Some interactions depend on HubSpot page context, cookies, third-party domains or server-side services. Use preview as the first QA stage, then repeat tests in a real HubSpot test page.
Visual comparison checklist
- Compare the header, logo, navigation and hero section.
- Check typography, font weights, line height and spacing.
- Verify section order, grids, buttons, cards and footer layout.
- Confirm that logos, icons and images load at the right size.
- Compare long pages as well as the first screen.
Responsive testing
Test at common phone, tablet and desktop widths. Check whether navigation collapses properly, columns stack in the correct order, buttons remain usable and text does not overflow. Resize the browser gradually as well as using device presets; layout issues often appear between common breakpoint sizes.
Functional testing
Click every important internal link and menu item. Test tabs, accordions, sliders and other JavaScript-driven elements. Submit forms using test data, verify validation messages and confirm that leads reach the intended destination. Check external embeds and integrations separately because they may behave differently in a sandboxed preview.
SEO, accessibility and performance checks
- Use one clear page-level H1 and logical H2/H3 sections.
- Confirm unique page titles, useful meta descriptions and canonical URLs.
- Check descriptive alt text for meaningful images.
- Verify keyboard navigation, visible focus and form labels.
- Check image dimensions, unnecessary scripts and loading behavior.
- Review redirects and ensure the intended pages are indexable.
Use the conversion report as a QA input
The DigiThinker HTML to HubSpot converter provides a source preview and a converted-page preview workflow, and its theme package includes a warning report for items that may need attention. Review each warning instead of treating the report as a complete test suite. A developer or site owner should sign off on important pages before launch.
Simple QA sign-off template
| Area | Pass condition |
|---|---|
| Visual design | Key sections match the approved source or design brief. |
| Responsive layout | No unusable overlap or overflow at tested widths. |
| Navigation | All required links lead to the correct pages. |
| Forms | Validation, submission and routing work with test data. |
| SEO | Titles, indexability, canonicals and redirects are reviewed. |
| Approval | Business owner confirms content and launch readiness. |
Frequently asked questions
Is a successful preview enough to publish?
No. Test the actual HubSpot page and its integrations as well. Some features require the live CMS context.
Who should approve a converted theme?
At minimum, a developer should validate functionality and a content or business owner should approve the page content and user journey.
What should happen to failed QA items?
Record the page, issue, expected behavior, owner and retest result. Resolve critical items before publication.
Bottom line: treat conversion and QA as separate steps. A clean checklist protects the launch from avoidable layout, link and lead-generation problems.
Related HubSpot conversion guide
For the complete workflow, read How to Convert an HTML Website to a HubSpot CMS Theme, then try the DigiThinker HTML to HubSpot converter.
For platform-specific background, see the relevant official documentation.