Viewing a response to: @pennsif/py06wp
it appears on STeemit and the other frontends but Alexa only notices when the content is accessed through Steemit.com
author | shadowspub |
---|---|
permlink | py1252 |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2019-09-18 12:46:15 |
last_update | 2019-09-18 12:46:15 |
depth | 3 |
children | 10 |
last_payout | 2019-09-25 12:46:15 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 117 |
author_reputation | 630,597,952,562,629 |
root_title | "Falling out with Alexa and making friends with Google - write as if your steem life depended on it..." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 90,695,283 |
net_rshares | 0 |
The issue here is one of "canonical URL"; the originating website of a post. This has been discussed a few times within the Leo chatroom because it was noticed that steemit.com is claiming as canonical posts that do not originate from its own site. This should be of concern to all platforms and to tribe websites. The setting is placed in the post header and the webmaster must know how the setting works and what to do about ensuring it retains canonical status if a post originates from somewhere other than steemit. Google is not the dumbest company on the planet and can tell the difference between theft and article farms (lol) and, if there are conflicts between the canonical status of a post it will use other metrics. I also noted that even if an article is posted from a tribe site, the timestamp of the Steemit "copy" is 3 seconds *before* it appears on the tribe site. These are all issues that a webmaster should be aware of.
author | onecent |
---|---|
permlink | py1b8y |
category | steem |
json_metadata | {"tags":["steem","steemleo"],"app":"steemleo/0.1"} |
created | 2019-09-18 16:02:57 |
last_update | 2019-09-18 16:02:57 |
depth | 4 |
children | 9 |
last_payout | 2019-09-25 16:02:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 945 |
author_reputation | 16,446,725,825,074 |
root_title | "Falling out with Alexa and making friends with Google - write as if your steem life depended on it..." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 90,701,499 |
net_rshares | 0 |
That is very interesting. The issue of the canonical URL will be ever more important for tribes to pull in new users of their content via organic search engines. I wonder where this needs to go to be explored and optimised...
author | pennsif |
---|---|
permlink | pya7ie |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2019-09-23 11:20:39 |
last_update | 2019-09-23 11:20:39 |
depth | 5 |
children | 2 |
last_payout | 2019-09-30 11:20:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 227 |
author_reputation | 636,410,097,572,565 |
root_title | "Falling out with Alexa and making friends with Google - write as if your steem life depended on it..." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 90,850,789 |
net_rshares | 0 |
I was told that steempress have long had a delay between publishing to the internet and then to the steem blockchain, precisely to allow their URL to propagate. Perhaps tribes need to look into something similar, perhaps with an edit-lock for however many seconds it takes to broadcast their canonical url. I wonder if a new aggregator would be a good idea. One that shows the originating website of each post, say with the tribe or platform logo in a corner. :-)
author | onecent |
---|---|
permlink | pybqgd |
category | steem |
json_metadata | {"tags":["steem","steemleo"],"app":"steemleo/0.1"} |
created | 2019-09-24 07:07:33 |
last_update | 2019-09-24 07:07:33 |
depth | 6 |
children | 1 |
last_payout | 2019-10-01 07:07:33 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.053 HBD |
curator_payout_value | 0.053 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 466 |
author_reputation | 16,446,725,825,074 |
root_title | "Falling out with Alexa and making friends with Google - write as if your steem life depended on it..." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 90,879,377 |
net_rshares | 495,293,589,689 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
accelerator | 0 | 495,293,589,689 | 21% |
My point was that Alexa is not seeing the post appear on Steemit.com .. it's seeing and tracking the visitors ... so when people visit the other frontends that shows increased visitors to that frontend which is a corresponding decrease to Steemit.com I don't consider that a bad thing because the ecosystem is the traffic that really matters and those other frontends are just access points as well. So, seeing a drop in steemit.com's Alexa ranking is not an indication of Steem's decline when the other frontends rankings are climbing. It's more an indication of the distribution of attention across the ecosystem.
author | shadowspub |
---|---|
permlink | py30ne |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2019-09-19 14:09:15 |
last_update | 2019-09-19 14:09:15 |
depth | 5 |
children | 5 |
last_payout | 2019-09-26 14:09:15 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 619 |
author_reputation | 630,597,952,562,629 |
root_title | "Falling out with Alexa and making friends with Google - write as if your steem life depended on it..." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 90,731,505 |
net_rshares | 0 |
True, but is the opposite of what I replied to ;-) Organic growth of visitors to the tribes is good, but those coming from a search engine are likely to be directed to the steemit version of an article, even if not the originating platform - and that has to do with what is considered the canonical url.
author | onecent |
---|---|
permlink | py34lx |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2019-09-19 15:34:45 |
last_update | 2019-09-19 15:34:45 |
depth | 6 |
children | 0 |
last_payout | 2019-09-26 15:34:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 304 |
author_reputation | 16,446,725,825,074 |
root_title | "Falling out with Alexa and making friends with Google - write as if your steem life depended on it..." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 90,734,073 |
net_rshares | 0 |
Do you think the distribution to the other front ends will impact on the potential advertising revenue from steemit.com? I wonder if some shared ad revenue model needs to be explored?
author | pennsif |
---|---|
permlink | pya7ky |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2019-09-23 11:22:12 |
last_update | 2019-09-23 11:22:12 |
depth | 6 |
children | 3 |
last_payout | 2019-09-30 11:22:12 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 184 |
author_reputation | 636,410,097,572,565 |
root_title | "Falling out with Alexa and making friends with Google - write as if your steem life depended on it..." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 90,850,825 |
net_rshares | 0 |