What an AI agent reads on Case Study Coffee Roasters
An assistant's crawler fetches the page once, without running JavaScript, and reads the text, the structured data and the links. Below is what it gets from casestudycoffee.com, taken from the copy the scanner kept.
482
characters of text without JavaScript, too few to answer questions from
none
structured data for the business
0
of 3 AI crawlers turned away at the edge
The words an agent gets
Title: Case Study Coffee Roasters – CASE STUDY COFFEE ROASTERS. First 482 of 482 characters:
Case Study Coffee Roasters – CASE STUDY COFFEE ROASTERS Close menu Search Coffees Merchandise Brew Gear Log In Create Account Shop Locations Catering Wholesale Subscription Your cart Close Cart Site navigation Site navigation Shop Coffees Merchandise Brew Gear Locations Catering Wholesale Subscription Log In Search Cart Cart New Location Coming Soon Take a look Facebook Instagram CASE STUDY COFFEE ROASTERS5347 NE Sandy BLVDPortland, OR 97213info@casestudycoffee.com Search
What it can say about the business
| A business type in JSON-LD | no |
| Name | no |
| Telephone | no |
| Address | no |
| Opening hours | no |
| Menu or price list | nothing |
| Cuisine in structured data | no |
| JSON-LD blocks | 0 (microdata:Organization) |
The links it would act on
No booking or ordering link found. An agent has nothing to act on.
Everything here comes from fetching the homepage once as a crawler. The report turns it into a score and a list of fixes, with code to paste.