n8n-nodes-pixelseo

An n8n community node for PixelSEO — generate SEO image metadata at scale inside your workflows: an optimized filename, alt text, and ImageObject (JSON-LD) schema for every image, generated in the context of the page each image lives on.

Most alt-text tools describe an image in isolation. PixelSEO reads the page the image will appear on and names, describes, and tags it for the job it's doing there — so a room photo on a flooring page becomes red-oak-hardwood-flooring-living-room, not bright-living-room-couch.

Operations

• Analyze Images (SEO Metadata) — Send an image (binary) and get back an SEO filename, alt text, and ImageObject schema. Pass a Page URL so the metadata reflects the page's topic and intent. This is the main operation.
• SEO Package From Image URL — Same output for an existing, publicly accessible image URL (no upload).
• Generate SEO Image — Generate an AI image from a style or custom prompt, with SEO metadata built in. Optionally return binary data for direct upload to Google Drive, WordPress, S3, and more.
• Check Credits — Check your remaining PixelSEO credit balance.
• List Styles — Get all available AI generation styles.

Installation

In your n8n instance: Settings → Community Nodes → Install → search for n8n-nodes-pixelseo.

Credentials

You need a PixelSEO API key. Get one from your PixelSEO dashboard under Account → API Keys.

In n8n: Credentials → New → PixelSEO API, paste your key, and click Test to confirm it works before running a workflow.

Usage

Bulk SEO metadata for a folder of images (in page context)

1. Google Drive (list files) → Google Drive (download file)
2. PixelSEO → Analyze Images (SEO Metadata)
   • Binary Property: data
   • Page URL: the page the image will live on (e.g. an expression mapping each row's target URL)
3. Google Sheets / HTTP Request (to your CMS) → write seo_filename, alt_text, and schema

Because this operation processes one image per item, use n8n's normal item flow (or a Loop) to run a batch — each item is charged 1 credit, and failed images aren't charged.

Output shape (Analyze Images)

Fields are returned at the top level for easy mapping:

{
  "original_filename": "IMG_4821.jpg",
  "seo_filename": "red-oak-hardwood-flooring-living-room.webp",
  "alt_text": "Red oak hardwood flooring in a bright, sunlit living room",
  "name": "red-oak-hardwood-flooring-living-room",
  "description": "...",
  "schema": { "@type": "ImageObject", "name": "...", "description": "..." },
  "credits_used": 1,
  "credits_remaining": 148
}

Reference downstream as {{ $json.seo_filename }}, {{ $json.alt_text }}, {{ $json.schema }}.

Upgrading from 0.8.x: the Analyze Images output is now unwrapped to the top level (previously nested under results[0]). Update any expressions that referenced $json.results[0].….

Generate an image and upload to Google Drive

1. PixelSEO → Generate SEO Image → choose a style or write a custom prompt
2. Enable Return Binary Data
3. Connect a Google Drive upload node (uses the returned SEO filename)

Credits

PixelSEO uses a credit system:

• Analyze Images (SEO Metadata): 1 credit per image
• Generate SEO Image: 1 credit
• SEO Package From Image URL: 0.1 credit

You're only charged for images that process successfully. Credits never expire.

Output format note (generation)

Images are generated as PNG by the AI and converted to your chosen format (WebP, JPEG, PNG) via Cloudflare's image transformation. The image_url always serves the correct format. Enable Return Binary Data to get the actual converted file bytes for piping into upload nodes.

Links

• PixelSEO
• Pricing & Credits
• npm package