Google says:
Is there an easy way to fix this?Add a <link> tag to the header of your home page with the following syntax: <link rel="shortcut icon" href="/path/to/favicon.ico">
Thank you.
Is there an easy way to fix this?Add a <link> tag to the header of your home page with the following syntax: <link rel="shortcut icon" href="/path/to/favicon.ico">
There's no fix necessary as nothing is broken, but if it's important for you then just do as Google suggests, + for each style you're using.
<head>
section of the document, simply attempt to get /favicon.ico in case that file exists." And what Google is recommending here is "rather than depend on legacy behavior of individual web browsers, specify a favicon file name and path in the <head>
section instead."Code: Select all
<!-- begin EA117 custom favicon modifications -->
<link rel="apple-touch-icon" sizes="180x180" href="{T_THEME_PATH}/images/apple-touch-icon.png?v=zXbdKz68p3">
<link rel="icon" type="image/png" sizes="32x32" href="{T_THEME_PATH}/images/favicon-32x32.png?v=zXbdKz68p3">
<link rel="icon" type="image/png" sizes="16x16" href="{T_THEME_PATH}/images/favicon-16x16.png?v=zXbdKz68p3">
<link rel="manifest" href="{T_THEME_PATH}/images/site.webmanifest?v=zXbdKz68p3">
<link rel="mask-icon" href="{T_THEME_PATH}/images/safari-pinned-tab.svg?v=zXbdKz68p3" color="#5bbad5">
<link rel="shortcut icon" href="{T_THEME_PATH}/images/favicon.ico?v=zXbdKz68p3">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="theme-color" content="#ffffff">
<!-- end EA117 custom favicon modifications -->
Code: Select all
<link rel="shortcut icon" href="/path/to/favicon.ico" />
Code: Select all
<link rel="shortcut icon" href="/path/to/favicon.ico">
From what I understand, nothing "should" care whether
<link>
was given a self-closing tag indication in HTML5 like phpBB styles generate by default. But that doesn't really answer whether Google "did" care, or what they might have done or dropped in response to that. I might also try running a validator like https://validator.w3.org/ against the page, just to make sure there isn't some kind of other subtle un-closed tag that is affecting the interpretation of the subsequent <link>
tag, without being "an issue with the syntax of the <link>
tag itself."Yes, most any placement before the
<head>
tag closes should be fine, including that one.If you're not seeing the
<style>
tag used literally inside the overall_header.html template itself, then I would suspect what you're seeing is a <style>
block being output by one of the extensions. Either during the overall_header_head_append
or overall_header_stylesheets_after
events, or through the INCLUDECSS
directive, which become output where you see the {$STYLESHEETS}
reference in overall_header.html.<style>
tag in the rendered HTML document, and making an educated guess based on the names of the classes or elements its attempting to style.The report seems to be calling out simply the difference betweenChinaGal wrote: ↑Wed Mar 11, 2020 9:37 pm On the second and third errors they are related to a link we added into to the footer, which links to a topic on our site about copyright. So it seems it doesn't like the format of the URL that phhBB creates for topics. Is there any way I can change the format of the URL so it doesn't cause these errors?
<a href=viewtopic.php?f=2&t=260>Full Disclaimer</a>
and <a href="viewtopic.php?f=2&t=260">Full Disclaimer</a>
. i.e. The value of the href= attribute is not in quotes. Is that not actually the case?<style>
block which uses <style type="text/css">
as its opening tag, and then cut and paste everything from that opening <style type="text/css">
tag to the countervailing </style>
tag, we might be able to guess which extension based on the class names or elements targeted by the contained CSS.<style type="text/css">
block. It's not necessarily being done that way, but it's one of the possibilities to check and rule out.Guidelines
You must follow these guidelines to be eligible for a favicon next to your search results. Note that a favicon isn't guaranteed in search results even if all guidelines are met.
Both the favicon file and the home page must be crawlable by Google (that is, they cannot be blocked to Google).
Your favicon should be a visual representation of your website's brand, in order to help users quickly identify your site when they scan through search results.
Your favicon should be a multiple of 48px square, for example: 48x48px, 96x96px, 144x144px and so on. SVG files, of course, do not have a specific size. Any valid favicon format is supported. Google will rescale your image to 16x16px for use in search results, so make sure that it looks good at that resolution. Note: do not provide a 16x16px favicon.
The favicon URL should be stable (don’t change the URL frequently).
Google will not show any favicon that it deems inappropriate, including pornography or hate symbols (for example, swastikas). If this type of imagery is discovered within a favicon, Google will replace it with a default icon.
How did it go for you? We're having similar issues on our site. For us, Google has reverted back to a very old Favicon which we have completely removed from our server years ago so it seems there is a bit of an issue on their end at the moment.
Unfortunately our Favicons are still not showing in any Google search results. We even moved the Google code to the very top of the head in the file and used search console to resubmit our site map to Google to try to get them to crawl again, but still no change on the favicon issue. If we search in DuckDuckGo though then we see our favicon come up within search results for our site.Forex Station wrote: ↑Fri Mar 20, 2020 5:59 pmHow did it go for you? We're having similar issues on our site. For us, Google has reverted back to a very old Favicon which we have completely removed from our server years ago so it seems there is a bit of an issue on their end at the moment.