# Problems with Error Checking AND Pinegrow rendering a HUGO site, both locally and via URL **URL:** \ **Category:** Bug Reports\ **Created:** [July 11, 2025, 5:33pm UTC](https://forum.pinegrow.com/t/problems-with-error-checking-and-pinegrow-rendering-a-hugo-site-both-locally-and-via-url/10933 "2025-07-11T17:33:31Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Emmanuel](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/emmanuel/32/6294_2.png) [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)\ **Post date:** [July 16, 2025, 10:46am UTC](https://forum.pinegrow.com/t/problems-with-error-checking-and-pinegrow-rendering-a-hugo-site-both-locally-and-via-url/10933/6 "2025-07-16T10:46:57Z")
> [@schpengle](#): > > Or maybe correctly to Pinegrow if its adhering strictly to its inbuilt syntax checking rules, which I would understand -although the same leniency that the normal browser applies, in order to render the page correctly would be nice, ALONGSIDE the errors , or maybe an option to see both broken and _lenient_ views of the page) Pinegrow’s HTML parser is stricter than a browser to function correctly. This is an important part of how the app works. Pinegrow doesn’t correct errors; it just highlights them when it detects them. The checking process isn’t perfect and might miss some errors, especially if there are a lot, which could impact how the app operates. > **[How to use valid W3C documents to maximize your experience with Pinegrow |...](https://pinegrow.com/blog/how-to-use-valid-w3c-documents-to-maximize-your-experience-with-pinegrow/)** > > To the best of our knowledge, Pinegrow is currently the only multi-platform visual HTML editor that allows you to create HTML documents and projects from scratch and import your existing HTML… --- _[View the full topic](https://forum.pinegrow.com/t/problems-with-error-checking-and-pinegrow-rendering-a-hugo-site-both-locally-and-via-url/10933)._