Skip to content
Login Contact

Marfeel Copilot CMS integration step by step

Marfeel Copilot integrates directly with the editor you already use, whether that is Google Docs, Microsoft Word, an in-house CMS, a commercial platform, or Marfeel Writer. The Chrome extension detects your content automatically and delivers AI-powered assistance right where you write.

Marfeel Copilot is natively integrated with major systems and works out of the box.

  1. Install the Marfeel Chrome extension.
  2. Browse to your CMS.
  3. Marfeel Copilot will autodetect your content and execute prompts contextually.
  4. The append and replace actions work immediately without additional configuration.

How Marfeel Copilot integrates with your CMS

Section titled “How Marfeel Copilot integrates with your CMS”

When you browse to a webpage, the Marfeel Chrome Extension analyzes it to identify text and input blocks following this detection chain:

  1. Commercial text editor fields:
    1. Google Docs
    2. Microsoft Word
    3. CKEditor 5
    4. TinyMCE
    5. ProseMirror
    6. WordPress Gutenberg
    7. PlateJs
    8. Lexical
    9. Discourse
  2. Generic text input elements:
    1. contentEditable elements
    2. TextArea
  3. Identify text blocks via a Reader view.
Let us know if your CMS isn't working properly by using the diagnose tool described below.

Diagnose the integration of Marfeel Copilot with your CMS

Section titled “Diagnose the integration of Marfeel Copilot with your CMS”

The Marfeel Copilot extension provides a built-in Diagnose tool that validates each integration point with your CMS. To run diagnostics:

  1. Open the Chrome Extension
  2. Go to Settings
  3. Open the Diagnose tab
  4. Execute the different checks that will validate everything is working as expected detecting selections and manipulating texts.

Marfeel Copilot CMS diagnose panel showing integration checks and validation results

If you encounter an error, send the Diagnose report, and our support or product team will reach out to assist you. We'll just need access to a test user in your CMS, and we'll take care of the rest.

While widely used CMS platforms are natively integrated, different versions or custom setups may affect feature availability.

Admin users can configure several aspects of the automatic CMS integration from Organization > Copilot.

Some CMS platforms have a separate field for the title, distinct from the main article body. You can provide a CSS selector that identifies the title field so title replacement actions work properly.

If the Marfeel Copilot extension is not correctly identifying the article body field, you can provide a CSS selector that overrides automatic detection. The extension will use it with precedence.

We discourage using this property unless instructed by your Account Manager or Product Team

You can restrict Copilot to detect text inputs only on the domain where your CMS is hosted.

When Marfeel Copilot identifies the main body as a TextArea, it uses the MIME type field to define the format expected by your CMS — markdown, HTML, or plain text.

Marfeel Copilot infers the language of its responses based on what the user is doing:

  1. In edit mode, when a text editor or CMS is detected, Copilot detects the language based on the content.
  2. In read mode, when analyzing articles, it uses the account language as defined in the account settings.

Which CMS editors does Marfeel Copilot support?

Marfeel Copilot supports Google Docs, Microsoft Word, CKEditor 5, TinyMCE, ProseMirror, WordPress Gutenberg, PlateJs, Lexical, Discourse, as well as generic contentEditable elements and TextArea fields.

How do I diagnose Marfeel Copilot CMS integration issues?

Open the Chrome Extension, go to Settings, open the Diagnose tab, and run the checks. If errors appear, send the Diagnose report and the support or product team will assist you.

How does Marfeel Copilot detect the language of content?

In edit mode, when a text editor or CMS is detected, Copilot detects the language based on the content. In read mode, when analyzing articles, it uses the account language defined in the account settings.