cincsystems.com — AI Site Grade

Analysis

I have enough data now. Let me compile the audit.

---

CINC Systems AI-Visibility Audit

The cold LLM knowledge of CINC Systems is stale by roughly two years: it still references a 2021 GI Partners acquisition, places headquarters in Austin (the site says Duluth, GA), and pegs the founding year at 2008 (the site says 2005). This gap means AI engines answering queries about CINC without live retrieval are already citing incorrect investor, location, and timeline data.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive full 200 responses with identical byte payloads (67,755 bytes) on the homepage. No UA-based blocking exists. The robots.txt contains only HubSpot CMS boilerplate disallows (/_hcms/preview/, /hs/manage-preferences/, etc.) and mentions no AI bots by name. The site runs on Cloudflare with HubSpot as the CMS. The trust center at trust.cincsystems.com is a Vanta-powered JS shell — all bots get a 200 but receive only 4,171 bytes of empty React bootstrap HTML with zero visible text content, making SOC 2 and security claims invisible to AI crawlers.

Content & Schema Posture

The homepage carries only two schema types: WebPage and a VideoObject for a hero video. No Organization, SoftwareApplication, FAQPage, or Product schema exists anywhere on the site, despite the homepage containing a 7-item FAQ section, explicit product names (Cephai, Payables+, CINC Manager), and customer count claims (1,000+ management companies, 51K+ HOAs, 6M+ doors). The /products URL redirects to /solutions. Blog posts use BlogPosting schema but the blog listing page, case studies page, and knowledge base pages carry zero schema at all. The knowledge base is branded "ONR" (the acquired product) but the /knowledge-base page has no schema and only 55 words of visible text.

Cold-Knowledge Gap

The model's prior knowledge differs from the live site on multiple material facts. The model says "founded in 2008, Austin, TX" — the site says "founded in 2005, Duluth, GA." The model says "acquired by GI Partners in 2021" — the site says backed by Hg Capital and Spectrum Equity (no mention of GI Partners). The model says "1 million residential units" — the site claims 6 million doors. The model knows nothing about Cephai (the AI product launched in 2023), the ONR acquisition (2025), Payables+, or the CINC Connect platform. Any AI answering a question about CINC without live retrieval will present materially outdated information.

External Signals

External search results for CINC Systems are remarkably sparse. Searches for reviews, Reddit discussions, G2/Capterra mentions, and press coverage returned zero results from DuckDuckGo. The DNS TXT records show domain verifications for Anthropic, Cursor, Atlassian, Stripe, and Zoho — indicating active AI-tool and vendor integrations — but no public review ecosystem surfaced. The only external links found on the site are to the Google Play Store and Apple App Store for the CINC Manager mobile app.

Structural Surprises

The ONR acquisition news page linked from the news listing returns a 404. The /products path is a 301 redirect to /solutions rather than a standalone product page. The knowledge base is branded "ONR" (the acquired company's product name) with no CINC branding, creating a fragmented user experience. Blog posts carry dates into April 2026, suggesting either forward-dated content or a publishing calendar that may confuse temporal signals. The FAQ section on the homepage has no FAQPage schema markup, meaning AI engines cannot extract those Q&A pairs as structured answers.

Findings

1. Cold LLM knowledge is two years out of date on founding year, HQ, investors, and scale High

   AI models without live retrieval cite CINC Systems as founded in 2008 in Austin, TX, acquired by GI Partners in 2021, and managing 1 million units. The site states founded in 2005 in Duluth, GA, backed by Hg Capital and Spectrum Equity, and managing 6 million doors. Products like Cephai, Payables+, and the ONR acquisition are absent from model knowledge.

   What to change: Publish an llms.txt file with canonical facts and update the site's structured data to reinforce accurate entity information.

2. Trust center renders as empty JavaScript shell for AI crawlers High

   The trust center at trust.cincsystems.com returns a 200 status but delivers only 4,171 bytes of React bootstrap HTML with no visible text content. GPTBot and ClaudeBot both receive the same empty shell, making SOC 2 and security claims invisible to AI crawlers.

   What to change: Implement server-side rendering or static HTML for the trust center content so AI crawlers can index security and compliance information.

3. No Organization or SoftwareApplication schema on homepage or product pages High

   The homepage contains only WebPage and VideoObject schema. Despite listing product names (Cephai, Payables+, CINC Manager) and customer counts, no Organization, SoftwareApplication, or Product schema is present. The /solutions page also lacks product schema.

   What to change: Add Organization, SoftwareApplication, and Product schema markup to the homepage and product pages, including all product names and customer metrics.

4. Homepage FAQ section lacks FAQPage schema markup Medium

   The homepage includes a 7-item FAQ section but no FAQPage or Question schema is present. AI engines cannot extract these Q&A pairs as structured answers for featured snippets or voice search.

   What to change: Add FAQPage and Question schema to the homepage FAQ section.

5. Blog listing page and case studies page have zero schema markup Medium

   The blog listing page, case studies page, and knowledge base pages carry no structured data. Blog posts individually have BlogPosting schema, but the listing pages lack CollectionPage or any schema, reducing discoverability.

   What to change: Add CollectionPage or ItemList schema to blog listing, case studies, and knowledge base pages.

6. Knowledge base branded as ONR with no CINC branding and minimal content Medium

   The knowledge base at /knowledge-base is branded 'ONR' (the acquired product) with no CINC Systems branding. The page contains only 55 words of visible text and no schema markup, creating a fragmented user and crawler experience.

   What to change: Rebrand the knowledge base under CINC Systems, add substantial content and schema markup, and ensure it is properly linked from the main site.

7. ONR acquisition news page returns 404 error Medium

   The news article about the ONR Applications acquisition, linked from the news listing, returns a 404 error. This broken link undermines credibility and prevents AI crawlers from indexing the acquisition announcement.

   What to change: Restore the ONR acquisition news page or set up a proper redirect to a working URL.

8. /products path redirects to /solutions instead of a dedicated product page Low

   The /products URL is a 301 redirect to /solutions, which is a general solutions page. There is no dedicated product listing page with individual product details, limiting AI crawlers' ability to understand the product portfolio.

   What to change: Create a dedicated /products page with individual product pages and proper schema markup.

9. Blog posts carry dates into April 2026, potentially confusing temporal signals Low

   Some blog posts have publication dates as far forward as April 2026. This may confuse AI crawlers and users about the timeliness and accuracy of content.

   What to change: Review and correct publication dates on blog posts to reflect actual publish dates.

10. No public review ecosystem found on G2, Capterra, or Reddit Low

    Searches for CINC Systems reviews on G2, Capterra, and Reddit returned zero results. The lack of external social proof may reduce trust signals for AI models and potential customers.

    What to change: Encourage customers to leave reviews on major platforms and consider publishing case studies with measurable results.

What's working

• All major AI crawlers receive full access with no UA-based blocking — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others all receive 200 responses with identical content on the homepage. The robots.txt does not disallow any AI bots.
• llms.txt file is published and contains useful site overview — An llms.txt file exists at the root, providing a summary of the site and links to key pages. This helps AI crawlers discover important content.
• Individual blog posts use BlogPosting schema markup — Blog posts are marked up with BlogPosting schema, which helps AI engines understand and surface article content.
• DNS records show domain verifications for multiple AI and vendor tools — TXT records include verifications for Anthropic, Cursor, Atlassian, Stripe, and Zoho, indicating active integrations and AI-tool readiness.
• Sitemap is available and contains 80 URLs — A sitemap is published with 80 URLs, helping search engines and AI crawlers discover site content.