Integrations Overview
ReachLLM integrations are grouped by what they let the platform do for a brand.
Search data
Section titled “Search data”Search data integrations help ReachLLM connect AI visibility work to real search behavior:
- Google Search Console
- Google Analytics 4
- Bing Webmaster Tools
- LLM Analytics
Search integrations feed Traffic, GEO Audit context, and agent analysis. LLM Analytics appears in Traffic with its own per-brand server-request connection and live status.
Content & CMS
Section titled “Content & CMS”Content & CMS integrations are the first-class publishing paths. They connect to the cmsConnection adapter system, so the app and agent can use one shared contract for status, capabilities, content retrieval, media upload, article drafts, page updates, metadata, schema, llms.txt, and robots.txt.
Active publishing paths:
- WordPress: publish article drafts, upload media into the Media Library, update pages and metadata, push schema, llms.txt, and robots.txt.
- GitHub: inspect a connected repository, read files, commit image assets, and open pull requests or direct commits for content and technical fixes.
- Webflow: list and read static pages, upload image assets, publish CMS items, update CMS item content, update metadata, and publish article drafts to CMS collections.
- Shopify: list and read Online Store pages and blog articles, upload theme image assets, publish article drafts, update page/article content, update metadata, and create llms.txt pages.
Website Generator source extraction
Section titled “Website Generator source extraction”When a Content & CMS integration is connected, Website Generator and page-source tools check the connected CMS first, then fall back to sitemap discovery. This lets ReachLLM extract the current source page before generating, redesigning, or fixing content.
Supported CMS source reads include:
- WordPress pages and posts.
- GitHub source files from the connected repository.
- Webflow static pages and CMS items.
- Shopify Online Store pages, blog articles, and theme assets when theme permissions are available.
The page source response marks whether the source came from the CMS or from the generated-site fallback, so the agent can choose the correct update path.
Workspace apps
Section titled “Workspace apps”Workspace apps give the agent context or action access outside the publishing adapter system. Examples include Google Docs, Google Drive, Google Sheets, Notion, Figma, Gmail, Outlook, Slack, Reddit, LinkedIn, calendars, and meeting tools.
LinkedIn supports Strategy feed posts through the connected LinkedIn account. In Account > Integrations, choose the posting account before publishing: a personal profile or a company page. If the company page is not discovered automatically, paste the LinkedIn company page URL or the numeric ID from the URL, for example 11756149 from /company/11756149/. Company pages require the connected LinkedIn member to have page posting access. LinkedIn Pulse style article work is draft and link-share only for now: ReachLLM can draft the long-form article and share an existing article URL, but the current LinkedIn connection does not expose native long-form article publishing.
External AI clients
Section titled “External AI clients”MCP Connector connects external AI clients such as Claude, Claude Code, Cursor, Codex, Windsurf, and Cline to ReachLLM through a remote MCP server. Generate an MCP access token in Account > MCP, choose account or brand scope, then add the ReachLLM server URL to your client.
Choosing the right path
Section titled “Choosing the right path”Use Content & CMS when the goal is to publish or edit the website. Use workspace apps when the agent needs context, outreach, collaboration, or file access. Use MCP when you want an external AI client to work with ReachLLM context and actions.