Workflows· SEO & AI Visibility

    The Blog SEO Track

    The Blog SEO Track automatically checks every blog draft for SEO issues as soon as it enters review and leaves a prioritized list of optimization suggestions directly in the CMS.

    automatingreviewing

    Description

    Steps

    Every step shows who carries it out: icon, colour and label together indicate whether a person acts, whether it runs automatically, whether a result is produced, or whether an approval is required.

    01Person

    A blog draft receives the status Draft or Review in the CMS.

    02Automated

    03Automated

    04Automated

    05Automated

    06Result

    Key
    PersonAutomatedResultApproval

    Requirements and operations

    Requirements

    • CMS WordPress, Webflow or Contentful, with status trigger and comment function.
    • Team chat Slack, Teams or Discord for the content channel.
    • Keyword tool (optional) Ahrefs, SEMrush or similar, for search volume in the prioritization.
    • LLM access API key for OpenAI, Claude or Gemini.

    Testing

    • Test draft Set up a test draft of around 500 to 1000 words with a clean heading structure and set the status to Draft.
    • Draft fetch Check whether title, content, meta description and target keyword are loaded in full.
    • Analysis and prioritization Check whether the suggestions are concrete and cleanly separated into Critical, Important and Optional.
    • Edge cases Test very short and very long drafts, a missing meta description, a missing target keyword and multilingual content.

    Go-live

    • Approve Activate the workflow only once trigger, suggestion list and CMS comment work cleanly together.
    • Guidelines Enrich the prompt with target audience, tone and your own content guidelines.
    • Mandatory field Maintain the target keyword as a mandatory field per article in the CMS.
    • Expand Extend the workflow as needed with competitor analysis, a reading score, keyword research or A/B headlines.

    Common issues

    • Workflow does not start Check the CMS webhook and the status filter for the draft.
    • Comment is not created Check the write permissions in the CMS and the comment format.
    • Suggestions too generic Enrich the prompt with target audience and content guidelines.
    • Meta over 155 characters Enforce the length strictly in the prompt and validate it in addition.

    Builder Prompt

    GOAL
    Build a workflow that automatically checks every blog draft for SEO as soon as it receives the status Draft or Review in the CMS: analysis of keywords, heading structure, meta description, linking and readability, resulting in a prioritized list of concrete optimization suggestions saved directly as a comment on the draft in the CMS.
    
    Adapt the structure to the concepts of your automation tool (for example nodes, steps, zaps or agent actions). While doing so, preserve the trigger logic, the sequence and the data flow.
    
    TRIGGER
    Type: CMS webhook (WordPress, Webflow or Contentful).
    Condition: A draft receives the status Draft or Review.
    
    STEPS (sequential)
    1. Fetch draft: load title, full content, current meta description and, if available, the target keyword from the CMS.
    2. AI step: SEO analysis and suggestions. Insert the working prompt "SEO Analysis and Suggestions" exactly as given (see the Working Prompts section). Result: a prioritized suggestion list (Critical, Important, Optional) and an optimized meta description.
    3. Save comment in CMS: save the suggestion list as a structured comment directly on the draft.
    4. Output: notify the content team in the team chat, with a link to the draft and a brief overview of the number of critical points.
    
    PROMPT GUIDANCE
    There is a fixed working prompt for the analysis step, see the Working Prompts section. Insert it unchanged and in full into step 2.
    
    DATA FLOW
    Trigger to step 1: draft ID or link to the draft.
    Step 1 to step 2: blog title, blog content, current meta description, target keyword as input for the corresponding placeholders in the working prompt.
    Step 2 to step 3: prioritized suggestion list and optimized meta description.
    Trigger to step 4: link to the draft.
    
    ERROR HANDLING
    Workflow does not start: check the CMS webhook and the status filter (Draft/Review).
    No target keyword set: run the analysis anyway and note the missing keyword in the comment. The target keyword should be maintained as a mandatory field in the CMS.
    Comment is not created: check the write permissions in the CMS and the comment format.
    Meta description suggestion over 155 characters: validate the length, regenerate once if exceeded.
    Suggestions too generic: enrich the prompt with target audience and content guidelines, as an optional configuration.
    Very long draft (token limit): split into sections and merge the results.
    
    PLACEHOLDER CONVENTION
    All placeholders in square brackets in the input section of the working prompt are variables and are mapped fully dynamically from the CMS: blog title, blog content, meta description and target keyword, as described in the data flow. There are no manual prompt placeholders. The square brackets in the output format of the working prompt are formatting instructions to the language model and remain unchanged. Only the CMS access, the status filter and the notification channel are configured manually.
    
    SELF CHECK BEFORE COMPLETION
    Check, before you report the workflow as finished:
    1. Are all steps connected correctly, and does the trigger fire only for the status Draft and Review?
    2. Is the working prompt inserted in full and unchanged, and are all CMS fields mapped correctly?
    3. Does the comment land structured on the correct draft, and is the meta length validated?
    4. Are all points listed that require manual configuration: CMS webhook and write permissions, target keyword as a mandatory field, notification channel and LLM access?

    Working prompts

    Prompt: SEO Analysis and Suggestions

    Checks the blog draft for SEO-relevant points and returns a prioritized list of concrete optimization suggestions plus an optimized meta description.

    You are an SEO expert for [COMPANY]. Analyze the following blog draft and create concrete optimization suggestions. Address the user in a professional manner throughout, wherever your output includes a form of address.
    
    INPUT
    Blog title: [BLOG_TITLE]
    Blog content: [BLOG_CONTENT]
    Current meta description: [META_DESCRIPTION]
    Target keyword (if available): [TARGET_KEYWORD]
    
    WORKING INSTRUCTIONS
    Conduct a comprehensive SEO analysis and check:
    1. Keyword optimization: primary and secondary keywords, keyword density, placement.
    2. Heading structure: H1, H2, H3, hierarchy and keyword integration.
    3. Meta description: length, call to action, keyword usage.
    4. Readability: sentence length, paragraph structure, subheadings.
    5. Internal and external linking opportunities.
    6. Alt texts for images, if mentioned in the content.
    
    Create a list of prioritized optimization suggestions in the following format:
    
    Critical (implement immediately):
    - [Concrete suggestion with example]
    
    Important (recommended):
    - [Concrete suggestion with example]
    
    Optional (nice to have):
    - [Concrete suggestion with example]
    
    Optimized meta description (maximum 155 characters):
    [Your suggestion]
    
    If information is missing, for example no target keyword is set, mark your assumption as such instead of making it silently. Be specific, actionable, and briefly justify each suggestion.

    JSON export

    Setup

    Two routes lead to the same result. Pick the one that fits your setup.

    Suitable when you want to build the workflow in your own automation tool.

    1. Open your workflow tool, for example n8n, Make, Zapier or Langdock.
    2. Create a new workflow and give it a name.
    3. Choose the AI-assisted build option if your tool offers one.
    4. Paste the builder prompt from above in full.
    5. Check the result against the step sequence in this document, then add your access credentials and channels.

    Suitable when you want to take the workflow over unchanged.

    1. Download the JSON file from the JSON export section.
    2. Open the workflow area of your tool and create a new workflow.
    3. Give it a name and confirm.
    4. Open the menu on the workflow name and choose to import a JSON file.
    5. Upload the file, then add your own access credentials.
    6. Run a test before you activate the workflow.

    Last reviewed:

    In the workshop this becomes your method.

    A single prompt becomes a repeatable method. We show that in the workshop From Prompt to Method.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call