Scanned sites / www.nativeme.com / 2026-09-24-0000
www.nativeme.com scan from 9/24/2026, 12:00:01 AM
Scan 2026-09-24-0000
Scanned 9/24/2026, 12:00:01 AM, finished 9/24/2026, 2:22:06 AM. Found on page 3 of chatgpt for browser (api usage) results
Site: https://www.nativeme.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 24, 2026 the Site Spider crawled 5000 pages and 1000 assets of www.nativeme.com, starting from https://www.nativeme.com/. It scored 91 out of 100, an excellent result. 9 of 14 checks found something to fix, led by sitemap coverage (2496), indexability (593), title tags (500); 5 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: Medium5 medium, 3 low and 1 info findings. See the security findings ↓
- Pages crawled
- 5000
- Assets fetched
- 1000
- Status
- Completed
- Checks with issues
- 9 of 14
- Title tags500 issues2044 of 4788 pages have title issues. 204 noindex or canonicalized pages excluded.
- Meta descriptions500 issues4788 of 4788 pages have meta description issues. 204 noindex or canonicalized pages excluded.
- Headings47 issues47 of 4788 pages have heading issues. 204 noindex or canonicalized pages excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- Redirects8 issues11 redirecting URLs, 2 of them chained.
- Non-200 responses1 issue13 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability593 issues593 of 4992 indexable pages have indexability warnings.
- Image alt text81 issues81 of 14824 image references have no alt attribute. 11 use an empty alt (decorative), which is fine.
- Heavy assets5 issues5 assets larger than 500 KB among the 100 heaviest.
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage2496 issuesNo sitemap found. Tried: https://www.nativeme.com/!ut/p/z0/04_Sj9CPykssy0xPLMnMz0vMAfIjo8zi3T28zTy8nA38DTxNTQwCvf39LLxczY0NDIz1vfSjgAoMcABHA5AJRkW-zr7p-lEFiSUZupl5afn6EcWZJam5iQV6Fbk5-gXZUZEAKC7-NQ!!/ (302), https://www.nativeme.com/sitemap.xml (302). Add one at /sitemap.xml or list it in robots.txt.
- Thin contentOK0 of 4788 pages have fewer than 200 words. 204 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1215 sites, median 82%, average 80%
www.nativeme.com scores 91%, higher than 88% of the 1215 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 findingsThere are several critical SEO issues on your site including redirects, status codes, and missing meta descriptions. Addressing these will enhance your site's search visibility and user experience.
- 1
Fix Redirects
Why: Eliminating redirects improves load speed and SEO.
How: Update the affected URLs to point directly to their final destinations.
Checks: redirects
- 2
Resolve Non-200 Responses
Why: Fixing these URLs ensures users access the correct pages.
How: Identify and restore the pages with non-200 status to functional URLs.
Checks: status-codes
- 3
Add Meta Descriptions
Why: Meta descriptions help improve click-through rates in search results.
How: Create unique meta descriptions for each page that summarize content effectively.
Checks: meta-descriptions
- 4
Fix Title Tag Issues
Why: Clear and relevant title tags enhance SEO and user experience.
How: Revise titles to ensure they are unique and at least 30 characters long.
Checks: titles
- 5
Establish Sitemap
Why: A sitemap aids in faster and more efficient indexing by search engines.
How: Create and upload a sitemap file at /sitemap.xml.
Checks: sitemap-coverage
- 6
Address Heading Issues
Why: Proper heading usage improves accessibility and SEO.
How: Ensure each page has a single, clear H1 tag and organize content with H2 and H3 tags.
Checks: headings
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 significant security weaknesses due to missing HTTP response headers and outdated libraries. Key protections against potential attacks, such as X-Frame-Options and Content Security Policy, are not implemented, increasing the risk of exploit. Immediate action is recommended to enhance security.
- 0 high
- 5 medium
- 3 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors may be intercepted when accessing your site via HTTP.
Fix: Implement HSTS by adding 'Strict-Transport-Security: max-age=63072000; includeSubDomains; preload' to your HTTP responses.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Absence of CSP allows any scripts and styles to load, making the site vulnerable to attacks.
Fix: Implement CSP by adding 'Content-Security-Policy: default-src 'self';' to your HTTP headers.
Evidence: Content Security Policy
- 3
No X-Frame-Options HeaderMedium
Why it matters: Without this header, your site can be embedded in frames, risking clickjacking.
Fix: Add 'X-Frame-Options: DENY' to your HTTP responses to prevent framing.
Evidence: Clickjacking protection
- 4
Cookies Missing Security FlagsMedium
Why it matters: Cookies without flags like Secure and HttpOnly can be hijacked.
Fix: Ensure cookies are set with 'Secure; HttpOnly; SameSite=Strict'.
Evidence: Cookie flags
- 5
Outdated JavaScript LibraryMedium
Why it matters: Using jQuery 3.3.1 with known vulnerabilities increases security risks.
Fix: Upgrade jQuery to version 3.5.0 or higher to fix known vulnerabilities.
Evidence: Vulnerable JavaScript libraries
- 6
Missing X-Content-Type-Options HeaderLow
Why it matters: Without this header, browsers might incorrectly execute scripts.
Fix: Add 'X-Content-Type-Options: nosniff' to your HTTP headers.
Evidence: MIME sniffing protection
- 7
No Referrer-Policy HeaderLow
Why it matters: Not using a Referrer-Policy may leak URL information to external sites.
Fix: Add 'Referrer-Policy: no-referrer' to your HTTP headers to limit this data leakage.
Evidence: Referrer policy
- 8
Server Version DisclosureLow
Why it matters: Revealing server version can help attackers find vulnerabilities.
Fix: Remove or obscure 'Server' and 'X-Powered-By' headers from HTTP responses.
Evidence: Software version disclosure
- 9
Missing Permissions-Policy HeaderInfo
Why it matters: A Permissions-Policy helps limit features on the site that could be exploited by malware.
Fix: Add 'Permissions-Policy: geolocation=(self), microphone=()' to your HTTP responses.
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.nativeme.com/products?clear=true → no strict-transport-security
- https://www.nativeme.com/about → no strict-transport-security
- https://www.nativeme.com/about/terms-of-use → no strict-transport-security
- https://www.nativeme.com/about/local-list → no strict-transport-security
- https://www.nativeme.com/contact → no strict-transport-security
- https://www.nativeme.com/category/2/Produce/ → no strict-transport-security
- https://www.nativeme.com/category/3/Apples/ → no strict-transport-security
- https://www.nativeme.com/category/4/Citrus/ → no strict-transport-security
- https://www.nativeme.com/category/5/Flowers/ → no strict-transport-security
- https://www.nativeme.com/category/6/Fruit/ → no strict-transport-security
- https://www.nativeme.com/category/7/Greens/ → no strict-transport-security
- https://www.nativeme.com/category/8/Herbs/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 4992 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.nativeme.com/products?clear=true → no content-security-policy
- https://www.nativeme.com/about → no content-security-policy
- https://www.nativeme.com/about/terms-of-use → no content-security-policy
- https://www.nativeme.com/about/local-list → no content-security-policy
- https://www.nativeme.com/contact → no content-security-policy
- https://www.nativeme.com/category/2/Produce/ → no content-security-policy
- https://www.nativeme.com/category/3/Apples/ → no content-security-policy
- https://www.nativeme.com/category/4/Citrus/ → no content-security-policy
- https://www.nativeme.com/category/5/Flowers/ → no content-security-policy
- https://www.nativeme.com/category/6/Fruit/ → no content-security-policy
- https://www.nativeme.com/category/7/Greens/ → no content-security-policy
- https://www.nativeme.com/category/8/Herbs/ → 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.nativeme.com/products?clear=true → no x-frame-options
- https://www.nativeme.com/about → no x-frame-options
- https://www.nativeme.com/about/terms-of-use → no x-frame-options
- https://www.nativeme.com/about/local-list → no x-frame-options
- https://www.nativeme.com/contact → no x-frame-options
- https://www.nativeme.com/category/2/Produce/ → no x-frame-options
- https://www.nativeme.com/category/3/Apples/ → no x-frame-options
- https://www.nativeme.com/category/4/Citrus/ → no x-frame-options
- https://www.nativeme.com/category/5/Flowers/ → no x-frame-options
- https://www.nativeme.com/category/6/Fruit/ → no x-frame-options
- https://www.nativeme.com/category/7/Greens/ → no x-frame-options
- https://www.nativeme.com/category/8/Herbs/ → 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.nativeme.com/products?clear=true → no x-content-type-options
- https://www.nativeme.com/about → no x-content-type-options
- https://www.nativeme.com/about/terms-of-use → no x-content-type-options
- https://www.nativeme.com/about/local-list → no x-content-type-options
- https://www.nativeme.com/contact → no x-content-type-options
- https://www.nativeme.com/category/2/Produce/ → no x-content-type-options
- https://www.nativeme.com/category/3/Apples/ → no x-content-type-options
- https://www.nativeme.com/category/4/Citrus/ → no x-content-type-options
- https://www.nativeme.com/category/5/Flowers/ → no x-content-type-options
- https://www.nativeme.com/category/6/Fruit/ → no x-content-type-options
- https://www.nativeme.com/category/7/Greens/ → no x-content-type-options
- https://www.nativeme.com/category/8/Herbs/ → 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://www.nativeme.com/products?clear=true → no referrer-policy
- https://www.nativeme.com/about → no referrer-policy
- https://www.nativeme.com/about/terms-of-use → no referrer-policy
- https://www.nativeme.com/about/local-list → no referrer-policy
- https://www.nativeme.com/contact → no referrer-policy
- https://www.nativeme.com/category/2/Produce/ → no referrer-policy
- https://www.nativeme.com/category/3/Apples/ → no referrer-policy
- https://www.nativeme.com/category/4/Citrus/ → no referrer-policy
- https://www.nativeme.com/category/5/Flowers/ → no referrer-policy
- https://www.nativeme.com/category/6/Fruit/ → no referrer-policy
- https://www.nativeme.com/category/7/Greens/ → no referrer-policy
- https://www.nativeme.com/category/8/Herbs/ → 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://www.nativeme.com/products?clear=true → no permissions-policy
- https://www.nativeme.com/about → no permissions-policy
- https://www.nativeme.com/about/terms-of-use → no permissions-policy
- https://www.nativeme.com/about/local-list → no permissions-policy
- https://www.nativeme.com/contact → no permissions-policy
- https://www.nativeme.com/category/2/Produce/ → no permissions-policy
- https://www.nativeme.com/category/3/Apples/ → no permissions-policy
- https://www.nativeme.com/category/4/Citrus/ → no permissions-policy
- https://www.nativeme.com/category/5/Flowers/ → no permissions-policy
- https://www.nativeme.com/category/6/Fruit/ → no permissions-policy
- https://www.nativeme.com/category/7/Greens/ → no permissions-policy
- https://www.nativeme.com/category/8/Herbs/ → 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 (6000 responses)
- x-powered-by: Servlet/3.1 (5044 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.
- JSESSIONID (set by https://www.nativeme.com/products?clear=true) lacks Secure, HttpOnly, SameSite
- WASReqURL (set by https://www.nativeme.com/myportal/products/!ut/p/z0/04_Sj9CPykssy0xPLMnMz0vMAfI…) lacks Secure, SameSite
- FoundVulnerable JavaScript librariesMedium
1 library with published vulnerabilities: jQuery 3.3.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 3.3.1 in https://www.nativeme.com/contenthandler/!ut/p/digest!J5cCsISUfWcrxhMWKFZgIw/mas…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
- 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 (80 script tags)
5 checks passed, 1 not applicable
- OKHTTPS
All 4992 crawled pages were served over HTTPS.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
40 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.
Sites scoring near www.nativeme.com
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- dalesautocare.com92/100 · rank 86 · 199 pages
- crowd-pinch.com92/100 · rank 86 · 5,000 pages
- downtowndentalcentre.com92/100 · rank 86 · 197 pages
- www.perfectionplumbing.ca91/100 · rank 110 · 409 pages
- www.allendaledental.ca91/100 · rank 110 · 78 pages
- kingsviewdental.ca91/100 · rank 110 · 134 pages
This report was produced by the DIY SEO Hub Site Spider crawling www.nativeme.com from its pages as published, the way a search engine does. It shows summary figures only.
Own www.nativeme.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.nativeme.com. Removal needs no account and no proof of purchase.