Distribution Management and Target Sites

Distribution Management and Target Sites

Distribution Management syncs reviewed or published GEOFlow content to external sites. It is not just article copying; it manages target channels, secrets, queues, remote settings, remote page generation, and logs.

1. Supported Channel Types

Channel type	Best fit	Core capabilities
GEOFlow Agent	Fresh target sites, lightweight sites, servers where you can upload a PHP package	Preconfigured target package, static home and article pages, sitemap, llms.txt, TXT maps, image sync, remote settings sync
WordPress REST	Existing WordPress sites	Publish, update, delete posts, upload media, and maintain categories/tags with Application Password authentication

2. Publication Scope

Tasks can choose one of three publication scopes:

• Local site plus channels: publish on the GEOFlow local frontend and enqueue selected distribution channels.
• Channels only: keep a private management copy in GEOFlow while target channels generate public content.
• Local site only: publish only on GEOFlow. Channel selection is disabled and no remote distribution job is created.

This prevents duplicate publishing and separates single-site operations from multi-site distribution workflows.

3. GEOFlow Agent Target-site Package

After creating or editing a GEOFlow Agent channel, download the target-site package from the channel detail page. The package is preconfigured with:

• Agent base URL
• key ID
• plaintext secret
• site title, description, copyright, and theme settings
• static asset paths
• Apache .htaccess and Nginx rewrite examples

Static mode is recommended by default. When an article is distributed, the target site regenerates its homepage, article page, sitemap, llms.txt, and TXT maps for search engines and LLM crawlers.

4. WordPress REST Channels

WordPress channels are for existing WordPress sites. Configuration usually includes:

• WordPress site URL
• WordPress username
• Application Password
• default category, post status, and tag strategy

GEOFlow manages remote posts through the WordPress REST API. Images are uploaded to the media library, and categories/tags are synchronized according to configuration.

5. Remote Settings Sync

The distribution channel edit page can manage target-site settings such as:

• site title
• subtitle and description
• copyright and filing text
• theme template
• categories

After saving, use “Update Target Site” to sync remote configuration, homepages, article pages, and map files. Run this after uploading a fresh target package or changing site settings.

6. Queue, Logs, and Remote Content Management

The distribution queue tracks each article on each channel:

• publish, update, and delete actions
• sync status
• remote URL
• attempt count
• latest error

You can edit remote articles or delete remote copies from the queue. Remote edits are written back to the local GEOFlow article; remote deletions refresh the target homepage and map files.

7. Troubleshooting

• Health check returns 404: confirm the GEOFlow Agent package is uploaded to the expected directory and the Agent base URL points to the package entry.
• Rewrite mode fails: prefer static mode first; if using rewrite mode, confirm server rules point to the package entry.
• WordPress authentication fails: confirm the Application Password has no spaces, the user can publish posts, and REST API access is not blocked by plugins.
• Images do not sync: check target-site write permissions or WordPress media upload permissions.