Publishing to your website

Summary#

Publish Integrations is the screen where finished content is meant to leave Metric Vault and land in the system your site actually runs on. It lists six destinations and shows which of them have been set up. Today the push itself is switched off for everyone: the screen reports status honestly and every attempt to push returns a message saying publishing is not enabled yet. Nothing is sent, and nothing can accidentally go live.

Purpose#

Moving a finished article into a content management system by hand is where a good afternoon becomes a public mistake. Formatting breaks, links break, and the button that saves your draft sits next to the button that publishes it to the world.

The design answer here has two halves. The first is that a push always creates a draft, never a live page. You review it in your own editor and press publish yourself. The second is that the feature is fail-closed: if the connection is not completely set up, it does nothing rather than doing something half-configured. That second half is why the screen currently reports itself as pending rather than pushing content.

The deliberate reason it is not enabled is credential safety. Publishing to a self-hosted site means holding a key to that site. Storing customer content management credentials is not something to do casually, so it waits until it can be done properly.

Requirements#

• A signed-in Metric Vault account.
• Nothing else. The screen loads and reports status for everyone.

There is currently nothing you can do on this screen that changes your site.

Permissions#

Any signed-in user can open Publish Integrations and read the status. There is no plan gate, no team role requirement, and no credit cost. Completing the setup for a platform is an administrator task, not a customer one.

Navigation Path#

Dashboard → Write & Optimize → Publish Integrations

The nav item carries a BETA badge.

Step-by-Step Guide#

1. Go to Dashboard → Write & Optimize → Publish Integrations.
2. The screen loads with Checking publishing connections… and then shows a card headed Publishing connections, with the platform count and the words drafts only.
3. Read the badge at the top right of that card. Setup pending means pushing is off. Enabled would mean it is on.
4. Below, the Platforms section lists each destination with its own badge and a one-line note.
5. Clicking Connect on any platform shows a message rather than starting a connection. That message is the current, accurate state of the feature.

The six destinations#

The split matters. WordPress, Medium and Ghost would use a credential you generate yourself and can revoke yourself, which is why the note names the exact kind of key rather than asking for your password. LinkedIn, Webflow and Shopify would use an approval flow on the platform, where you grant access without Metric Vault ever seeing a password.

Reading the badges#

The card badge at the top is separate:

What happens when you click Connect#

The request goes out and comes back with:

Publishing is not enabled yet. Once your admin finishes connecting a platform, drafts are pushed as unpublished (never live).

If the response cannot be read at all, you see This platform is not enabled yet. instead. Either way nothing was sent to any platform and nothing changed on your site.

What you can do instead today#

Finished content does not have to stay stuck. Every content tool gives you the article in a form you can move by hand:

• Export the piece from My Content and paste it into your editor. See My Content.
• If you publish through Metric Vault's own blog system rather than an external site, that path is live and unaffected by any of this. See Blog Studio.
• Plan the publishing dates in the editorial calendar so the schedule survives the manual step. See Editorial Workflow & Calendar.

Limitations#

• No push happens. Not to a draft, not to a live page, not to any of the six platforms.
• There is no per-user connection to make. You cannot supply your own WordPress application password on this screen today.
• Nothing is stored. No site addresses, no keys, no tokens. There is nothing to clean up later.
• The screen does not tell you which piece of content would be pushed. It is a connections screen, not a content picker.

Troubleshooting#

FAQs#

Could this accidentally publish something live? No. Two things prevent it. Pushing is off entirely, and the design fixes every push to draft status even when it is on. Making a draft public would always be an action you take in your own editor.

Does it cost credits? No.

Will my WordPress password be stored? No, and it would not be asked for. The design uses an application password, which is a separate, limited key you create in WordPress and can revoke there without changing your login.

Is LinkedIn here the same as the LinkedIn social channel? They are different features. The social channel publishes short posts from the composer and works today. The entry on this screen is about publishing long-form articles and is part of the same pending feature as the rest. See Publishing and scheduling posts.

How will I know when it is switched on? The top badge changes from Setup pending to Enabled, and the platform cards stop returning the not-enabled message. See Release notes.