> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/marketing-studio/turning-your-blog-posts-into-linkedin-posts.md).
# Turning your blog posts into LinkedIn Posts
Turn an approved blog post into a LinkedIn post, adjust its title, tone and hashtags, then schedule a publishing date and mark it published.
Once your idea has been transformed into a blog post and approved, you can easily repurpose it into an optimized LinkedIn post tailored to your style and preferred length.
To do this, simply open the approved blog post and click **"Turn into: Linkedin post."** This option allows you to review and adjust the title, focus keywords, and other settings to match your goals.
You can also edit the title, focus keyword, and tone you want for the LinkedIn post. You can also choose the number of hashtags, decide whether to include emojis, and make any final edits to align with your writing style.
With these quick adjustments, you’ll have a LinkedIn post optimized for engagement and perfectly tailored to your audience.
### Approving Publishing Your LinkedIn Post
Once your LinkedIn post draft is approved, you can assign a **publishing date** and then click **"Mark as Published"** to finalize it. This allows you to schedule the post for release at your chosen time, ensuring it aligns with your content calendar and audience engagement strate.
### You’re All Set to Go! :rocket:
With your post scheduled and marked as published, you’re ready to share your content with the world. Great job, and happy posting!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dapta.ai/marketing-studio/turning-your-blog-posts-into-linkedin-posts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
