HINODE.COM.BR Website-Rezension

Indizierte Seiten

Bing:
Google:

Seiteninformationen

Titel:
Loja Oficial Hinode | Beleza, Maquiagem, Fragrâncias e muito mais
Länge: 65 Zeichen; Beste Länge: 10 ~ 60 Zeichen

Der HTML-Titeltag ist eines der wichtigsten Elemente der On-Page-SEO und erscheint in Suchergebnissen, Browser-Tabs und Lesezeichen.

Ihr Titel-Tag scheint nicht die ideale Länge zu haben.

Die Suchergebnisse von Google kürzen Titel, die länger als 60 Zeichen sind. Die Suchergebnisse von Bing kürzen Titel, die länger als 70 Zeichen sind.

Hier sind die Best Practices für Meta-Titel:

  • Beschränken Sie sich bei der Titellänge auf 10–60 Zeichen.
  • Machen Sie Schlüsselwörter/Schlüsselphrasen deutlich
  • Integrieren Sie relevante Power-Wörter
  • Seien Sie klar, aber präzise
Meta-Beschreibung:
Na loja virtual da Hinode você encontra os melhores fragrâncias, maquiagens, produtos para o corpo e rosto. Acesse agora e compre de qualquer lugar do Brasil!
Länge: 158 Zeichen; Beste Länge: 50 ~ 160 Zeichen
Meta-Schlüsselwörter:
Länge: 0 Zeichen; Beste Länge: 10 ~ 255 Zeichen

The length of your meta keywords seems to be outside the recommended range. Ideally, a meta keywords should be between 10 and 255 characters, including spaces.

Meta keywords are a specific type of meta tag that appear in the HTML code of a web page. They provide information to search engines about the topic of the page. Meta keywords were once used to help rank web pages in search engine results. However, due to the abuse by webmasters and marketers, Google claims to have stopped using them more than a decade ago. Despite this, there are still reasons to consider using meta keywords:

  • Uncertain Impact on Google's Algorithm: While Google devalued meta keywords, it is uncertain if they were entirely removed from its ranking algorithm. Google keeps its ranking algorithms top secret to deter people from gaming the system.
  • Other Search Engines and CMS: Other search engines like Yandex, Baidu, and Naver may still use meta keywords. Additionally, some internal CMS search systems, such as SOLR and Algolia, also utilize the meta keywords tag.

Best practices for Meta Keywords

  • Relevance is Key: It is crucial to choose keywords that accurately reflect the content of your page.
  • Keep it Limited: It is generally recommended not to exceed more than 10 meta keywords for a single page. Also, the content length should not exceed 255 characters (including spaces).
  • Consider Long-Tail Keywords: Long-tail keywords are more specific and longer phrases that target a niche audience. These keywords can be highly effective in driving targeted traffic to your website.

Remember, meta keywords are just one aspect of search engine optimization (SEO), and search engines now place less emphasis on them compared to other factors. However, by following these best practices, you can still optimize your meta keywords effectively and improve the visibility of your web pages.

H1 Tag:
Länge: 0 Zeichen; Beste Länge: 10 ~ 255 Zeichen

Your page does not include an H1 tag.

The H1 tag in HTML is the main headline users see first when a page loads. It conveys the page's topic, enticing visitors to read further. H1 tags are crucial for SEO, user experience, and accessibility. They distinguish the main title on a webpage, aiding search engines and users in understanding the content.

Here are best practices for H1 tags

  • Use H1 tags for page titles.
  • Limit to one H1 tag per page.
  • Keep H1 tags short and concise.
  • Structure headings hierarchically.
  • Include your main keyword.
  • Ensure H1 tags are engaging.

Site-Technologie

Server:
nginx
SSL-gesichert:
Verfügbar
robots.txt:
Nicht verfügbar
XML-Sitemap:
Nicht verfügbar
Gzip-Komprimierung:
Verfügbar
favicon.ico:
Nicht verfügbar

HTTP-Header-Analyse

HTTP-Header-Felder sind Bestandteile des Nachrichtenheaders von Anfragen und Antworten im Hypertext Transfer Protocol (HTTP). Sie definieren die Betriebsparameter einer HTTP-Transaktion. Die Header-Felder werden von normalen Webbrowsern wie Internet Explorer, Google Chrome, Firefox usw. nicht direkt angezeigt. Nachfolgend finden Sie die HTTP-Header-Informationen von hinode.com.br:
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Date: Tue, 13 Jan 2026 04:43:00 GMT
X-VTEX-Cache-Backend-Connect-Time: 0.000
X-VTEX-Cache-Backend-Header-Time: 0.151
Server: nginx
Cache-Control: public, max-age=626, s-maxage=60, stale-while-revalidate=1200, stale-if-error=3600
Content-Encoding: gzip
ETag: "57A8DD01E7605789EA32F2535EF2A2B1"
X-VTEX-Janus-Router-Backend-App: io-production-vstore-group-2-1d-4rt
X-Router-Cache: MISS
X-Vtex-Io-Cluster-Id: prod-dj-iostore-eks-use1d-4rt
X-Frame-Options: SAMEORIGIN
x-vtex-product: store
x-vtex-renderer: render@8
x-vtex-etag-control: public, max-age=626
Link: ; rel="dns-prefetch",; rel="preconnect"; crossorigin,; rel="dns-prefetch",; rel="dns-prefetch",; rel="dns-prefetch"
X-Vtex-Router-Elapsed-Time: 00:00:00.1485167
X-Request-ID: 60e1071f806446bb83ff6acc295f7dc4
X-Vtex-Router-Version: 9.17.17
X-Vtex-Backend-Elapsed-Time: 00:00:00.1467517
X-VTEX-Cache-Status: MISS
X-Powered-By-VTEX-Cache: 2.6.1
X-VTEX-Cache-Server: ip-10-203-75-181.ec2.internal
X-VTEX-Cache-Time: 0.151
Vary: accept-encoding
X-Cache: Hit from cloudfront
Via: 1.1 3cee1b61334bd8139fe0ff6d7079a1e4.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: JFK50-P15
X-Amz-Cf-Id: WWvWbsQWHevm4pHVIAYoJfLAskQ9Z4r-a-iJJtjls7Nfe33jb7wECQ==
Age: 45

DNS-Eintragsanalyse

Domain Name Systes (DNS) übersetzt leicht zu merkende Domänennamen in numerische IP-Adressen, die zum weltweiten Auffinden von Computerdiensten und Geräten erforderlich sind. Es gibt insgesamt 24 DNS-Einträge von hinode.com.br.
Gastgeber Typ IP/Ziel TTL Zusätzliche Informationen
hinode.com.brA300
hinode.com.brA300
hinode.com.brNS21600
hinode.com.brNS21600
hinode.com.brSOA1800expire: 604800
serial: 2392462370
hinode.com.brMX300pri: 10
hinode.com.brMX300pri: 5
hinode.com.brMX300pri: 1
hinode.com.brMX300pri: 10
hinode.com.brMX300pri: 5
hinode.com.brTXT
y5v79vwpswnm7t2ycwsd508dk9pqk3lk
300
hinode.com.brTXT
google-site-verification=YvHle52JJeMFpcTE6VlUizvT1rI7orEcZWe-DcgZIno
300
hinode.com.brTXT
vk2zydbwk1zd3cxl73r2kj9ts5t0crkf
300
hinode.com.brTXT
google-site-verification=6dwvBEZHlA7TRqmCALAVCbAYy24vhLOG3i4xAkIOQrk
300
hinode.com.brTXT
google-site-verification=i4u2HyzCPF5Bc6OwCVcO930HP1z4MgoFKGRbC1Sazx4
300
hinode.com.brTXT
google-site-verification=_tmsFnbr7uJJTH5YBHPF7iyydUODTxxs_bP5UsN0QYw
300
hinode.com.brTXT
google-site-verification=tJD1TSUDWNCzjG7VZt0r5QU6m-n_jUHPtBAbgURKyTc
300
hinode.com.brTXT
google-site-verification=zvHo9vkfWZSTQnwgFdPVWtkGsBx4R_G_bBDXsuVUrb0
300
hinode.com.brTXT
N2IzMjY4ZTk2NzE0MWVmYTMzZGFjNzc5YTE0MjVmYjM=
300
hinode.com.brTXT
v=spf1 include:_spf.rdstation.com.br include:sendgrid.net ~all
300
hinode.com.brTXT
gbzcfvg0xmw2r30hbpt5hkwzy8t7zny4
300
hinode.com.brTXT
e6a1ab51edd04c8ab8d82325aa3159ef
300
hinode.com.brAAAA
2606:4700:3032::ac43:b2dd
300
hinode.com.brAAAA
2606:4700:3030::6815:11ef
300