forked from molecule-ai/molecule-core
docs: brand discoverability audit — Molecule AI SERP pollution (2026-04-16)
This commit is contained in:
parent
0bdb0e899e
commit
fcee2a1863
215
docs/marketing/seo/2026-04-16-brand-discoverability.md
Normal file
215
docs/marketing/seo/2026-04-16-brand-discoverability.md
Normal file
@ -0,0 +1,215 @@
|
||||
# Brand Discoverability Brief: "Molecule AI" SERP Pollution
|
||||
**Date:** 2026-04-16
|
||||
**Owner:** SEO / Growth Analyst
|
||||
**Trigger:** Social Media Brand audit flag, 20:00 2026-04-16
|
||||
**Status:** Active — feeds PMM brand naming conversation
|
||||
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
The brand name "Molecule AI" is severely polluted. A full audit of the head-term SERP today shows **zero results for our product in the top 10 results** — every slot is occupied by drug-discovery and biotech companies. Our product does not appear in any developer-intent search without additional qualifiers, and even those modifier queries are unowned. This is not a fixable-with-content problem alone; it warrants a formal PMM conversation about whether the brand needs a persistent qualifier in developer contexts.
|
||||
|
||||
**Pollution severity: 9/10 (critical)**
|
||||
|
||||
---
|
||||
|
||||
## 1. Pollution Audit: Top 10 SERP for "Molecule AI" (2026-04-16)
|
||||
|
||||
| Rank | Result | Owner | Relevant to us? |
|
||||
|------|--------|-------|----------------|
|
||||
| 1 | moleculeai.com | Molecule AI Pvt. Ltd. (Delhi) — drug discovery SaaS, MoleculeGEN platform | ❌ Noise |
|
||||
| 2 | linkedin.com/company/molecule-ai | LinkedIn page — description reads "AI-based drug design" | ❌ Noise (their page) |
|
||||
| 3 | moleculeai.io | AI Powered Molecular Intelligence — drug/target interaction | ❌ Noise |
|
||||
| 4 | playmolecule.ai | PlayMolecule — computational chemistry platform | ❌ Noise |
|
||||
| 5 | molecule.one | Making Molecules / Discovering Chemistry | ❌ Noise |
|
||||
| 6 | shuttlepharma.com article | Shuttle Pharma LOI to acquire molecule.ai | ❌ Noise |
|
||||
| 7 | icahn.mssm.edu | Icahn School of Medicine AI Drug Discovery Center | ❌ Noise |
|
||||
| 8 | moleculeai.com/products | Molecule AI drug discovery products page | ❌ Noise |
|
||||
| 9 | shuttlepharma.com article #2 | Second molecule.ai acquisition announcement | ❌ Noise |
|
||||
| 10 | eisai.com | Eisai pharmaceutical AI-driven drug design | ❌ Noise |
|
||||
|
||||
**Score: 0/10 results are ours.**
|
||||
|
||||
Additional collision surfaces discovered:
|
||||
- **moleculeai.tech** — a blockchain/crypto project also calling itself "MoleculeAI" (Base-powered SDK, MOLAI token) — a third-namespace collision in developer spaces
|
||||
- **github.com/MolecularAI** — owned by AstraZeneca (REINVENT4 molecular design tool, 1k+ stars) — appears in developer searches and is easily confused
|
||||
- **Multiple LinkedIn entities** named "Molecule AI" — drug-discovery companies have established pages
|
||||
|
||||
---
|
||||
|
||||
## 2. Handle & SERP Ownership Assessment
|
||||
|
||||
### Google SERP — Modifier Queries
|
||||
|
||||
| Query | Do we appear? | Who does appear? |
|
||||
|-------|--------------|-----------------|
|
||||
| "Molecule AI developer platform" | ❌ No | Generic AI orchestration roundups (IBM, Kore.ai, Domo) |
|
||||
| "Molecule AI agents" | ❌ No | Generic multi-agent framework articles |
|
||||
| "Molecule AI orchestration" | ❌ No | Generic orchestration guides (LangChain, CrewAI) |
|
||||
| "molecule.ai agents" | ❌ No | moleculeai.com drug-discovery products page |
|
||||
| "Molecule AI runtime" | ❌ No | Generic agent runtime articles |
|
||||
|
||||
**We own zero SERP slots — not even the branded modifier queries.** There is no Google Knowledge Panel for us; when one appears, it will likely be for the drug-discovery companies given their domain authority and Crunchbase/LinkedIn establishment.
|
||||
|
||||
### X (Twitter) Handle
|
||||
|
||||
| Handle | Status | Notes |
|
||||
|--------|--------|-------|
|
||||
| @molecule_ai | Ours (confirmed) | **17 posts total** — extremely low activity; profile is not discoverable in X search for "molecule ai developer" |
|
||||
| X bio/description | Unknown | Not visible in SERP snippet; needs to explicitly say "AI agent platform" to disambiguate |
|
||||
|
||||
**Assessment:** @molecule_ai is the right handle but the account is nearly dormant (17 posts). X's algorithm surfaces accounts by follower count × recency × keyword match. At 17 posts we will not surface for any brand-related X search. Drug-discovery companies with active social presences will dominate X search for "Molecule AI" just as they dominate Google.
|
||||
|
||||
### LinkedIn
|
||||
|
||||
The LinkedIn `company/molecule-ai` page appears in SERP but the description snippet that Google indexes reads as drug-design content — meaning the page may belong to the drug-discovery "Molecule AI" company, not us, or our page description is absent/wrong. Either way, our developer identity is not present on LinkedIn's version of our brand name.
|
||||
|
||||
---
|
||||
|
||||
## 3. Top 3 Actionable Recommendations
|
||||
|
||||
Ranked by impact × speed. Full option matrix follows.
|
||||
|
||||
---
|
||||
|
||||
### Recommendation 1 (Highest impact): Publisher Strategy — Own the Developer Modifier SERP Immediately
|
||||
|
||||
**The insight:** The head term "Molecule AI" is unwinnable in the short term — drug-discovery companies have domain authority, press coverage, Crunchbase profiles, and 3+ years of indexed content. But **every developer-modifier combination is completely empty.** No competitor (drug-discovery or otherwise) has published content targeting:
|
||||
- "Molecule AI agent platform"
|
||||
- "Molecule AI orchestration"
|
||||
- "Molecule AI runtime"
|
||||
- "Molecule AI developer"
|
||||
- "Molecule AI multi-agent"
|
||||
|
||||
These are our brand name + our product category. We can own 100% of this modifier SERP within 60–90 days with consistent publishing.
|
||||
|
||||
**Specific actions:**
|
||||
|
||||
1. Every blog post, doc page, press mention, and social post should include the phrase "Molecule AI agent platform" or "Molecule AI multi-agent runtime" — written out, not shortened. This is a content instruction, not a style preference.
|
||||
2. The homepage `<title>` tag should read: `Molecule AI — AI Agent Platform for Developers` (not just `Molecule AI`).
|
||||
3. Homepage and `/about` H1 must include: "The AI agent platform built for developers" with "Molecule AI" in the page's `<h1>` or prominent above-the-fold text — Google uses this to anchor the entity.
|
||||
4. Publish 3 anchor pieces targeting modifier queries (see Keyword Targets below).
|
||||
|
||||
**Effort:** Low-Medium (content + on-page changes). **Timeline:** 30–60 days to first ranking.
|
||||
|
||||
---
|
||||
|
||||
### Recommendation 2 (Medium impact, fast): Organization Schema + Knowledge Panel Claim
|
||||
|
||||
**The insight:** Google serves a Knowledge Panel for "Molecule AI" if it can find a confident entity match. Right now it's returning drug-discovery content because those companies have structured data (Crunchbase, Wikipedia/Wikidata, LinkedIn pages with descriptions) and we don't.
|
||||
|
||||
**Specific actions:**
|
||||
|
||||
1. **Add `Organization` JSON-LD to `<head>` of homepage immediately:**
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "Organization",
|
||||
"name": "Molecule AI",
|
||||
"description": "AI agent platform for developers. Build, deploy, and orchestrate multi-agent systems across any runtime.",
|
||||
"url": "https://molecule.ai",
|
||||
"logo": "https://molecule.ai/logo.png",
|
||||
"foundingDate": "2024",
|
||||
"applicationCategory": "DeveloperApplication",
|
||||
"sameAs": [
|
||||
"https://x.com/molecule_ai",
|
||||
"https://github.com/Molecule-AI",
|
||||
"https://www.linkedin.com/company/molecule-ai"
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
2. **Create a Wikidata entity** for Molecule AI (our company). Wikidata is Google's primary Knowledge Graph source. Requirements: 3+ independent citations (press articles, blog mentions). We need to produce/earn these via DevRel outreach and release announcements.
|
||||
3. **Claim/verify Google Search Console** for all owned properties and submit updated sitemap.
|
||||
4. **Ensure NAP consistency** (Name/Address/Email) across Crunchbase, LinkedIn, AngelList, GitHub org description, and website footer — Google uses inconsistency as a signal to de-prioritize a Knowledge Panel.
|
||||
|
||||
**Effort:** Low (schema = 1 hour dev work). **Timeline:** Schema helps within 2–4 weeks; Knowledge Panel takes 60–90 days after citations are established.
|
||||
|
||||
---
|
||||
|
||||
### Recommendation 3 (Strategic): X Bio + Cadence Fix to Reclaim Social Discoverability
|
||||
|
||||
**The insight:** @molecule_ai with 17 posts is invisible. X's search surfaces accounts by bio keyword match + account authority. Our bio must explicitly contain "AI agent platform" and we need a minimum content floor to rank in X search.
|
||||
|
||||
**Specific actions:**
|
||||
|
||||
1. **Update X bio immediately** to: `AI agent platform for developers. Build and deploy multi-agent systems across Gemini CLI, Claude Code, and any runtime. #AIAgents #DevTools`
|
||||
2. **Pinned post:** Publish a pinned tweet explicitly about Molecule AI as a developer agent platform — this is what X surfaces first when someone clicks our profile from search.
|
||||
3. **Cadence floor:** Minimum 5 posts/week to build account authority. Below this threshold, X algorithm will not surface us for brand queries. Coordinate with Social Media Brand to set this.
|
||||
4. **Handle assessment:** @molecule_ai is fine and defensible — do NOT change it. Changing handles destroys existing follower graph and creates dead-link problems. If APAC developer audiences are underserved, consider a secondary handle (@moleculeai_dev or @moleculeai_apac) but only after primary handle activity is healthy.
|
||||
|
||||
**Effort:** Very low (bio update = 5 minutes; cadence = editorial calendar item). **Timeline:** X discoverability improves within 2–4 weeks of consistent posting.
|
||||
|
||||
---
|
||||
|
||||
## 4. Quick Wins vs. 30-Day Plays
|
||||
|
||||
### Quick Wins (This Week, ≤3 Days Each)
|
||||
|
||||
| Action | Owner | Time |
|
||||
|--------|-------|------|
|
||||
| Update `<title>` tag on homepage to `Molecule AI — AI Agent Platform for Developers` | Frontend Engineer | 1 hr |
|
||||
| Add `Organization` JSON-LD schema to homepage `<head>` | Frontend Engineer | 1 hr |
|
||||
| Update X bio to include "AI agent platform" and "multi-agent" keywords | Social / Marketing | 15 min |
|
||||
| Publish pinned tweet explicitly positioning Molecule AI as a developer agent platform | Social / Marketing | 30 min |
|
||||
| Audit and correct LinkedIn company page description (ensure ours says "AI agent platform", not drug design) | Marketing Lead | 30 min |
|
||||
| Add Molecule AI to Crunchbase with correct category ("Developer Tools", "AI/ML") | Marketing Lead | 1 hr |
|
||||
| Ensure GitHub org description reads "AI agent platform — multi-agent orchestration for developers" | Dev Lead | 15 min |
|
||||
|
||||
**Combined quick-win impact:** These 7 actions take <1 day total and immediately begin building the entity disambiguation signal Google needs to separate us from drug-discovery noise.
|
||||
|
||||
### 30-Day Plays
|
||||
|
||||
| Action | Owner | Timeline |
|
||||
|--------|-------|----------|
|
||||
| Publish 3 anchor blog posts targeting "Molecule AI agent platform", "Molecule AI orchestration", "Molecule AI runtime" | Content + SEO | Week 2–4 |
|
||||
| Earn 3+ independent press citations (launch announcement, ProductHunt, Hacker News Show HN) | Marketing Lead + DevRel | Week 2–4 |
|
||||
| Create Wikidata entity with citations | SEO | Week 3–4 (requires citations first) |
|
||||
| Bring X posting to minimum 5/week cadence | Social | Ongoing from Week 1 |
|
||||
| Build `/about` page with full company description, team, schema markup | Frontend + Content | Week 2–3 |
|
||||
| File for Google Knowledge Panel verification (via Search Console + Wikidata) | SEO | Week 4 (after citations exist) |
|
||||
| Add Molecule AI to developer tool directories: There's An AI For That, Futurepedia, AI Tools Directory | Marketing | Week 2 |
|
||||
| Request coverage in "AI agent frameworks" roundup articles (currently appearing in: KDNuggets, Vellum.ai, Guideflow) | DevRel | Week 3–4 |
|
||||
|
||||
---
|
||||
|
||||
## Branded Search Term Ownership Plan
|
||||
|
||||
These are the modifier queries we should own within 90 days. Each needs at least one page/post anchoring it:
|
||||
|
||||
| Target Term | Content Vehicle | Current Rank |
|
||||
|------------|----------------|-------------|
|
||||
| `Molecule AI agent platform` | Homepage, /about | ❌ Unranked |
|
||||
| `Molecule AI orchestration` | Blog post (anchor) | ❌ Unranked |
|
||||
| `Molecule AI runtime` | /runtimes index + blog | ❌ Unranked |
|
||||
| `Molecule AI multi-agent` | Blog post | ❌ Unranked |
|
||||
| `Molecule AI developer` | Blog + docs | ❌ Unranked |
|
||||
| `Molecule AI Gemini` | /runtimes/gemini-cli (in progress — #514) | ❌ Unranked |
|
||||
| `molecule.ai agents` | Homepage (canonical domain claim) | ❌ Unranked |
|
||||
|
||||
---
|
||||
|
||||
## 5. Flag: Does This Warrant a Brand Naming Conversation with PMM?
|
||||
|
||||
**Yes. Recommend escalating.**
|
||||
|
||||
The collision is not cosmetic. The drug-discovery "Molecule AI" namespace is:
|
||||
- Established with funded companies (Shuttle Pharma acquisition underway)
|
||||
- Active in PR/press (Shuttle Pharma press releases dominate Google News)
|
||||
- Occupying the exact domain variants we cannot acquire (moleculeai.com, moleculeai.io)
|
||||
- Producing content that will only grow as APAC pharma AI investment increases
|
||||
|
||||
**Risk horizon:** If Shuttle Pharma completes the moleculeai.io/molecule.ai acquisition, their combined entity becomes a well-funded, PR-active brand with our exact name in the pharmaceutical AI space. Google, X, and LinkedIn will further consolidate results toward them.
|
||||
|
||||
**PMM conversation agenda:**
|
||||
1. Should "Molecule AI" carry a persistent developer qualifier in all marketing contexts? Options: `Molecule AI Platform`, `Molecule AI (DevTools)`, `Molecule — AI Agent Platform`
|
||||
2. Is there a differentiated handle strategy worth pursuing? Options: @moleculeai_dev, @molecule_agents, @getmoleculeai
|
||||
3. What is the threshold for a brand rename vs. a qualifier strategy? (Estimate: if drug-discovery companies consolidate under the name within 12 months, a rename is cheaper than SEO remediation)
|
||||
4. Can we acquire molecule.ai domain or molecule.dev as a canonical domain redirect?
|
||||
|
||||
**My recommendation:** Don't rename now, but adopt "Molecule AI Platform" as the consistent long-form in all B2B/developer contexts and double down on the developer-modifier SERP ownership strategy above. Revisit in 90 days after measuring whether modifier queries are ranking.
|
||||
|
||||
---
|
||||
|
||||
*Generated by SEO / Growth Analyst — 2026-04-16. Data: web SERP audit, X handle research, LinkedIn brand audit, competitive landscape analysis.*
|
||||
Loading…
Reference in New Issue
Block a user