Scanned sites / www.azpest.com / 2026-09-14-1200

www.azpest.com scan from 2026-09-14 12:00:01 UTC DR 34

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

Scan 2026-09-14-1200

Scanned 2026-09-14 12:00:01 UTC, finished 2026-09-14 12:02:42 UTC. Found on page 3 of chatgpt for browser (api usage) results

Site: https://www.azpest.com/about-us/

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

84/ 100Good

On September 14, 2026 the Site Spider crawled 59 pages and 81 assets of www.azpest.com, starting from https://www.azpest.com/about-us/. It scored 84 out of 100, a good result. 7 of 27 checks found something to fix, led by title tags (31), meta descriptions (19), sitemap coverage (22); 12 checks passed. Most of the points went to title tags (−7), meta descriptions (−3.5), sitemap coverage (−3). 8 checks found something the score does not count, listed as noted. 10 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: Medium2 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
59
Assets fetched
81
Status
Completed
Checks with issues
7 of 27
CoverageComplete crawl

140 of 165 discovered URLs were fetched, 23 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 87 link destinations on other sites were checked.

  • Title tags31 issues
    31 of 44 pages have title issues.
    −7 points
  • Meta descriptions19 issues
    19 of 44 pages have meta description issues.
    −3.5 points
  • Headings2 issues
    2 of 44 pages have heading issues.
    −0.3 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1,769 noted
    0 destinations answered with an error, 68 could not be determined (timeouts, rate limits or refusals), of 87 destinations checked.
  • Redirects16 issues
    15 redirecting URLs, 1 of them chained.
    −1.5 points
  • Non-200 responses15 noted
    15 URLs did not return a 2xx response. 15 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 44 indexable pages have indexability warnings.
  • Image alt text17 issues
    17 of 5135 image references have no alt attribute. 79 use an empty alt (decorative), which is fine.
  • Heavy assets1 issue
    1 asset larger than 500 KB among 81 fetched assets.
    −0.6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage22 issues
    No sitemap found. Tried: https://www.azpest.com/sitemap.xml (skipped), https://www.azpest.com/sitemap_index.xml (skipped). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link counts26 noted
    Internal link counts for 44 pages; 26 worth a look.
  • Thin contentOK
    0 of 44 pages have fewer than 200 words.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 59 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 44 pages have a canonical worth checking.
  • Robots directives44 noted
    44 pages carry a robots directive; 0 carry none.
  • Anchor text6 noted
    6 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure11 noted
    11 of 44 pages could use the title, heading and snippet space better.
  • Image weight and alt length4 noted
    4 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 44 pages answering 200 reads like an error page.
  • 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.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 10 response headers recorded across 140 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 44 pages; 0 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 Insights3 noted
    Mobile performance 88 on average across 5 pages; 3 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2873 sites, median 80%, average 79%

www.azpest.com scores 84%, higher than 65% of the 2873 scanned sites. See the full ranking.

0751500%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 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%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 95 sites87%: 96 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 sites84% 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. 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 shows good health, but several issues need addressing. Prioritize fixing redirect chains, title tags, meta descriptions, missing headings, and adding a sitemap for better SEO performance.

  1. 1

    Fix Redirects and Chains

    Why: Improves site speed and avoids user confusion.

    How: Remove the chained redirect. Redirect all non-www requests directly to the www version.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Ensures all pages return valid responses, improving user experience.

    How: Check the URLs causing non-200 responses and update or remove them.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Shortening titles boosts clarity and improves click-through rates.

    How: Adjust 31 title tags to be under 60 characters reflecting page content.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: Better descriptions can enhance search visibility and CTR.

    How: Revise 9 meta descriptions to be unique and concise, under 160 characters.

    Checks: meta-descriptions

  5. 5

    Add Missing Headings

    Why: Enhances content structure and readability.

    How: Insert a clear H1 tag on the pages missing one.

    Checks: headings

  6. 6

    Create a Sitemap

    Why: Improves search engine indexing of your pages.

    How: Generate a sitemap and place it at https://www.azpest.com/sitemap.xml.

    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

Your website has several security weaknesses that need to be addressed. Critical protections against script attacks and clickjacking are missing, which could expose users to risks. Additionally, server version disclosure can aid attackers, and the use of third-party scripts without integrity checks increases vulnerability. Addressing these issues will improve your site's security significantly.

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

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without a CSP, your site is vulnerable to attacks such as XSS (cross-site scripting) since any scripts can run.

    Fix: Add a Content-Security-Policy header, such as: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  2. 2

    No X-Frame-Options SetMedium

    Why it matters: Missing X-Frame-Options allows your pages to be embedded in frames, risking clickjacking attacks.

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

    Evidence: Clickjacking protection

  3. 3

    Lack of X-Content-Type-OptionsLow

    Why it matters: Without X-Content-Type-Options, browsers may execute files as scripts based on content rather than type.

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

    Evidence: MIME sniffing protection

  4. 4

    Server Version DisclosureLow

    Why it matters: The server version is exposed, which allows attackers to exploit known vulnerabilities.

    Fix: Configure the server to hide version details, or set the header: Server: Custom-Server for obfuscation.

    Evidence: Software version disclosure

  5. 5

    Third-Party Scripts without Subresource IntegrityLow

    Why it matters: Scripts from other domains are used without integrity checks, posing a risk if those domains are compromised.

    Fix: Implement Subresource Integrity where applicable or create a CSP that restricts script sources.

    Evidence: Third-party scripts

  6. 6

    Sensitive Paths in robots.txtInfo

    Why it matters: Exposing /wp-admin/ in robots.txt can guide attackers to sensitive paths.

    Fix: Remove or protect sensitive paths with proper access controls instead of relying on robots.txt.

    Evidence: Sensitive paths in robots.txt

What the checks found

  • FoundContent Security PolicyMedium

    None of the 44 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.azpest.com/about-us/ → no content-security-policy
    • https://www.azpest.com/special-offers/ → no content-security-policy
    • https://www.azpest.com/about-us/pest-control-career-opportunities/ → no content-security-policy
    • https://www.azpest.com/ → no content-security-policy
    • https://www.azpest.com/pest-control/ → no content-security-policy
    • https://www.azpest.com/pest-control/residential-pest-control/ → no content-security-policy
    • https://www.azpest.com/pest-control/commercial-pest-control/ → no content-security-policy
    • https://www.azpest.com/pest-control/az-pest-termite-control-reviews/ → no content-security-policy
    • https://www.azpest.com/tucson-termite-control/ → no content-security-policy
    • https://www.azpest.com/rodent-control/ → no content-security-policy
    • https://www.azpest.com/bee-and-wasp-control/ → no content-security-policy
    • https://www.azpest.com/bee-and-wasp-control/beehive-removal/ → 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.azpest.com/about-us/ → no x-frame-options
    • https://www.azpest.com/special-offers/ → no x-frame-options
    • https://www.azpest.com/about-us/pest-control-career-opportunities/ → no x-frame-options
    • https://www.azpest.com/ → no x-frame-options
    • https://www.azpest.com/pest-control/ → no x-frame-options
    • https://www.azpest.com/pest-control/residential-pest-control/ → no x-frame-options
    • https://www.azpest.com/pest-control/commercial-pest-control/ → no x-frame-options
    • https://www.azpest.com/pest-control/az-pest-termite-control-reviews/ → no x-frame-options
    • https://www.azpest.com/tucson-termite-control/ → no x-frame-options
    • https://www.azpest.com/rodent-control/ → no x-frame-options
    • https://www.azpest.com/bee-and-wasp-control/ → no x-frame-options
    • https://www.azpest.com/bee-and-wasp-control/beehive-removal/ → 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.azpest.com/about-us/ → no x-content-type-options
    • https://www.azpest.com/special-offers/ → no x-content-type-options
    • https://www.azpest.com/about-us/pest-control-career-opportunities/ → no x-content-type-options
    • https://www.azpest.com/ → no x-content-type-options
    • https://www.azpest.com/pest-control/ → no x-content-type-options
    • https://www.azpest.com/pest-control/residential-pest-control/ → no x-content-type-options
    • https://www.azpest.com/pest-control/commercial-pest-control/ → no x-content-type-options
    • https://www.azpest.com/pest-control/az-pest-termite-control-reviews/ → no x-content-type-options
    • https://www.azpest.com/tucson-termite-control/ → no x-content-type-options
    • https://www.azpest.com/rodent-control/ → no x-content-type-options
    • https://www.azpest.com/bee-and-wasp-control/ → no x-content-type-options
    • https://www.azpest.com/bee-and-wasp-control/beehive-removal/ → no x-content-type-options
  • 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.24.0 (Ubuntu) (140 responses)
  • NoteThird-party scripts

    Scripts run from 3 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)
    • www.google.com (14 script tags)
    • cdn.callrail.com (14 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: /wp-admin/
6 checks passed, 4 not applicable
  • OKHTTPS

    All 44 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 44 HTML pages.

  • OKMixed content

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

  • OKForms over HTTPS

    91 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 applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • 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 www.azpest.com

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

Own www.azpest.com?