Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed favicon path #8070

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fixed favicon path #8070

wants to merge 2 commits into from

Conversation

squidfunk
Copy link
Owner

This PR ensures that the favicon path is absolute if site_url is set, and attempt to fix #8066.

@kamilkrzyskow
Copy link
Collaborator

This was the initial idea, taken from Google docs and W3Schools, however as mentioned later this site:

Has been using the site_url and favicon combo for 12 years.

Therefore it's unlikely that it would help with the detection in general 😞

It looks like currently the root domain favicon or lack of it will be prioritized over everything 😞

So the current solution is to add the favicon on the root domain or add a redirection, which works on GMC, or does it...?

GMC could also be using a cached icon from the time it did work and the redirection doesn't help on Google, just appears to help for now.

Apart of that the change LGTM. The docs could mention that using an user/organization level GitHub Pages https://pages.github.com/ additionally to the repository project page could help the most.

@squidfunk
Copy link
Owner Author

Thanks! Let's wait for 2 weeks and then check our search results. If it did not help, we can close this PR.

@niclasheinz
Copy link
Collaborator

Maybe I'm too stupid to understand the real problem here, but there is a “default” favicon set in the docs that no longer exists in the repository. In the docs there is a link to the default image , which no longer exists. In my opinion, the correct favicon is here. Plus, I can't see any favicon in the docs/assets folder.
Maybe this is just a problem with the documentation

@kamilkrzyskow
Copy link
Collaborator

The documentation issue is separate, but you're right that the old link wasn't updated after the switch to using the templates directory.

In 56b96b4 the theme data was moved, but for the end-user the way it's accessed stayed the same, as the templates directory became the root for the theme.

Plus, I can't see any favicon in the docs/assets folder.

You won't find it there because it's exposed as part of the theme, which you linked above

the correct favicon is here.

The theme root works like customization:

The files inside are merged with the final site build, the favicon is provided for all users by default.
You can see the favicon here, because the creators only configured the logo:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Favicon not displayed in Google Search Results
3 participants