How AI assistants read sawkill.nyc
An automated read of sawkill.nyc against the signals AI search engines use to crawl, parse, and cite a website.
AI assistants can only partially read this site.
The four signals
Whether AI crawlers (GPTBot, ClaudeBot, PerplexityBot and others) are allowed to fetch the site in robots.txt.
Whether Schema.org markup tells AI what the business is and what it offers.
Whether key content is server-rendered and cleanly structured for agents that do not run JavaScript.
Whether the site signposts agents with /llms.txt and a sitemap in robots.txt.
What we found
- ✓ Content is server-rendered
- ✗ No /llms.txt
- ✓ Organization / WebSite schema
- ✗ No Product / Service schema
- ✗ No FAQ schema
- ✗ No sitemap in robots.txt
- ✓ Has a page title
- ✓ Has a meta description
Structured data detected: WebSite, Organization, ImageObject, PostalAddress, WebPage.
Priority fixes
- highNo Product/Offer/Service schema.Add Schema.org Product or Service JSON-LD with name, description, and offers (price, availability).
- highAgent crawler Amazonbot (Amazon) is blocked in robots.txt.Allow Amazonbot so this engine's agents can read the page.
- mediumNo FAQ/QA schema.Add FAQPage JSON-LD for the questions agents are likely to ask.
- mediumNo /llms.txt.Publish /llms.txt pointing agents to your key pages and policies.
- lowNo BreadcrumbList schema.Add BreadcrumbList JSON-LD so agents understand site structure.
- lowPage has 2 H1 headings (expected exactly 1).Use exactly one H1 that states the page topic.
- lowrobots.txt does not reference a sitemap.Add a Sitemap: line to robots.txt.
This readiness check shows whether AI can read sawkill.nyc. The full audit goes further: it tests whether ChatGPT, Perplexity, Claude, and Google AI actually cite sawkill.nyc across real buyer questions.
Is this your site? Request a re-scan or removal →
Automated assessment of publicly observable signals only. RankEcho is independent and not affiliated with sawkill.nyc. How scoring works →