Google Search Icon of Website is not set up correctly

[maxstridde]

In the google serach my own blog as well as the current al folio version only has this standard globe icon (see below). Id love to be able to change this icon to make my page look more professional. Id be happy to have it be the same icon selected in the config file as the favicon or an own pic or another emoji (potentially the same if left blank for example.

What are your thoughts on this? I have not found any similar discussion or issue here. Should I open a feauture request?

vs the Favicon

[george-gca]

According to Google's documentation:

---

Add a tag to the header of your home page with the following syntax:

<link rel="icon" href="/path/to/favicon.ico">

For historical reasons, we also support shortcut icon, which is an earlier, alternative version of icon.

---

And we add this version in our template:

al-folio/_includes/head.liquid

Lines 69 to 76 in 8815d40

	{% if site.icon.size <= 4 %}
	<link
	rel="shortcut icon"
	href="data:image/svg+xml,<svg xmlns=%22http://www.w3.org/2000/svg%22 viewBox=%220 0 100 100%22><text y=%22.9em%22 font-size=%2290%22>{{ site.icon }}</text></svg>"
	>
	{% elsif site.icon != blank %}
	<link rel="shortcut icon" href="{{ site.icon | prepend: '/assets/img/' | relative_url | bust_file_cache}}">
	{% endif %}

Not sure if simply changing to icon fixes that. And note that you can ask Google to recrawl your site.

[maxstridde]

I do not really understand exactly, whats going on in that passage. I assume the link tag is supposed to be constructed. Google mentions that "shortcut icon" is supported for legacy reasons, so maybe something else is wrong?

Or do you think, google did not recreawl the al folio website since then? Ill try and test some things on my blog in the next days.

[george-gca]

Yes, it is where the link tag is constructed. This is liquid language, used by Jekyll, and it is the basis of our template site. Like I said, maybe just changing this from shortcut icon to icon fixes it, but I am not sure.

If you want to learn more about the liquid language and how this code works, maybe this is a good test for the AI solutions we recently added to our repository. I haven't tested them thoroughly myself, but they seem to be good at explaining parts of the code. I added a link for them in our main README file (CodeWiki and DeepWiki), more specifically: