WordPress Publishing

Floyi’s WordPress Publishing integration lets you push finished content from the Content Creation workspace straight to your WordPress site. No copy-pasting, no reformatting. Your drafts arrive in WordPress with the correct post type, categories, tags, author, and SEO metadata already set. Publishing to a Git-based static site instead? See publishing to GitHub repositories.

What You’ll Learn

How to install the Floyi Connect plugin on WordPress
How to connect your WordPress site to Floyi
How to publish, schedule, and update articles
How to configure SEO metadata for Yoast, Rank Math, AIOSEO, and SEOPress
How to manage connected sites and troubleshoot issues

Part 1: Installing the Floyi Connect Plugin

Before you can connect a WordPress site, you need to install the Floyi Connect plugin on that site.

Requirements

Requirement	Minimum Version
WordPress	5.8 or higher (including WordPress 7.0)
PHP	7.4 or higher
User Role	Administrator
Floyi Plan	Any paid plan
SEO Plugin (optional)	Yoast SEO, Rank Math, AIOSEO, or SEOPress

Installation Steps

Floyi Connect is available in the official WordPress Plugin Directory, so you can install and update it directly from your WordPress admin.

In your WordPress admin, go to Plugins > Add New and search for Floyi Connect.
Click Install Now, then Activate.
Navigate to Settings > Floyi in your WordPress admin to confirm the plugin is active.

After activation, the plugin will display a “Not Connected” status with instructions to connect to Floyi.

Part 2: Connecting Your WordPress Site

Connection uses a secure token-based handshake. You generate a token in Floyi, paste it in WordPress, and the two systems authenticate automatically.

Step-by-Step Connection

In Floyi:

Go to Settings > Integrations.
Scroll to the WordPress section.
Click Connect Site.
A modal appears with a connection token and a 10-minute countdown timer.
Click the Copy button to copy the token to your clipboard.

In WordPress:

Go to Settings > Floyi in your WordPress admin.
Paste the token into the Connection Token field. The format is XXXX-XXXX-XXXX.
Click Connect.

The plugin sends your site details to Floyi and establishes a secure connection. Once complete, both Floyi and WordPress will show a green “Connected” status.

What Gets Shared During Connection

When your WordPress site connects, Floyi receives:

Site name and URL
Available post types (Posts, Pages, and any custom post types)
Categories and tags available on the site
Authors who can be assigned to posts
SEO plugin name and version, if installed (supported: Yoast SEO, Rank Math, AIOSEO, SEOPress)
Editor type (Block Editor or Classic Editor)

Floyi never receives your WordPress login credentials. All communication uses signed API requests.

Part 3: Managing Connected Sites

After connecting, your WordPress site appears in Settings > Integrations under the WordPress section.

Connection Card

Each connected site shows:

Site name and URL (clickable to visit)
Status badge — Connected (green), Disconnected (yellow), or Failed (red)
SEO plugin — Detected plugin name and version, if any
Health check button — Tests the connection and shows response latency
Disconnect button — Removes the connection

Health Check

Click the health check icon on any connected site to verify the connection is working. A successful check shows the response time (e.g., “Connection healthy (245ms)”). If the check fails, review the error message and verify that:

The Floyi Connect plugin is still activated in WordPress
Your WordPress site is accessible (not in maintenance mode)
The site URL has not changed

Connection Limits

Your Floyi plan determines how many sites you can connect, and WordPress and GitHub connections share the same limit. The connection count appears as a badge (e.g., “2/5”) next to the section header. If you reach your limit, disconnect an unused site or upgrade your plan.

Disconnecting a Site

Click the Disconnect button (trash icon) on the site card.
Confirm the disconnection in the dialog.

Disconnecting removes the active link between Floyi and WordPress. Previously published posts remain on WordPress. You can reconnect the same site later by generating a new token.

You can also disconnect from the WordPress side by going to Settings > Floyi and clicking Disconnect.

Part 4: Publishing Content to WordPress

You can publish any article from the Content Creation workspace to a connected WordPress site.

Open an article in the Content Editor.
Open the Publish dropdown in the editor header and choose Publish to WordPress. The dropdown is available once the draft is ready.
The publish modal opens with your publishing options.

Selecting a Site

If you have multiple connected sites, choose the target site from the WordPress Site dropdown. The dropdown shows each site’s name and URL.

Click Sync from WordPress to pull the latest categories, tags, authors, and pages from your site. This is useful if you recently added new categories or authors in WordPress.

Choosing Post Type

Select the content type for your article:

Post Type	Use For
Post	Blog articles, news, regular content
Page	Static pages, landing pages, evergreen content
Custom types	Any custom post types registered on your WordPress site

Setting Parent Page

When publishing as a Page, you can select a parent page to place your content within WordPress’s page hierarchy. The dropdown shows your existing pages with indentation to indicate nesting.

For example, selecting “Products” as a parent for a page titled “Best SEO Tools” would create the URL path /products/best-seo-tools/.

Floyi uses the last part of the topic’s URL slug as the WordPress slug (for ibs/diagnosis, the slug is diagnosis). For a page, choose the parent page to rebuild the rest of the path.

Select (No parent - top level) to create a top-level page.

Publish Status

Choose how the article should appear on WordPress:

Status	What Happens
Draft	Saved to WordPress but not visible to the public. You can review and edit before going live.
Publish Now	Immediately visible on your WordPress site.
Schedule	Set a future date and time for automatic publication.

When you select Schedule, a date and time picker appears. Choose your desired publish date and the article will go live automatically at that time. Times are in your own time zone, and the picker names it.

[!NOTE] For a new article, Publish Status starts on Draft, so nothing goes live until you choose Publish Now or Schedule.

Categories and Tags

For Post type articles, you can assign categories and tags from your WordPress site.

Categories appear as selectable buttons. Click to toggle selection.
Tags appear as selectable buttons (up to 20 shown). Click to toggle.

If no categories or tags appear, click Sync from WordPress to load them from your site.

Selecting an Author

Choose which WordPress author should be credited for the post. The dropdown lists all authors from your connected site.

Configuring SEO Metadata

If your WordPress site has a supported SEO plugin installed, Floyi can send SEO metadata along with your content.

Supported SEO plugins:

Yoast SEO
Rank Math
All in One SEO (AIOSEO)
SEOPress

Expand the SEO Metadata section to configure:

Field	Description	Guideline
SEO Title	The title tag for search engines	Keep under 60 characters
Meta Description	The description shown in search results	Keep under 160 characters
Focus Keyword	The primary keyword for SEO analysis	Used by your SEO plugin’s scoring

Floyi auto-fills these fields from your content brief when available. You can edit them before publishing.

Toggle Include SEO metadata when publishing to control whether SEO data is sent. SEO metadata is only sent when Floyi detects one of the supported SEO plugins on your site.

Publishing

After configuring your options, click the publish button. The label changes based on your selected status:

Publish to WordPress — for immediate publication
Save as Draft — for draft status
Schedule Post — for future publication

A loading state appears while the article is being sent to WordPress. Once complete, you see a success screen with a link to View on WordPress (for published posts) or Preview on WordPress (for drafts).

Part 5: Updating Published Content

When you edit an article in Floyi after it has been published to WordPress, the publish modal shows a blue banner indicating the article is already live.

How Updates Work

Open the previously published article in the Content Editor.
Open Publish and choose Update or Publish to Another Site.
The modal shows a “Published on WordPress” banner with:
- Current WordPress status (Live, Draft, Private, Pending, or Scheduled)
- Last updated date
- A link to view the live page
- A “(Changes pending)” note, shown when the article’s content has changed since the last publish, or when a topic it links to has since gone live on this site
Modify any publishing settings if needed (categories, tags, SEO metadata).
Click Update on WordPress (or Update Draft or Reschedule, depending on the status) to push the latest version. Rescheduling a post that’s already on WordPress needs Floyi Connect 1.2.3 or later.

The updated content replaces the existing WordPress post. The WordPress post ID, URL, and permalink remain the same. Floyi never changes the slug of a post that is or was live, or a slug you edited in WordPress. One exception: a draft Floyi sent earlier with the parts of a nested slug run together (such as ibsdiagnosis) gets the last part (diagnosis) the next time you publish it, as long as it has never been live. This needs Floyi Connect 1.2.3 or later.

Syncing Status from WordPress

If someone changes the post status directly in WordPress (e.g., unpublishes a post), click Sync from WordPress to pull the latest status back into Floyi.

Part 6: Content Formatting

Floyi automatically converts your editor content to the appropriate WordPress format.

Structured Data (JSON-LD)

If your article has structured data enabled, Floyi automatically includes JSON-LD schema markup in the page head when publishing. Supported schema types — Article, FAQ, HowTo, LocalBusiness, Organization, and BreadcrumbList — are generated from your article and brand data. The Floyi Connect plugin renders the JSON-LD using WordPress’s wp_print_inline_script_tag() for compatibility with WordPress 7.0 and plugin check standards.

You can toggle structured data on or off in the publish modal before publishing.

Editing Schema in the WordPress Editor

Floyi Connect 1.2.0 adds a Floyi Structured Data panel to the WordPress Block Editor, so you can view, edit, and validate a post’s schema without leaving WordPress. Open a post in the editor and find the panel in the settings sidebar (the same column as Categories and Tags).

The panel lets you:

View and edit the JSON-LD — the exact schema on the page is shown in an editable field. Make a correction and it saves with the post.
Validate as you type — the panel checks that the JSON is valid, confirms the schema structure, and warns about missing recommended fields (for example, an Article with no author or image).
Fill from post — click this to pull the WordPress post’s author and featured image into the schema when either is missing. The author’s profile URL is included automatically.
Test in Google Rich Results — a link opens Google’s Rich Results Test for the published URL, the authoritative check for whether search engines can read your schema.
Clear — empties the schema field for the post.

Who Owns the Schema: Floyi vs. WordPress

The Include structured data checkbox in Floyi’s publish modal decides what happens to your WordPress schema on each publish:

Checked — Floyi regenerates the schema and overwrites what’s in WordPress, including any edits you made in the Structured Data panel.
Unchecked — Floyi sends no schema, so your WordPress edits are preserved untouched.

So if you fine-tune schema in the WordPress panel and want to keep those changes, leave Include structured data unchecked the next time you publish from Floyi. To hand control back to Floyi, check it again.

Images

The first time you publish, Floyi uploads each image to your WordPress Media Library. Updates reuse those uploads, so they don’t add copies. An image you deleted from the Media Library, or changed in Floyi, is uploaded again. The image under the article’s Featured Image heading becomes the post’s featured image and is removed from the body. If you change an image’s alt text in Floyi, the next publish updates it in the Media Library (Floyi Connect 1.2.3 or later).

Internal Links

Links to topics already live on the same WordPress site point to those posts’ WordPress addresses. Links to other topics use your website address plus the topic’s URL slug. When one of those topics goes live later, the articles that link to it show (Changes pending). Publish them again to point the link at the new post.

Block Editor (Gutenberg)

If your site uses the Block Editor, Floyi converts your content into native Gutenberg blocks:

Headings (H1–H6)
Paragraphs
Ordered and unordered lists
Tables
Code blocks
Blockquotes
Images

Classic Editor

Floyi sends content as Gutenberg blocks. Block markup is standard HTML, so it renders on the front end of your site even if you use the Classic Editor.

Part 7: WordPress Plugin Settings

After connecting, the Floyi Connect plugin settings page in WordPress (Settings > Floyi) shows:

Connection Status

Connected (green badge) with your Site ID, connection date, and last sync time
Disconnect button to remove the connection

Site Capabilities

A summary of what Floyi can see on your site:

Post Types (e.g., “Post, Page, Project”)
Categories count
Tags count
Authors count
SEO Plugin (e.g., “Yoast SEO 19.5” or “None detected”)
Editor type (Block Editor or Classic Editor)

Webhook Queue

The plugin uses webhooks to notify Floyi when post statuses change in WordPress. The queue shows:

Pending — Webhooks waiting to be sent
Retrying — Webhooks that failed and are being retried
Failed — Webhooks that could not be delivered after multiple attempts

Failed webhooks do not affect your published content. They only mean that Floyi may not reflect the latest WordPress status until the next manual sync.

System Information

Technical details for troubleshooting: WordPress version, PHP version, plugin version, and site URL.

Part 8: Topical Authority Integration

When an article linked to a topic in your Topical Map goes live on WordPress, Floyi automatically updates your Topical Authority data. A post saved as a draft doesn’t change it until it’s published, and a scheduled post updates it when it goes live:

The topic node is marked as Published in the Topical Authority Planner
Your coverage metrics update to reflect the newly published content
The Topical Authority Scorecard reflects the change in your next refresh

This creates a closed loop: plan topics in your Topical Map, create briefs and drafts, publish to WordPress, and track authority growth — all within Floyi.

Part 9: Troubleshooting Cloudflare or Firewall Blocks

If your WordPress site is behind Cloudflare (or another bot-protection service), publishing may fail with an error like:

Your WordPress site is behind Cloudflare and is blocking Floyi’s REST API requests with a bot challenge.

This means Cloudflare’s bot protection is intercepting Floyi’s requests with a JavaScript challenge (“Just a moment…”) before they reach your WordPress server. Floyi authenticates every request with an HMAC-signed token, but Cloudflare doesn’t know that, so it treats automated traffic as suspicious.

You need to allow Floyi’s requests through Cloudflare. Floyi’s plugin uses a dedicated URL path (/wp-json/floyi/v1/*), so you can scope the bypass narrowly without weakening protection on the rest of your WordPress REST API.

Option 1 (Recommended): Add a WAF Custom Rule with Skip

Best for: Cloudflare Pro, Business, or Enterprise plans (where the Skip action can target Super Bot Fight Mode and Managed Rules).

This is the safest option because it only skips the challenge for requests that include Floyi’s signed X-Floyi-Token header — bot traffic without that header is still challenged.

In Cloudflare, go to Security > WAF > Custom rules.
Click Create rule and name it Allow Floyi WordPress publishing.
Set the rule expression to:
- Field: URI Path
- Operator: contains
- Value: /wp-json/floyi/
- AND
- Field: Request Headers
- Header name: x-floyi-token
- Operator: exists
Set Action to Skip and select all available skip targets that apply to your plan:
- All remaining custom rules
- Super Bot Fight Mode (Pro+)
- Managed Rules (Pro+)
- Rate limiting rules
Click Deploy.

Only authenticated Floyi requests bypass the firewall — no other traffic is affected.

Option 2: Reduce Security Level for the Floyi Path (any plan)

Best for: any plan, including Free. This does not bypass Bot Fight Mode itself, but lowering the path-specific Security Level eliminates the IP-reputation-driven challenges that account for most blocked publish attempts.

In Cloudflare, go to Rules > Configuration Rules (or Page Rules on legacy plans).
Click Create rule and name it Floyi WordPress publishing.
Set the rule expression to:
- Field: URI Path
- Operator: contains
- Value: /wp-json/floyi/
Under Settings, set:
- Security Level → Essentially Off
- Browser Integrity Check → Off
Click Deploy.

This narrows the change to Floyi’s plugin namespace. Other WordPress REST endpoints (/wp-json/wp/v2/*) keep their normal Security Level.

Option 3: Disable Bot Fight Mode globally (Free plan only, last resort)

If Options 1 and 2 do not resolve the block, the trigger is likely Bot Fight Mode, which on the Free plan can only be toggled site-wide.

In Cloudflare, go to Security > Bots.
Toggle Bot Fight Mode to Off.

Verifying the Fix

After applying either option:

Wait 30 seconds for Cloudflare to propagate the rule.
In Floyi, go to Settings > Integrations and click the health check icon on the affected site.
A successful check confirms Floyi can reach WordPress through Cloudflare.
Retry the publish from the Content Editor.

If the health check still fails, contact your Cloudflare administrator to confirm the rule is active and ordered above any blocking rules.

Permissions

WordPress publishing is available to team members based on their role:

Action	Required Role
Connect a new site	Team Admin or Owner
Disconnect a site	Team Admin or Owner
Update connection settings	Team Admin or Owner
Publish or update articles	Any team member
Run health checks	Any team member

Frequently Asked Questions

How many WordPress sites can I connect?

The number of connections depends on your Floyi plan. Your current usage and limit are shown in the WordPress section header (e.g., “2/5”). Free plans do not include WordPress publishing.

Can I publish the same article to multiple WordPress sites?

Yes. Open the publish modal and select a different site from the dropdown. Each site maintains its own publish record, so you can publish the same Floyi article to multiple WordPress sites with different settings.

What happens if I disconnect and reconnect the same site?

Previously published posts remain on WordPress. After reconnecting, Floyi creates a new connection record. Existing publish records from the previous connection are preserved but linked to the old connection.

Why are my categories or tags not showing?

Click Sync from WordPress in the publish modal to reload your site’s categories, tags, and authors. If they still do not appear, verify that categories and tags exist on your WordPress site and that the Floyi Connect plugin is active.

Does Floyi modify my existing WordPress content?

Floyi only creates or updates posts that were published through Floyi. It never modifies posts that were created directly in WordPress.

What happens if publishing fails?

Floyi retries a failed publish up to 3 times, waiting 1, 2 and then 4 minutes. While it waits, the modal shows Retrying (1 of 3) with the latest error. If the last try fails, you see the error from WordPress. Click Try Again to retry manually. Common causes include:

WordPress site is temporarily unreachable
The Floyi Connect plugin was deactivated
WordPress server returned an error (disk full, database issue)
Cloudflare or another bot-protection service is blocking Floyi’s requests (see Part 9: Troubleshooting Cloudflare or Firewall Blocks)

Cloudflare bot challenges are not retried — they require a Cloudflare configuration change before publishing will succeed.

Can I schedule posts for a specific time?

Yes. Select Schedule, then pick the date and time in your own time zone. The post goes live automatically at that time, handled by WordPress. To reschedule a post that’s already on WordPress, your site needs Floyi Connect 1.2.3 or later.

Which SEO plugins are supported?

Floyi detects and sends metadata to: Yoast SEO, Rank Math, All in One SEO (AIOSEO), and SEOPress. If none of these is installed, Floyi doesn’t send SEO metadata.

How do I know if my content is up to date on WordPress?

The publish modal shows a “(Changes pending)” indicator when the article’s content in Floyi has changed since the last publish, or when a topic it links to has gone live on the site since. Click Update on WordPress to push the latest version.

Is the connection secure?

Yes. All communication between Floyi and your WordPress site uses HMAC-SHA256 signed requests. Floyi never stores or transmits your WordPress login credentials. Connection tokens expire after 10 minutes and can only be used once.