Feedback Needed on New Blog Writing Agent for Clients

David M. · 2025-10-28T17:58:22.340Z

:party_blob:Hey Lindy Community!:party_blob: I would love your feedback on this blog writing agent. Background: I built this agent so that my clients could request a blog article and have it written for them and then eventually posted to their website with very little intervention from my team. :typingcat: All you need to do is add a new line of information to a Google Sheet and then the agent checks the sheet daily and if it finds new information added, it will run the agent and produce a blog article. I made a quick video that walks through the agent (https://www.loom.com/share/302d23d429de44eaa09e4459450b2da2). <<-- Click to see the video (3 minutes) MY ASK: I would love your feedback on how I could improve this agent and make it better. Are there additional Lindy integrations that can help with SEO, better writing, or anything?? I would love any feedback you have.

Feedback Needed on New Blog Writing Agent for Clients | Lindy Community

4 comments

· Sorted by Oldest

michael r.
·
·
appreciate the build update! we helped a client build out their own blog post writing agent and some things you may enjoy trying: 1️⃣ try seo specific integrations
(attached) data for seo integration (haven't used it personally, but always good to benchmark what you're doing in perplexity v. a specific integration for SEO keywords)
2️⃣ separate SEO from AEO
you could take keywords and pass those to a google search to see what top results are in google to build a reference knowledge base when designing the specific blog post for what already ranks
for AEO you could create another branch, or additional nodes that help turn keywords into QA, as much of AEO ends up being well referenced writing that's relevant to an AI Agent or AI web tool reading the web
maybe for your clients publish a separate blog just for AEO that's LLM friendly and optimized
3️⃣ add in images
with new generate image node with Nano Banana and Imagen, you could generate images or even figures
here's library of a bunch of use cases to see what nano banana can do for inspiration
4️⃣ add in a voice/brand guideline to make sure blog post is specific to your client
you can pull from a google doc (if more dynamic and client facing edit) or enrich in the LLM Call Prompt with examples of voice and tone through guidelines and examples
this helps make it specific to the voice of the client and not general LLM optimized text
5️⃣ add in an editing node
use a smarter model, like sonnet 4.5 to play an adversarial role in editing a piece to make sure it's more specific and interesting than one shotting a blog post
you can then feed the feedback into another writing node
excited to see it plug into wordpress for automatic publishing
Loading attachments
David M.
·
·
michael r., this is super helpful! I am going to start working on this now. Also, there is a WP app within Lindy that I found that has a “Create Post” action. I used this inside the Lindy Computer and it posted a draft article for me from a Google Doc. It did not format the headings correctly on my first run, so that I what I am going to be working on next. But I am super excited that it works. I can’t wait until I have and end to end blog posting agent that will do all the steps for me!
🔥1
michael r.
·
·
for formatting you can try markdown or other formats that WP node may import easier looking forward to seeing the update!
David M.
·
·
True… I did specify to the Lindy Computer this last time to take into consideration the formatting (H1, H2) of the Google doc and it uploaded it correctly this time!
👍1

michael r.
·
·
appreciate the build update! we helped a client build out their own blog post writing agent and some things you may enjoy trying: 1️⃣ try seo specific integrations
(attached) data for seo integration (haven't used it personally, but always good to benchmark what you're doing in perplexity v. a specific integration for SEO keywords)
2️⃣ separate SEO from AEO
you could take keywords and pass those to a google search to see what top results are in google to build a reference knowledge base when designing the specific blog post for what already ranks
for AEO you could create another branch, or additional nodes that help turn keywords into QA, as much of AEO ends up being well referenced writing that's relevant to an AI Agent or AI web tool reading the web
maybe for your clients publish a separate blog just for AEO that's LLM friendly and optimized
3️⃣ add in images
with new generate image node with Nano Banana and Imagen, you could generate images or even figures
here's library of a bunch of use cases to see what nano banana can do for inspiration
4️⃣ add in a voice/brand guideline to make sure blog post is specific to your client
you can pull from a google doc (if more dynamic and client facing edit) or enrich in the LLM Call Prompt with examples of voice and tone through guidelines and examples
this helps make it specific to the voice of the client and not general LLM optimized text
5️⃣ add in an editing node
use a smarter model, like sonnet 4.5 to play an adversarial role in editing a piece to make sure it's more specific and interesting than one shotting a blog post
you can then feed the feedback into another writing node
excited to see it plug into wordpress for automatic publishing
Loading attachments
David M.
·
·
michael r., this is super helpful! I am going to start working on this now. Also, there is a WP app within Lindy that I found that has a “Create Post” action. I used this inside the Lindy Computer and it posted a draft article for me from a Google Doc. It did not format the headings correctly on my first run, so that I what I am going to be working on next. But I am super excited that it works. I can’t wait until I have and end to end blog posting agent that will do all the steps for me!
🔥1
michael r.
·
·
for formatting you can try markdown or other formats that WP node may import easier looking forward to seeing the update!
David M.
·
·
True… I did specify to the Lindy Computer this last time to take into consideration the formatting (H1, H2) of the Google doc and it uploaded it correctly this time!
👍1