Scanned sites / papeeria.com

SEO report for papeeria.com

The latest Site Spider scan of papeeria.com, with 1 scan on record. Each scan is at its own address, for example /domain/papeeria-com/2026-09-26-0514.

Latest scan

Scanned 9/26/2026, 5:14:09 AM, finished 9/26/2026, 5:57:36 AM

Site: https://papeeria.com/

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

63/ 100Needs work

On September 26, 2026 the Site Spider crawled 873 pages and 60 assets of papeeria.com, starting from https://papeeria.com/. It scored 63 out of 100, a result that needs work. 12 of 14 checks found something to fix, led by indexability (836), thin content (824), title tags (500); 2 checks passed. 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
873
Assets fetched
60
Status
Completed
Checks with issues
12 of 14
  • Title tags500 issues
    836 of 836 pages have title issues.
  • Meta descriptions500 issues
    836 of 836 pages have meta description issues.
  • Headings500 issues
    832 of 836 pages have heading issues.
  • Broken links27 issues
    27 internal links point at 27 broken URLs.
  • Redirects8 issues
    8 redirecting URLs, 3 of them chained.
  • Non-200 responses29 issues
    40 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability836 issues
    836 of 836 indexable pages have indexability warnings.
  • Image alt text20 issues
    20 of 3313 image references have no alt attribute. 2457 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among the 60 heaviest.
  • Orphan pages2 issues
    2 pages have no internal links pointing at them.
  • Sitemap coverage418 issues
    No sitemap found. Tried: https://papeeria.com/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
  • Thin content824 issues
    824 of 836 pages have fewer than 200 words.
  • Duplicate content45 issues
    10 groups of pages with identical HTML.

Where this site sits among all scanned sites

1271 sites, median 82%, average 80%

papeeria.com scores 63%, higher than 6% of the 1271 scanned sites. See the full ranking.

034670%: 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%: 0 sites15%: 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%: 0 sites34%: 0 sites35%: 1 site36%: 1 site37%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 3 sites46%: 2 sites47%: 1 site48%: 1 site49%: 0 sites50%: 3 sites51%: 4 sites52%: 4 sites53%: 4 sites54%: 4 sites55%: 2 sites56%: 2 sites57%: 3 sites58%: 8 sites59%: 4 sites60%: 7 sites61%: 9 sites62%: 12 sites63%: 5 sites64%: 9 sites65%: 10 sites66%: 10 sites67%: 16 sites68%: 29 sites69%: 14 sites70%: 26 sites71%: 25 sites72%: 29 sites73%: 28 sites74%: 33 sites75%: 30 sites76%: 41 sites77%: 42 sites78%: 39 sites79%: 37 sites80%: 51 sites81%: 57 sites82%: 58 sites83%: 53 sites84%: 60 sites85%: 54 sites86%: 49 sites87%: 55 sites88%: 60 sites89%: 47 sites90%: 67 sites91%: 42 sites92%: 26 sites93%: 20 sites94%: 18 sites95%: 11 sites96%: 11 sites97%: 4 sites98%: 3 sites99%: 2 sites100%: 23 sites63% 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

Multiple issues found on your website affecting SEO. Prioritize fixing broken links, redirects, and creating title tags to enhance your site's performance. Implementing a sitemap can also help with indexing.

  1. 1

    Fix Broken Links

    Why: 27 broken internal links hurt user experience and SEO.

    How: Locate the broken URLs and update or remove the links from affected pages.

    Checks: broken-links

  2. 2

    Resolve Redirects

    Why: 8 redirecting URLs, with 3 chained, confuse users and search engines.

    How: Eliminate chain redirects by linking directly to the final destination URLs.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: 40 URLs returning non-200 responses can harm site accessibility.

    How: Identify the URLs with status codes = 4xx or 3xx and fix or remove them.

    Checks: status-codes

  4. 4

    Update Title Tags

    Why: 836 pages with title issues can lead to poor search visibility.

    How: Craft unique, descriptive titles for each page, ideally between 50-60 characters.

    Checks: titles

  5. 5

    Create Meta Descriptions

    Why: 836 pages lack unique meta descriptions, affecting click-through rates.

    How: Write engaging meta descriptions for each page, keeping them under 160 characters.

    Checks: meta-descriptions

  6. 6

    Implement a Sitemap

    Why: No sitemap detected can hinder search engines from indexing your pages.

    How: Create a sitemap and upload it at /sitemap.xml, then reference it in the robots.txt file.

    Checks: sitemap-coverage

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 several security issues including missing headers for HTTP Strict Transport Security and Content Security Policy. These may expose users to risks such as man-in-the-middle attacks and allow cross-site scripting vulnerabilities. Additionally, vulnerable JavaScript libraries and insecure cookie flags further heighten risk. Immediate action is recommended.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on their first request if they access via HTTP.

    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: No CSP to restrict where scripts, styles, and frames can load from increases XSS risks.

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

    Evidence: Content Security Policy

  3. 3

    Insecure Cookie FlagsMedium

    Why it matters: Cookies lacking Secure and HttpOnly flags can be accessed or transmitted over insecure channels.

    Fix: Set headers for cookies: Secure; SameSite=Lax; HttpOnly for all cookies.

    Evidence: Cookie flags

  4. 4

    Vulnerable JavaScript LibraryMedium

    Why it matters: jQuery 1.8.3 has known vulnerabilities that could be exploited.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing Referrer-PolicyLow

    Why it matters: Without Referrer-Policy, sensitive information in URLs can be sent to other sites.

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

    Evidence: Referrer policy

  6. 6

    Exposing Server VersionLow

    Why it matters: Revealing server and framework version details makes it easier for attackers to find exploits.

    Fix: Hide the server version in responses. For Nginx, set: server_tokens off;

    Evidence: Software version disclosure

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Lack of Permissions Policy means unnecessary browser features remain active, increasing risk.

    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://papeeria.com/ → no strict-transport-security
    • https://papeeria.com/landing → no strict-transport-security
    • https://papeeria.com/about/pricing → no strict-transport-security
    • https://papeeria.com/about/tos → no strict-transport-security
    • https://papeeria.com/about/contacts → no strict-transport-security
    • https://papeeria.com/signup?redirect=%2F → no strict-transport-security
    • https://papeeria.com/signup → no strict-transport-security
    • https://papeeria.com/signin → no strict-transport-security
    • https://www.papeeria.com/templates → no strict-transport-security
    • https://papeeria.com/signup?redirect=%2Flanding → no strict-transport-security
    • https://papeeria.com/signup?redirect=%2Fabout%2Fpricing → no strict-transport-security
    • https://papeeria.com/signup?redirect=%2Fme → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 836 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://papeeria.com/ → no content-security-policy
    • https://papeeria.com/landing → no content-security-policy
    • https://papeeria.com/about/pricing → no content-security-policy
    • https://papeeria.com/about/tos → no content-security-policy
    • https://papeeria.com/about/contacts → no content-security-policy
    • https://papeeria.com/signup?redirect=%2F → no content-security-policy
    • https://papeeria.com/signup → no content-security-policy
    • https://papeeria.com/signin → no content-security-policy
    • https://www.papeeria.com/templates → no content-security-policy
    • https://papeeria.com/signup?redirect=%2Flanding → no content-security-policy
    • https://papeeria.com/signup?redirect=%2Fabout%2Fpricing → no content-security-policy
    • https://papeeria.com/signup?redirect=%2Fme → no content-security-policy
  • 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://papeeria.com/ → no referrer-policy
    • https://papeeria.com/landing → no referrer-policy
    • https://papeeria.com/about/pricing → no referrer-policy
    • https://papeeria.com/about/tos → no referrer-policy
    • https://papeeria.com/about/contacts → no referrer-policy
    • https://papeeria.com/signup?redirect=%2F → no referrer-policy
    • https://papeeria.com/signup → no referrer-policy
    • https://papeeria.com/signin → no referrer-policy
    • https://www.papeeria.com/templates → no referrer-policy
    • https://papeeria.com/signup?redirect=%2Flanding → no referrer-policy
    • https://papeeria.com/signup?redirect=%2Fabout%2Fpricing → no referrer-policy
    • https://papeeria.com/signup?redirect=%2Fme → 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://papeeria.com/ → no permissions-policy
    • https://papeeria.com/landing → no permissions-policy
    • https://papeeria.com/about/pricing → no permissions-policy
    • https://papeeria.com/about/tos → no permissions-policy
    • https://papeeria.com/about/contacts → no permissions-policy
    • https://papeeria.com/signup?redirect=%2F → no permissions-policy
    • https://papeeria.com/signup → no permissions-policy
    • https://papeeria.com/signin → no permissions-policy
    • https://www.papeeria.com/templates → no permissions-policy
    • https://papeeria.com/signup?redirect=%2Flanding → no permissions-policy
    • https://papeeria.com/signup?redirect=%2Fabout%2Fpricing → no permissions-policy
    • https://papeeria.com/signup?redirect=%2Fme → 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.14.0 (Ubuntu) (933 responses)
  • FoundCookie flagsMedium

    2 of 2 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.

    • PLAY_SESSION (set by https://papeeria.com/) lacks Secure, SameSite
    • PlaygroundUserID (set by https://papeeria.com/auth/demo) lacks Secure, HttpOnly, SameSite
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 1.8.3. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.8.3 in https://papeeria.com/assets/2021-10-13/javascripts/jquery-1.8.3.js: CVE-2012-6708 (selector XSS), CVE-2015-9251, CVE-2019-11358, CVE-2020-11022, CVE-2020-11023; fixed in 3.5.0
  • NoteThird-party scripts

    Scripts run from 2 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.)

    • ajax.googleapis.com (6 script tags)
    • www.googleadservices.com (40 script tags)
7 checks passed, 1 not applicable
  • OKHTTPS

    All 836 crawled pages were served over HTTPS.

  • OKClickjacking protection

    x-frame-options is set on all 836 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 836 HTML pages.

  • OKMixed content

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

  • OKForms over HTTPS

    130 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 applicableSensitive paths in robots.txt

    No robots.txt was fetched.

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.

Earlier scans of papeeria.com

No other scans of this site yet.

Sites scoring near papeeria.com

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

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

Own papeeria.com?

papeeria.com SEO report | DIY SEO Hub