|
1 | | - |
2 | | -## 2x-ing upper-funnel content |
| 1 | +## Nail the content growth review |
3 | 2 |
|
4 | 3 | **Owner:** Natalia Amorim |
5 | 4 |
|
6 | | -**Motivation:** We want to build a repeatable system for refreshing existing content and expand our upper-funnel library to capture more organic traffic. The goal is to make our content engine more sustainable, ensuring older articles stay current while consistently adding new ones that meet users earlier in their discovery journey. |
| 5 | +**Motivation:** The foundation exists, but we need this to be a real, recurring ritual that actually shapes what we do. |
7 | 6 |
|
8 | 7 | **What we'll ship:** |
9 | | - |
10 | | -* Test AirOps as a tool to refresh existing articles at scale, optimizing them for both traditional search and LLM visibility. This includes updating metadata, improving page structure for LLM readability, refreshing content, and ensuring all PostHog features and positioning are current. |
11 | | -* Create new upper-funnel content (alternatives, listicles, etc.) that targets high-volume keywords and attracts users in the awareness and consideration stages across all product categories. |
| 8 | +- Monthly Content Growth Review on a locked-in cadence |
| 9 | +- Streamlined reporting that pulls SEO, AEO, and newsletter metrics into one place |
| 10 | +- A clear "so what" section with actionable next steps that feed into planning |
12 | 11 |
|
13 | 12 | **We'll know we're successful when:** |
| 13 | +- We've run the review every month this quarter, no skips |
| 14 | +- Insights from reviews have meaningfully influenced content decisions |
| 15 | +- The team knows where we stand without needing to ask |
14 | 16 |
|
15 | | -* We’ve established a repeatable refresh workflow that improves LLM visibility and keeps articles accurate and current. |
16 | | -* We have strong upper funnel content coverage capturing high-volume searches across all product categories |
17 | | -* LLM outputs reflect accurate, up-to-date info about PostHog. |
18 | | -* We see steady growth in visibility from both traditional search and LLM outputs. |
19 | | - |
20 | | -## Sharpening our AEO strategy |
| 17 | +## New upper-funnel content on a consistent cadence |
21 | 18 |
|
22 | 19 | **Owner:** Natalia Amorim |
23 | 20 |
|
24 | | -**Motivation:** We want to ensure PostHog is represented accurately and prominently in LLM outputs by tracking prompts, monitoring citations, and running experiments to see how optimized and new content can influence the answers these models generate. |
25 | | - |
26 | | -**What we'll ship** |
27 | | - |
28 | | -* Roll out an AEO tracking tool to monitor prompts and citations at both a general and per-product level. |
29 | | -* Run a Q4 “blitz” on error tracking as treatment vs control to measure AEO impact before scaling. |
30 | | - * Create and/or optimize content specifically for LLMs |
31 | | - * Pilot YouTube as an AEO lever via prescriptive creator briefs |
32 | | - |
33 | | -**We'll know we're successful when** |
34 | | - |
35 | | -* We have end-to-end visibility on how PostHog shows up in LLMs across products |
36 | | -* Key competitor and product prompts consistently surface PostHog in accurate, positive ways and echo our developer tool positioning |
37 | | -* We can measure the impact of AEO efforts and expand proven tactics across product lines. |
38 | | - |
39 | | -## Better reporting on content performance |
40 | | - |
41 | | -**Owner:** Natalia Amorim |
42 | | - |
43 | | -**Motivation:** Right now, performance data is scattered and often looked at in isolation. We want to introduce a structured monthly content performance review to give the team clearer visibility across products, spot trends, and use those insights to guide planning, prioritization, and decision-making. |
44 | | - |
45 | | -**What we'll ship** |
46 | | - |
47 | | -* A recurring monthly content review |
48 | | -* Dashboards and supporting materials |
| 21 | +**Motivation:** We need a sustainable rhythm for LLM/SEO-optimized content production that balances growth with maintenance. |
49 | 22 |
|
50 | | -**We'll know we're successful when** |
| 23 | +**What we'll ship:** |
| 24 | +- New upper-funnel content on a consistent cadence |
| 25 | +- Ongoing optimization of existing articles, including refreshing metadata, updating positioning, improving structure for LLM readability, and ensuring PostHog features are current |
51 | 26 |
|
52 | | -* The team has clear visibility into how content is performing at both an overall and per-product level. |
53 | | -* Everyone can access and understand key metrics without needing to dig. |
54 | | -* Insights from reviews consistently shape our content planning and prioritization. |
| 27 | +**We'll know we're successful when:** |
| 28 | +- New articles are ranking first page for target keywords |
| 29 | +- Optimized articles show measurable improvement in traffic, rankings, or citations/mentions post-refresh |
| 30 | +- This feels like a system, not a scramble |
55 | 31 |
|
56 | | -## Newsletter |
| 32 | +## More people writing newsletters |
57 | 33 |
|
58 | | -**Owner:** Ian Vanagas |
| 34 | +**Owner:** Jina Yoon |
59 | 35 |
|
60 | | -**Motivation:** We've scaled back our paid acquisition with the newsletter, because it was bringing in low quality subscribers and clouding our ability to understand how the newsletter is performing. If we want the newsletter to be successful for the long term, we need it to grow organically. |
| 36 | +**Motivation:** A lot of the responsibility for the newsletter has been with a small set of people, there are many more people at PostHog who could contribute, whether that is through research or literally writing articles. |
61 | 37 |
|
62 | 38 | **What we'll ship:** |
63 | | - |
64 | | -- A great newsletter every two weeks |
65 | | -- Audit of subscriber list to remove inactive subs |
66 | | -- 3 social (primarily LinkedIn) posts per newsletter to build our social posting muscle |
| 39 | +- A better, clearer contribution guide |
| 40 | +- Newsletters by people other than Ian, Andy, Charles, and James |
| 41 | +- Internal efforts to encourage people to write newsletters (onboarding item, promoting in `#tell-posthog-anything`, etc.) |
| 42 | +- Social promotion of those newsletters by them too |
67 | 43 |
|
68 | 44 | **We'll know we're successful when:** |
| 45 | +- Jina ships at least two newsletters |
| 46 | +- Four people outside our regular contributors ship (or scheduled to ship) a newsletter (Jina and Cleo are already scheduled, so we need 2 more) |
| 47 | +- We've got people lined up to work with us on newsletters, it's clearer how to work with us. |
69 | 48 |
|
70 | | -- We're growing our newsletter audience organically |
71 | | -- We are confident the newsletters we are publishing are performing well |
72 | | - |
73 | | -## Better high-level messaging |
| 49 | +## New series |
74 | 50 |
|
75 | 51 | **Owner:** Ian Vanagas |
76 | 52 |
|
77 | | -**Motivation:** We’ve had a lot of changes in terms of positioning of the company lately and that has left a scattering of messaging across our site, content, and how we talk about ourselves. |
| 53 | +**Motivation:** Series help us publish high quality content with less effort and gives something for readers to look forward to |
78 | 54 |
|
79 | 55 | **What we'll ship:** |
80 | | - |
81 | | -- A marketing handbook page with key messaging, such as |
82 | | - - What is PostHog? |
83 | | - - What are the benefits of using PostHog? |
84 | | - - Why use PostHog over other options? |
85 | | -- Update pages that talk about these things to be consistent |
86 | | -- A statement we can use everywhere |
| 56 | +- A plan for a multi-part newsletter series (maybe "how we AI at PostHog") |
| 57 | +- At least one post from a new newsletter series |
87 | 58 |
|
88 | 59 | **We'll know we're successful when:** |
| 60 | +- We've published at least the first post in the new series |
| 61 | +- Have plans for the next few posts in the series |
| 62 | +- Readers want more |
89 | 63 |
|
90 | | -- Our own team and content is using this messaging more |
91 | | -- We hear that messaging back from users |
92 | | -- People on social media use this messaging, instead of "product analytics" |
93 | | - |
94 | | -## Ship the product engineer handbook this time |
| 64 | +## Social posters unite |
95 | 65 |
|
96 | | -**Owner:** Andy |
| 66 | +**Owner:** Ian Vanagas |
97 | 67 |
|
98 | | -**Motivation:** We want to completely own the concept of the Product Engineer by creating its central text. We're 80% of the way there. Need to ship final 20%. |
| 68 | +**Motivation:** Our team ships all the time, we should be posting all the time too |
99 | 69 |
|
100 | 70 | **What we'll ship:** |
| 71 | +- Daily posts on LinkedIn from Ian and others promoting the newsletter. |
| 72 | +- Regular posts from people outside editorial, with help from us (posting templates, ghostwriting, etc.) |
| 73 | +- Hire a social person and get them up to speed |
| 74 | +- Test more native content as well as channels like X and Reddit |
101 | 75 |
|
102 | | -* Intro chapters of the handbook using a similar structure to the company handbook. |
103 | | - |
104 | | -**We'll know we're successful when** |
105 | | - |
106 | | -* We've shipped the first version of the guide |
107 | | -* Positive initial reaction from our users and readers |
108 | | -* Ranking for product engineer keywords in search |
109 | | -* Incoming users convert to reading other parts of guide |
110 | | -* Converting handbook readers to subscribers of the newsletter |
111 | | - |
112 | | -## Anti-goals |
113 | | - |
114 | | -* Digital PR (both on the community side with Reddit and GitHub, and on the PR outreach side for publications); it's something that could help us move the needle with LLMs, but not a priority in the short or medium term. |
115 | | -* Multimedia product comparisons. Could be a strategic advantage, not something we have capacity to take on right now |
116 | | -* Figuring out long term newsletter strategy |
| 76 | +**We'll know we're successful when:** |
| 77 | +- We're driving significant amounts of traffic and subscribers from social |
| 78 | +- We feel we've built the posting muscle internally |
| 79 | +- We know the next phase of social we want to focus on |
0 commit comments