Skip to content

Commit 231bf57

Browse files
committed
Tweak to blog post structure
1 parent 73ee304 commit 231bf57

3 files changed

Lines changed: 17 additions & 28 deletions

File tree

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,24 @@
11
---
22
layout: post
3-
title: Increase Like button clicks on informational websites
4-
permalink: increasing-like-button-clicks/
3+
title: Increase Like Button Clicks
4+
permalink: increase-like-button-clicks/
55
---
66
A colleague of mine [Ross](http://rosstavendale.com/) suggested an interesting idea for increasing social sharing on informational websites. By placing social sharing buttons alongside key content, rather than at the top or bottom of a page, it highlights specific sections of a page that are likely to be shared. This approach could potentially boost the rate at which users interact with social sharing buttons, especially the Facebook Like button, ultimately expanding visibility and followers on Facebook.
77

88
> I wanted to explore how this could work and understand its potential benefits—this took a bit more digging
99
1010
While it’s common for e-commerce websites to boost Like button clicks using Facebook Open Graph mark-up (e.g., declaring products as objects and placing share buttons alongside), this method is tailored to single-product pages. A great example of this is [ASOS](http://www.asos.com) where products are shared easily through social media.
1111

12-
However, the question arose: How does this work on informational sites, where you're not sharing a product but rather specific sections of a page without compromising the message of the page as a whole? This was the aspect that intrigued me, and I wanted to understand how sites were pulling this off—and if there were any potential SEO implications.
12+
However, the question arose: How does this work on informational sites, where you're not sharing a product but rather specific sections of a page without compromising the message of the page as a whole? This was the aspect that intrigued me, and I wanted to understand how sites were pulling this off—and if there were any potential SEO implications.
1313

1414
Let’s explore an example Ross shared with me: [Britain Magazine](http://www.britain-magazine.com/).
1515

16-
Britain Magazine boosts Facebook Like button clicks by adding the ability to share individual quotes on a page. The challenge, however, is that only one set of Open Graph mark-up can be applied to a page. This means that the entire page would need to be focused on a single quote, despite containing other valuable content.
17-
16+
Britain Magazine boosts Facebook Like button clicks by adding the ability to share individual quotes on a page. The challenge, however, is that only one set of Open Graph mark-up can be applied to a page. This means that the entire page would need to be focused on a single quote, despite containing other valuable content.
17+
1818

1919
##How do they achieve this?
20-
It’s quite simple! They use one Like button for the homepage and then link to unique URLs for each quote. These URLs feature their own relevant Open Graph mark-up.
21-
20+
It’s quite simple! They use one Like button for the homepage and then link to unique URLs for each quote. These URLs feature their own relevant Open Graph mark-up.
21+
2222
This method ensures that every quote has its own unique URL. The visitor is not technically sharing the quote itself, but the unique URL for that quote—something the typical user won't notice. The actual URL being shared can be seen within the iFrame.
2323

2424
##The user journey
@@ -27,8 +27,8 @@ This method ensures that every quote has its own unique URL. The visitor is not
2727
- The visitor shares a unique URL [http://www.britain-magazine.com/special-post/quotes/alfred-tennyson/](http://www.britain-magazine.com/special-post/quotes/alfred-tennyson/), which only provides a single quote and no other content
2828

2929
## A great idea with wider implications*
30-
- SEO Benefits: Google will crawl these unique URLs, meaning each quote could be indexed as a separate page.
31-
- Improved User Experience: When shared, users land on a page with just the quote and navigation, rather than the original section of the homepage.
30+
- SEO Benefits: Google will crawl these unique URLs, meaning each quote could be indexed as a separate page.
31+
- Improved User Experience: When shared, users land on a page with just the quote and navigation, rather than the original section of the homepage.
3232
- Increased Engagement: This method likely increases Like button clicks across the site, helping boost overall engagement with your content.
3333

34-
Essentially, this strategy provides an effective way to increase Like button clicks, improve visibility, and enhance brand interaction. While it may offer minimal SEO value and potential indexing issues (unless spider controls like noindex are used), it’s still a clever and creative way to encourage social sharing and engagement.
34+
Essentially, this strategy provides an effective way to increase Like button clicks, improve visibility, and enhance brand interaction. While it may offer minimal SEO value and potential indexing issues (unless spider controls like noindex are used), it’s still a clever and creative way to encourage social sharing and engagement.

_posts/2022-02-17-product-roadmaps.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,11 @@ permalink: product-roadmaps
66

77
I wanted to share some thoughts on how our product management team has approached one of the most divisive topics in the product community: product roadmaps.
88

9-
---
109

1110
## What was the aim?
1211

1312
> Improve our current product roadmap so everyone across the business can understand what problems we intend to solve for users, in what order, and have some indication of when a customer *might* see these changes.
1413
15-
---
1614

1715
## What problem were we looking to solve?
1816

@@ -28,21 +26,19 @@ The survey revealed that people found the roadmap unclear. Specifically, we hadn
2826
- When people might expect to see these changes
2927
- Consistency in the level of detail provided
3028

31-
---
3229

3330
## How did we action the changes?
3431

3532
We assumed that changing too much at once could create confusion. When solving multiple problems simultaneously, there’s always a risk of introducing new ones. To avoid this, we decided to work incrementally, starting with the existing format.
3633

37-
### Our process:
34+
### Our process
3835

3936
1. **Surveyed the business** to gather likes and dislikes about the current roadmap.
4037
2. Held a **session with senior management** to understand their needs.
4138
3. **Proposed and got approval** for recommended changes.
4239
4. **Collaborated with product managers** to refine the updates.
4340
5. **Communicated updates** to the company and provided guidance on the new roadmap.
4441

45-
---
4642

4743
## Roadmap qualities
4844

@@ -57,11 +53,10 @@ We introduced several key changes to make the roadmap clearer and more actionabl
5753
- **Consistent granularity** between items to improve readability.
5854
- **Links to opportunity assessments** for evaluating the value of ideas.
5955

60-
### Example internal roadmap:
56+
### Example internal roadmap:
6157

6258
[![13PrMX.md.png](https://iili.io/13PrMX.md.png)](https://freeimage.host/i/13PrMX)
6359

64-
---
6560

6661
## What about a public roadmap?
6762

@@ -77,7 +72,6 @@ However, we’re working on an alternative public roadmap format for our communi
7772

7873
[![13P4Pn.md.png](https://iili.io/13P4Pn.md.png)](https://freeimage.host/i/13P4Pn)
7974

80-
---
8175

8276
## What’s next?
8377

_posts/2024-07-17-five-adages-product-managers.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,6 @@ I recently came across these adages while browsing the web, and they resonated w
1414

1515
Let’s explore each one and how you can apply them in your role as a Product Manager.
1616

17-
---
1817

1918
### Murphy’s Law
2019

@@ -23,55 +22,51 @@ Let’s explore each one and how you can apply them in your role as a Product Ma
2322
2423
This may sound gloomy, but I’ve found it to be a helpful mindset—especially after first hearing it in *Interstellar*.
2524

26-
#### How to Apply It:
25+
#### How to Apply It
2726
- **Expect Challenges:** Working in software means recognizing that not everything is within your control. While you can manage certain aspects, you often depend on others (e.g., usable designs, reliable code) to ensure success.
2827
- **Plan for Edge Cases:** Invest time in planning. Consider potential issues by discussing designs and implementations with engineers, always keeping the customer perspective in mind.
2928
- **Stay Positive:** When things go wrong (and they will), approach problems with energy and positivity. Engage the right people to address the issue. View setbacks as opportunities to learn rather than as failures.
3029

31-
---
3230

3331
### Gilbert’s Law
3432

3533
> “The biggest problem with any task or job is that no one tells you what and how to do it.”
3634
3735
Fun fact: Gilbert also happens to be my father-in-law’s name!
3836

39-
#### How to Apply It:
37+
#### How to Apply It
4038
- **Be Organized:** As a Product Manager, it’s your job to bring structure to ambiguity. Before diving into new work, take a moment to map out what’s needed to move from problem to solution.
4139
- **Communicate Clearly:** Whether you’re using formal product development principles or a simple checklist, create a plan and share it with the right stakeholders. The plan can take as little as five minutes to draft, but its impact will be significant.
4240

43-
---
4441

4542
### Kidlin’s Law
4643

4744
> “If you write the problem down clearly, then the matter is half solved.”
4845
4946
I’m not sure where this adage originates, but it’s one of my favorites.
5047

51-
#### How to Apply It:
48+
#### How to Apply It
5249
- **Define the Problem:** Writing a clear, succinct problem statement is one of the hardest—and most crucial—tasks in product development. A well-defined problem helps prevent teams from jumping to solutions prematurely.
5350
- **Validate Understanding:** Replay the problem statement to your colleagues and customers. Is it specific? Is this the exact issue you want to solve?
5451
- **Iterate Confidently:** Once you’ve nailed the problem, you can start exploring solutions. Expect to discover new insights along the way—that’s part of the process.
5552

56-
---
5753

5854
### Wilson’s Law
5955

6056
> “Wealth is not an immediate goal but a byproduct of prioritizing knowledge and intelligence.”
6157
6258
This might sound counterintuitive at first, but there’s more to it than meets the eye.
6359

64-
#### How to Apply It:
60+
#### How to Apply It
6561
- **Focus on Growth:** Your value as a Product Manager increases with experience. Take on challenges that push you outside your comfort zone, and you’ll open doors to new opportunities.
6662
- **Redefine Wealth:** Wealth isn’t just about money. Roles that emphasize the product and people can be deeply rewarding. Also, don’t forget to prioritize what truly matters—like family and personal time.
6763

68-
---
6964

7065
### Falkland’s Law
7166

7267
> “Think about the things that are absolutely necessary.”
7368
7469
This adage is a game-changer for prioritization.
7570

76-
#### How to Apply It:
71+
#### How to Apply It
7772
- **Stay Focused:** Once you’ve identified a specific problem, resist the temptation to tackle unrelated issues. Stay disciplined and solve the problem you set out to address.

0 commit comments

Comments
 (0)