Scanned sites / linkuo.io / 2026-10-18-1428

linkuo.io scan from 2026-10-18 14:28:52 UTC DR 0

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

Scan 2026-10-18-1428

Scanned 2026-10-18 14:28:52 UTC, finished 2026-10-18 14:37:36 UTC. Found with 42backlinks.com tool directory

Site: https://linkuo.io/

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

96/ 100Excellent

On October 18, 2026 the Site Spider crawled 727 pages and 308 assets of linkuo.io, starting from https://linkuo.io/. It scored 96 out of 100, an excellent result. 4 of 33 checks found something to fix, led by meta descriptions (225), title tags (77), heavy assets (1); 14 checks passed. Most of the points went to meta descriptions (−2.5), title tags (−1.1), heavy assets (−0.6). 15 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: Medium4 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
727
Assets fetched
308
Status
Completed
Checks with issues
4 of 33
CoverageComplete crawl

1,035 of 1,037 discovered URLs were fetched, 2 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 6 link destinations on other sites were checked.

  • Title tags77 issues
    77 of 660 pages have title issues. 66 noindex or canonicalized pages excluded.
    −1.1 points
  • Meta descriptions225 issues
    225 of 660 pages have meta description issues. 66 noindex or canonicalized pages excluded.
    −2.5 points
  • HeadingsOK
    0 of 660 pages have heading issues. 66 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites726 noted
    0 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 6 destinations checked.
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses1 noted
    1 URL did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 726 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 8898 image references have no alt attribute. 5082 use an empty alt (decorative), which is fine.
  • Heavy assets1 issue
    1 asset larger than 500 KB among 308 fetched assets.
    −0.6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverageOK
    1 sitemap listing 660 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
  • Internal link countsOK
    Internal link counts for 500 pages; none is a dead end or buried.
  • Thin content5 issues
    5 of 660 pages have fewer than 200 words. 66 noindex or canonicalized pages excluded.
    −0.1 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format66 noted
    66 of 727 page URLs are harder to read, share or cache than they need to be.
  • Canonicals66 noted
    66 of 726 pages have a canonical worth checking.
  • Robots directives726 noted
    726 pages carry a robots directive; 0 carry none.
  • Anchor text582 noted
    582 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure536 noted
    536 of 660 pages could use the title, heading and snippet space better. 66 noindex or canonicalized pages excluded.
  • Image weight and alt length264 noted
    262 images over 100 KB; 2 with 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 726 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflang528 noted
    66 of 726 pages with hreflang have problems: 528 findings.
  • Structured data6 noted
    702 of 660 indexable pages carry structured data: Organization (654), BreadcrumbList (624), ListItem (624), FAQPage (624), Question (624). 6 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 660 pages with enough text to compare.
  • Soft 404s1 noted
    1 page answer 200 but say they are not there.
  • 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookies3 noted
    3 cookies set by the site, 3 missing a protective flag; 9 response headers recorded across 1035 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 726 pages; 480 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 Insights5 noted
    Mobile performance 79 on average across 5 pages; 5 below Google's good thresholds.
  • Spelling43 noted
    43 words an English dictionary does not know, on 98 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2284 sites, median 79%, average 78%

linkuo.io scores 96%, higher than 96% of the 2284 scanned sites. See the full ranking.

0581150%: 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%: 7 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 21 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 45 sites70%: 41 sites71%: 68 sites72%: 71 sites73%: 65 sites74%: 70 sites75%: 72 sites76%: 86 sites77%: 91 sites78%: 106 sites79%: 87 sites80%: 105 sites81%: 108 sites82%: 115 sites83%: 95 sites84%: 104 sites85%: 85 sites86%: 66 sites87%: 71 sites88%: 62 sites89%: 61 sites90%: 34 sites91%: 44 sites92%: 32 sites93%: 21 sites94%: 14 sites95%: 10 sites96%: 9 sites97%: 9 sites98%: 4 sites99%: 0 sites100%: 70 sites96% 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

Written from an earlier version of the analysis (rules v5). The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

Your site has minor SEO issues that can improve performance. Focus on fixing title and meta description problems, addressing redirects, and optimizing heavy assets.

  1. 1

    Fix Redirect Issue

    Why: Redirects can slow down page loading and impact SEO.

    How: Change the redirect from https://linkuo.io/ to its final URL directly.

    Checks: redirects

  2. 2

    Optimize Title Tags

    Why: 77 pages have title issues affecting search visibility.

    How: Revise titles for 18 affected pages, ensuring they are relevant and within optimal length.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: 225 pages have meta description issues that can hinder click-through rates.

    How: Assign unique meta descriptions to shared entries and ensure optimal length for affected pages.

    Checks: meta-descriptions

  4. 4

    Reduce Heavy Assets Size

    Why: Heavy assets can negatively impact load times.

    How: Compress and optimize the large RSS feeds on your site.

    Evidence: 326 KB of other, loaded by 121 pages, so every visitor to any of them downloads it.

    121 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    Checks: heavy-assets

  5. 5

    Address Thin Content

    Why: 5 pages with thin content may rank poorly.

    How: Enhance the text on these pages to exceed 200 words for better engagement.

    Checks: thin-content

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 linkuo.io has several critical security issues that need attention. Important security headers like HSTS and Content Security Policy are missing, making the site vulnerable to several attacks. Additionally, cookies lack protective flags, and sensitive paths are visible in the robots.txt file. Addressing these issues should enhance the site's security significantly.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on initial requests to HTTP versions of the site.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows any script, style, or frame to load, increasing XSS attack vulnerability.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Not having this protection allows clickjacking vulnerabilities, where pages can be framed by malicious sites.

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

    Evidence: Clickjacking protection

  4. 4

    Missing SameSite Cookie FlagsMedium

    Why it matters: Cookies without SameSite can be sent along with unwanted cross-site requests, increasing CSRF risks.

    Fix: Set cookies with SameSite=None; Secure and HttpOnly flags.

    Evidence: Cookie flags

  5. 5

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this header, browsers may incorrectly interpret files, leading to potential execution of malicious code.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Without a Referrer Policy, full URLs may leak, exposing sensitive information.

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

    Evidence: Referrer policy

  7. 7

    Server Version DisclosureLow

    Why it matters: Revealing server versions allows attackers to exploit known vulnerabilities.

    Fix: Remove or modify headers revealing server details (e.g., remove X-Powered-By).

    Evidence: Software version disclosure

  8. 8

    Sensitive Paths in robots.txtInfo

    Why it matters: Exposing paths like /admin/ may help attackers target sensitive areas.

    Fix: Implement proper access controls on sensitive directories instead of relying on robots.txt.

    Evidence: Sensitive paths in robots.txt

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://linkuo.io/es → no strict-transport-security
    • https://linkuo.io/en → no strict-transport-security
    • https://linkuo.io/fr → no strict-transport-security
    • https://linkuo.io/de → no strict-transport-security
    • https://linkuo.io/it → no strict-transport-security
    • https://linkuo.io/pt → no strict-transport-security
    • https://linkuo.io/es/comparador-precios-enlaces → no strict-transport-security
    • https://linkuo.io/en/link-price-comparison → no strict-transport-security
    • https://linkuo.io/fr/comparateur-prix-liens → no strict-transport-security
    • https://linkuo.io/de/linkpreis-vergleich → no strict-transport-security
    • https://linkuo.io/it/comparatore-prezzi-link → no strict-transport-security
    • https://linkuo.io/pt/comparador-precos-links → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 726 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://linkuo.io/es → no content-security-policy
    • https://linkuo.io/en → no content-security-policy
    • https://linkuo.io/fr → no content-security-policy
    • https://linkuo.io/de → no content-security-policy
    • https://linkuo.io/it → no content-security-policy
    • https://linkuo.io/pt → no content-security-policy
    • https://linkuo.io/es/comparador-precios-enlaces → no content-security-policy
    • https://linkuo.io/en/link-price-comparison → no content-security-policy
    • https://linkuo.io/fr/comparateur-prix-liens → no content-security-policy
    • https://linkuo.io/de/linkpreis-vergleich → no content-security-policy
    • https://linkuo.io/it/comparatore-prezzi-link → no content-security-policy
    • https://linkuo.io/pt/comparador-precos-links → 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://linkuo.io/es → no x-frame-options
    • https://linkuo.io/en → no x-frame-options
    • https://linkuo.io/fr → no x-frame-options
    • https://linkuo.io/de → no x-frame-options
    • https://linkuo.io/it → no x-frame-options
    • https://linkuo.io/pt → no x-frame-options
    • https://linkuo.io/es/comparador-precios-enlaces → no x-frame-options
    • https://linkuo.io/en/link-price-comparison → no x-frame-options
    • https://linkuo.io/fr/comparateur-prix-liens → no x-frame-options
    • https://linkuo.io/de/linkpreis-vergleich → no x-frame-options
    • https://linkuo.io/it/comparatore-prezzi-link → no x-frame-options
    • https://linkuo.io/pt/comparador-precos-links → 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://linkuo.io/es → no x-content-type-options
    • https://linkuo.io/en → no x-content-type-options
    • https://linkuo.io/fr → no x-content-type-options
    • https://linkuo.io/de → no x-content-type-options
    • https://linkuo.io/it → no x-content-type-options
    • https://linkuo.io/pt → no x-content-type-options
    • https://linkuo.io/es/comparador-precios-enlaces → no x-content-type-options
    • https://linkuo.io/en/link-price-comparison → no x-content-type-options
    • https://linkuo.io/fr/comparateur-prix-liens → no x-content-type-options
    • https://linkuo.io/de/linkpreis-vergleich → no x-content-type-options
    • https://linkuo.io/it/comparatore-prezzi-link → no x-content-type-options
    • https://linkuo.io/pt/comparador-precos-links → 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://linkuo.io/es → no referrer-policy
    • https://linkuo.io/en → no referrer-policy
    • https://linkuo.io/fr → no referrer-policy
    • https://linkuo.io/de → no referrer-policy
    • https://linkuo.io/it → no referrer-policy
    • https://linkuo.io/pt → no referrer-policy
    • https://linkuo.io/es/comparador-precios-enlaces → no referrer-policy
    • https://linkuo.io/en/link-price-comparison → no referrer-policy
    • https://linkuo.io/fr/comparateur-prix-liens → no referrer-policy
    • https://linkuo.io/de/linkpreis-vergleich → no referrer-policy
    • https://linkuo.io/it/comparatore-prezzi-link → no referrer-policy
    • https://linkuo.io/pt/comparador-precos-links → 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://linkuo.io/es → no permissions-policy
    • https://linkuo.io/en → no permissions-policy
    • https://linkuo.io/fr → no permissions-policy
    • https://linkuo.io/de → no permissions-policy
    • https://linkuo.io/it → no permissions-policy
    • https://linkuo.io/pt → no permissions-policy
    • https://linkuo.io/es/comparador-precios-enlaces → no permissions-policy
    • https://linkuo.io/en/link-price-comparison → no permissions-policy
    • https://linkuo.io/fr/comparateur-prix-liens → no permissions-policy
    • https://linkuo.io/de/linkpreis-vergleich → no permissions-policy
    • https://linkuo.io/it/comparatore-prezzi-link → no permissions-policy
    • https://linkuo.io/pt/comparador-precos-links → 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 (1035 responses)
    • x-powered-by: PHP/8.4.26, PleskLin (734 responses)
    • x-powered-by: PleskLin (301 responses)
  • FoundCookie flagsMedium

    3 of 3 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • XSRF-TOKEN (set by https://linkuo.io/) lacks HttpOnly, SameSite
    • linkuo_session (set by https://linkuo.io/) lacks SameSite
    • locale (set by https://linkuo.io/es) lacks SameSite
  • 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.)

    • www.googletagmanager.com (40 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /admin/
5 checks passed, 1 not applicable
  • OKHTTPS

    All 726 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

    6 forms 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.

  • 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 linkuo.io

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 linkuo.io from its pages as published, the way a search engine does. It shows summary figures only.

Own linkuo.io?