goodlord.co — AI Site Grade

Analysis

Goodlord.co — AI-Visibility Audit

The bare domain goodlord.co is a ghost — it immediately 301-redirects to www.goodlord.com, and every standard AI-signposting file (robots.txt, llms.txt, sitemap.xml) on the bare domain also redirects to the homepage rather than resolving independently, meaning no crawler ever sees a robots.txt or sitemap at the canonical domain root.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive a 200 with full HTML content on both goodlord.co and www.goodlord.com. No UA-based blocking exists. The site is hosted on Cloudflare (CDN) and built on HubSpot (x-hs-* headers). The blog subdomain (blog.goodlord.co) has its own robots.txt with a permissive User-agent: * rule blocking only preview/cache-busting parameters — AI bots are fully welcome. However, the main www.goodlord.com domain has no robots.txt at all (returns 200 but it's the homepage HTML). The /llms.txt file also 404s into a homepage redirect on both domains.

Cold-Knowledge Gap

The LLM prior knows Goodlord as a UK proptech company founded in 2014 by Richard White, Tom Mundy, and William Reeve, with Vouch acquisition in 2021 and funding from Octopus Ventures. It mentions "reputational signals" around customer service delays in 2023. The actual site tells a dramatically different story: no mention of founders, no mention of Vouch as an acquisition (Vouch is now a product tier called "Control (Vouch)"), no funding history, no Octopus Ventures. The site positions itself as "AI-enhanced lettings" with an "AI Everywhere" programme, a "renAI" Renters' Rights Act assistant, and claims of being the "gold-standard platform" — none of this AI-forward messaging exists in the cold model's knowledge. The model is 2-3 years stale on the brand narrative.

Schema Posture

Despite being a SaaS platform with multiple product tiers, insurance products, and a rental index data product, zero JSON-LD schema of any business-critical type (Organization, Product, SoftwareApplication, FAQPage, Article) was found across the homepage, platform page, referencing page, landlord solutions page, or rental index page. The only schema detected was VideoObject on the About and Careers pages. The platform page has an FAQ section with 6 questions rendered in visible HTML but no FAQPage schema wrapping them. This is a significant missed signal for AI answer engines.

Content & JS-Rendering Risk

The homepage and most subpages serve rich server-rendered HTML (~900-2,400 words extracted). However, the renters-rights-act-assistant page (the renAI tool) returned zero visible text — a pure JavaScript shell. Any AI crawler hitting this page sees nothing. The blog (blog.goodlord.co) is content-rich with 1,135 URLs in its sitemap and publishes actively (May 2026 posts), but the blog is on a separate subdomain with no cross-domain schema linking it to the main brand entity.

External Signals

DuckDuckGo searches for Goodlord returned zero results across multiple queries — no reviews, no press mentions, no Trustpilot pages surfaced. This is unusual for a company claiming "thousands of agents" and "£0 billion protected in annualised rent." The site's own customer stories page and case studies exist on the blog subdomain but are not surfaced in search results. The DNS TXT records show integrations with Google Workspace, Atlassian, Zapier, JetBrains, KnowBe4, and Apple — a mature tech stack — but no external reputation footprint visible via standard search.

Findings

1. No robots.txt on www.goodlord.com High

   The main domain www.goodlord.com returns the homepage HTML instead of a robots.txt file, leaving crawlers without explicit instructions.

   What to change: Serve a valid robots.txt at https://www.goodlord.com/robots.txt that allows all AI crawlers and points to the sitemap.

2. Bare domain goodlord.co redirects all signposting files High

   The bare domain goodlord.co immediately 301-redirects to www.goodlord.com, and its robots.txt, llms.txt, and sitemap.xml also redirect to the homepage, making them unresolvable.

   What to change: Configure the bare domain to serve proper robots.txt and sitemap files, or ensure the redirect preserves these paths.

3. No llms.txt file on either domain Medium

   The /llms.txt endpoint on both goodlord.co and www.goodlord.com returns a redirect to the homepage, providing no AI-specific guidance.

   What to change: Create an llms.txt file at both domains listing key pages and resources for AI crawlers.

4. Renters' Rights Act assistant page renders as empty JS shell High

   The /renters-rights-act-assistant page returns zero visible text to crawlers, likely requiring JavaScript execution that AI bots do not perform.

   What to change: Server-render the page content or provide a static fallback for crawlers.

5. No business-critical JSON-LD schema on key pages High

   The homepage, platform page, referencing page, landlord solutions page, and rental index page lack Organization, Product, SoftwareApplication, FAQPage, or Article schema. Only VideoObject schema was found on About and Careers pages.

   What to change: Add Organization, SoftwareApplication, and FAQPage schema to relevant pages, and Product schema for insurance offerings.

6. FAQ section on platform page lacks FAQPage schema Medium

   The platform page has 6 visible FAQ questions but no FAQPage JSON-LD markup, reducing chances of appearing in AI answer snippets.

   What to change: Wrap the FAQ section with FAQPage schema using Question and Answer properties.

7. LLM knowledge of Goodlord is 2-3 years out of date Medium

   The model's prior knowledge lacks the current AI-forward messaging, renAI assistant, and 'AI Everywhere' programme, and still references old funding and acquisition details not present on the site.

   What to change: Publish structured data and authoritative content (e.g., a Wikipedia page or press releases) to update the model's knowledge.

8. Near-zero external search presence for brand queries Medium

   Multiple DuckDuckGo searches for Goodlord returned zero results, including reviews, press mentions, and Trustpilot pages, despite claims of thousands of agents.

   What to change: Encourage customer reviews on third-party platforms and improve SEO to surface case studies and press mentions.

9. Blog on separate subdomain with no cross-domain schema linking Low

   The blog at blog.goodlord.co is content-rich but lacks schema linking it to the main brand entity, diluting authority signals.

   What to change: Add sameAs or isPartOf schema linking the blog to the main organization.

10. Sitemap missing on bare domain goodlord.co Low

    The sitemap at goodlord.co/sitemap.xml returns 0 URLs, while the www subdomain has a valid sitemap with 80 URLs.

    What to change: Serve a sitemap on the bare domain or ensure the redirect preserves the sitemap path.

What's working

• All major AI crawlers receive full HTML content — All tested AI crawlers (GPTBot, ClaudeBot, etc.) receive 200 responses with full HTML on both goodlord.co and www.goodlord.com, with no UA-based blocking.
• Blog robots.txt allows AI crawlers — The blog subdomain's robots.txt has a permissive User-agent: * rule that only blocks preview parameters, allowing AI bots full access.
• Blog publishes actively with 1,135 URLs — The blog subdomain has a sitemap with 1,135 URLs and recent posts (May 2026), providing a steady stream of content.
• Key pages are server-rendered with substantial text — The homepage, platform, referencing, landlord solutions, and rental index pages serve 500-2,400 words of server-rendered HTML, making them crawlable.
• VideoObject schema present on About and Careers pages — The About and Careers pages include VideoObject JSON-LD schema, which can enhance rich results.
• Mature tech stack with integrations visible in DNS — DNS TXT records show integrations with Google Workspace, Atlassian, Zapier, JetBrains, KnowBe4, and Apple, indicating a sophisticated infrastructure.