Scanned sites / lidea-seeds.hu / 2026-10-21-0929

lidea-seeds.hu scan from 2026-10-21 09:29:07 UTC DR 19

A newer scan exists. See the latest report for lidea-seeds.hu.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-10-21-0929

Scanned 2026-10-21 09:29:07 UTC, finished 2026-10-21 09:31:52 UTC

Site: https://lidea-seeds.hu/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

79/ 100Good

On October 21, 2026 the Site Spider crawled 103 pages and 33 assets of lidea-seeds.hu, starting from https://lidea-seeds.hu/. It scored 79 out of 100, a good result. 10 of 33 checks found something to fix, led by sitemap coverage (79), meta descriptions (50), title tags (30); 17 checks passed. Most of the points went to sitemap coverage (−6), meta descriptions (−5.1), title tags (−3.8). 6 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: Medium3 medium, 4 low and 1 info findings. See the security findings ↓

Pages crawled
103
Assets fetched
33
Status
Completed
Checks with issues
10 of 33
CoverageComplete crawl

136 of 136 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 7 link destinations on other sites were checked.

  • Title tags30 issues
    30 of 79 pages have title issues.
    −3.8 points
  • Meta descriptions50 issues
    50 of 79 pages have meta description issues.
    −5.1 points
  • HeadingsOK
    0 of 79 pages have heading issues.
  • Broken links4 issues
    8 internal links point at 4 broken URLs.
    −1 points
  • Links to other sites80 noted
    0 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 7 destinations checked.
  • Redirects20 issues
    20 redirecting URLs, 1 of them chained.
    −1 points
  • Non-200 responses4 issues
    24 URLs did not return a 2xx response. 24 of them are pages, 4 with an error status; the rest are assets or redirects.
    −0.5 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2 issues
    2 of 79 indexable pages have indexability warnings.
    −0.3 points
  • Image alt textOK
    0 of 330 image references have no alt attribute.
  • Heavy assetsOK
    0 assets larger than 500 KB among 33 fetched assets.
  • Orphan pages14 issues
    14 pages have no internal links pointing at them.
    −0.7 points
  • Sitemap coverage79 issues
    1 sitemap listing 0 URLs: 79 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −6 points
  • Internal link countsOK
    Internal link counts for 79 pages; none is a dead end or buried.
  • Thin content23 issues
    23 of 79 pages have fewer than 200 words.
    −2.3 points
  • Duplicate content4 issues
    1 group of pages with identical HTML.
    −0.4 points
  • URL format2 noted
    2 of 103 page URLs are harder to read, share or cache than they need to be.
  • Canonicals2 noted
    2 of 79 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 79 pages are open to search engines.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure46 noted
    46 of 79 pages could use the title, heading and snippet space better.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 79 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    No page carries structured data (79 indexable pages checked).
  • Near duplicatesOK
    No near duplicates among 79 pages with enough text to compare.
  • Soft 404sOK
    None of 79 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positions2 noted
    2 of 65 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 10 response headers recorded across 136 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 79 pages; 44 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • SpellingOK
    No unfamiliar lower-case words on 79 pages (English pages only).

Where this scan sits among all scanned sites

2301 sites, median 79%, average 78%

lidea-seeds.hu scores 79%, higher than 47% of the 2301 scanned sites. See the full ranking.

0581160%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 16 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 21 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 46 sites70%: 43 sites71%: 68 sites72%: 71 sites73%: 67 sites74%: 68 sites75%: 71 sites76%: 86 sites77%: 91 sites78%: 105 sites79%: 86 sites80%: 106 sites81%: 107 sites82%: 116 sites83%: 96 sites84%: 108 sites85%: 84 sites86%: 69 sites87%: 73 sites88%: 60 sites89%: 60 sites90%: 34 sites91%: 45 sites92%: 36 sites93%: 20 sites94%: 16 sites95%: 10 sites96%: 9 sites97%: 11 sites98%: 4 sites99%: 1 site100%: 70 sites79% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Your website has several SEO issues that need addressing, including broken links, missing meta descriptions, and redirects. Prioritize fixing these for improved SEO performance.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and SEO, negatively affecting your ranking.

    How: Review the broken links and either update them to point to existing pages or remove the links if the destination is no longer available.

    Evidence: https://lidea-seeds.hu/products/boostandgo-napraforgo answers 404, and 3 pages link to it with anchor text such as "BOOST&GO®".

    3 pages affected

    Depends on: If the destination was deleted on purpose, remove the links rather than redirecting to an unrelated page.

    Checks: broken-links

  2. 2

    Create and Update Meta Descriptions

    Why: Meta descriptions improve click-through rates and affect search rankings.

    How: Write unique meta descriptions for the 7 pages without them and revise those with issues.

    Checks: meta-descriptions

  3. 3

    Resolve Non-200 Responses

    Why: Non-200 status codes can hurt user experience and SEO indexing.

    How: Investigate the pages returning errors and address them by correcting the URLs or restoring the pages.

    Checks: status-codes

  4. 4

    Optimize Title Tags

    Why: Proper title tags help search engines understand your page content and improve SERP visibility.

    How: Shorten or enhance titles that are too long or too short, ensuring they are relevant to their respective pages.

    Checks: titles

  5. 5

    Improve Sitemap Coverage

    Why: A proper sitemap helps search engines index the site effectively.

    How: Update your sitemap to include all crawled pages to enhance discoverability.

    Checks: sitemap-coverage

  6. 6

    Address Indexability Warnings

    Why: Pages flagged with indexability warnings may not be properly indexed.

    How: Confirm the need for canonical tags on warned pages and implement them to prevent potential duplication problems.

    Evidence: 2 pages flagged: No canonical.

    2 pages affected

    Depends on: Confirm the pages really share a cause before changing them together.

    Checks: indexability

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

The website has critical security weaknesses, primarily a lack of essential HTTP response headers. These deficiencies could make it vulnerable to various attacks, including hijacking and data exposure. Immediate actions are recommended to enhance security.

  • 0 high
  • 3 medium
  • 4 low
  • 1 info
  1. 1

    Missing HSTS HeaderMedium

    Why it matters: Lack of HTTP Strict Transport Security may expose users to interception on initial HTTP connections.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Absence of a Content Security Policy can allow untrusted content to be loaded, risking XSS attacks.

    Fix: Add the header: Content-Security-Policy: default-src 'self'

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, the site is vulnerable to clickjacking attacks by being embedded in malicious frames.

    Fix: Add the header: X-Frame-Options: DENY

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Not having this header can allow browsers to misinterpret files, leading to script execution vulnerabilities.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-Policy HeaderLow

    Why it matters: Absence of a Referrer Policy exposes sensitive URL details to third-party sites.

    Fix: Add the header: Referrer-Policy: no-referrer

    Evidence: Referrer policy

  6. 6

    Server Version DisclosureLow

    Why it matters: Exposing server software versions can help attackers identify vulnerabilities.

    Fix: Configure the server to not disclose version in the 'server' or 'x-powered-by' headers.

    Evidence: Software version disclosure

  7. 7

    Third-Party Scripts Without SRILow

    Why it matters: Loading scripts from external sources without Subresource Integrity increases risk in case of compromise.

    Fix: Implement a strict Content-Security-Policy to control loading of third-party scripts, and consider using SRI where applicable.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions-Policy HeaderInfo

    Why it matters: Without this header, there is no limit on browser capabilities that could be exploited through injected scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(), camera=()

    Evidence: Permissions policy

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://lidea-seeds.hu/ → no strict-transport-security
    • https://lidea-seeds.hu/crops → no strict-transport-security
    • https://lidea-seeds.hu/csapatunk → no strict-transport-security
    • https://lidea-seeds.hu/lidea-1 → no strict-transport-security
    • https://lidea-seeds.hu/karrier → no strict-transport-security
    • https://lidea-seeds.hu/news → no strict-transport-security
    • https://lidea-seeds.hu/contact-us → no strict-transport-security
    • https://lidea-seeds.hu/news/lidea → no strict-transport-security
    • https://lidea-seeds.hu/news/kukorica → no strict-transport-security
    • https://lidea-seeds.hu/news/napraforgo → no strict-transport-security
    • https://lidea-seeds.hu/news/repce → no strict-transport-security
    • https://lidea-seeds.hu/news/cirok → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 79 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.

    • https://lidea-seeds.hu/ → no content-security-policy
    • https://lidea-seeds.hu/crops → no content-security-policy
    • https://lidea-seeds.hu/csapatunk → no content-security-policy
    • https://lidea-seeds.hu/lidea-1 → no content-security-policy
    • https://lidea-seeds.hu/karrier → no content-security-policy
    • https://lidea-seeds.hu/news → no content-security-policy
    • https://lidea-seeds.hu/contact-us → no content-security-policy
    • https://lidea-seeds.hu/news/lidea → no content-security-policy
    • https://lidea-seeds.hu/news/kukorica → no content-security-policy
    • https://lidea-seeds.hu/news/napraforgo → no content-security-policy
    • https://lidea-seeds.hu/news/repce → no content-security-policy
    • https://lidea-seeds.hu/news/cirok → no content-security-policy
  • FoundClickjacking protectionMedium

    No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://lidea-seeds.hu/ → no x-frame-options
    • https://lidea-seeds.hu/crops → no x-frame-options
    • https://lidea-seeds.hu/csapatunk → no x-frame-options
    • https://lidea-seeds.hu/lidea-1 → no x-frame-options
    • https://lidea-seeds.hu/karrier → no x-frame-options
    • https://lidea-seeds.hu/news → no x-frame-options
    • https://lidea-seeds.hu/contact-us → no x-frame-options
    • https://lidea-seeds.hu/news/lidea → no x-frame-options
    • https://lidea-seeds.hu/news/kukorica → no x-frame-options
    • https://lidea-seeds.hu/news/napraforgo → no x-frame-options
    • https://lidea-seeds.hu/news/repce → no x-frame-options
    • https://lidea-seeds.hu/news/cirok → no x-frame-options
  • FoundMIME sniffing protectionLow

    No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://lidea-seeds.hu/ → no x-content-type-options
    • https://lidea-seeds.hu/crops → no x-content-type-options
    • https://lidea-seeds.hu/csapatunk → no x-content-type-options
    • https://lidea-seeds.hu/lidea-1 → no x-content-type-options
    • https://lidea-seeds.hu/karrier → no x-content-type-options
    • https://lidea-seeds.hu/news → no x-content-type-options
    • https://lidea-seeds.hu/contact-us → no x-content-type-options
    • https://lidea-seeds.hu/news/lidea → no x-content-type-options
    • https://lidea-seeds.hu/news/kukorica → no x-content-type-options
    • https://lidea-seeds.hu/news/napraforgo → no x-content-type-options
    • https://lidea-seeds.hu/news/repce → no x-content-type-options
    • https://lidea-seeds.hu/news/cirok → no x-content-type-options
  • FoundReferrer policyLow

    No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://lidea-seeds.hu/ → no referrer-policy
    • https://lidea-seeds.hu/crops → no referrer-policy
    • https://lidea-seeds.hu/csapatunk → no referrer-policy
    • https://lidea-seeds.hu/lidea-1 → no referrer-policy
    • https://lidea-seeds.hu/karrier → no referrer-policy
    • https://lidea-seeds.hu/news → no referrer-policy
    • https://lidea-seeds.hu/contact-us → no referrer-policy
    • https://lidea-seeds.hu/news/lidea → no referrer-policy
    • https://lidea-seeds.hu/news/kukorica → no referrer-policy
    • https://lidea-seeds.hu/news/napraforgo → no referrer-policy
    • https://lidea-seeds.hu/news/repce → no referrer-policy
    • https://lidea-seeds.hu/news/cirok → no referrer-policy
  • FoundPermissions policyInfo

    No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.

    • https://lidea-seeds.hu/ → no permissions-policy
    • https://lidea-seeds.hu/crops → no permissions-policy
    • https://lidea-seeds.hu/csapatunk → no permissions-policy
    • https://lidea-seeds.hu/lidea-1 → no permissions-policy
    • https://lidea-seeds.hu/karrier → no permissions-policy
    • https://lidea-seeds.hu/news → no permissions-policy
    • https://lidea-seeds.hu/contact-us → no permissions-policy
    • https://lidea-seeds.hu/news/lidea → no permissions-policy
    • https://lidea-seeds.hu/news/kukorica → no permissions-policy
    • https://lidea-seeds.hu/news/napraforgo → no permissions-policy
    • https://lidea-seeds.hu/news/repce → no permissions-policy
    • https://lidea-seeds.hu/news/cirok → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: nginx/1.18.0 (Ubuntu) (136 responses)
    • x-powered-by: Next.js (83 responses)
  • NoteThird-party scripts

    Scripts run from 1 other domain without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)

    • lideaseedsfr.matomo.cloud (40 script tags)
6 checks passed, 2 not applicable
  • OKHTTPS

    All 79 crawled pages were served over HTTPS.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    1 form found, all on HTTPS pages posting to HTTPS addresses.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Sites scoring near lidea-seeds.hu

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling lidea-seeds.hu from its pages as published, the way a search engine does. It shows summary figures only.

Own lidea-seeds.hu?