๐ Automated SEO - WordPress Integration
Publish automated blog posts directly to your WordPress site using the WordPress REST API. This method is secure, official, and works with any WordPress site.
Official WordPress Integration
Uses WordPress REST API with Application Passwords - the recommended method by WordPress.org
Requirements
- โ WordPress 5.6 or higher
- โ REST API enabled (enabled by default)
- โ
User account with
publish_postscapability (Author, Editor, or Administrator) - โ HTTPS recommended for security
Step-by-Step Setup
Step 1: Create Application Password in WordPress
- Log into your WordPress admin dashboard
- Go to Users โ Profile (or Users โ Your Profile)
- Scroll down to the "Application Passwords" section
- In the "New Application Password Name" field, enter:
Fast SEO Fix Publishing - Click "Add New Application Password"
- Copy the generated password immediately (format:
xxxx xxxx xxxx xxxx xxxx xxxx)
Save Your Password!
The application password is shown only once. Copy it immediately before closing the page.
Step 2: Add WordPress Connection in Fast SEO Fix
- Go to Dashboard โ Publishing Connections
- Click "Add Publishing Connection"
- Select "WordPress" from the platform dropdown
- Fill in the connection details:
- Connection Name: e.g., "My WordPress Blog"
- Site URL: Your full WordPress URL including
https:// - Username: Your WordPress admin username
- Application Password: Paste the password from Step 1
- Click "Add Connection"
- Click "Sync" to test the connection
Publishing Your First Post
- Generate a blog post in your content calendar
- Click "Publish" on the generated post
- Select your WordPress connection
- Configure publishing settings:
- Categories: Will be auto-created in WordPress if they don't exist
- Tags: Auto-populated from target keywords
- Status: Choose "Published", "Draft", or "Scheduled"
- Click "Publish Now"
Troubleshooting
REST API Not Available
Some hosting providers disable the REST API. Contact your host for support.
Authentication Failed
Double-check:
- Username is correct (not email)
- Application password was copied correctly (no spaces)
- User has publishing permissions