> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/copywriter/wordpress-article-delivery-formats.md). # WordPress article delivery formats (Native blocks and page builders) Rankability delivers articles to WordPress in the format your site's editor actually uses — native Gutenberg blocks on block-editor sites, clean HTML on page-builder sites like Elementor and Divi. One setting controls it; detection is automatic. WordPress sites don't all use the same editor. Some use the native block editor (Gutenberg); many use a page builder like Elementor, Divi, Beaver Builder, Bricks, Oxygen, or WPBakery. Rankability detects which one your client's site runs and delivers published articles in the format that editor understands — so content arrives clean and editable, never as a wall of garbled markup. ## The Article delivery setting Each WordPress connection has one setting that controls this, found in the connection's publish settings in the client's Copywriter workspace: 1. Open the client and go to their WordPress connection settings (the same card where you set default status, category, and post type). 2. Find the **Article delivery** dropdown. 3. Choose one of two options: * **Classic HTML (default)** — Articles are delivered as clean, formatted HTML. This works on every WordPress site regardless of editor, builder, or plugin version. It is the safe baseline. * **Native blocks** — Articles are delivered in the richest format the site supports. Rankability picks the exact format automatically based on what it detects on the site (see below). Click **Save defaults** after changing the setting. It applies to all future publishes on that connection — including scheduled auto-publishes. ## What Native blocks does on each kind of site ### Block editor (Gutenberg) sites — real editable blocks If no page builder is detected, articles open in the WordPress block editor as individual native blocks: each heading, paragraph, list, image, and quote is its own separately editable block — exactly as if the article had been written inside WordPress. No more single “Classic” block containing the whole article. Tables, embeds, and other complex elements are preserved verbatim in HTML blocks so nothing gets reformatted or broken. ### Page-builder sites — clean HTML, automatically If the site runs a layout builder — Elementor, Elementor Pro, Divi, Beaver Builder, Bricks, Oxygen, or WPBakery — Rankability delivers clean, semantic HTML instead. Those builders manage the page layout in their own editors, and block-editor markup would show up as noise inside their widgets. Clean HTML drops into the builder's text/HTML content area and renders correctly. You don't choose this per site — detection is automatic. If a client later removes their page builder, the next publish adapts on its own. ## How site detection works The Rankability WordPress plugin reports the site's environment — which builders and major plugins are active — whenever it checks in. Each WordPress connection card shows an **Environment** section listing: * The detected page builders (for example “Elementor”), if any. * When the site last reported in. * A refresh button to request an updated report on demand. If the Environment section is empty, the site hasn't reported yet — usually because the plugin needs an update or hasn't checked in since installation. Publishing still works, but because the plugin version is unknown, articles are delivered as classic HTML until the site reports in (see the plugin version requirements below). Once it does, the next publish uses the richest format the site supports. ## Plugin version requirements Native blocks delivery requires a recent version of the Rankability WordPress plugin on the client's site. If you select **Native blocks** and the site's plugin is too old (or has never reported its version), a notice appears under the setting: *“Plugin update required for native blocks — articles will be delivered as classic HTML until the Rankability plugin on this site is updated.”* Nothing breaks in the meantime — publishes succeed and articles arrive as classic HTML. Update the plugin from the WordPress admin (Plugins → Updates) and the next publish uses the richer format automatically. The plugin self-updates on most sites, but sites with infrequent traffic may need a manual update. ## What stays the same * **Content is identical** — The words, images, links, and SEO assets (title, slug, meta description) are exactly the same in every format. Only the packaging changes. * **No extra cost** — Delivery format has no effect on credits. * **Draft vs. publish, categories, author, post type** — All existing publish options work identically in every format. * **Publishing history** — Every attempt is still recorded per project, and any format fallback is noted there in plain language. ## Troubleshooting * **Article arrived as one big block** — The connection is set to Classic HTML, or the plugin on the site is too old for native blocks. Check the Article delivery setting and the plugin-update notice. * **Block markup visible as text on a builder site** — The site's builder wasn't detected yet. Open the connection's Environment section and click refresh; if the builder still doesn't appear, update the Rankability plugin on the site. * **Environment section is empty** — The plugin hasn't reported in. Update the plugin on the WordPress site, then refresh the environment from the connection card. ## Related articles * [Exporting your content](/copywriter/exporting-your-content.md) — All export destinations, including WordPress and Webflow. * [Creating a content project](/copywriter/creating-a-content-project.md) — Start a new article in the Copywriter. * [Troubleshooting common issues](/troubleshooting/troubleshooting-common-issues.md) — Fixes for connection and export problems. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.rankability.com/copywriter/wordpress-article-delivery-formats.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.