SEO Content Machine icon

SEO Content Machine

SEO Content Machine node
Join our community

Actions12

Overview

This node integrates with the SEO Content Machine API to perform various SEO-related content tasks. Specifically, for the "Other" resource and the "About Me" operation, it sends a keyword to the API and retrieves related "about me" content generated or fetched by the service.

Common scenarios where this node is beneficial include:

  • Automatically generating personalized "about me" sections for websites or profiles based on a keyword.
  • Enriching user profiles or content pages with SEO-optimized descriptive text.
  • Quickly obtaining relevant biographical or descriptive content snippets without manual writing.

Example use case: You provide a keyword like "digital marketing expert," and the node returns an SEO-friendly "about me" description that can be used on a personal website or portfolio.

Properties

Name Meaning
Keyword The keyword used to generate or fetch the "about me" content. This should be a string describing the subject or theme for the about me text.

Output

The node outputs JSON data in the json field of each item. This JSON contains the response from the SEO Content Machine API's /task/aboutme endpoint, which includes the generated or retrieved "about me" content related to the provided keyword.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the SEO Content Machine API (referred to generically as an API key credential).
  • The node makes authenticated HTTP requests to the SEO Content Machine API base URL.
  • Proper configuration of the API key credential within n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Providing an empty or invalid keyword may result in no content or error responses.
    • Network connectivity problems can prevent reaching the API endpoint.

  • Error messages:

    • Authentication errors typically indicate issues with the API key; verify the credential setup.
    • HTTP request errors may include status codes and messages from the API; check the keyword validity and API availability.
    • If the node throws an error referencing item index, it indicates which input caused the failure.

  • Resolutions:

    • Ensure the API key credential is correctly configured and active.
    • Validate the keyword input before running the node.
    • Check network access and API service status.

Links and References

Discussion