blockscout / frontend

Front-end application for Blockscout
https://blockscout.com
GNU General Public License v3.0
170 stars 462 forks source link

ETH - SEO Tweaks for Gas Tracker Page #2340

Open maikReal opened 1 week ago

maikReal commented 1 week ago

We are experimenting with a new initiative by tweaking pages to help rank them better on Google. The following suggestions are recommended to be added to FE for Gas Tracker Page in order to get a higher listing based on rich text and optimizations. We will attempt this for ETH instance and if it works well we can proceed with others. For full research on this please take a look at this notion page

Blockscout suggested additions for “ETH Gas”

isstuev commented 1 week ago

I'm just going to leave this here Image

isstuev commented 1 week ago

I also disagree with adding current gas price to the H1. A static H1 is generally better for SEO, as constantly changing headers can hinder indexing and ranking consistency.

isstuev commented 1 week ago

I don't quite get what to do with 'SEO suggestions' and 'Enhanced snippets' part, it's not like we can just put an invisible text somewhere and make it work. Also I didn't find an 'enhanced snippet' definition, there is a 'featured snippet' and there is no specific way to make our snippet 'featured' Image

isstuev commented 1 week ago

Also I found out that it's not recommended to use brands in the FAQ (if it's for SEO purposes) Because the idea is to provide answers to the popular questions, and a question 'How can I check Ethereum gas fees using Blockscout' is probably less popular than 'How can I check Ethereum gas fees'

maikReal commented 1 week ago

@TheD0SH Can you pls check the comments above?

TheD0SH commented 1 week ago

I'm just going to leave this here Image

Yes i saw this as well but its still being utilized within the rich-text check, why show this if its not being used? Up to you really if we want to proceed here

I also disagree with adding current gas price to the H1. A static H1 is generally better for SEO, as constantly changing headers can hinder indexing and ranking consistency.

number 1 result is ES, they have it right within the H1, 2nd result Blocknative same here. What suggestion do you have here that could help us rank? image

I don't quite get what to do with 'SEO suggestions' and 'Enhanced snippets' part, it's not like we can just put an invisible text somewhere and make it work. Also I didn't find an 'enhanced snippet' definition, there is a 'featured snippet' and there is no specific way to make our snippet 'featured' Image

The idea behind the featured/enhanced snippet is to create a subtitle under H1 or some relative text that can include those words. I know it hinders the UX but maybe something along these lines could work wyt? image

Also I found out that it's not recommended to use brands in the FAQ (if it's for SEO purposes) Because the idea is to provide answers to the popular questions, and a question 'How can I check Ethereum gas fees using Blockscout' is probably less popular than 'How can I check Ethereum gas fees'

Feel free to tweak the text as you see fit, after all this is a test to see if we can produce any results on our ranking.

isstuev commented 1 week ago

Yes i saw this as well but its still being utilized within the rich-text check, why show this if its not being used?

I don't see any connection in their docs between reach text and AMP, they are separate parts of the doc. In general, AMP is a lighter version of a website, like one more web app. It shows less content, uses less JS, etc (that's not for our case). And it's a separate app, not just some meta-tags on an existing page.

isstuev commented 1 week ago

What suggestion do you have here that could help us rank?

I checked Google Search console and found out that URL https://eth.blockscout.com/gas-tracker wasn't indexed at all. I requested indexing, but it looks like the first problem we have to sold here is how to make google index that page

isstuev commented 1 week ago

we can start with fixing sitemap (it doesn't work for the mainnet rn) and I also proposed a fix for our navigation markup