Skip to content

Commit 9d1c722

Browse files
Fixed some typos. clarified writing and renamed KPIs not equal post.
1 parent fa4fbd5 commit 9d1c722

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

_posts/2024-03-07-targets-not-equal.md renamed to _posts/2024-03-07-kpis-not-all-equal.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,19 +19,20 @@ header:
1919

2020
# Not all KPIs are created equal #
2121

22-
I advocate for metrics tied to actual business value, like KPIs, but I sometime see these miss the mark.
22+
I advocate for metrics tied to actual business value, like KPIs, but I sometimes see these miss the mark.
2323

24-
For example, I worked with an eCommerce software company and was tasked with an SEO target of increasing the ranking of the site to increase revenue.
25-
This was in early 2016 when Google and other search engines weren't crawling single page applications properly, so the site was not appearing high up
26-
or at all in searches for our product catalogue.
24+
For example, I worked with an eCommerce software company and was tasked with meeting a SEO target of increasing the ranking of the site to increase revenue.
25+
This was in early 2016 when Google and other search engines weren't crawling single page applications properly. So the site was not appearing high up,
26+
or at all, in searches for our product catalogue.
2727

2828
On the surface this seems like a very reasonable target. We spent several weeks investigating rewriting parts of the single page application to
29-
pre-render server side to allow the search engines to crawl the data.
29+
pre-render server side to allow the search engines to crawl the data. This was going to be a radical rewrite which would take most of the engineering
30+
teams many months.
3031

3132
However, during this process we started to look at the data we had around our user profiles and the usage patterns on the site. The site sold high-end
3233
luxury fashion clothes and jewellery. The conversion rate was quite low but the average basket value was very high (> £30k).
3334

34-
By examining this data and devising a survey attached to the registration and checkout processes we determined that almost all of these high value clients were
35+
By examining this data and publishing a survey attached to the registration and checkout processes we determined that almost all of these high value clients were
3536
not even searching for our site through search engines. The traffic to the site was driven pretty evenly from fashion magazine advertising and
3637
social media posts.
3738

0 commit comments

Comments
 (0)