# 'Content too wide' error triggered by disallowing Google crawl

**URL:** <https://forums.realmacsoftware.com/t/content-too-wide-error-triggered-by-disallowing-google-crawl/42039>\
**Category:** RapidWeaver Classic\
**Created:** [January 22, 2022, 11:31am UTC](https://forums.realmacsoftware.com/t/content-too-wide-error-triggered-by-disallowing-google-crawl/42039 "2022-01-22T11:31:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![manofdogz](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/manofdogz/32/26314_2.png) [@manofdogz](https://forums.realmacsoftware.com/u/manofdogz)\
**Post date:** [January 22, 2022, 11:31am UTC](https://forums.realmacsoftware.com/t/content-too-wide-error-triggered-by-disallowing-google-crawl/42039/1 "2022-01-22T11:31:26Z")

</div>

I get a lot of ‘content too wide for screen’ errors from Google mobile usability when all pages are in fact 100% fine. However, it appears the error can actually be triggered by htaccess or robots.txt requesting Google doesn’t crawl a particular page as Google can therefore not measure content width of that page.

In my case this is because I use Formloom with the helper stack to import the form onto a stacks page. I therefore set the main Formloom page to be ‘not indexed’ as well as not in navigation. This in turn throws the width error on most of my sites.

Any thoughts on this?

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/system/32/25301_2.png) [@system](https://forums.realmacsoftware.com/u/system)\
**Post date:** [February 21, 2022, 9:31pm UTC](https://forums.realmacsoftware.com/t/content-too-wide-error-triggered-by-disallowing-google-crawl/42039/2 "2022-02-21T21:31:51Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.