WordPress Integration Guide

1. Create an Application Password

On your WordPress site, logged in with an account that can publish content: Profile → Application Passwords (native since WordPress 5.6, no plugin needed). Give it a name (e.g. "iziRanker") and copy the generated password — it will never be shown again.

2. (Optional) Create WooCommerce credentials

If you also want to publish Product Sheets, from WooCommerce → Settings → Advanced → REST API, create a key with Read/Write permissions. Copy the generated Consumer Key and Consumer Secret. Without WooCommerce installed, you can skip this step and connect only Articles/Pages.

3. Connect the site

From the Integrations page, in the "WordPress" block, enter the site URL, the username, and the Application Password created in step 1, and — if you have them — the WooCommerce Consumer Key/Secret from step 2. Access is verified immediately against your site before being saved (credentials encrypted, never stored in plain text). Only organization owners/admins can connect or disconnect a site.

4. Where each content type lands

• Blog Article → a WordPress article (post).
• Local Page, Service Page → a WordPress page (page).
• Product Sheet → a WooCommerce product (requires the Consumer Key/Secret from step 2 — without them, the publish button links back to Integrations to add them).

In all cases, the generated slug becomes the WordPress/WooCommerce slug, and republishing content already sent (same slug) updates the existing article/page/ product instead of creating a duplicate.

5. Publish or schedule

From Copywriting, each generated content has a Publish to WordPress button, with a Schedule (optional) field: leave it empty to publish immediately, or pick a future date/time — processed automatically at the set time (checked every 5 minutes), and can be cancelled as long as it hasn't gone out yet.

6. The content in the editor

The content is sent as HTML directly into the body of the article/page/product — WordPress displays it perfectly on the site. If you then reopen the content in the Gutenberg editor, it appears as a single "Custom HTML" block rather than separate blocks (paragraph, heading, image...): this is normal and has no effect on the public display.

7. Security

• Credentials are never shown in plain text again after being saved — if in doubt, disconnect the site and reconnect it with new credentials.
• An Application Password or a WooCommerce key can be revoked at any time from WordPress, without affecting your main password.