Integrations
BOOSTD integrations, with the honest status of each one
Every tool BOOSTD is designed to connect to, grouped by what it is for, with a plain status beside each: available at launch, in development, or planned. None is live yet.
Prefer to talk it through? Book a strategy call
Before the list
None of these is connected yet
BOOSTD is in early access. No customer can connect an account yet, so every integration below is described by what it will do and how far it has got, not by what it does today. Statuses were last checked against our implementation checklist on 18 September 2026.
Of the 41 integrations listed, 6 are in the first-release scope, 25 are in development and 10 are planned with no code yet. “Tested against simulated data” means the code has run against a stand-in for the real service and has not yet talked to the real one.
Company names are used to describe what BOOSTD connects to. No logos are shown, and none of these companies has endorsed or partnered with BOOSTD.
Search and analytics
Search and analytics connections
The evidence everything else is judged against. Search Console is the first thing BOOSTD asks to connect, because it is the only first-party record of how Google sees your site.
| Dimension | Status | What it is for | Where it stands |
|---|---|---|---|
| Google Search Console | Available at launch | The searches your pages appear for, clicks, impressions and indexing problems. | Connection code is written and tested against simulated data. It has not yet connected to a real property. |
| Google Analytics 4 | Available at launch | Visits, conversions and where they came from, so changes are judged on outcomes rather than rankings. | Tested against simulated data only. It has not yet connected to a real property. |
| PageSpeed Insights | Available at launch | Page speed and Core Web Vitals for the pages that carry your traffic and enquiries. | An adapter is written against Google’s published API. It has not yet made a live request. |
| Site crawler (built by BOOSTD) | Available at launch | Reads your pages the way a search engine does: status codes, titles, canonicals, links and structured data. | Built and tested, including a guard that stops it being pointed at private network addresses. Not yet run against customer sites. |
| Keyword and search-results data | Available at launch | Search demand and what currently ranks, so priorities rest on evidence rather than guesses. | The connection standard and a simulated provider exist. The data vendor has not been chosen. |
| Backlink data | In development | Who links to you and to your competitors, for authority and digital PR work. | The connection standard and a simulated provider exist. It will sit behind add-on budgets because the data is expensive. |
| Bing Webmaster Tools | Planned | Indexing and search performance on Bing. | Named in the integration plan. No code has been written for it yet. |
AI visibility
AI assistants and generated search answers
How assistants describe your business is measured by asking them, repeatedly, and recording what comes back. It is always reported as a sample with its method stated, never as a complete picture.
| Dimension | Status | What it is for | Where it stands |
|---|---|---|---|
| ChatGPT, Gemini, Perplexity, Microsoft Copilot and Claude | In development | Whether assistants mention you, how they describe you, and which sources they cite when they do. | Prompt sets, answer collection and citation extraction are built and tested against simulated answers. No assistant has been queried live. |
| Google AI Overviews and AI Mode | In development | Whether Google’s generated answers above the results mention or cite your pages. | Collected through a search-data provider that has not been chosen yet. Tested against simulated results only. |
Local and reputation
Listings, maps and reviews
Several local platforms are partly manual by design, with postcard or phone verification. Where there is no API, BOOSTD gives you a short guided task instead of pretending to do it for you.
| Dimension | Status | What it is for | Where it stands |
|---|---|---|---|
| Google Business Profile | In development | Your listing’s details, categories and hours, and how you rank on the map across your service area. | Listing checks, consistency checks and local ranking grids are built against a simulated provider. Google API access is not set up yet. |
| Bing Places | In development | Your business listing on Bing and the surfaces that draw on it. | Built against a simulated provider. Steps Bing keeps manual will appear as guided tasks. |
| Apple Business Connect | In development | Your listing in Apple Maps, where Apple’s API allows it. | Built against a simulated provider. Partly manual by design on Apple’s side. |
| Review platforms: Google, Facebook, Trustpilot | In development | New reviews and sentiment, with replies drafted for your approval. BOOSTD never writes, buys or filters reviews. | Review sync, reply drafting and policy checks are built against a simulated provider. No review platform is connected. |
Your website
Website platforms and content management systems
Every write goes through one pipeline: take a snapshot, prepare a draft, publish, check the live page, and roll back if the check fails. The pipeline exists; the platform connections mostly do not yet.
| Dimension | Status | What it is for | Where it stands |
|---|---|---|---|
| WordPress | In development | Metadata, structured data, internal links and drafts written as CMS revisions, so every change has a version to return to. | The shared snapshot, verify and rollback pipeline runs against a simulated CMS. The WordPress connection itself is not written yet. |
| Shopify | In development | Product and collection page metadata and structured data. Checkout and account pages are protected by default. | Same pipeline, simulated. The Shopify connection itself is not written yet. |
| Webflow | In development | Page metadata, content drafts and internal links through Webflow’s own publishing flow. | Same pipeline, simulated. The Webflow connection itself is not written yet. |
| Wix, Squarespace and WooCommerce | Planned | The same work on the next most common platforms, within what each platform’s API allows. | Named in the integration plan. No code has been written for it yet. |
| Custom and headless sites | Planned | Sites with their own content API, connected through a documented interface. | Named in the integration plan. No code has been written for it yet. |
| BigCommerce and Adobe Commerce (Magento) | Planned | Ecommerce catalogues on these platforms. | Named in the plan, to be added based on demand. No code yet. |
CRM, email and SMS
CRM, email and text messaging
These close the loop from a ranking to an enquiry to revenue. They are also where consent law bites hardest, so consent and quiet hours are checked before anything is sent, not after.
| Dimension | Status | What it is for | Where it stands |
|---|---|---|---|
| HubSpot | In development | Leads and deals from your site, so reporting can follow an enquiry through to revenue. | The CRM connection standard and a simulated provider exist. The CRM module that would use them has not been started. |
| Salesforce | In development | The same lead and pipeline reporting for teams that run on Salesforce. | Covered by the same connection standard and simulated provider. No Salesforce connection yet. |
| Pipedrive | In development | Deals and activities for smaller sales teams. | Covered by the same connection standard and simulated provider. No Pipedrive connection yet. |
| GoHighLevel, Zoho CRM and Microsoft Dynamics | Planned | The same reporting on other common CRMs. | Named in the integration plan. No code has been written for it yet. |
| Marketing email (Mailchimp and others) | In development | Sequences sent only to people who agreed to receive them, with suppression lists respected. | The email connection standard and a simulated provider exist. Email sequences themselves are not built. |
| SMS (Twilio or equivalent) | In development | Text messages, with recorded consent and local quiet hours enforced before a send. | The SMS connection standard and a simulated provider exist. Nothing sends. |
| WhatsApp Business | Planned | Customer messaging where WhatsApp is the normal channel. | Named in the integration plan. No code has been written for it yet. |
| Calendly and call tracking such as CallRail | Planned | Bookings and phone calls counted as conversions, not only form fills. | Named in the integration plan. No code has been written for it yet. |
Advertising
Advertising platforms
Spend is the one place a mistake costs money the same day. BOOSTD does not move or raise a budget without a person approving it, and no plan can exceed the limit you set.
| Dimension | Status | What it is for | Where it stands |
|---|---|---|---|
| Google Ads | In development | Spend, conversions and search terms, with changes proposed for approval. | The ads connection standard, a simulated provider and a daily spend-cap rule exist. The paid media module has not been started. |
| Microsoft Ads | In development | The same reporting and proposals for Bing and Microsoft placements. | Covered by the same connection standard and simulated provider. No live connection. |
| Meta Ads | In development | Facebook and Instagram campaign spend and results. | Covered by the same connection standard and simulated provider. No live connection. |
| LinkedIn Ads and TikTok Ads | In development | Campaign spend and results on these platforms. | Covered by the same connection standard and simulated provider. No live connection. |
Creative
Image and video generation
Creative generation is expensive and easy to overuse, so every job is quoted before it runs, capped by your plan, and shown as a preview before anything is final.
| Dimension | Status | What it is for | Where it stands |
|---|---|---|---|
| Image generation | In development | Images for posts, pages and ads, generated within your brand rules and your plan’s limits. | The first provider connection is written behind a vendor-neutral standard, with hard spending caps. It has never generated an asset. |
| Video generation | In development | Short video for social and ads, with the same quote, cap and preview steps as images. | Same provider standard and caps. Nothing is generated until the plan limits have been set, so it fails closed today. |
Payments and automation
Payments and automation tools
Stripe is how you would pay BOOSTD. Card details are entered on Stripe’s own pages and are never stored by BOOSTD. Automation tools come later, once there is a public API to connect them to.
| Dimension | Status | What it is for | Where it stands |
|---|---|---|---|
| Stripe | Available at launch | Plans, invoices, receipts and the billing portal for your BOOSTD subscription. | An adapter is written against Stripe’s published API, including webhook signature checks. It has never made a live call. |
| Zapier | Planned | Sending BOOSTD events, such as an approved change or a new lead, into the tools you already use. | Named in the integration plan. No code has been written for it yet. |
| Make and n8n | Planned | The same events for teams that run their automation on these tools. | Named in the integration plan. No code has been written for it yet. |
How every connection behaves
The rules every integration follows
These apply to every connection on this page, whichever company is on the other end, and they are part of how each connection is built rather than a setting.
Every connection
- Asks for the narrowest permission the feature needs, when you first use it
- Stores its access token encrypted, and never in a log or your browser
- Shows its status and last successful sync, including when it has broken
- Revokes access at the provider when you disconnect it
No connection
- Requests admin access to run a report
- Publishes, spends or replies without passing the approval rules
- Shares one business’s data with another
- Reports a write as done before it has been checked
Questions
Questions about connecting your tools
Can I connect my accounts today?
No. BOOSTD is in early access and no customer account can connect anything yet. Integrations marked available at launch are the ones the first release is being built around.
Until then, the free audit is run by a person using public information about your site, so it needs no connection at all.
My platform is not listed. Will it be supported?
Possibly. Integrations are added based on how many businesses use a platform and whether its API allows the work to be done safely, with a way to check and undo each change.
Tell us which platform you use through the contact page. It is a genuine input to the order things are built in.
Why are there no logos on this page?
Because we do not have permission to use them. Showing a company’s logo on an integrations page implies a relationship, and none of these companies has endorsed or partnered with BOOSTD. The names are used only to say what BOOSTD is being built to connect to.
What permissions will BOOSTD ask for?
The narrowest permission each feature needs, requested at the moment you first use that feature. If you decline a permission, only the features that depend on it are switched off.
Each connection will show what it was granted, whether it is healthy and when it last synced, and disconnecting revokes access at the provider.
Start with a review that needs no connection
The free audit is run by a person using what is publicly visible about your site. It needs no access to your accounts, and it tells you what to fix first.
Last updated · Not yet approved for publication
Social and video
Social platforms and YouTube
Drafting and scheduling are separate from publishing, and publishing waits for approval. Each platform also has its own review of the app before it grants the permissions publishing needs.