Loupe has written six comparisons, three "best alternatives" guides, five topic pages and a glossary, and says AlphaSense is the most direct comparison in buyer conversations. All of it is blocked from Google, Bing and DuckDuckGo in robots.txt and exists only as markdown for AI agents, and the sitemap has four URLs. So a portfolio manager who types "AlphaSense alternatives" or "broker research aggregation" into a search engine cannot find Loupe, and assistants that ground their answers in a search index see nothing either. The content work is done; it is just not visible where buyers search.
First action
Pick the four pages and draft the HTML template.
How to measure it
Qualified access requests from organic search
- Now
- –
- Target
- 40 a month
- By
- 90 days
Steps
Pick four pages
Highest buyer intent first.
Growth lead 1 day
Check rival facts
Current, sourced, fair.
Content lead 3 days
Design the template
Table, summary, request form.
Founding engineer 2 days
Publish
HTML pages with canonicals; .md kept for agents.
Founding engineer 2 days
Update robots and sitemap
Allow the new pages.
Founding engineer 1 hour
Submit
Search Console and Bing Webmaster Tools.
Growth lead 1 hour
Track
Impressions, rankings and requests by page.
Growth lead weekly
Add the rest
Remaining comparisons and topic pages.
Content lead 1 month
Why it works
Render the best of it as normal, designed web pages: start with Loupe vs AlphaSense, Best AlphaSense alternatives, Loupe vs Bloomberg Terminal and Broker research aggregation. Allow them in robots.txt, add them to the sitemap, keep the .md files for agents with a canonical tag pointing to the HTML page, and end every page with a request-access form that asks role and asset class. Check that every statement about a rival is current and sourced before publishing.
Comparison and "alternatives" searches come from people already shopping. Pages that rank there bring the buy-side and analyst sign-ups a pre-launch waitlist needs, and the robots worry (raw markdown showing up in results) goes away once the pages are real HTML.
Ready to use
ChecklistIndexable comparisons
[ ] Loupe vs AlphaSense page [ ] Best AlphaSense alternatives page [ ] Loupe vs Bloomberg Terminal page [ ] Broker research aggregation page [ ] Rival facts checked and dated [ ] robots.txt allows the HTML pages [ ] Sitemap lists them [ ] .md canonical to HTML [ ] Request form asks role and asset class
Risks and how to handle them
Statements about rivals go out of date
Date every page and review quarterly.
Raw markdown still appears in results
Keep .md files disallowed and canonical to the HTML page.
Evidence
- Your websiterobots.txt: for Google, Bing and DuckDuckGo the posture is "index landing pages only"; "The /vs/*, /alternatives/*, /docs/*, /articles/*, /glossary.md and keyword-anchor .md files are blocked so they never surface as separate Google results", while AI search assistants get "full access" and AI training crawlers are "blocked entirely".Source
- Your websitellms.txt lists content written for AI agents as markdown files: six comparisons (Bloomberg Terminal, AlphaSense, AIera, Samaya AI, Rogo/Hebbia, Perplexity Finance), three "best alternatives" pages (AlphaSense, Bloomberg, AI-native platforms), five topic pages (investment research platform, hedge fund research software, research management platform, broker research aggregation, AI financial copilot), a glossary and one article, "How Hedge Funds Consume Research in 2026".Source
- Your websiteSitemap: four URLs (home, manifesto, privacy, terms), all dated May 29, 2026.Source
- Your websiteLoupe vs. AlphaSense: AlphaSense is "the most direct comparison Loupe faces in buyer conversations"; Loupe is "Multi-asset, starting fixed income, expanding", with a user model of "Individual analyst → firm" and the feed as "the curated morning brief".Source
- Your websiteFull product context (llms-full.txt): primary users are buy-side investors, sell-side analysts, independent analysts and corporate development teams; Loupe is "a feed-driven marketplace" with AI summarisation and "compliance-first publishing" (audit trails, MiFID II reporting fields). "There is no self-serve signup"; the team "prioritises buy-side investors, sell-side desks, and established independent analysts during the closed beta"; pricing will be tiered "for individual analysts, boutique funds, and enterprise (multi-seat) plans at GA"; "Beta access is free for selected design partners". No public API or MCP server yet.Source