Configuration Guide

I want to use Respira for WordPress to optimize my WordPress site. Execute this complete setup and optimization plan:

## Phase 1: MCP Server Installation & Configuration

1. **Download and Install MCP Server:**
   - Go to https://github.com/webmyc/respira-wordpress/releases
   - Find the latest release with tag `mcp-v*` (e.g., `mcp-v1.3.1`)
   - Download `respira-wordpress-mcp-server-*.zip` or `respira-wordpress-mcp-server-*.tar.gz`
   - Extract to a permanent location (e.g., `~/.respira/mcp-server/` or `/opt/respira-mcp-server/`)
   - Verify the `dist/index.js` file exists in the extracted folder
   - Note the full path to `dist/index.js` for configuration

2. **Create Respira Configuration File:**
   - Create directory: `~/.respira/` (if it doesn't exist)
   - Create file: `~/.respira/config.json`
   - Add this content (replace with actual values):
   ```json
   {
     "sites": [
       {
         "id": "my-site",
         "name": "My WordPress Site",
         "url": "https://your-wordpress-site.com",
         "apiKey": "respira_your-api-key-here",
         "default": true
       }
     ],
     "preferences": {
       "autoDuplicate": true,
       "securityChecks": true
     }
   }
   ```

3. **Configure Cursor MCP:**
   - Create or update `.cursor/mcp.json` in the current project root
   - Add this configuration (replace `/path/to/mcp-server/dist/index.js` with the actual path from step 1):
   ```json
   {
     "mcpServers": {
       "respira-wordpress": {
         "command": "node",
         "args": ["/path/to/mcp-server/dist/index.js"]
       }
     }
   }
   ```
   - If the file already exists, merge the `respira-wordpress` entry into the existing `mcpServers` object

4. **Verify Installation:**
   - Check that Node.js is installed: `node --version` (should be >= 18.0.0)
   - Verify the MCP server path is correct
   - Note: Cursor will need to be restarted for MCP changes to take effect

## Phase 2: Site Connection & Context

5. **Connect to WordPress Site:**
   - Use the `wordpress_get_site_context` tool to verify connection
   - Confirm you can retrieve site information
   - If connection fails, verify:
     * API key is correct in `~/.respira/config.json`
     * WordPress site URL is correct and accessible
     * Respira plugin is installed and activated on WordPress

6. **Get Comprehensive Site Context:**
   - Retrieve full site information:
     * WordPress version and PHP version
     * Active theme and version
     * All active plugins with versions
     * Detected page builders
     * Site structure and configuration

## Phase 3: Comprehensive Site Analysis

7. **Identify Key Pages to Analyze:**
   - List all pages using `wordpress_list_pages`
   - Identify the most important pages (homepage, main landing pages, high-traffic pages)
   - Prioritize pages that need optimization

8. **Run Performance Analysis:**
   - For each key page, run `wordpress_analyze_performance`:
     * Core Web Vitals (LCP, FID, CLS)
     * Load time metrics
     * Image optimization opportunities
     * CSS/JS optimization needs
     * Caching opportunities
   - Run `wordpress_get_core_web_vitals` for detailed metrics
   - Run `wordpress_analyze_images` for image-specific issues

9. **Run SEO Analysis:**
   - For each key page, run `wordpress_analyze_seo`:
     * Meta tags (title, description, OG tags)
     * Heading structure (H1, H2, H3 hierarchy)
     * Image alt text coverage
     * Internal linking analysis
     * Schema markup presence
     * Content quality and readability
   - Run `wordpress_check_seo_issues` for quick issue identification
   - Run `wordpress_analyze_readability` for content readability scores

10. **Run AEO (AI Engine Optimization) Analysis:**
    - For each key page, run `wordpress_analyze_aeo`:
      * Structured data presence and quality
      * Content clarity for AI understanding
      * Semantic HTML usage
      * Entity recognition
      * Content depth and comprehensiveness
      * FAQ opportunities
    - Run `wordpress_check_structured_data` for schema markup details

## Phase 4: Improvement Recommendations

11. **Create Comprehensive Improvement Report:**
    - Compile all analysis results into a structured report
    - Categorize by:
      * Performance optimizations (high/medium/low priority)
      * SEO improvements (critical/important/nice-to-have)
      * AEO enhancements (high impact/medium impact/low impact)
    - Include specific, actionable recommendations for each page
    - Prioritize recommendations by impact and effort
    - Note which pages need the most work

## Phase 5: Safe Implementation (CRITICAL: Always Use Duplicates)

12. **For ANY page or post that needs editing:**
    - **ALWAYS create a duplicate first** using `wordpress_create_page_duplicate` or `wordpress_create_post_duplicate`
    - **NEVER edit published content directly**
    - Only edit the duplicate versions
    - The duplicate will be created as a draft automatically

13. **Implement Improvements:**
    - Start with highest-priority recommendations
    - For each page that needs changes:
      1. Create duplicate (if not already done)
      2. Make edits to the duplicate
      3. Document what changes were made
    - Focus on:
      * Performance: Image optimization, lazy loading, caching headers
      * SEO: Meta tags, headings, alt text, internal links, schema markup
      * AEO: Structured data, semantic HTML, content clarity, entity markup

14. **Verify Improvements:**
    - After implementing changes on duplicates, run follow-up analysis:
      * Re-analyze performance metrics
      * Re-check SEO scores
      * Re-analyze AEO scores
    - Compare before/after metrics
    - Document improvements achieved

## Phase 6: Final Report

15. **Generate Final Summary:**
    - List all improvements made
    - Show before/after metrics where applicable
    - Note any remaining recommendations for future work
    - Provide instructions for reviewing and publishing duplicates in WordPress admin

## Important Rules:
- **NEVER edit published pages/posts directly** - always create duplicates first
- **Always verify connection before making changes**
- **Test changes on duplicates before publishing**
- **Document all changes made for review**

Begin by installing the MCP server and configuring Cursor, then proceed through each phase systematically.