74/ 100
Grade: B− — Strong brand, real gaps in the machine layer
When someone asks an AI assistant to recommend project management software, Basecamp's reputation carries it — but the site itself hands AI engines less than it should. Three specific, fixable gaps are leaving recommendation quality and coverage on the table.
People increasingly ask an AI — ChatGPT, Claude, Perplexity, Gemini — instead of scrolling search results. This audit measures one thing: how well an AI assistant can find, understand, and confidently recommend you. Seven signals, each scored from public data, each with the specific fix.
The seven signals
1
AI recommendation
Strong · 9/10
FoundAcross assistant queries (including this auditor), Basecamp surfaces reliably as a recommendation for small-team / simple project management. Decade-plus brand equity does the heavy lifting.
WhyThis is the outcome that matters — and your strongest asset. The job now is protecting it as competitors optimize for the same answer slot.
FixMaintain the lead by closing the input gaps below — they're what determines how accurately and how often you're surfaced as the field gets crowded.
2
Structured data (schema)
Partial · 5/10
FoundSchema is present but navigational only — WebSite, WebPage, SiteNavigationElement, ItemList. The high-value types that describe the product and company are absent: no SoftwareApplication, Organization, Offer/Product, or FAQPage.
WhyThose are exactly the types AI uses to state what you are, what you cost, and what you do. Without them, the model infers — and inference is where it gets you wrong or omits you.
FixAdd SoftwareApplication + Organization + Offer schema to the homepage and pricing page, and FAQPage to support content. ~half a day for a developer.
3
Answerability
Partial · 5/10
FoundPricing, support, and testimonials pages exist, but the site carries little question-and-answer-formatted content (one question-style heading on the homepage; no on-page FAQ block). Buyer questions — "how much is Basecamp," "Basecamp vs Asana," "is it good for small teams" — aren't answered in a directly quotable form.
WhyAI assistants lift direct answers. If you don't phrase the answer, a third-party site (or a competitor's comparison page) does — and gets cited instead of you.
FixAdd a concise FAQ (pricing, team size, comparisons, key limits) in plain Q&A, marked up with FAQPage schema.
4
AI crawlability
Good, one gap · 7/10
Foundrobots.txt is open, a sitemap is declared, and the homepage serves real content + schema to AI crawlers (verified under an AI-crawler user agent — content is in the HTML, not JS-locked). But there is no llms.txt (returns 404).
Whyllms.txt is the emerging convention for telling AI models, in plain language, what you are and which pages matter — a direct line to the systems now doing the recommending.
FixPublish an llms.txt at the domain root: one paragraph on what Basecamp is and who it's for, plus links to pricing, features, and support. ~30 minutes.
5
Third-party presence
Strong · 9/10
FoundDeep footprint in the sources AI trusts — independent reviews, roundups, long discussion history, and the 37signals book catalog (Rework, Shape Up). Models have plenty of corroborating signal.
WhyAI weights third-party corroboration heavily — it's how it decides you're real and recommendable. This is a moat most companies lack.
FixMaintain it; ensure recent reviews and comparison pages stay current so the corroboration doesn't go stale.
6
Entity clarity
Strong · 9/10
FoundCrystal-clear positioning — the meta description ("the calm, organized way to manage projects… trusted by millions") states what it is and who made it in one line. No ambiguity for a model to trip on.
WhyA model can only recommend what it can cleanly identify. Clear entity = clean recommendation.
FixReinforce by adding the Organization schema from signal 2 so the clear human-readable identity is also machine-readable.
7
Freshness
Good · 7/10
FoundActively maintained product and site (versioned assets, current pricing). No obviously stale claims surfaced in the public pages reviewed.
WhyAI down-weights content it judges outdated. Freshness keeps you in the answer.
FixDate key pages and keep comparison/pricing content current; revisit quarterly.
Do these three first
The 80/20 — highest impact, lowest effort
- Publish an
llms.txt (~30 min). A direct, plain-language line to the models doing the recommending — and the single fastest gap to close.
- Add product + company schema — SoftwareApplication, Organization, Offer (~half a day). Stops AI from guessing what you are, what you cost, and what you do.
- Add an FAQ in plain Q&A with FAQPage schema (~half a day). Wins the direct-answer slot for buyer questions instead of ceding it to comparison sites.
Want this run on your site? A full AI-visibility audit, scored across all seven signals, with a prioritized fix list your developer can action — and an optional monthly monitor as the models keep changing.
Audit $149launch price $99 · monitor $39/mo
Methodology. Scored from public data on June 15, 2026. Each signal is checked at source — pages are fetched under an AI-crawler user agent to see what the models actually receive (not what a browser renders), and the AI-recommendation signal is assessed via assistant queries. Weighting: AI recommendation 25%, structured data / answerability / crawlability / third-party presence 15% each, entity clarity 10%, freshness 5%. Scores are a point-in-time estimate; AI systems and their sources change, which is what the monthly monitor tracks. Findings reflect public information only — nothing was sent to or requested from the subject.