Scanned sites / www.seolium.com / 2026-10-03-1027
www.seolium.com scan from 10/3/2026, 10:27:37 AM
Scan 2026-10-03-1027
Scanned 10/3/2026, 10:27:37 AM, finished 10/4/2026, 6:47:57 AM. Found on page 5 of brave web search results
Site: https://www.seolium.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On October 3, 2026 the Site Spider crawled 5000 pages and 1000 assets of www.seolium.com, starting from https://www.seolium.com/. It scored 64 out of 100, a result that needs work. 12 of 23 checks found something to fix, led by indexability (4,972), meta descriptions (4,607), headings (4,878); 4 checks passed. Most of the points went to indexability (−10), meta descriptions (−7.4), headings (−5.9). 7 checks found something the score does not count, listed as noted. 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, 2 low and 1 info findings. See the security findings ↓
- Pages crawled
- 5000
- Assets fetched
- 1000
- Status
- Completed
- Checks with issues
- 12 of 23
6,000 of 6,000 discovered URLs were fetched, 565,037 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 115111 left unchecked.
- Title tags1,423 issues1423 of 4977 pages have title issues. 1 noindex or canonicalized page excluded.−2.9 points
- Meta descriptions4,607 issues4607 of 4977 pages have meta description issues. 1 noindex or canonicalized page excluded.−7.4 points
- Headings4,878 issues4878 of 4977 pages have heading issues. 1 noindex or canonicalized page excluded.−5.9 points
- Broken links22 issues5403 internal links point at 22 broken URLs.−0.1 points
- Links to other sites5 issues5 destinations answered with an error, 51 could not be determined (timeouts, rate limits or refusals), 115111 were left unchecked by the per-scan cap, of 300 destinations checked.
- RedirectsOK0 redirecting URLs, 0 of them chained.
- Non-200 responses22 issues74 URLs did not return a 2xx response. 22 of them are pages, 22 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability4,972 issues4972 of 4978 indexable pages have indexability warnings.−10 points
- Image alt text166,722 issues166722 of 204910 image references have no alt attribute. 27987 use an empty alt (decorative), which is fine.−4.9 points
- Heavy assets3 issues3 assets larger than 500 KB among 1000 fetched assets.−1.8 points
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage2,489 issuesNo sitemap found. Tried: https://www.seolium.com/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.−3 points
- Internal link counts489 notedInternal link counts for 500 pages; 489 worth a look.
- Thin content1 issue1 of 4977 pages have fewer than 200 words. 1 noindex or canonicalized page excluded.
- Duplicate content19 issues2 groups of pages with identical HTML.
- URL format1 noted1 of 5000 page URLs are harder to read, share or cache than they need to be.
- Canonicals1 noted1 of 4978 pages have a canonical worth checking.
- Robots directives143 noted143 pages carry a robots directive; 4835 carry none.
- Anchor text95 noted95 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure839 noted839 of 4977 pages could use the title, heading and snippet space better. 1 noindex or canonicalized page excluded.
- Image weight and alt length36 noted32 images over 100 KB; 4 with alt text over 100 characters.
- Response anomaliesOKNo redirect loops, header redirects or pages served as something other than HTML.
Where this scan sits among all scanned sites
2128 sites, median 79%, average 78%
www.seolium.com scores 64%, higher than 9% of the 2128 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsWritten from an earlier version of the analysis (rules v4). 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 several issues needing attention, primarily broken links and missing SEO elements like title tags, meta descriptions, and headings. Fixing these can improve user experience and search visibility.
- 1
Fix Broken Links
Why: 5403 internal links point to broken URLs, severely impacting user experience and SEO.
How: Identify and update or remove the links to the broken URLs. Check each linking page and replace or remove the link.
Checks: broken-links
- 2
Implement Sitemap
Why: No sitemap found, hindering search engines from crawling your site efficiently.
How: Create an XML sitemap and upload it to /sitemap.xml. Include it in your robots.txt file.
Checks: sitemap-coverage
- 3
Add Missing H1 Tags
Why: 4044 pages lack H1 tags, negatively affecting their SEO and content structure.
How: Edit each page to include a clear and relevant H1 tag at the beginning of the content.
Checks: headings
- 4
Resolve Title Tag Issues
Why: 1423 pages have title issues, which may lead to lower rankings and poor visibility.
How: Review and optimize title tags to be clear, unique, and within 50-60 characters.
Checks: titles
- 5
Add Meta Descriptions
Why: 4607 pages have missing or poor meta descriptions, reducing click-through rates.
How: Write engaging meta descriptions for each page that summarize the content accurately.
Checks: meta-descriptions
- 6
Address Indexability Warnings
Why: 4972 pages show indexability warnings which could hinder SEO performance.
How: Ensure proper meta tags, including adding 'lang' attributes to relevant pages.
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 crawlThe website has several security vulnerabilities, including the lack of crucial response headers and vulnerable JavaScript libraries. Implementing recommended headers and updating libraries are necessary to protect visitors and enhance security posture.
- 0 high
- 4 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors can be intercepted when accessing the site without HTTPS.
Fix: Add the header `Strict-Transport-Security: max-age=31536000; includeSubDomains` to all responses.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: A lack of CSP permits scripts from potentially malicious sources to run.
Fix: Add a CSP header, e.g., `Content-Security-Policy: default-src 'self';`.
Evidence: Content Security Policy
- 3
Missing X-Frame-Options HeaderMedium
Why it matters: Without this header, the site can be embedded in frames, leading to clickjacking.
Fix: Add the header `X-Frame-Options: DENY` or use the CSP frame-ancestors directive.
Evidence: Clickjacking protection
- 4
Vulnerable JavaScript LibrariesMedium
Why it matters: Outdated libraries may expose the site to known vulnerabilities.
Fix: Upgrade jQuery to version 3.5.0 or higher and Bootstrap to version 3.4.1 or higher.
Evidence: Vulnerable JavaScript libraries
- 5
Missing X-Content-Type-Options HeaderLow
Why it matters: This header prevents browsers from interpreting files as something other than declared.
Fix: Add the header `X-Content-Type-Options: nosniff` to all responses.
Evidence: MIME sniffing protection
- 6
Server Version DisclosureLow
Why it matters: Exact server version may allow attackers to exploit known vulnerabilities.
Fix: Consider hiding server banners or using a reverse proxy to obscure details.
Evidence: Software version disclosure
- 7
Missing Permissions Policy HeaderInfo
Why it matters: Not using this header means all features (camera, microphone) are available by default.
Fix: Add a Permissions-Policy header, e.g., `Permissions-Policy: geolocation=(self), microphone=()`.
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://www.seolium.com/ → no strict-transport-security
- https://www.seolium.com/blog/ → no strict-transport-security
- https://www.seolium.com/blog/best-131-seo-agencies-in-usa/ → no strict-transport-security
- https://www.seolium.com/cheapest-rank-tracker/ → no strict-transport-security
- https://www.seolium.com/we-are-a-google-rank-tracking-tool/ → no strict-transport-security
- https://www.seolium.com/blog/best-147-web-design-agencies-in-usa/ → no strict-transport-security
- https://www.seolium.com/seo-quora/ → no strict-transport-security
- https://www.seolium.com/seo-glossary/ → no strict-transport-security
- https://www.seolium.com/seo/how-to-optimize/ → no strict-transport-security
- https://www.seolium.com/seo-talent-quiz/ → no strict-transport-security
- https://www.seolium.com/interview-rand-fishkin/ → no strict-transport-security
- https://www.seolium.com/interview-bill-slawski/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 4978 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://www.seolium.com/ → no content-security-policy
- https://www.seolium.com/blog/ → no content-security-policy
- https://www.seolium.com/blog/best-131-seo-agencies-in-usa/ → no content-security-policy
- https://www.seolium.com/cheapest-rank-tracker/ → no content-security-policy
- https://www.seolium.com/we-are-a-google-rank-tracking-tool/ → no content-security-policy
- https://www.seolium.com/blog/best-147-web-design-agencies-in-usa/ → no content-security-policy
- https://www.seolium.com/seo-quora/ → no content-security-policy
- https://www.seolium.com/seo-glossary/ → no content-security-policy
- https://www.seolium.com/seo/how-to-optimize/ → no content-security-policy
- https://www.seolium.com/seo-talent-quiz/ → no content-security-policy
- https://www.seolium.com/interview-rand-fishkin/ → no content-security-policy
- https://www.seolium.com/interview-bill-slawski/ → 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://www.seolium.com/ → no x-frame-options
- https://www.seolium.com/blog/ → no x-frame-options
- https://www.seolium.com/blog/best-131-seo-agencies-in-usa/ → no x-frame-options
- https://www.seolium.com/cheapest-rank-tracker/ → no x-frame-options
- https://www.seolium.com/we-are-a-google-rank-tracking-tool/ → no x-frame-options
- https://www.seolium.com/blog/best-147-web-design-agencies-in-usa/ → no x-frame-options
- https://www.seolium.com/seo-quora/ → no x-frame-options
- https://www.seolium.com/seo-glossary/ → no x-frame-options
- https://www.seolium.com/seo/how-to-optimize/ → no x-frame-options
- https://www.seolium.com/seo-talent-quiz/ → no x-frame-options
- https://www.seolium.com/interview-rand-fishkin/ → no x-frame-options
- https://www.seolium.com/interview-bill-slawski/ → 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://www.seolium.com/ → no x-content-type-options
- https://www.seolium.com/blog/ → no x-content-type-options
- https://www.seolium.com/blog/best-131-seo-agencies-in-usa/ → no x-content-type-options
- https://www.seolium.com/cheapest-rank-tracker/ → no x-content-type-options
- https://www.seolium.com/we-are-a-google-rank-tracking-tool/ → no x-content-type-options
- https://www.seolium.com/blog/best-147-web-design-agencies-in-usa/ → no x-content-type-options
- https://www.seolium.com/seo-quora/ → no x-content-type-options
- https://www.seolium.com/seo-glossary/ → no x-content-type-options
- https://www.seolium.com/seo/how-to-optimize/ → no x-content-type-options
- https://www.seolium.com/seo-talent-quiz/ → no x-content-type-options
- https://www.seolium.com/interview-rand-fishkin/ → no x-content-type-options
- https://www.seolium.com/interview-bill-slawski/ → no x-content-type-options
- 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://www.seolium.com/ → no permissions-policy
- https://www.seolium.com/blog/ → no permissions-policy
- https://www.seolium.com/blog/best-131-seo-agencies-in-usa/ → no permissions-policy
- https://www.seolium.com/cheapest-rank-tracker/ → no permissions-policy
- https://www.seolium.com/we-are-a-google-rank-tracking-tool/ → no permissions-policy
- https://www.seolium.com/blog/best-147-web-design-agencies-in-usa/ → no permissions-policy
- https://www.seolium.com/seo-quora/ → no permissions-policy
- https://www.seolium.com/seo-glossary/ → no permissions-policy
- https://www.seolium.com/seo/how-to-optimize/ → no permissions-policy
- https://www.seolium.com/seo-talent-quiz/ → no permissions-policy
- https://www.seolium.com/interview-rand-fishkin/ → no permissions-policy
- https://www.seolium.com/interview-bill-slawski/ → 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: Apache/2.4.52 (Ubuntu) (6000 responses)
- FoundVulnerable JavaScript librariesMedium
5 libraries with published vulnerabilities: jQuery 1.10.2, jQuery 2.1.4, jQuery 2.2.4, jQuery 3.2.1, Bootstrap 3.3.7. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 1.10.2 in https://www.seolium.com/js/jquery.js: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
- jQuery 2.1.4 in https://www.seolium.com/js/jquery-2.1.4.min.js: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
- jQuery 2.2.4 in https://code.jquery.com/jquery-2.2.4.min.js: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
- jQuery 3.2.1 in https://code.jquery.com/jquery-3.2.1.min.js: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
- Bootstrap 3.3.7 in https://www.seolium.com/js/bootstrap.min.js: CVE-2016-10735, CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 3.4.1
- NoteThird-party scripts
Scripts run from 9 other domains 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)
- cdnjs.cloudflare.com (44 script tags)
- code.jquery.com (14 script tags)
- cdn.datatables.net (19 script tags)
- stackpath.bootstrapcdn.com (7 script tags)
- cdn.jsdelivr.net (7 script tags)
- oss.maxcdn.com (2 script tags)
- engine.seolium.com (1 script tag)
- ssl.gstatic.com (1 script tag)
- 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: /wp-admin/
6 checks passed, 1 not applicable
- OKHTTPS
All 4978 crawled pages were served over HTTPS.
- OKReferrer policy
A referrer policy is set through a <meta name="referrer"> tag.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
116 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 applicableCookie flags
The crawl set no cookies, so there are no cookie flags to check.
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 www.seolium.com
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- www.cahillfuneralchapel.com64/100 · rank 1918 · 1,039 pages
- digivale.com64/100 · rank 1918 · 11 pages
- www.qualityfoodcompany.com64/100 · rank 1918 · 41 pages
- www.topnotchbarbershop.ca64/100 · rank 1918 · 111 pages
- fallentimbersfarm.com64/100 · rank 1918 · 239 pages
- www.odinseyetattoo.com64/100 · rank 1918 · 43 pages
This report was produced by the DIY SEO Hub Site Spider crawling www.seolium.com from its pages as published, the way a search engine does. It shows summary figures only.
Own www.seolium.com?
- Claim this site to manage the listing, hide it from the public lists, or keep it.
- Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming www.seolium.com. Removal needs no account and no proof of purchase.