{"id":330477,"date":"2026-06-24T12:26:49","date_gmt":"2026-06-24T12:26:49","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/blippinz-ai-seo\/"},"modified":"2026-06-24T12:26:27","modified_gmt":"2026-06-24T12:26:27","slug":"blippinz-ai-seo","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/blippinz-ai-seo\/","author":23520654,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"1.0","tested":"7.0","requires":"5.6","requires_php":"7.4","requires_plugins":null,"header_name":"Blippinz AI SEO","header_author":"Iwan Saputra","header_description":"Blippinz AI generated SEO content","assets_banners_color":"","last_updated":"2026-06-24 12:26:27","external_support_url":"","external_repository_url":"","donate_link":"https:\/\/blippinz.co.nz\/","header_plugin_uri":"https:\/\/blippinz.co.nz","header_author_uri":"https:\/\/ngonar.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":50,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0":{"tag":"1.0","author":"blippinz","date":"2026-06-24 12:26:27"}},"upgrade_notice":{"1.0.0":"

First release. After activating, visit Settings \u2192 Blippinz AI SEO<\/strong> and set a strong API key before making any REST API calls. The endpoint will reject all API-key-based requests until a key is configured.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[2353,181641,268716,23853,186],"plugin_category":[55],"plugin_contributors":[268717],"plugin_business_model":[],"class_list":["post-330477","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-content-automation","plugin_tags-post-creation","plugin_tags-rest-api","plugin_tags-seo","plugin_category-seo-and-marketing","plugin_contributors-blippinz","plugin_committers-blippinz"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/blippinz-ai-seo.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n

Blippinz AI SEO<\/strong> is a lightweight WordPress plugin that bridges your external AI content generation service with your WordPress site. It registers a secure, configurable REST API endpoint that accepts AI-generated articles \u2014 including HTML content, titles, and featured images \u2014 and creates them as WordPress posts automatically.<\/p>\n\n

This plugin was built for the Blippinz<\/a> platform, which uses artificial intelligence to generate SEO-optimised articles. Instead of manually copying content from an AI tool into WordPress, Blippinz AI SEO handles the entire publish flow: receive content \u2192 upload image \u2192 set featured image \u2192 create post \u2192 go live.<\/p>\n\n\n\n

How it works:<\/strong><\/p>\n\n

    \n
  1. Your AI service (or any HTTP client) sends a POST request to \/wp-json\/blipaise\/v1\/addPost<\/code><\/li>\n
  2. The request is authenticated using an API key you set in the WordPress admin<\/li>\n
  3. The plugin sanitises and validates all inputs<\/li>\n
  4. It creates the WordPress post with the provided title, content, and status<\/li>\n
  5. If an image is included (base64 or file upload), it is uploaded to the Media Library and set as the post's featured image<\/li>\n
  6. The API returns the new post ID, permalink, and media URL<\/li>\n<\/ol>\n\n\n\n

    Key Features:<\/strong><\/p>\n\n

      \n
    • Secure API key authentication<\/strong> \u2014 All requests to the post creation endpoint must carry a secret key set exclusively by you in WP Admin. No hardcoded defaults.<\/li>\n
    • Base64 image upload<\/strong> \u2014 Send an image as a base64-encoded string in the JSON payload and the plugin automatically decodes, validates, and uploads it to the Media Library.<\/li>\n
    • Multipart file upload<\/strong> \u2014 Alternatively, upload a file directly using multipart\/form-data<\/code>.<\/li>\n
    • Automatic featured image<\/strong> \u2014 Uploaded images are set as the post's featured image automatically.<\/li>\n
    • Configurable upload limits<\/strong> \u2014 Set the maximum file size (1\u201350 MB) and allowed MIME types (JPEG, PNG, GIF, WEBP, PDF) from the settings page.<\/li>\n
    • Full input sanitisation<\/strong> \u2014 All fields are sanitised using native WordPress functions (sanitize_text_field<\/code>, wp_kses_post<\/code>, sanitize_key<\/code>, absint<\/code>, sanitize_file_name<\/code>).<\/li>\n
    • MIME type validation<\/strong> \u2014 File types are verified against the server's actual file contents using wp_check_filetype_and_ext<\/code>, not just the filename or client-reported type.<\/li>\n
    • WordPress-native internationalisation<\/strong> \u2014 All user-facing strings use the blippinz-ai-seo<\/code> text domain and are ready for translation.<\/li>\n<\/ul>\n\n

      Configuration<\/h3>\n\n

      After activation, go to Settings \u2192 Blippinz AI SEO<\/strong> to configure:<\/p>\n\n

      Blippinz API Key<\/strong>\nThe secret key that must be included in every request to the addPost<\/code> endpoint. Use a long, random string (e.g. a UUID or 32-character random hex string). This key is stored in the WordPress options table and is never exposed in the front-end.<\/p>\n\n

      Max Upload Size (MB)<\/strong>\nMaximum file size allowed for image uploads via this plugin. Range: 1\u201350 MB. The effective limit is also capped by your server's PHP upload_max_filesize<\/code> setting.<\/p>\n\n

      Allowed File Types<\/strong>\nChoose which MIME types are accepted for image uploads. Available options: JPEG, PNG, GIF, WEBP, PDF.<\/p>\n\n

      REST API Reference<\/h3>\n\n

      Base URL<\/h4>\n\n
      https:\/\/yoursite.com\/wp-json\/blipaise\/v1\n<\/code><\/pre>\n\n\n\n
      Authentication<\/h4>\n\n
      All requests to the addPost<\/code> endpoint must be authenticated. There are two methods:<\/p>\n\n
      Method 1 \u2014 HTTP Header (recommended):<\/strong><\/p>\n\n
      X-BLIPAISE-KEY: your-secret-api-key\n<\/code><\/pre>\n\n
      Method 2 \u2014 Query parameter:<\/strong><\/p>\n\n
      ?api_key=your-secret-api-key\n<\/code><\/pre>\n\n
      Requests with a missing, empty, or incorrect key will receive a 401 Unauthorized<\/code> response.<\/p>\n\n
      WordPress administrators logged in via cookie\/nonce (e.g. from the WP admin) can also call the endpoint without an API key, provided they have the edit_posts<\/code> capability.<\/p>\n\n\n\n
      Endpoints<\/h4>\n\n
      GET \/status<\/strong><\/p>\n\n
      Returns the plugin status. Requires edit_posts<\/code> capability (logged-in WordPress users only).<\/p>\n\n
      Response:<\/p>\n\n
      {\n  \"status\": \"ok\",\n  \"plugin\": \"blippinz-ai-seo\",\n  \"version\": \"1.0.0\"\n}\n<\/code><\/pre>\n\n\n\n
      POST \/addPost<\/strong><\/p>\n\n
      Creates a new WordPress post. Accepts JSON or multipart\/form-data.<\/p>\n\n
      Request Headers:<\/em><\/p>\n\n
      Content-Type: application\/json\nX-BLIPAISE-KEY: your-secret-api-key\n<\/code><\/pre>\n\n
      JSON Body Parameters:<\/em><\/p>\n\n\n\n\n  Field\n  Type\n  Required\n  Description\n\n\n\n\n  title<\/code>\n  string\n  Yes\n  The post title. Sanitised with sanitize_text_field<\/code>.\n\n\n  content<\/code>\n  string\n  Yes\n  The post body. Full HTML is accepted and sanitised with wp_kses_post<\/code>.\n\n\n  status<\/code>\n  string\n  No\n  Post status. One of: publish<\/code>, draft<\/code>, pending<\/code>, private<\/code>. Defaults to publish<\/code>.\n\n\n  featured_media<\/code>\n  integer\n  No\n  The attachment ID of an existing media library item to use as the featured image.\n\n\n  image_data<\/code>\n  string\n  No\n  A base64-encoded image to upload and set as the featured image. May include a data URI prefix (e.g. data:image\/jpeg;base64,...<\/code>).\n\n\n  image_mime<\/code>\n  string\n  No\n  The MIME type of the image_data<\/code> image. Defaults to image\/jpeg<\/code>. Must be in your configured allowlist.\n\n\n\n\n
      Example request (JSON with base64 image):<\/em><\/p>\n\n
      curl -X POST \"https:\/\/yoursite.com\/wp-json\/blipaise\/v1\/addPost\" \\\n  -H \"Content-Type: application\/json\" \\\n  -H \"X-BLIPAISE-KEY: your-secret-api-key\" \\\n  -d '{\n    \"title\": \"10 SEO Tips That Actually Work in 2024\",\n    \"content\": \"<h2>Introduction<\/h2><p>Search engine optimisation has changed...<\/p>\",\n    \"status\": \"publish\",\n    \"image_data\": \"\/9j\/4AAQSkZJRgABAQAAAQABAAD...\",\n    \"image_mime\": \"image\/jpeg\"\n  }'\n<\/code><\/pre>\n\n
      Example request (multipart file upload):<\/em><\/p>\n\n
      curl -X POST \"https:\/\/yoursite.com\/wp-json\/blipaise\/v1\/addPost\" \\\n  -H \"X-BLIPAISE-KEY: your-secret-api-key\" \\\n  -F \"title=My Article\" \\\n  -F \"content=<p>Body content here.<\/p>\" \\\n  -F \"status=publish\" \\\n  -F \"file=@\/path\/to\/image.jpg\"\n<\/code><\/pre>\n\n
      Success Response (200 OK):<\/em><\/p>\n\n
      {\n  \"status\": \"ok\",\n  \"plugin\": \"blippinz-ai-seo\",\n  \"version\": \"1.0.0\",\n  \"post_id\": 42,\n  \"link\": \"https:\/\/yoursite.com\/10-seo-tips-that-actually-work-in-2024\/\",\n  \"uploaded_media_id\": 17,\n  \"uploaded_media_url\": \"https:\/\/yoursite.com\/wp-content\/uploads\/2024\/06\/blipaise-20240622-120000.jpg\"\n}\n<\/code><\/pre>\n\n
      Error Responses:<\/em><\/p>\n\n\n\n\n  HTTP Code\n  Error Code\n  Cause\n\n\n\n\n  400\n  blipaise_invalid_payload<\/code>\n  Request body is empty or not valid JSON\n\n\n  400\n  blipaise_missing_fields<\/code>\n  title<\/code> or content<\/code> is empty\n\n\n  400\n  blipaise_invalid_file_type<\/code>\n  Uploaded file MIME type is not in the allowlist\n\n\n  400\n  blipaise_file_too_large<\/code>\n  Uploaded file exceeds the configured size limit\n\n\n  400\n  blipaise_invalid_image_data<\/code>\n  image_data<\/code> is not valid base64 content\n\n\n  400\n  blipaise_upload_failed<\/code>\n  WordPress file system error during upload\n\n\n  401\n  \u2014\n  Missing or incorrect API key\n\n\n
      From the WordPress Admin (recommended):<\/strong><\/p>\n\n
        \n
      1. Go to Plugins \u2192 Add New<\/strong> in your WordPress dashboard.<\/li>\n
      2. Search for Blippinz AI SEO<\/strong>.<\/li>\n
      3. Click Install Now<\/strong>, then Activate<\/strong>.<\/li>\n
      4. Navigate to Settings \u2192 Blippinz AI SEO<\/strong> and configure your API key.<\/li>\n<\/ol>\n\n
        Manual installation:<\/strong><\/p>\n\n
          \n
        1. Download the plugin ZIP file.<\/li>\n
        2. Extract and upload the blippinz-ai-seo<\/code> folder to \/wp-content\/plugins\/<\/code> on your server.<\/li>\n
        3. Go to Plugins<\/strong> in your WordPress dashboard and click Activate<\/strong> next to Blippinz AI SEO.<\/li>\n
        4. Navigate to Settings \u2192 Blippinz AI SEO<\/strong> and set a strong, unique API key.<\/li>\n<\/ol>\n\n
          Important:<\/strong> The REST endpoint will reject all API-key-authenticated requests until you have saved a key in the settings page.<\/p>\n\n\n
          \n
          The endpoint returns 401. What's wrong?<\/h3><\/dt>\n
          Make sure you have saved an API key in Settings \u2192 Blippinz AI SEO<\/strong> and that you are sending it exactly as saved \u2014 either in the X-BLIPAISE-KEY<\/code> header or as the api_key<\/code> query parameter. The key comparison is case-sensitive.<\/p><\/dd>\n
          Can I send HTML in the content field?<\/h3><\/dt>\n
          Yes. The content<\/code> field is processed through WordPress's wp_kses_post()<\/code>, which allows safe post HTML including headings, paragraphs, lists, links, images, tables, and inline styles. Script tags and event attributes are stripped.<\/p><\/dd>\n
          What happens to the uploaded image?<\/h3><\/dt>\n
          The image is decoded (if base64) and written to the WordPress uploads directory, then registered as a Media Library attachment and set as the post's featured image. It is treated identically to any image uploaded via the WordPress media uploader.<\/p><\/dd>\n
          Can I use this without the Blippinz platform?<\/h3><\/dt>\n
          Yes \u2014 the plugin is a general-purpose authenticated REST endpoint for post creation. Any HTTP client or script can call it with the correct API key.<\/p><\/dd>\n
          How do I rotate or reset the API key?<\/h3><\/dt>\n
          Go to Settings \u2192 Blippinz AI SEO<\/strong>, enter a new key, and click Save Settings<\/strong>. Old keys are immediately invalidated.<\/p><\/dd>\n
          Does uninstalling the plugin delete my posts?<\/h3><\/dt>\n
          No. Posts created via this plugin are standard WordPress posts and remain after uninstalling. However, the plugin's stored options (API key and upload settings) are deleted from the database on uninstall.<\/p><\/dd>\n\n<\/dl>\n\n\n
          1.0.0<\/h4>\n\n
            \n
          • Initial public release.<\/li>\n
          • Registered POST \/wp-json\/blipaise\/v1\/addPost<\/code> endpoint with API key authentication.<\/li>\n
          • Registered GET \/wp-json\/blipaise\/v1\/status<\/code> endpoint (requires edit_posts<\/code> capability).<\/li>\n
          • Admin settings page for API key and upload configuration (max size, allowed MIME types).<\/li>\n
          • Base64 image upload support with automatic Media Library registration and featured image assignment.<\/li>\n
          • Multipart file upload support (keys: file<\/code>, image<\/code>, featured_image<\/code>, featured_media<\/code>).<\/li>\n
          • MIME type validation using wp_check_filetype_and_ext<\/code> against server-side file inspection.<\/li>\n
          • Full input sanitisation on all fields using native WordPress functions.<\/li>\n
          • Plugin options deleted on uninstall to prevent credential leakage.<\/li>\n<\/ul>","raw_excerpt":"Publish AI-generated SEO posts directly to WordPress via a secure REST API, with image uploads and full HTML content support.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/330477","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=330477"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/blippinz"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=330477"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=330477"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=330477"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=330477"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=330477"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=330477"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}