hometap.com — AI Site Grade

Analysis

Hometap's homepage and all key pages carry zero JSON-LD schema — a fintech company selling a complex financial product that AI engines must describe accurately has no Organization, Product, FAQPage (except on /faqs), or WebSite structured data on its most-trafficked pages.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive a full 200 response with identical byte payload (~282KB) to a browser baseline. The site runs on Vercel (Next.js SSR) with no Cloudflare or WAF layer that discriminates by user-agent. The robots.txt is a bare-bones wildcard allow with only two disallowed paths (/subdomains/invest and /*), and no AI-bot-specific directives exist. The /llms.txt returns a 404 (rendered as a Next.js error page with noindex). The sitemap contains 223 URLs and is well-formed.

Cold-Knowledge Gap

The LLM prior knows Hometap as a Boston-based fintech (founded 2017) offering home equity investments with no monthly payments, and recalls regulatory scrutiny in Massachusetts and customer complaints about high costs if home values rise. The actual site makes no mention of regulatory challenges, does not address the "high cost if home appreciates" criticism directly, and presents only positive testimonials. The site's newsroom shows $2 billion in HEI originations, a $300M securitization, and a $50M funding round from Gallatin Point — none of which appears in the cold LLM knowledge. The model also does not know about the Home Equity Dashboard digital platform, which is a core differentiator on the site.

Schema Posture

Only one page (/faqs) carries structured data — a FAQPage schema with 5 Q&A entries. The homepage, /how-it-works, /home-equity-investment-vs-traditional-loans, /reviews, and all 20+ location pages have zero JSON-LD of any type. No Organization schema (with logo, sameAs, founding date), no Product or FinancialProduct schema for the HEI product, no WebSite with searchAction, no BreadcrumbList. Blog articles use Article schema with author, publisher, and dates — this is the only consistent schema implementation.

Content & Answer Signals

The homepage delivers 1,303 words of visible text (SSR-rendered, no JS dependency). The comparison page (/home-equity-investment-vs-traditional-loans) contains a comparison table (HEI vs HELOC vs home equity loan vs cash-out refi vs reverse mortgage) that renders as visible HTML — AI crawlers can parse it. The FAQ page has 30+ Q&A pairs but only 5 are in the FAQPage schema. The glossary page contains ~4,000 words of definitional content but has no DefinedTermSet or DefinedTerm schema. Location pages (20+ states) are thin — ~300 words each — and lack local-business or geographic schema.

External Signals

The site prominently displays a 4.8–4.9/5 Trustpilot rating with "over 3,000 reviews" and "25,000+ happily funded homeowners." The newsroom lists press mentions from Boston Globe, American Banker, Forbes, Bankrate, HousingWire, Fast Company (Most Innovative Companies 2023), and Inc. 5000 rankings. No negative press or regulatory controversy is linked or addressed. The DNS TXT records reveal an anthropic-domain-verification token, confirming Hometap has proactively verified its domain with Anthropic for Claude crawler access — a sophisticated AI-visibility signal that few brands implement.

Findings

1. Zero JSON-LD schema on homepage and all key pages except /faqs High

   The homepage, /how-it-works, /home-equity-investment-vs-traditional-loans, /reviews, and all location pages carry no JSON-LD structured data. Only the /faqs page has a FAQPage schema. This prevents AI engines from accurately describing the company, product, and content.

   What to change: Add Organization, Product (or FinancialProduct), WebSite, and BreadcrumbList JSON-LD to the homepage and all key pages. Extend FAQPage schema to cover all Q&As on the /faqs page.

2. /llms.txt returns 404, missing AI discovery file Medium

   The /llms.txt endpoint returns a 404 error page with a noindex directive. This file is used by AI crawlers to discover key resources and context about the site.

   What to change: Create a valid /llms.txt file that lists key pages, the sitemap, and a brief description of the site for AI crawlers.

3. Location pages are thin (~300 words) and lack local schema Medium

   Each of the 20+ location pages contains only about 300 words of content and no local business or geographic schema. This limits their ability to rank for local AI queries.

   What to change: Expand location pages with more detailed content about local services, and add LocalBusiness or Place schema with geographic coordinates.

4. Glossary page lacks DefinedTermSet schema Medium

   The glossary page contains ~4,000 words of definitional content but has no DefinedTermSet or DefinedTerm structured data, reducing its utility for AI knowledge extraction.

   What to change: Add DefinedTermSet and DefinedTerm schema to the glossary page to mark up each term and definition.

5. Site does not address known regulatory scrutiny or cost criticism Medium

   LLM prior knowledge includes regulatory scrutiny in Massachusetts and customer complaints about high costs if home values rise. The site makes no mention of these issues and presents only positive testimonials, which may reduce trustworthiness in AI-generated summaries.

   What to change: Add a dedicated page or section that transparently addresses regulatory compliance and explains scenarios where costs may be higher, to provide balanced information for AI crawlers.

6. No FinancialProduct schema for the HEI product High

   The core product (Home Equity Investment) is described on multiple pages but never marked up with Product or FinancialProduct schema. This prevents AI engines from understanding the product's features, rates, and terms.

   What to change: Add FinancialProduct or Product schema to the homepage and /how-it-works page, including properties like name, description, offers, and fees.

7. FAQPage schema covers only 5 of 30+ Q&As Medium

   The /faqs page has over 30 Q&A pairs but only 5 are included in the FAQPage schema. The remaining content is invisible to AI crawlers as structured data.

   What to change: Expand the FAQPage schema to include all Q&A pairs on the /faqs page.

8. Missing Organization schema on homepage High

   The homepage does not include Organization schema with logo, sameAs, founding date, or other corporate information. This limits AI engines' ability to display rich knowledge panel data.

   What to change: Add Organization schema to the homepage with properties such as name, url, logo, sameAs (social profiles), foundingDate, and description.

9. No BreadcrumbList schema on any page Low

   No page on the site uses BreadcrumbList schema, which helps AI crawlers understand site structure and navigation paths.

   What to change: Add BreadcrumbList schema to all pages with breadcrumb navigation.

10. No WebSite schema with searchAction Low

    The site does not implement WebSite schema, which could provide a search action for AI assistants to query the site directly.

    What to change: Add WebSite schema to the homepage with potentialAction for search.

11. robots.txt lacks AI-bot-specific directives Low

    The robots.txt file is a bare-bones wildcard allow with only two disallowed paths and no specific rules for AI crawlers like GPTBot or ClaudeBot. While not blocking, it misses an opportunity to guide AI crawlers to important content.

    What to change: Add specific directives for AI crawlers, such as allowing access to key pages and disallowing low-value paths.

12. Site does not address negative press or customer complaints Medium

    The site presents only positive testimonials and press mentions, with no reference to regulatory scrutiny or customer complaints that appear in LLM prior knowledge. This can lead to unbalanced AI summaries.

    What to change: Consider adding a page that transparently discusses regulatory compliance and customer feedback, including negative reviews, to provide a balanced view for AI crawlers.

What's working

• Proactive Anthropic domain verification for Claude crawler — DNS TXT records include an anthropic-domain-verification token, confirming Hometap has proactively verified its domain with Anthropic for Claude crawler access. This is a sophisticated AI-visibility signal that few brands implement.
• All major AI crawlers receive full 200 responses — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, and Applebot-Extended all receive identical 200 responses with full page content. No bot is blocked or throttled.
• Key pages are server-side rendered with no JS dependency — The homepage and comparison page deliver visible HTML content without requiring JavaScript execution, ensuring AI crawlers can parse all text.
• Blog articles use Article schema with author and publisher — Blog posts consistently implement Article schema with author, publisher, and date information, providing structured metadata for AI crawlers.
• FAQPage schema present on /faqs page — The /faqs page includes a FAQPage schema with 5 Q&A entries, providing some structured data for AI crawlers to extract common questions.
• Sitemap contains 223 URLs and is well-formed — The sitemap is accessible and contains 223 URLs, helping crawlers discover all pages on the site.
• Strong external signals from press and reviews — The site displays a 4.8-4.9/5 Trustpilot rating with over 3,000 reviews, and press mentions from Boston Globe, Forbes, Fast Company, and Inc. 5000. These signals enhance credibility and AI trust.
• Comparison table renders as visible HTML for AI crawlers — The comparison page includes a table comparing HEI vs HELOC vs home equity loan vs cash-out refi vs reverse mortgage, all as visible HTML that AI crawlers can parse.