# Turning your blog posts into LinkedIn Posts

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.

<figure><img src="/files/RB5jp02AnhRndEFRqHk4" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="/files/Mv71ysY9x0nQf4jFC3Va" alt=""><figcaption></figcaption></figure>

With these quick adjustments, you’ll have a LinkedIn post optimized for engagement and perfectly tailored to your audience.

<figure><img src="/files/Y9CRlYzVOvHE79Qqt13E" alt=""><figcaption></figcaption></figure>

### Approving Publishing Your LinkedIn Post

<figure><img src="/files/sibwqMonHZFsqvaqe7Fy" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="/files/ifUipd5nJGQIvVfYiBzw" alt=""><figcaption></figcaption></figure>

### 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: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dapta.ai/marketing-studio/turning-your-blog-posts-into-linkedin-posts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.