Technical signals observed for prismpartners.space
A point-in-time automated screen of captured homepage HTML, robots.txt rules, and /llms.txt availability. It does not test whether an AI provider reached, fetched, parsed, indexed, cited, or represented the site.
This capture scored in RankEcho's highest band for the checked technical signals.
Four heuristic dimensions
How captured robots.txt rules resolve for RankEcho's configured crawler tokens; not a test of provider fetching or reachability.
Presence of selected Schema.org @type strings in captured HTML; not provider use or understanding.
Title, meta description, H1, canonical, language, Open Graph, and extracted-text checks; not a test of provider parsing or rendering.
Presence of /llms.txt, a Sitemap directive, and FAQ schema strings; not proof that a provider uses them.
What we found
- ✓ At least 500 characters of text extracted from fetched HTML
- ✓ Publishes /llms.txt
- ✓ Organization / WebSite schema
- ✓ Product / Service schema
- ✓ FAQ schema
- ✓ Sitemap in robots.txt
- ✓ Has a page title
- ✓ Has a meta description
Matching Schema.org @type strings in captured HTML: PostalAddress, GeoCoordinates, OpeningHoursSpecification, FAQPage, Question, Answer, Service, LocalBusiness, City, Offer, CoworkingSpace.
Priority fixes
- lowNo BreadcrumbList schema.Add BreadcrumbList JSON-LD only where it matches visible breadcrumb navigation. Validation describes the markup, not provider comprehension.
This technical screen does not establish provider access, eligibility, indexing, citation, or representation. A full audit separately runs configured prompts and records the mentions and citations returned in those audit runs.
Is this your site? Request a re-scan or removal →
Point-in-time RankEcho heuristic based on publicly observable captured inputs. It is not a provider reachability, eligibility, indexing, citation, or representation test. RankEcho is independent and not affiliated with prismpartners.space. How scoring works →