Connect Meeeters to your stack

No. Application passwords are built into WordPress since version 5.6, and Meeeters uses the standard WordPress REST API. Nothing to install, nothing to update.

No. Every article arrives with the draft status. You open it in wp-admin, edit if you want, and press publish yourself.

It only grants the API access of the user who created it, and you can revoke it anytime from the same screen. Meeeters stores it server-side only, encrypted at rest on our locked credentials table, and never shows it again.

Three usual causes: the site URL must be the root (https://yoursite.com, no /wp-admin), the username is your WordPress login (not the email in some setups), and some security plugins block the REST API, add an exception for /wp-json.

No. Meeeters only calls the WordPress REST API to create draft posts. It never sees your theme, your plugins, your files or your code, and it has no way to reach a custom dashboard or the logged-in area of your product. For extra safety, create the application password on an Editor account rather than an Administrator one.

It is a normal WordPress draft: you fix it in wp-admin like any other post. Nothing Meeeters sends is locked or managed remotely. Once a draft lands on your site, it is entirely yours.

Yes. Paste a Webflow site API token in Meeeters Settings and we auto-detect your blog collection and its fields. Drafts are created directly in your CMS, never published without you.

We pick the collection whose name looks like a blog (blog, posts, articles, news), or the first collection with a rich text field. The connection screen confirms which one was selected. If you have no CMS collection with a rich text field yet, create one first.

CMS read + write, and Sites read. You generate the token in Webflow under Site settings, Apps and integrations, API access. It is stored server-side only and never shown again.

Yes, the signed webhook remains available as an advanced option. Point it at a Make/Zapier webhook trigger and map title, meta_description and markdown to a Create CMS item action. Most Webflow users no longer need this.

No. The scopes limit it to CMS items and basic site info. Meeeters creates draft items in one collection, and that is all it can do: it cannot edit your designs, your pages, your custom code or your site settings. You can revoke the token in Webflow at any time.

It is a normal CMS item in your Webflow collection: open it in the Editor or Designer and fix it like any other item. Nothing is locked, the content is yours the moment it lands in your CMS.

You invent it. Click Generate in the Meeeters connect card, then store the same value in your endpoint's environment variables. It is a shared secret: Meeeters signs every request with it, your endpoint verifies the signature.

Skip the webhook entirely. Use the WordPress connector: create an application password in your WP profile, paste it in Meeeters, done. Drafts land directly in your wp-admin.

No. Meeeters only sends drafts. Your endpoint decides what to do with them, and the recommended pattern is to store them as drafts for review.

The send fails and the member sees an error in the dashboard, nothing is lost: the draft stays in Meeeters and can be re-sent or copied manually.

No. A webhook is one-way delivery: Meeeters POSTs a JSON payload to your URL and that is all. It cannot read your database, your code, your dashboard or anything else on your site. The only code with any power is the endpoint you wrote yourself, and it does exactly what you programmed, nothing more.

Never. Meeeters only sees what everyone sees: your public site. A third-party tool cannot reach a private repository unless you explicitly install it there, and Meeeters does not ask for that. Publishing works through credentials you choose to share (a CMS token) or through this webhook, where your own code stays in full control.

The content lives on your site, so you edit it there like any other content, nothing is locked. You can also edit the draft in Meeeters and re-send it: if your endpoint matches incoming drafts by title or slug and replaces the existing entry, corrections apply cleanly.

Any site whose content lives as markdown files in a repository: Astro, Next.js with MDX, Hugo, Jekyll, Docusaurus, Eleventy, or a Lovable app synced to GitHub. If your host redeploys on push (Vercel, Netlify, Cloudflare Pages), articles go from Meeeters to production with zero glue code.

Only what you scoped: Contents read and write on the one repository you chose. It cannot touch other repos, settings, actions or members, and you can revoke it on GitHub at any time. It is stored server-side only, encrypted at rest, and never shown again.

No. Articles are committed with draft: true in the frontmatter, so your site hides them until you set draft: false. If you prefer straight-to-live, enable auto-publish in Meeeters and drafts are committed publishable.

Meeeters only adds or updates its own article files inside the content folder you configured. It never touches your code, your components or other content, so conflicts with your day-to-day work do not happen in practice.

Not a one-click one yet. The clean path is the signed webhook feeding a small automation that calls the Ghost Admin API to create the post with status draft. Copy markdown into the Ghost editor works everywhere with zero setup.

A Custom Integration in Ghost, under Settings, Advanced, Integrations. It gives you an Admin API key and URL. Your automation uses them to create posts. Meeeters always sends status draft, so nothing publishes on its own.

Yes. Send the article as HTML or Lexical to Ghost and headings, lists and links come through. If you copy markdown by hand, paste it into a markdown card in the editor.

Yes. Whether you use Super, Potion, Notion Sites or a headless setup, your posts live in a Notion database. Meeeters drafts can be created there automatically via the Notion API, or you paste markdown into a page.

You create a Notion internal integration, share your blog database with it, then have a Make or Zapier step call Create database item. Meeeters sends the signed webhook payload with title, meta_description, lang and markdown to map onto your properties.

Use a Published checkbox or Status property in your database and leave it off. Meeeters always sends drafts, so your automation should create items with Published unchecked. You flip it live yourself after review.

Not yet, it is on the roadmap. Today the paths that work are the signed webhook feeding a Flow/Make/Zapier automation that creates a hidden blog article, or copy markdown into the Shopify editor.

Hidden is Shopify's draft state for blog posts. Your automation should create articles as hidden so you review and set them visible yourself, consistent with how Meeeters works everywhere: drafts only.

For SEO, yes. Store blogs earn the informational rankings and the backlinks that product pages rarely attract, and internal links pass that authority to your collections.

Not yet. Framer has a CMS with a blog collection, and two paths work today: the signed webhook feeding a Make or Zapier automation that adds a collection entry, or copy markdown into a new draft entry by hand.

Your blog or articles CMS collection. Make sure it has fields for title, a rich text or markdown body, and a meta description, so the mapping is clean. Create the collection first if you do not have one.

Add a Published toggle or use Framer's draft state on the collection, and leave new entries unpublished. Meeeters only ever sends drafts, so you review and publish from the Framer CMS yourself.

Not yet. Today the reliable paths are copy markdown into a new Wix blog draft, or the signed webhook feeding a Make or Zapier automation that creates a draft post. Wix Blog also has APIs via Velo for advanced setups.

Yes. A store or business site earns informational rankings and backlinks through its blog that product and service pages rarely attract, and internal links pass that authority across your site.

Create the post in Wix without publishing, or have your automation set it to draft. Meeeters only ever sends drafts, so nothing goes live until you review and publish it in the Wix editor.

Not yet. Squarespace has no open write API for the blog, so the fastest reliable path is copy markdown into a new draft post. For automation, a signed webhook into Zapier can create the post where a connection is available.

Generate the draft, copy the markdown, then in a new blog post add a Markdown block and paste. Squarespace renders headings, lists and links. Save the post as a draft, never published automatically.

Set the SEO description in the post's Options, SEO tab. The Meeeters draft gives you a ready meta_description to paste, so the page ships with a proper search snippet.

Yes, through GitHub. Lovable syncs your app to a GitHub repository, and the Meeeters GitHub connector commits articles as markdown files into your content folder with draft: true. The signed webhook and copy markdown remain available as alternatives. You keep full control of the code.

No. Lovable writes it from a prompt. Ask it to add a blog route that renders markdown articles from a content folder or an API endpoint, and it scaffolds the pages, routing and styles for you.

Wherever your Lovable app reads content: a markdown file you paste, or a record your webhook automation creates. Nothing deploys automatically. You review in the Lovable preview and ship when you are happy.

The Model Context Protocol, an open standard that lets assistants like Claude call external tools. Meeeters exposes its link building knowledge base through an MCP-compatible endpoint, so Claude can query it directly during a conversation.

No, and that is deliberate. Publishing always goes through your review in the Meeeters dashboard and your CMS. Claude is for thinking and rewriting, not for pushing content live.

Any plan that supports custom connectors/MCP servers (Claude desktop and claude.ai support this). The polish workflow in step 3 works with every plan, including free.

Because a chat window starts from nothing. Meeeters starts from your audit: it knows which page your structure is missing, in which silo, for which intent, and drafts accordingly. ChatGPT is the polish pass, not the strategy.

No. Publishing always goes through your review and your CMS. The routine here is edit-only, which is exactly where assistants shine.

Yes. The routine is plain prompting, no plugins or actions required.

Perplexity answers with live sources and citations, so it is the fact and freshness pass: recent numbers, current prices, real references you can link. Meeeters decides which page to write and drafts it; Perplexity makes the facts trustworthy.

No. Publishing always goes through your review and your CMS. This routine is research and verification only, which is exactly where a cited answer engine is strongest.

Yes. The routine is plain prompting with sources. A paid plan mainly adds more Pro searches, not a different workflow.