I'm assuming that your website must be focused entirely around static text content, like a blog. That type of website doesn't need any special treatment to be readable by web crawlers. I would expect a lightweight website like that to score great for on-page SEO metrics like page load time and (obviously) page weight. In other words, there would be nothing ...
There are a couple things you can do about it:
Add canonical tags to every page on your site. For example one of the pages on your site should have this tag in the <head> section:
<link rel=canonical href=https://www.mysurname.example/mped.html>
Doing this will let Google know which is the correct URL to index, even when it finds the same ...
It isn't dangerous. Looking at DNS, both those domains are hosted through cloudflare, so it likely a misconfiguration there.
If it bothers you it is possible to stop them displaying your content. Here is a technical answer https://security.stackexchange.com/questions/83362/how-can-i-stop-someone-from-displaying-my-website-on-his-domain You could ask the ...
The message you're receiving from Google "Indexed, not submitted in sitemap" is typical of any page Google finds through any means other than a sitemap. It's not an error.
If you only have one page, index.html and Google has already found it, you really don't need a sitemap. Sitemaps are not necessary in most cases and Google seems to prefer ...
Short answer, it won't have any negative impact on the SEO.
For more details
Because it prevents passing the referrer information to the target website, this will change the behavior from Google analytic traffic which will show the link as Direct Traffic instead of Referral from some website.
Have no impact at all, should always be used ...
According to the Mozilla website, about the «ARIA: heading role»:
The best way to use this role is to not use it at all, and instead use the native heading tags through as shown in the example above. The heading role and aria-level attribute should only be used to retrofit accessibility on legacy code that you cannot make major changes to.
Also, about ...
Semantic elements are parts of the current Html standard. With the correct syntax, these elements help search engines and browsers understand the hierarchical structure of a web page, and in turn displays this structure for users and this makes it easier to quickly browse the content and navigate to the user's goal. Also, semantic elements help screen ...
I would argue that the episode number and name are equally important since the user may know one or the other. Generally, in HTML, the document body is the main section of your HTML page and can only contain a single H1. In HTML5 the <section> element allows you to have multiple headers in the main document as long as they're within these section tags. ...
You're going to run into duplicate <h1> tags across other episode pages if the <h1> only includes creative work name.
Speaking of semantics, why are we using <div class="header"> when we have the <header> element?
The page should be constructed semantically with no consideration to layout or style at all. In my opinion the correct markup should be:
<h1>Creative work name</h1>
This makes the most sense to Google, and to screen-readers etc. Then simply use CSS to display the ...
Google is concerned with showing the result that matches the query of the user. I think that it's going to be rare that someone searches for a specific line of the lyrics to a song and expects to find the lyrics with chords.
I don't fully know what your site is about, but music, lyrics, and chords gives me enough to say that the following are likely going to ...
The size of your favicon must be a multiple of 48 pixels square, for example:
48 x 48 px
96 x 96 px
144 x 144 px
Don't use 16x16 size, Google will resize it automatically.
Define a favicon to show in search results
<link rel="icon" type="image/png" sizes="48x48" href="public/icon/favicon-48x48.png">
I still haven't found a clear answer for making icon links easily crawlable, however using JSON-LD the schema validators at least show the search engines will see the schema if you set it up correctly and know the name of the icon link that way.
As far as accessibility, all you need to do is add an aria-label to your icon link and screen readers will see it. ...