Scanned sites / www.lovelocal.com

SEO report for www.lovelocal.com

The latest Site Spider scan of www.lovelocal.com, with 2 scans on record. Each scan is at its own address, for example /domain/www-lovelocal-com/2026-10-02-0236.

Latest scan

Scanned 10/2/2026, 2:36:41 AM, finished 10/2/2026, 8:04:38 AM. Found on page 1 of brave web search results

Site: https://www.lovelocal.com/

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

49/ 100Poor

On October 2, 2026 the Site Spider crawled 2321 pages and 964 assets of www.lovelocal.com, starting from https://www.lovelocal.com/. It scored 49 out of 100, a poor result. 12 of 16 checks found something to fix, led by broken links (2,002), non-200 responses (2,002), heavy assets (46); 3 checks passed. Most of the points went to broken links (−20), non-200 responses (−10), heavy assets (−6). 1 check 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: Medium5 medium, 1 low and 1 info findings. See the security findings ↓

Pages crawled
2321
Assets fetched
964
Status
Completed
Checks with issues
12 of 16
CoverageComplete crawl

3,285 of 3,285 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 607 left unchecked.

  • Title tags122 issues
    122 of 293 pages have title issues. 17 noindex or canonicalized pages excluded.
    −3.9 points
  • Meta descriptions156 issues
    156 of 293 pages have meta description issues. 17 noindex or canonicalized pages excluded.
    −4 points
  • Headings138 issues
    138 of 293 pages have heading issues. 17 noindex or canonicalized pages excluded.
    −2.7 points
  • Broken links2,002 issues
    5239 internal links point at 2002 broken URLs.
    −20 points
  • Links to other sites7 issues
    7 destinations answered with an error, 111 could not be determined (timeouts, rate limits or refusals), 607 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.9 points
  • Redirects9 issues
    10 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses2,002 issues
    2018 URLs did not return a 2xx response. 2011 of them are pages, 2002 with an error status; the rest are assets or redirects.
    −10 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 293 indexable pages have indexability warnings. 17 pages noindex by design.
  • Image alt text73 issues
    73 of 5661 image references have no alt attribute. 2042 use an empty alt (decorative), which is fine.
    −0.1 points
  • Heavy assets46 issues
    46 assets larger than 500 KB among 964 fetched assets.
    −6 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage155 issues
    No sitemap found. Tried: https://www.lovelocal.com/sitemap.xml (301), https://www.lovelocal.com/sitemap_index.xml (403). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link countsOK
    Internal link counts for 310 pages.
  • Thin content56 issues
    56 of 293 pages have fewer than 200 words. 17 noindex or canonicalized pages excluded.
    −1.4 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this site sits among all scanned sites

1898 sites, median 80%, average 79%

www.lovelocal.com scores 49%, higher than 1% of the 1898 scanned sites. See the full ranking.

0551090%: 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%: 2 sites36%: 1 site37%: 2 sites38%: 2 sites39%: 1 site40%: 2 sites41%: 2 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 4 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 7 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 6 sites57%: 6 sites58%: 15 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 17 sites63%: 16 sites64%: 11 sites65%: 21 sites66%: 22 sites67%: 37 sites68%: 30 sites69%: 26 sites70%: 39 sites71%: 40 sites72%: 56 sites73%: 52 sites74%: 49 sites75%: 61 sites76%: 76 sites77%: 72 sites78%: 88 sites79%: 69 sites80%: 91 sites81%: 109 sites82%: 84 sites83%: 86 sites84%: 87 sites85%: 65 sites86%: 74 sites87%: 63 sites88%: 64 sites89%: 54 sites90%: 36 sites91%: 36 sites92%: 29 sites93%: 15 sites94%: 13 sites95%: 13 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 55 sites49% 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 needs significant fixes, particularly with broken links and meta descriptions. Implementing the highest priority issues can greatly enhance user experience and SEO performance. Follow the recommendations below.

  1. 1

    Fix Broken Links

    Why: 5239 internal links lead to broken URLs, harming SEO and user experience.

    How: Identify invalid links on affected pages and either update or remove them.

    Checks: broken-links

  2. 2

    Add Meta Descriptions

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

    How: Create and implement unique descriptions for affected pages to enhance visibility in search results.

    Checks: meta-descriptions

  3. 3

    Improve Accessibility with Alt Text

    Why: 73 images lack alt attributes, impacting accessibility.

    How: Add relevant alt text to images that currently lack it to ensure all users can understand the content.

    Checks: images-alt

  4. 4

    Create a Sitemap

    Why: No sitemap found, which hinders search engines from indexing your pages effectively.

    How: Generate a sitemap and make it accessible at /sitemap.xml.

    Checks: sitemap-coverage

  5. 5

    Reduce Heavy Assets

    Why: 46 assets are larger than 500 KB, slowing down site loading speed.

    How: Optimize or compress images and other assets to improve load time.

    Checks: heavy-assets

  6. 6

    Address Thin Content

    Why: 56 pages contain fewer than 200 words, potentially affecting search rankings.

    How: Add high-quality, relevant content to these pages to improve their value.

    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 site lacks essential security headers, which increases exposure to potential attacks like man-in-the-middle and clickjacking. Two vulnerable JavaScript libraries may lead to risks depending on usage. Recommended fixes include adding security headers and updating libraries.

  • 0 high
  • 5 medium
  • 1 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, attackers can intercept connections when users type the URL without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-OptionsMedium

    Why it matters: Lack of this header allows clickjacking attacks, where another site can embed your pages in a frame.

    Fix: Add the header: X-Frame-Options: DENY or add a CSP frame-ancestors directive.

    Evidence: Clickjacking protection

  3. 3

    Cookie Flags MissingMedium

    Why it matters: Cookies lacking secure flags can be accessed by unsecured scripts, increasing vulnerability.

    Fix: Set HttpOnly for _fbp and add SameSite='None' to wordpress_test_cookie.

    Evidence: Cookie flags

  4. 4

    Vulnerable JavaScript LibrariesMedium

    Why it matters: Using outdated libraries may expose the site to known vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Leaked Google API KeyMedium

    Why it matters: Exposing API keys can lead to unauthorized usage unless restricted in the Google Cloud console.

    Fix: Restrict the API key usage by domain referrer and review access settings in the Google Cloud console.

    Evidence: Keys and secrets in page code

  6. 6

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this header, browsers may incorrectly execute files as scripts based on their contents.

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

    Evidence: MIME sniffing protection

  7. 7

    Missing Permissions-Policy HeaderInfo

    Why it matters: This header can limit permissions for features you don't use, reducing the impact of potential attacks.

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

    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.lovelocal.com/ → no strict-transport-security
    • https://www.lovelocal.com/suggest-a-company/ → no strict-transport-security
    • https://www.lovelocal.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.lovelocal.com%2F → no strict-transport-security
    • https://www.lovelocal.com/sign-up/ → no strict-transport-security
    • https://www.lovelocal.com/search/ → no strict-transport-security
    • https://www.lovelocal.com/categories/ → no strict-transport-security
    • https://www.lovelocal.com/about/ → no strict-transport-security
    • https://www.lovelocal.com/contact/ → no strict-transport-security
    • https://www.lovelocal.com/blog/ → no strict-transport-security
    • https://www.lovelocal.com/wheretobuy/local-shops/ → no strict-transport-security
    • https://www.lovelocal.com/wheretobuy/shop-online/ → no strict-transport-security
    • https://www.lovelocal.com/wheretobuy/farms/ → no strict-transport-security
  • FoundClickjacking protectionMedium

    17 of 310 HTML pages send 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.lovelocal.com/ → no x-frame-options
    • https://www.lovelocal.com/suggest-a-company/ → no x-frame-options
    • https://www.lovelocal.com/sign-up/ → no x-frame-options
    • https://www.lovelocal.com/search/ → no x-frame-options
    • https://www.lovelocal.com/categories/ → no x-frame-options
    • https://www.lovelocal.com/about/ → no x-frame-options
    • https://www.lovelocal.com/contact/ → no x-frame-options
    • https://www.lovelocal.com/blog/ → no x-frame-options
    • https://www.lovelocal.com/wheretobuy/local-shops/ → no x-frame-options
    • https://www.lovelocal.com/wheretobuy/shop-online/ → no x-frame-options
    • https://www.lovelocal.com/wheretobuy/farms/ → no x-frame-options
    • https://www.lovelocal.com/wooden-brushes/ → 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.lovelocal.com/ → no x-content-type-options
    • https://www.lovelocal.com/suggest-a-company/ → no x-content-type-options
    • https://www.lovelocal.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.lovelocal.com%2F → no x-content-type-options
    • https://www.lovelocal.com/sign-up/ → no x-content-type-options
    • https://www.lovelocal.com/search/ → no x-content-type-options
    • https://www.lovelocal.com/categories/ → no x-content-type-options
    • https://www.lovelocal.com/about/ → no x-content-type-options
    • https://www.lovelocal.com/contact/ → no x-content-type-options
    • https://www.lovelocal.com/blog/ → no x-content-type-options
    • https://www.lovelocal.com/wheretobuy/local-shops/ → no x-content-type-options
    • https://www.lovelocal.com/wheretobuy/shop-online/ → no x-content-type-options
    • https://www.lovelocal.com/wheretobuy/farms/ → 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.lovelocal.com/ → no permissions-policy
    • https://www.lovelocal.com/suggest-a-company/ → no permissions-policy
    • https://www.lovelocal.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.lovelocal.com%2F → no permissions-policy
    • https://www.lovelocal.com/sign-up/ → no permissions-policy
    • https://www.lovelocal.com/search/ → no permissions-policy
    • https://www.lovelocal.com/categories/ → no permissions-policy
    • https://www.lovelocal.com/about/ → no permissions-policy
    • https://www.lovelocal.com/contact/ → no permissions-policy
    • https://www.lovelocal.com/blog/ → no permissions-policy
    • https://www.lovelocal.com/wheretobuy/local-shops/ → no permissions-policy
    • https://www.lovelocal.com/wheretobuy/shop-online/ → no permissions-policy
    • https://www.lovelocal.com/wheretobuy/farms/ → no permissions-policy
  • 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.

    • _fbp (set by https://www.lovelocal.com/robots.txt) lacks HttpOnly
    • wordpress_test_cookie (set by https://www.lovelocal.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.lovelocal.…) lacks SameSite
  • FoundVulnerable JavaScript librariesMedium

    2 libraries with published vulnerabilities: jQuery 2.2.4, jQuery 3.1.2. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 2.2.4 in https://code.jquery.com/jquery-2.2.4.min.js?ver=828e556bd48d67d701282ac998f21f2b: 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.1.2 in https://www.lovelocal.com/wp-content/plugins/gravityforms/js/placeholders.jquer…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…zk (39 chars) in https://www.lovelocal.com/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteThird-party scripts

    Scripts run from 8 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 (64 script tags)
    • privacy-proxy.usercentrics.eu (32 script tags)
    • app.usercentrics.eu (32 script tags)
    • www.google.com (41 script tags)
    • code.jquery.com (32 script tags)
    • cdnjs.cloudflare.com (2 script tags)
    • accounts.google.com (40 script tags)
    • policies.termageddon.com (4 script tags)
8 checks passed
  • OKHTTPS

    All 310 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 17 of 310 pages.

  • OKReferrer policy

    A referrer policy is set through a <meta name="referrer"> tag.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKMixed content

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

  • OKForms over HTTPS

    53 forms found, all on HTTPS pages posting to HTTPS addresses.

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

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 www.lovelocal.com

Sites scoring near www.lovelocal.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 www.lovelocal.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.lovelocal.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.lovelocal.com. Removal needs no account and no proof of purchase.
www.lovelocal.com SEO report | DIY SEO Hub