Catalog / hyre.no
64

SEO audit for hyre.no

Hyre | Lei bil enkelt med mobilen fra 399,- døgnet

other

Health 64/100 (fair) · 50 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

Tusenvis av leiebiler i Oslo, Bergen, Trondheim, Stockholm og København

Screenshot of hyre.no
50
pages crawled
47
indexable pages
2
errors
124
warnings
391
notices
0
orphan pages
1
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Crawlability 98 1 0 0
Links 98 1 0 0
Canonical 72 0 47 0
Performance 72 0 47 97
Duplicate 92 0 13 12
Headings 96 0 6 5
Agent Readiness 98 0 4 49
Content 98 0 4 54
Images 99 0 1 30
Indexability 99 0 1 0
Titles 99 0 1 11
Cache 100 0 0 47
Meta Description 100 0 0 18
Security 100 0 0 58
Sitemap 100 0 0 3
Structured Data 100 0 0 2
URL 100 0 0 5
Findings

Errors (2 rules)

error Broken internal link (target 4xx/5xx)

Rule links.broken_internal · Links · 1 occurrence(s)

error Client error (4xx) response

Rule status.4xx · Crawlability · 1 occurrence(s)

Warnings (10 rules)

warning Control has no accessible name

Rule agent.control_no_name · Agent Readiness · 4 occurrence(s)

warning Missing canonical tag

Rule canonical.missing · Canonical · 47 occurrence(s)

warning Thin content (low word count)

Rule content.thin · Content · 4 occurrence(s)

warning Duplicate page content

Rule duplicate.content · Duplicate · 2 occurrence(s)

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 11 occurrence(s)

warning Missing <h1>

Rule h1.missing · Headings · 6 occurrence(s)

warning Images missing alt text

Rule images.missing_alt · Images · 1 occurrence(s)

warning Hero/LCP image is lazy-loaded (loading=lazy delays LCP)

Rule images.no_lazy_lcp_candidate · Performance · 47 occurrence(s)

  • https://www.hyre.no/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2Fsummer_campaign-beach-square2.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/artikler/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2FGemini_Generated_Image_av2mhoav2mhoav2m.png&w=2048&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/artikler/af-energi-byttet-til-bildeling/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2FEIK_2087.JPG&w=2048&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/bergen/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2Fbz4x_no.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/flesland/ — the likely hero/LCP image (ikon-dinosaur.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/flyplass/ — the likely hero/LCP image (ikon-dinosaur.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/gardermoen/ — the likely hero/LCP image (ikon-dinosaur.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/jobbprofil/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=%2F_next%2Fstatic%2Fmedia%2Fjobbprofil-cropped2.36236349.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/karriere/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Fimages%2FId4_in_city_summer.width-1000.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/karriere/skadebehandler-deltid/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=%2F_next%2Fstatic%2Fmedia%2Ffooter-illustration-2.5d0671e5.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/lastned/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2Fno-app-lastned.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/oslo/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2FPolestar_no.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/priser/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2Fcupra-born-2_1.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/sameie/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2Fcupra-born-2_1.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/slett-brukerkonto/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=%2F_next%2Fstatic%2Fmedia%2Ffooter-illustration-2.5d0671e5.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/stavanger/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2Fvw_ID4_69CNjuk.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/telia/ — the likely hero/LCP image (chevron-right.a44cad92.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/trondheim/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2FFord_Explorer_no.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/vaernes/ — the likely hero/LCP image (ikon-dinosaur.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/varebil-bergen/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2Fproace_ev_no.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/varebil-oslo/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2Fproace_ev_no.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/varebil-trondheim/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2Fproace_ev_no.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/varebil/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=https%3A%2F%2Fcms-backend-uploads.s3.amazonaws.com%2Foriginal_images%2Fford_e-transit.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/vilk%C3%A5r/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=%2F_next%2Fstatic%2Fmedia%2Ffooter-illustration-2.5d0671e5.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hyre.no/vilk%C3%A5r/personvernerkl%C3%A6ring/ — the likely hero/LCP image (https://www.hyre.no/_next/image/?url=%2F_next%2Fstatic%2Fmedia%2Ffooter-illustration-2.5d0671e5.png&w=3840&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.

warning Page is noindex

Rule index.noindex · Indexability · 1 occurrence(s)

warning Title likely truncated in SERP (too wide)

Rule title.too_long · Titles · 1 occurrence(s)

Notices (24 rules)

notice Heading levels skip a level

Rule agent.heading_skip · Agent Readiness · 46 occurrence(s)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

  • https://www.hyre.no/ — no llms.txt found at the site root — add one so AI agents get a curated site summary

notice No main landmark for AI agents

Rule agent.no_main_landmark · Agent Readiness · 2 occurrence(s)

notice Page served uncached (no-store/private or CDN bypass)

Rule cache.not_cacheable · Cache · 47 occurrence(s)

notice Low text-to-HTML ratio

Rule content.low_ratio · Content · 42 occurrence(s)

notice Main text is hard to read (low Flesch Reading Ease)

Rule content.readability_poor · Content · 12 occurrence(s)

  • https://www.hyre.no/artikler/ — this page reads as difficult (Flesch Reading Ease 45, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/artikler/af-energi-byttet-til-bildeling/ — this page reads as difficult (Flesch Reading Ease 49, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/bedrift/hjelp/azuread/ — this page reads as difficult (Flesch Reading Ease 42, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/erstatningsbil/ — this page reads as difficult (Flesch Reading Ease 37, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/jobbprofil/ — this page reads as difficult (Flesch Reading Ease 48, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/karriere/utvikler/ — this page reads as difficult (Flesch Reading Ease 48, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/om-oss/ — this page reads as difficult (Flesch Reading Ease 48, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/om-oss/aapenhetsloven/ — this page reads as very difficult (Flesch Reading Ease 28, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/personvernerklaering/ — this page reads as difficult (Flesch Reading Ease 37, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/slett-brukerkonto/ — this page reads as difficult (Flesch Reading Ease 48, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/vilk%C3%A5r/ — this page reads as difficult (Flesch Reading Ease 46, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.hyre.no/vilk%C3%A5r/personvernerkl%C3%A6ring/ — this page reads as difficult (Flesch Reading Ease 37, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 12 occurrence(s)

notice Multiple <h1> elements

Rule h1.multiple · Headings · 5 occurrence(s)

notice Image alt text is very long (possible keyword stuffing)

Rule images.alt_too_long · Images · 2 occurrence(s)

notice Images without width/height (layout shift / CLS)

Rule images.missing_dimensions · Images · 28 occurrence(s)

notice Meta description too long

Rule meta_desc.too_long · Meta Description · 10 occurrence(s)

notice Meta description too short

Rule meta_desc.too_short · Meta Description · 8 occurrence(s)

notice Large HTML document

Rule perf.large_html · Performance · 2 occurrence(s)

notice No ETag header (no conditional GET for unchanged pages)

Rule perf.no_etag · Performance · 47 occurrence(s)

  • https://www.hyre.no/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/artikler/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/artikler/af-energi-byttet-til-bildeling/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/bergen/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/flesland/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/flyplass/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/gardermoen/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/jobbprofil/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/karriere/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/karriere/skadebehandler-deltid/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/lastned/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/oslo/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/priser/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/sameie/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/slett-brukerkonto/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/stavanger/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/telia/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/trondheim/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/vaernes/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/varebil-bergen/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/varebil-oslo/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/varebil-trondheim/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/varebil/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/vilk%C3%A5r/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.hyre.no/vilk%C3%A5r/personvernerkl%C3%A6ring/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.

notice No Last-Modified header (no conditional GET for unchanged pages)

Rule perf.no_last_modified · Performance · 47 occurrence(s)

  • https://www.hyre.no/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/artikler/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/artikler/af-energi-byttet-til-bildeling/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/bergen/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/flesland/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/flyplass/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/gardermoen/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/jobbprofil/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/karriere/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/karriere/skadebehandler-deltid/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/lastned/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/oslo/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/priser/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/sameie/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/slett-brukerkonto/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/stavanger/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/telia/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/trondheim/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/vaernes/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/varebil-bergen/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/varebil-oslo/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/varebil-trondheim/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/varebil/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/vilk%C3%A5r/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.hyre.no/vilk%C3%A5r/personvernerkl%C3%A6ring/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.

notice Slow server response

Rule perf.slow_response · Performance · 1 occurrence(s)

notice Deep page has no BreadcrumbList structured data

Rule schema.breadcrumb_missing · Structured Data · 2 occurrence(s)

notice Missing recommended security headers

Rule security.missing_headers · Security · 48 occurrence(s)

notice target=_blank link without rel=noopener (tab-napping)

Rule security.unsafe_cross_origin_links · Security · 10 occurrence(s)

  • https://www.hyre.no/bedrift/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hyre.no/bedrift/kom-i-gang/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hyre.no/bergen/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hyre.no/en/oslo/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hyre.no/haugesund/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hyre.no/hyre-pass/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hyre.no/oslo/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hyre.no/priser/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hyre.no/stavanger/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hyre.no/trondheim/ — 1 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".

notice Indexable page not listed in sitemap

Rule sitemap.orphan_not_listed · Sitemap · 3 occurrence(s)

notice Title tag is identical to the H1 (missed keyword variation)

Rule title.same_as_h1 · Titles · 2 occurrence(s)

notice Title is very short

Rule title.too_short · Titles · 9 occurrence(s)

notice Non-ASCII characters in URL path

Rule url.non_ascii · URL · 2 occurrence(s)

notice Underscores in URL path (prefer hyphens)

Rule url.underscores · URL · 3 occurrence(s)

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
https://www.hyre.no/
Hyre | Lei bil enkelt med mobilen fra 399,- døgnet		 200 yes 931 45
https://www.hyre.no/oslo/
Enkel tilgang på leiebil i Oslo fra 399,- døgnet		 200 yes 1059 41
https://www.hyre.no/bedrift/
Hyre for Bedrift | Enklere leiebil for hele bedriften		 200 yes 897 44
https://www.hyre.no/flyplass/
Enkel tilgang på leiebil på Oslo, Bergen og Trondheim lufthavn fra 399,-		 200 yes 579 44
https://www.hyre.no/priser/
Checkmark		 200 yes 668 44
https://www.hyre.no/karriere/
Se ledige stillinger i Hyre og søk i dag		 200 yes 194 42
https://www.hyre.no/erstatningsbil/
Oppdag erstatningsbil fra Hyre		 200 yes 871 41
https://www.hyre.no/hyre-pass/
Checkmark		 200 yes 1471 41
https://www.hyre.no/artikler/
Artikler om Hyre og mobilitet		 200 yes 1104 40
https://www.hyre.no/bergen/
Checkmark		 200 yes 847 40
https://www.hyre.no/drammen/
Enkelt tilgang på leiebil i Drammen		 200 yes 472 40
https://www.hyre.no/haugesund/
Enkelt tilgang på leiebil i Haugesund		 200 yes 513 40
https://www.hyre.no/hjelp/
Vanlige spørsmål og svar		 200 yes 2249 40
https://www.hyre.no/om-oss/
Om Hyre | Nordens største bildelingstjeneste		 200 yes 963 40
https://www.hyre.no/p-plass/
Vi i Hyre vokser og har behov for nye parkeringsplasser. Fyll ut skjemaet og tips oss i Hyre!		 200 yes 148 40
https://www.hyre.no/sameie/
Få bildeling i ditt nabolag eller sameie		 200 yes 646 40
https://www.hyre.no/stavanger/
Enkelt tilgang på leiebil i Stavanger		 200 yes 727 40
https://www.hyre.no/trondheim/
Checkmark		 200 yes 885 40
https://www.hyre.no/varebil/
Lei en varebil fra 229,- timen		 200 yes 620 40
https://www.hyre.no/vilk%C3%A5r/
Vilkår for bruk av Hyre		 200 yes 220 40
https://www.hyre.no/vilk%C3%A5r/personvernerkl%C3%A6ring/
Personvernerklering for Hyre		 200 yes 2077 40
https://www.hyre.no/en/
Hyre		 200 yes 3305 15
https://www.hyre.no/en/oslo/
Access to rental cars in Oslo from 399,- per day		 200 yes 1073 4
https://www.hyre.no/slik-fungerer-hyre/
Slik fungerer leiebil med Hyre		 200 yes 611 7
https://www.hyre.no/erstatningsbil/erstatningsbil-mollerbil-sor/
Driver erstatningsbil med egen bilflåte		 200 yes 812 2
https://www.hyre.no/artikler/af-energi-byttet-til-bildeling/
AF Energi byttet til bildeling. Bra både for miljøet og bunnlinja.		 200 yes 755 2
https://www.hyre.no/flesland/
Enkel tilgang på leiebil på Bergen airport, Flesland fra 399,- døgnet		 200 yes 575 4
https://www.hyre.no/gardermoen/
Enkel tilgang på leiebil fra Gardermoen, Oslo lufthavn fra 399,- døgnet		 200 yes 583 4
https://www.hyre.no/vaernes/
Lei bil på Trondheim lufthavn, Værnes fra 399,- døgnet		 200 yes 573 4
https://www.hyre.no/bedrift/kom-i-gang/
Hyre		 200 yes 311 3
https://www.hyre.no/karriere/utvikler/
Hyre		 200 yes 583 1
https://www.hyre.no/om-oss/aapenhetsloven/
Slik møter Hyre åpenhetsloven - Hyre		 200 yes 1016 1
https://www.hyre.no/en/articles/af-energy-switch-to-car-sharing/
AF Energy switched to car sharing. Good for profits and the environment.		 200 yes 799 1
https://www.hyre.no/bedrift/hjelp/azuread/
Autentisere Azure AD for synkronisering av ansattliste		 200 yes 257 1
https://www.hyre.no/hidden_hmp_calculator_v2_beta/
Hyre		 200 yes 151 0
https://www.hyre.no/jobbprofil/
Opprett jobbprofil på Hyre		 200 yes 426 0
https://www.hyre.no/karriere/skadebehandler-deltid/
Hyre søker skadebehandler, deltid		 200 yes 648 0
https://www.hyre.no/lastned/
Last ned Hyre-appen		 200 yes 335 0
https://www.hyre.no/lillehammer/
Enkelt tilgang på leiebil i Lillehammer		 200 yes 2775 0
https://www.hyre.no/medlemmer/
Inviter medlemmer til Hyre for Bedrift		 200 yes 389 0
https://www.hyre.no/personvernerklaering/
Personvernerklering for Hyre		 200 yes 2077 0
https://www.hyre.no/slett-brukerkonto/
Sletting av brukerkonto på Hyre		 200 yes 183 0
https://www.hyre.no/storefront/how-it-works/
Hyre		 200 yes 1074 0
https://www.hyre.no/telia/
Kom i gang med Hyre		 200 yes 346 0
https://www.hyre.no/varebil-bergen/
Lei varebil i Bergen fra 249,- timen		 200 yes 586 0
https://www.hyre.no/varebil-oslo/
Lei varebil i Oslo fra 249,- timen		 200 yes 620 0
https://www.hyre.no/varebil-trondheim/
Lei varebil i Trondheim fra 249,- timen		 200 yes 584 0
https://www.hyre.no/en/business/help/azuread/ 404 no 0 1
https://www.hyre.no/hyre_for_telia.pdf 200 no 0 1
https://www.hyre.no/hyre_for_telia_admin.pdf 200 no 0 1

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →