Agent readiness report
nyfulcrum.com
What an AI agent can and cannot do on this site, measured by an unauthenticated crawl and scored against the published rubric.
Scanned · rubric v1.0.1 · scored as a general site · re-scan (results are cached for seven days)
What to fix first
Ranked by impact first, then by how cheap the fix is — the same ordering the engine uses.
Add JSON-LD to the homepage. Organization or WebSite is the baseline, and it is what tells a machine who you are rather than making it infer that from prose.
Missing: Organization or WebSite sitewide; type-specific markup (Article, FAQPage, Service, SoftwareApplication). For a other site, Article or FAQPage or Service or SoftwareApplication is what lets an agent understand what you actually offer rather than that you exist.
No forms were found on the crawled pages, so form usability could not be assessed. If you add a contact or signup form, give every input a real label and a correct input type.
No machine-readable endpoint of any kind. Most sites score zero here, which is exactly why it is the cheapest differentiation on this rubric: an agents.json is a static file, and a documented read-only API is usually a subset of something you already run.
Publish an llms.txt at the root: an H1, a one-line summary, then described links to your most useful pages. It is a text file and it takes an hour — the cheapest points on this rubric.
Every check, with the evidence
No finding without evidence: each result shows what we actually captured during the crawl.
ADiscovery & access
- A1Partial
robots.txt exists and parses
1/2Publish a robots.txt. A missing file leaves the site open by default, so nothing is blocked — but it also means crawlers get no sitemap reference and no explicit signal about AI agents.
What we captured
{ "status": 404 } - A2Pass
Major AI crawlers allowed
6/6What we captured
{ "of": 6, "allowed": 6, "blocked": [] } - A3Fail
XML sitemap valid and referenced
0/3Fix: no sitemap.xml at the root; not referenced from robots.txt. A sitemap referenced from robots.txt is how a crawler discovers pages that are not linked from the homepage.
What we captured
{ "exists": false, "urlCount": 0, "referencedInRobots": false } - A4Fail
llms.txt present
0/4Publish an llms.txt at the root: an H1, a one-line summary, then described links to your most useful pages. It is a text file and it takes an hour — the cheapest points on this rubric.
What we captured
{ "status": 404, "present": false } - A5Pass
Bot user-agent HTTP health
3/3What we captured
{ "probes": [ { "name": "GPTBot", "status": 200, "ttfbMs": 558 }, { "name": "ClaudeBot", "status": 200, "ttfbMs": 161 }, { "name": "PerplexityBot", "status": 200, "ttfbMs": 1206 } ], "medianTtfbMs": 558, "edgeBlockingDespiteRobots": false } - A6Pass
No hard interstitial
2/2What we captured
{ "markers": [] } - A7Not applicable
Server-rendered content parity
0/5No headless render was captured, so parity could not be measured. Re-run with rendering enabled.
What we captured
{ "rendered": false }
BUnderstanding
- B1Fail
JSON-LD present and valid
0/5Add JSON-LD to the homepage. Organization or WebSite is the baseline, and it is what tells a machine who you are rather than making it infer that from prose.
What we captured
{ "pagesCrawled": 6, "pagesWithValidJsonLd": 0, "homepageHasValidJsonLd": false, "pagesWithInvalidJsonLd": 0 } - B2Fail
Correct schema types for the site type
0/5Missing: Organization or WebSite sitewide; type-specific markup (Article, FAQPage, Service, SoftwareApplication). For a other site, Article or FAQPage or Service or SoftwareApplication is what lets an agent understand what you actually offer rather than that you exist.
What we captured
{ "matched": [], "missing": [ "Organization or WebSite sitewide", "type-specific markup (Article, FAQPage, Service, SoftwareApplication)" ], "siteType": "other", "typesFound": [] } - B3Partial
Semantic HTML structure
3/4Headings and landmarks are how a machine builds an outline of the page. One h1, no skipped levels, and real main/nav/footer elements — all template-level fixes, applied once.
What we captured
{ "problems": [ "https://nyfulcrum.com/about: 0 h1 elements", "https://nyfulcrum.com/blogs: 0 h1 elements", "https://nyfulcrum.com/case-studies: 0 h1 elements" ], "singleH1": 3, "allLandmarks": 6, "pagesCrawled": 6, "noSkippedLevels": 6 } - B4Partial
Meta and Open Graph
1/3Fix: 1 title(s) outside 15–70 characters; 5 description(s) outside 50–160 characters.
What we captured
{ "goodTitles": 5, "pagesCrawled": 6, "uniqueTitles": true, "goodDescriptions": 1, "completeOpenGraph": 6 } - B5Partial
Clean text ratio
1/3Visible text is 3.2% of your markup. Deeply nested wrapper elements make a page expensive to parse and dilute the content an agent extracts. Script and style contents are already excluded from this measure, so this is markup weight, not framework overhead.
What we captured
{ "perPage": [ 0.018, 0.044, 0.055, 0.015, 0.055, 0.007 ], "averageRatio": 0.032 } - B6Partial
Alt text coverage
1/272 of 162 content images have no alt text. An agent cannot see the image; the alt attribute is the only description it gets.
What we captured
{ "withAlt": 90, "coverage": 0.56, "contentImages": 162 } - B7Partial
Canonical and duplication hygiene
1/3Fix: 6 page(s) missing or with a mismatched rel=canonical. Duplicate hosts split whatever authority the page has earned.
What we captured
{ "hostVariants": [ { "url": "https://www.nyfulcrum.com", "status": 200 }, { "url": "http://nyfulcrum.com", "status": 308, "location": "https://nyfulcrum.com/" } ], "pagesCrawled": 6, "selfConsistentCanonicals": 0 }
CActionability
- C1Partial
Form usability
3.67/6.11No forms were found on the crawled pages, so form usability could not be assessed. If you add a contact or signup form, give every input a real label and a correct input type.
What we captured
{ "formsFound": 0 } - C2Fail
Navigable link graph
0/4.89Fix: 10 clickable element(s) that are not anchors — an agent cannot follow a div; 16% of links use contextless text like "click here"; no breadcrumbs or clear URL hierarchy.
What we captured
{ "anchors": 50, "genericLinks": 8, "genericRatio": 0.16, "hasBreadcrumb": false, "clickableNonAnchors": 10 } - C3Partial
Interactive element semantics
2.44/4.89Fix: 10 element(s) act as buttons without being buttons. A div with a click handler is invisible to anything driving the page programmatically.
What we captured
{ "realButtons": 9, "positiveTabindex": 0, "clickableNonButtons": 10, "keyboardTrapsTested": false } - C4Fail
Machine endpoints and agent manifests
0/6.11No machine-readable endpoint of any kind. Most sites score zero here, which is exactly why it is the cheapest differentiation on this rubric: an agents.json is a static file, and a documented read-only API is usually a subset of something you already run.
What we captured
{ "found": [] } - C5Not applicable
Commerce actionability
0/4Not a commerce site; these points are redistributed across C1–C4.
What we captured
{ "siteType": "other" } - C6Fail
On-site search
0/3No on-site search found. If you have search, expose it as a GET form with a query parameter so an agent can jump straight to results.
What we captured
{ "searchForm": false, "searchAction": false }
DTrust & freshness
- D1Partial
Transport security
3/4Fix: 1 insecure subresource reference(s).
What we captured
{ "hsts": true, "tlsValid": true, "mixedContentReferences": 1 } - D2Partial
Verifiable identity
2/4Fix: no Organization schema. sameAs links to a company profile are how a model corroborates that you are who the page says you are.
What we captured
{ "sameAsCount": 0, "contactDiscoverable": true, "hasOrganizationSchema": false } - D3Partial
Policies discoverable
2/4Fix: no privacy policy linked.
What we captured
{ "hasTerms": true, "siteType": "other", "hasPrivacy": false, "hasReturns": false, "hasShipping": false } - D4Fail
Freshness signals
0/4Fix: sitemap has no lastmod values; only 0% of sitemap URLs modified in the last 90 days; no visible dates on content. Staleness is a ranking signal for models deciding what to cite.
What we captured
{ "sitemapUrls": 0, "withLastmod": 0, "visibleDates": false, "modifiedLast90Days": 0 } - D5Partial
Identity consistency
1/3Fix: site name differs across title, og:site_name and schema name. An unexplained name mismatch reads as a signal the site may not be what it claims.
What we captured
{ "title": "Fulcrum Solutions | CTO-as-a-SERVICE & Software Development for Startups", "hasFavicon": true, "hasOgImage": true, "ogSiteName": "Fulcrum Solutions | CTO-as-a-SERVICE & Software Development for Startups", "schemaName": "" } - D6Fail
security.txt
0/2Publish /.well-known/security.txt with a Contact field and a future-dated Expires field. It is a five-line text file.
What we captured
{ "status": 404, "present": false } - D7Pass
Multi-page stability
4/4What we captured
{ "nonOk": [], "slowPages": 0, "pagesCrawled": 6, "consistentTemplate": true }
Keep this report
Get the permanent link and the ranked fix list by email. One message, no list.
Want this fixed?
We audit in depth and implement the fixes — in your codebase or your CMS, scoped by architecture.
Own this site?
This report and its leaderboard entry come from a public crawl. Prove you own the domain with an email address on it, and you can hide the report or publish it again yourself, in minutes.
To block future scans instead, disallow AgentFriendlyRankBot in your robots.txt — see how our crawler works.
Scan your own site
Same rubric, same evidence standard, about a minute.