papercut.com — AI Site Grade

Analysis

PaperCut AI-Visibility Audit

The site has zero structured data across its entire public surface — no Organization, SoftwareApplication, or Product schema on any page — despite being a 20-year-old software company with 115 million users, making it effectively invisible to AI engines that rely on schema for entity understanding.

Crawler Access

All major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended) receive 200 status with full HTML content identical to browser delivery. The robots.txt uses a single User-agent: * catch-all with no AI-bot-specific directives — no Disallow: / for any crawler, no GPTBot or ClaudeBot section. The site runs on Cloudflare behind Google infrastructure (via: 1.1 google), with s-maxage=2419200 (28-day CDN cache). No JS-rendering risk: all pages deliver full text on plain GET.

Schema Posture

The homepage, products page, about page, FAQ page, and blog all return zero JSON-LD schema blocks. The only page with any structured data is /products/hive/, which has a FAQPage schema with three Q&A entries. No Organization, SoftwareApplication, WebSite, BreadcrumbList, or Product schema exists anywhere. The site has no llms.txt (returns 404). The DNS TXT records include an openai-domain-verification token, confirming PaperCut has engaged with OpenAI's crawler verification program — but the site has not followed through with the schema or content signals that would make that verification useful.

Cold-Knowledge Gap

The LLM's cold knowledge correctly identifies PaperCut as a print management company with products MF, NG, Hive, and Pocket, and mentions the CVE-2023-27350 security vulnerability as a "reputational signal." The site itself contains zero mention of this vulnerability anywhere — no security advisory, no patch notice, no "we fixed it" page. The /get/g2-report-print-management/ URL (prominently linked from the homepage as "PaperCut ranked #1 in Print Management") returns a 404. The homepage claims "PaperCut ranked #1 in Print Management" but the link to the G2 report is broken.

Content Signals

The FAQ page at /faq/ contains ~4,800 words of plain-text Q&A but uses no FAQ schema — it is invisible to AI answer extraction. The blog has only three posts visible, the most recent dated April 2026, suggesting either a very low publishing cadence or a truncated feed. The customer stories page lists dozens of case studies across education, healthcare, legal, and government sectors — strong social proof — but none carry Article or CaseStudy schema. The ARM64 printing guide is a well-written, timely piece (referencing Windows 10 EOL in October 2025) that would serve well as an AI-retrieval target, but has no schema markup.

Findings

1. Zero structured data across all public pages High

   No Organization, SoftwareApplication, Product, or WebSite schema exists on any page. The only schema is a FAQPage on /products/hive/ with three entries. This makes the site invisible to AI engines that rely on schema for entity understanding.

   What to change: Add JSON-LD structured data for Organization, SoftwareApplication, and Product schema on relevant pages. Implement BreadcrumbList and WebSite schema site-wide.

2. Broken link to G2 report from homepage High

   The homepage links to /get/g2-report-print-management/ claiming 'PaperCut ranked #1 in Print Management', but this URL returns a 404 error.

   What to change: Fix the broken link or remove the claim from the homepage until the report is accessible.

3. No mention of known CVE-2023-27350 vulnerability Medium

   The site contains zero content about the CVE-2023-27350 security vulnerability, which is a known reputational signal in LLM knowledge. This omission may erode trust with AI-driven research.

   What to change: Publish a security advisory or patch notice page addressing CVE-2023-27350 and link it from the site.

4. No llms.txt file for AI guidance Medium

   The site returns a 404 for /llms.txt, missing an opportunity to provide AI crawlers with a curated list of important pages and context.

   What to change: Create an llms.txt file listing key pages like products, FAQ, and customer stories.

5. FAQ page lacks FAQ schema Medium

   The /faq/ page contains ~4,800 words of plain-text Q&A but uses no FAQ schema, making it invisible to AI answer extraction.

   What to change: Add FAQPage schema to the /faq/ page.

6. Customer stories lack Article or CaseStudy schema Medium

   The /customer-stories/ page lists dozens of case studies but none carry Article or CaseStudy schema, reducing their discoverability by AI.

   What to change: Add Article or CaseStudy schema to each customer story.

7. Blog shows only three posts with low cadence Low

   The blog page displays only three posts, with the most recent dated April 2026, indicating very low publishing frequency which limits fresh content for AI indexing.

   What to change: Increase blog publishing frequency to at least monthly.

8. ARM64 printing guide lacks schema markup Low

   The well-written guide at /discover/how-papercut-solves-the-arm64-printing-problem/ has no schema markup, missing an opportunity for AI retrieval.

   What to change: Add Article schema to the guide page.

What's working

• All major AI crawlers receive full HTML content — All tested AI crawlers (GPTBot, ClaudeBot, etc.) receive 200 status with full HTML content identical to browser delivery, with no JS-rendering risk.
• OpenAI domain verification token present in DNS — DNS TXT records include an openai-domain-verification token, confirming PaperCut has engaged with OpenAI's crawler verification program.
• FAQPage schema on /products/hive/ — The /products/hive/ page includes a FAQPage schema with three Q&A entries, providing some structured data for AI extraction.
• robots.txt does not block any AI crawlers — The robots.txt uses a single User-agent: * catch-all with no AI-bot-specific directives, allowing all crawlers full access.
• Sitemap available with 80 URLs — The sitemap at /sitemap.xml returns 200 with 80 URLs, aiding crawler discovery.
• Dozens of customer stories across sectors — The customer stories page lists case studies across education, healthcare, legal, and government sectors, providing strong social proof.