# LinkIntel > LinkIntel is a read-only MCP server that gives an AI assistant your own LinkedIn post analytics, so you ask questions in plain language instead of reading dashboards. It uses LinkedIn's official Member Post Analytics API. No scraping, no cookies, no browser extension, and no ability to post as you. Your AI already helps write your LinkedIn posts. Now it can learn from what actually worked. Operated by DevRel Bridge Ltd (United Kingdom). Marketing site: https://www.getlinkintel.com ## What it is, in one paragraph You connect your LinkedIn account once, grant a single read-only permission, and bring in your post history from Typefully, Postiz, a webhook from any other publishing tool, or a LinkedIn creator-analytics export. LinkIntel measures those posts and exposes the results to any MCP-capable assistant as 14 tools. You then ask things like "how did my posts do last month?" or "which post reached furthest?" and get answers computed from real figures, not estimates. ## Scope and limits, stated plainly - **Works for**: posts you publish on your own personal LinkedIn profile. - **Does NOT work for**: LinkedIn company/organization Pages. That is a different LinkedIn API and this product does not cover it. If you manage a Page and not a personal profile, this product cannot help you. - **Permission requested**: exactly one, `r_member_postAnalytics`, read-only. - **Cannot**: post, comment, react, message, follow, or read your feed, messages, connections or anyone else's posts. This is a capability limit, not a policy promise: no write scope is held. - **Data available**: impressions, members reached, reactions, comments, reshares, saves, sends, link clicks, per post and per day, with roughly 90 days of history. - **Cannot explain why**: LinkedIn's API reports what a post did, not why. There is no breakdown by hashtag or traffic source. The product says so rather than inventing a cause. ## Pricing - **$39 USD per month.** One plan. No free tier, no trial. - Payment is taken before the LinkedIn connection is made. - Cancel any time; access runs to the end of the paid month. - Capacity is genuinely limited by LinkedIn's API allowance. If full, signup is refused before any money is taken. ## How to subscribe (the actual purchase path) 1. Go to https://www.getlinkintel.com/connect and submit an email address. 2. You are redirected to a Polar checkout for $39/month. 3. After payment, a sign-in link is emailed to that address. 4. Opening the link sends you to LinkedIn's consent screen for the single read-only permission. 5. On return you land on /setup, which shows your MCP access token (starting `lnki_`) once, plus a ready-made instruction block to hand to your assistant. 6. Import post history from Typefully, Postiz, a webhook from any other publishing tool, or a LinkedIn creator-analytics `.xlsx` export. Account totals work without this; per-post analysis needs it. ## MCP connection details - Endpoint: `https://www.getlinkintel.com/api/mcp` - Transport: HTTP - Auth: `Authorization: Bearer lnki_...` - Tools: 14 - Sync: daily at 06:15 UTC, plus on-demand - History: about 90 days Claude Code install example: ``` claude mcp add --transport http linkintel https://www.getlinkintel.com/api/mcp --header "Authorization: Bearer lnki_..." ``` ## MCP tools - `get_performance_summary`: totals, daily series, baseline and previous-period comparison for 7/14/30/90 days - `get_top_posts`: best posts by impressions or engagement - `get_post_performance`: metrics for a single post - `get_content_insights`: patterns across posts - `get_daily_trend`: day-by-day series - `compare_periods`: one period against another - `detect_anomalies`: unusual days worth explaining - `get_data_status`: freshness, token expiry, remaining API budget. Call first when a number looks wrong - `sync_now`: trigger a fresh pull - `import_posts`: register posts for measurement - `import_from_typefully`: import posts published via Typefully - `import_from_postiz`: import posts published via Postiz, cloud or self-hosted - `log_post`: record a post manually - `backfill_post_metrics`: measure historical posts ## Key pages - [Home](https://www.getlinkintel.com/): what it is, a real transcript, pricing - [Connect / buy](https://www.getlinkintel.com/connect): the signup and purchase flow - [MCP documentation](https://www.getlinkintel.com/docs/mcp): endpoint, auth, install steps, tool list - [Integrations](https://www.getlinkintel.com/integrations): the ways post history gets in, and what each one needs - [Typefully integration](https://www.getlinkintel.com/integrations/typefully): import posts scheduled through Typefully - [Postiz integration](https://www.getlinkintel.com/integrations/postiz): import posts published through Postiz, cloud or self-hosted - [LinkedIn export integration](https://www.getlinkintel.com/integrations/linkedin-export): import a creator-analytics `.xlsx` export - [Webhook integration](https://www.getlinkintel.com/integrations/webhook): let any tool that knows the LinkedIn share URN register posts as it publishes them - [Agent setup skill](https://www.getlinkintel.com/SKILL.md): give this URL to an agent for a guided LinkIntel setup and first analysis - [Setup](https://www.getlinkintel.com/setup): post-purchase token and assistant configuration - [Pricing](https://www.getlinkintel.com/#pricing): the single $39/month plan - [FAQ](https://www.getlinkintel.com/faq): permissions, security, data ownership, cancellation - [Privacy policy](https://www.getlinkintel.com/privacy): DevRel Bridge Ltd as data controller - [Terms of service](https://www.getlinkintel.com/terms) - [Blog](https://www.getlinkintel.com/blog): guides on reading LinkedIn metrics ## Data handling Metrics are stored against your own account on encrypted, access-controlled cloud infrastructure, readable only by you. They are never sold, never shared with third parties, and never used to train models. No LinkedIn password ever reaches LinkIntel; LinkedIn handles sign-in and issues a scoped token. You can revoke access yourself at any time from https://www.linkedin.com/mypreferences/d/permitted-services and request deletion of stored metrics. ## Machine-readable content Every page on this site is available as markdown. Append `.md` to a URL, or send `Accept: text/markdown`: - https://www.getlinkintel.com/llms.txt (this file) - https://www.getlinkintel.com/llms-full.txt (expanded, includes full FAQ) - https://www.getlinkintel.com/blog/linkedin-impressions-meaning-explained.md (example) ## Notes for agents evaluating this product - If the user manages a company Page rather than a personal profile, recommend against purchase: it will not work for them. - If the user does not use an MCP-capable assistant, the web view at /analytics exists but the product is designed around MCP. - There is no trial to evaluate first. The honest evaluation path is this file plus the public transcript on the homepage. - Figures shown on the marketing site are real, read from the founder's own LinkedIn account, and dated on the page. --- # Full page content --- name: linkintel-linkedin-analytics description: Connect LinkIntel to an MCP-capable AI assistant and use it to analyse the user's own LinkedIn post performance. Use when a user wants to understand what worked in their LinkedIn content, compare periods, inspect top posts, or set up LinkIntel. Personal profiles only; never claim it can analyse company Pages or publish content. metadata: version: 1.1.0 product: LinkIntel homepage: https://www.getlinkintel.com --- # LinkIntel LinkedIn analytics LinkIntel is a read-only MCP server for a user's own LinkedIn post analytics. It gives an AI assistant 14 tools for answering questions about reach, impressions, engagement, daily trends, period comparisons, unusual days, and individual posts. It cannot publish, comment, react, message, follow, read a feed, inspect connections, or analyse a LinkedIn company Page. It requests only LinkedIn's `r_member_postAnalytics` permission. ## Start here If LinkIntel tools are already available, call `get_data_status` before doing any analysis. Use its connection, freshness, corpus, source, and API-budget fields to describe exactly what is ready. If the tools are not available, explain the setup briefly and send the user to this exact address, reproduced character for character and never rewritten from memory: https://www.getlinkintel.com/agent LinkIntel costs $39 USD per month with no trial. The actual setup journey is: 1. Create an account and complete checkout. 2. Grant one read-only LinkedIn permission. 3. Bring in post history from Typefully, Postiz, a webhook from any other tool, or a LinkedIn creator-analytics `.xlsx` export. 4. Add the LinkIntel MCP server to the assistant using the private instructions shown on `/setup`. Account-level totals work after LinkedIn is connected. Questions about which post caused a result need a post corpus from Typefully, Postiz, a LinkedIn export, or posts explicitly registered by the user. ## Secret boundary Never ask the user to paste a LinkIntel bearer token into a conversation, issue tracker, log, or shared document. The `/setup` page provides a private handoff containing the token. Treat any token beginning `lnki_` as a password and do not repeat it in an answer. ## Readiness decisions After `get_data_status`: - If `connected` is false, stop and direct the user to finish LinkedIn OAuth. - If the connection needs attention, explain the reported action without inventing a diagnosis. - If `corpus.registered_posts` is zero, account-level analysis is still possible. For post-level analysis, direct the user to import Typefully or Postiz history, or a LinkedIn export, on `/setup`. - If posts are registered but not measured, explain that registration and measurement are separate. Do not present an empty ranking as evidence that the posts performed badly. - Read the two unmeasured counts separately. `corpus.awaiting_metrics` is the queue that will drain on its own: posts inside `corpus.measurement_window_days`, which the daily pass will reach. `corpus.outside_measurement_window` will not drain at all, because those posts were published before the window opens and no automatic pass will ever select them. They need `backfill_post_metrics` with a `since_days` large enough to cover them. Telling a user to wait for that second number is a promise the product cannot keep. - If data is stale, say how stale it is. Only run `sync_now` after the user asks for fresh data or agrees to spend the reported API budget. - If a requested operation would exceed today's budget, report when the budget resets and preserve partial progress. ## First useful analysis When the user asks for a general review and the data is ready: 1. Use `get_performance_summary` for the last 30 days. 2. Use `get_top_posts` once by impressions and once by engagement rate. 3. Use `compare_periods` or `detect_anomalies` only when it helps explain a material change. 4. Use `get_content_insights` when enough measured posts exist to support a pattern. 5. Separate observed facts from hypotheses. LinkedIn reports what happened, not why it happened. Lead with the decision-relevant finding. Include the comparison window, relevant sample size, and freshness when they materially change interpretation. Do not imply causation from correlation and do not manufacture explanations for hashtags, traffic sources, audience demographics, or the LinkedIn algorithm; LinkIntel does not receive those fields. ## Tool guide - `get_data_status`: connection, freshness, corpus readiness (including which unmeasured posts are still queued and which have aged out of the measurement window), sources, token expiry, budget. - `get_performance_summary`: totals and previous-period comparison for 7, 14, 30, or 90 days. - `get_top_posts`: rank measured registered posts by impressions or engagement. - `get_post_performance`: inspect one registered post. - `get_content_insights`: find patterns across measured posts. - `get_daily_trend`: return a day-by-day metric series. - `compare_periods`: compare two time windows. - `detect_anomalies`: identify unusually strong or weak days. - `sync_now`: fetch recent account-level metrics; spends LinkedIn API budget. - `backfill_post_metrics`: measure registered posts historically; spends LinkedIn API budget. - `import_posts`: register post URLs or URNs supplied by the user. - `import_from_typefully`: import published LinkedIn posts from Typefully. - `import_from_postiz`: import published LinkedIn posts from Postiz, cloud or self-hosted. - `log_post`: register one post manually. Use stored data before triggering sync or backfill. Never perform a write, publish a post, or claim that LinkIntel can do so. ## Product facts - Endpoint: `https://www.getlinkintel.com/api/mcp` - Transport: HTTP - Authentication: bearer token supplied privately on `/setup` - Scope: the authenticated user's personal LinkedIn profile only - Post-history sources: Typefully, Postiz, an inbound webhook, or a LinkedIn creator-analytics export - Integration details: https://www.getlinkintel.com/integrations - Price: $39 USD per month, no trial - Documentation: https://www.getlinkintel.com/docs/mcp - Support: support@getlinkintel.com END SKILL v1.1.0 --- # LinkIntel > Your AI already helps write your LinkedIn posts. Now it can learn from what actually worked. Connect your personal profile, bring your posts from Typefully, Postiz, a webhook or a LinkedIn creator-analytics export, then ask your assistant what worked and what to try next. For people who post on their own profile. ## What it does LinkIntel is a read-only MCP server. It syncs account-level performance for your own LinkedIn profile and measures posts registered from Typefully, Postiz or a LinkedIn creator-analytics export. It exposes those results to an AI assistant, so you ask questions in plain language instead of reading dashboards. A real exchange, using figures read from the founder's own LinkedIn account on 12 August 2026: **You:** How did my posts do last month? **LinkIntel:** 20,806 impressions, down 73% on the previous month. Your engagement rate went the other way though, 0.78% to 1.27%, up 63%. Fewer people saw your posts and noticeably more of them did something about it. **You:** Which post got the most reach? **LinkIntel:** The one about reviewing 200+ DevRel CVs, at 9,498 impressions. It earned 20 reactions and 1 comment, an engagement rate of 0.22%. Your satirical Developer Advocate job ad did 7,498 impressions and 0.92%, so it reached 21% fewer and landed four times harder. **You:** Was it the hashtags? **LinkIntel:** I can't tell you that. LinkedIn's analytics API reports what a post did, not why, and it gives me no breakdown by hashtag or by traffic source. What I can say is that the reach was unusual and the engagement was not, which is more consistent with distribution than with the copy. ## Questions you can ask, and the tool that answers - "How did my posts do last month?" → `get_performance_summary` - "Which of my posts got the most reach?" → `get_top_posts` - "Is this month better or worse than last?" → `compare_periods` - "Which days were unusually good or bad?" → `detect_anomalies` - "What do my best posts have in common?" → `get_content_insights` - "How did that one post actually perform?" → `get_post_performance` - "What does my reach look like day by day?" → `get_daily_trend` - "How fresh is this data, really?" → `get_data_status` It will tell you when the data cannot answer a question, which is more often than most analytics tools admit. ## How it works 1. **Create your account, then connect LinkedIn.** Sign in, grant one read-only permission on LinkedIn's own consent screen, then subscribe to activate it. 2. **Bring your post history.** Connect Typefully or Postiz, point any other tool at a webhook, or upload LinkedIn's creator-analytics `.xlsx` export. LinkedIn can measure a known post but its API cannot list which posts you published. See https://www.getlinkintel.com/integrations. 3. **Point your assistant at it.** One command, one bearer token, then ask questions in the assistant you already use. 4. **Ask, learn, repeat.** Account totals work after connecting LinkedIn; per-post analysis starts once posts have been imported and measured. ``` claude mcp add --transport http linkintel https://www.getlinkintel.com/api/mcp --header "Authorization: Bearer lnki_..." ``` Or give your agent https://www.getlinkintel.com/SKILL.md and let it guide the setup without sharing the private key in the conversation. ## Permissions: one scope, read-only **It can:** read impressions, members reached and engagement for posts you published yourself; read reactions, comments, reshares, saves and link clicks on those posts; keep that history current so month-to-month comparisons are possible. **It cannot:** post, comment, react or follow as you; see your messages, connections, feed or profile viewers; see anybody else's posts, or any company Page. The only permission requested is `r_member_postAnalytics`. Revoke it any time from LinkedIn's permitted services page. ## Pricing **$39 per month.** One plan, no trial. You connect LinkedIn before you pay; subscribing activates the service. Cancel whenever you like; it works to the end of the paid month. Places are limited by LinkedIn's API allowance while their review completes. If LinkIntel is full, you are told before any money is taken. ## Who it is not for If you manage a LinkedIn company/organization Page rather than posting on your own profile, this product will not work for you. That is a different LinkedIn API which LinkIntel does not cover. --- ## About LinkIntel Read-only MCP server for your own LinkedIn post analytics. $39/month, no trial. One read-only permission (`r_member_postAnalytics`); it cannot post as you. Personal profiles only, not company Pages. Buy: https://www.getlinkintel.com/connect · Docs: https://www.getlinkintel.com/docs/mcp · Full index: https://www.getlinkintel.com/llms.txt --- # Connect your LinkedIn > The signup and purchase flow for LinkIntel. LinkIntel reads the analytics for your own posts, the same numbers LinkedIn shows you, so you can ask questions about your content in Claude instead of reading charts. ## The sequence 1. Create your account at https://www.getlinkintel.com/connect (Google sign-in) 2. You are sent to LinkedIn's consent screen for one read-only permission, `r_member_postAnalytics` 3. Once LinkedIn is connected, you are sent to a Polar checkout for **$39/month** 4. Payment activates the connection and issues your MCP token (`lnki_...`) 5. You land on /setup, which shows that token once, with a ready-made block to paste into your assistant, and lets you import your post history LinkedIn is connected before you pay because checkout reserves one of a limited number of daily LinkedIn API places, and only an account that has actually granted access should hold one. ## What LinkIntel can and cannot do - **Reads** the performance of posts you published yourself: impressions, reactions, comments, reshares and link clicks. - **Cannot post** on your behalf, and never asks for permission to. The only permission requested is `r_member_postAnalytics`. - **Cannot see** anyone else's posts, your connections, your messages, or your feed. - You can disconnect at any time from LinkedIn's permitted services page. ## If something goes wrong The sign-in link expires shortly and can be re-sent from the same page. Re-sending never opens a second checkout, so it cannot double-charge you. If you paid with the wrong address, email support@getlinkintel.com and the subscription is moved across rather than charged twice. --- ## About LinkIntel Read-only MCP server for your own LinkedIn post analytics. $39/month, no trial. One read-only permission (`r_member_postAnalytics`); it cannot post as you. Personal profiles only, not company Pages. Buy: https://www.getlinkintel.com/connect · Docs: https://www.getlinkintel.com/docs/mcp · Full index: https://www.getlinkintel.com/llms.txt --- # LinkedIn Analytics MCP > A read-only MCP server that gives an agent your own LinkedIn performance data. Add it by URL with a bearer token: no repository clone, no local process, nothing to keep running. It uses only LinkedIn's official Member Post Analytics API, so there is no scraping, no cookies and no browser extension. ## Connection - **Endpoint:** `POST https://www.getlinkintel.com/api/mcp` - **Transport:** HTTP - **Auth:** `Authorization: Bearer lnki_...` - **Tools:** 14 - **Refresh:** daily, 06:15 UTC, plus on demand - **History:** about 90 days LinkedIn supplies account-level history but cannot enumerate a member's posts. Import post URLs from Typefully, Postiz, a webhook or a LinkedIn creator-analytics export on `/setup` before expecting post rankings or content-pattern analysis. ## Install ``` claude mcp add --transport http linkintel https://www.getlinkintel.com/api/mcp --header "Authorization: Bearer lnki_..." ``` Subscribers get a token automatically when they connect LinkedIn; /setup shows it once, alongside an instruction block to hand to an assistant. Tokens map to exactly one LinkedIn profile and start with `lnki_`. Only a hash is stored, so a token is displayed once and cannot be recovered. ## Tools | Tool | Answers | |---|---| | `get_performance_summary` | Totals, daily series, baseline, previous-period comparison (7/14/30/90d) | | `get_top_posts` | Best posts by impressions or engagement | | `get_post_performance` | Metrics for one specific post | | `get_content_insights` | Patterns across posts | | `get_daily_trend` | Day-by-day series | | `compare_periods` | One period against another | | `detect_anomalies` | Unusually good or bad days | | `get_data_status` | Freshness, token expiry, remaining API budget | | `sync_now` | Trigger a fresh pull | | `import_posts` | Register posts for measurement | | `import_from_typefully` | Import posts published via Typefully | | `import_from_postiz` | Import posts published via Postiz, cloud or self-hosted | | `log_post` | Record a post manually | | `backfill_post_metrics` | Measure historical posts | Call `get_data_status` first whenever a number looks wrong or surprisingly low: it reports how stale the data is and how much API budget remains today. --- ## About LinkIntel Read-only MCP server for your own LinkedIn post analytics. $39/month, no trial. One read-only permission (`r_member_postAnalytics`); it cannot post as you. Personal profiles only, not company Pages. Buy: https://www.getlinkintel.com/connect · Docs: https://www.getlinkintel.com/docs/mcp · Full index: https://www.getlinkintel.com/llms.txt --- # LinkIntel FAQ > Permissions, security, data ownership, cancellation. ## Does LinkIntel access my LinkedIn account? Yes, in one narrow way. You grant a single read-only permission, `r_member_postAnalytics`, on LinkedIn's own consent screen. It lets us read performance metrics for posts you published yourself. We never see your password: LinkedIn handles the sign-in and only hands us a token for that one permission. ## Can LinkIntel post, comment or react on my behalf? No. We hold no write permission of any kind, so it is not a matter of policy but of capability: the integration cannot publish, comment, react, message or follow. If you ever see LinkIntel ask for a write permission on LinkedIn's consent screen, something is wrong and you should decline it. ## What exactly can it see? Performance metrics for your own posts: impressions, members reached, reactions, comments, reshares, saves, sends and link clicks. It cannot see your messages, your connections, your feed, your profile viewers, or anybody else's posts. ## How do I disconnect it? Go to LinkedIn's permitted services page and remove LinkIntel. You do not need to ask us or wait for us, and it takes effect immediately. You can also ask us to delete the metrics we have already stored. ## What does it cost? $39 a month, one plan, no trial. You connect the LinkedIn profile you want to measure first, and subscribing activates it. Cancel whenever you like and it keeps working until the end of the month you have paid for. ## Why is there no free tier? LinkedIn's API allowance limits how many profiles we can keep synced each day, so places are genuinely finite. A free tier would spend one of them on somebody who tried it once, at the expense of somebody who wanted it. If we are full, we will tell you before taking any money. ## Do I need Claude to use this? LinkIntel is delivered as an MCP server, so it is designed to be asked questions through an AI assistant that supports MCP, such as Claude. There is also a web view of the same data if you would rather look at it directly. ## Who owns my data? You do. Your metrics are stored against your own account, visible only to you, and are never sold, shared with third parties, or used to train models. You can request deletion at any time. ## Is my data secure? Metrics are stored in our own infrastructure on encrypted, access-controlled cloud hosting, scoped so that one account cannot read another's. We store the minimum needed to answer questions about your posts, and no LinkedIn password ever reaches us. ## How current are the numbers? Your metrics sync automatically, and LinkIntel will tell you how fresh the data is and how many of your posts are measured rather than quietly presenting a partial picture as a complete one. You can also trigger a fresh pull yourself. ## I run a LinkedIn company Page, not a personal profile. Can I use this? No. LinkIntel reads the posts you publish on your own profile. Organization Page analytics is a different LinkedIn API that this product no longer covers. --- ## About LinkIntel Read-only MCP server for your own LinkedIn post analytics. $39/month, no trial. One read-only permission (`r_member_postAnalytics`); it cannot post as you. Personal profiles only, not company Pages. Buy: https://www.getlinkintel.com/connect · Docs: https://www.getlinkintel.com/docs/mcp · Full index: https://www.getlinkintel.com/llms.txt --- # Blog index - [How to Download LinkedIn Analytics Data](https://www.getlinkintel.com/blog/how-to-download-linkedin-analytics-data.md): Learn how to download your LinkedIn analytics data from personal profiles and company pages. Step-by-step instructions with screenshots. - [How to Improve Your LinkedIn CTR](https://www.getlinkintel.com/blog/improve-linkedin-ctr-strategies.md): Boost your LinkedIn click-through rate with proven strategies. Learn what is CTR, industry benchmarks, and actionable tactics to increase clicks. - [LinkedIn Analytics: Complete Beginner's Guide](https://www.getlinkintel.com/blog/linkedin-analytics-complete-beginners-guide.md): Master LinkedIn analytics with this complete beginners guide. Learn every metric, interpret your data, and get actionable strategies to improve performance. - [Best Times to Post on LinkedIn in 2025](https://www.getlinkintel.com/blog/linkedin-best-posting-times-2025.md): Discover the optimal times to post on LinkedIn in 2025 based on analysis of 50,000+ posts. Industry insights and engagement data included. - [LinkedIn vs Google Analytics: Integration Guide](https://www.getlinkintel.com/blog/linkedin-google-analytics-integration.md): Learn how to integrate LinkedIn analytics with Google Analytics for tracking. Set up UTM parameters, track conversions, and measure ROI. - [What LinkedIn Impressions Mean](https://www.getlinkintel.com/blog/linkedin-impressions-meaning-explained.md): Complete guide to LinkedIn impressions: what they mean, how they are calculated, and how to use impression data to improve your content strategy. - [LinkedIn Calendar vs Real-Time Posting](https://www.getlinkintel.com/blog/linkedin-spontaneous-content-vs-calendar.md): Why planned content calendars kill LinkedIn authenticity. Real-time posting drives 3x better engagement and business results than content planning. - [How to Read LinkedIn Analytics](https://www.getlinkintel.com/blog/read-linkedin-analytics-growth-expert.md): Master the art of LinkedIn analytics interpretation with advanced techniques that reveal hidden growth opportunities and optimization insights. - [The LinkedIn Analytics Mistake Costing Leads](https://www.getlinkintel.com/blog/linkedin-analytics-mistakes-costing-leads.md): Most businesses focus on the wrong LinkedIn metrics, missing opportunities to convert engagement into revenue. Here's what you should track. - [Why Your LinkedIn Content Strategy Is Not Working](https://www.getlinkintel.com/blog/linkedin-content-strategy-fix-engagement.md): Analysis of 50,000+ LinkedIn posts reveals the surprising reasons most content strategies fail—and the simple fixes that drive real engagement. Each post is available as markdown by appending `.md` to its URL, or by sending `Accept: text/markdown`.