Scanned sites / floridarevenue.com

SEO report for floridarevenue.com DR 82

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

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

Latest scan

Scanned 2026-09-18 07:00:02 UTC, finished 2026-09-18 09:36:45 UTC. Found on page 2 of chatgpt for browser (api usage) results

Site: https://floridarevenue.com/faq/Pages/contactus.aspx

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

65/ 100Needs work

On September 18, 2026 the Site Spider crawled 969 pages and 5057 assets of floridarevenue.com, starting from https://floridarevenue.com/faq/Pages/contactus.aspx. It scored 65 out of 100, a result that needs work. 14 of 26 checks found something to fix, led by sitemap coverage (3,369), heavy assets (28), meta descriptions (650); 4 checks passed. Most of the points went to heavy assets (−6), sitemap coverage (−6), meta descriptions (−5.9). 8 checks found something the score does not count, listed as noted. 11 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: Medium3 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
969
Assets fetched
5057
Status
Completed
Checks with issues
14 of 26
CoverageJob finished, partial coverage

6,026 of 6,689 discovered URLs were fetched, 1 failed, 155 blocked by robots.txt, 709 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. 327 link destinations on other sites were checked, 535 left unchecked.

  • Title tags458 issues
    458 of 659 pages have title issues. 220 noindex or canonicalized pages excluded.
    −5.2 points
  • Meta descriptions650 issues
    650 of 659 pages have meta description issues. 220 noindex or canonicalized pages excluded.
    −5.9 points
  • Headings376 issues
    376 of 659 pages have heading issues. 220 noindex or canonicalized pages excluded.
    −2.6 points
  • Broken links23 issues
    444 internal links point at 23 broken URLs.
    −0.5 points
  • Links to other sites42 issues
    42 destinations answered with an error, 108 could not be determined (timeouts, rate limits or refusals), 535 were left unchecked by the per-scan cap, of 300 destinations checked.
    −1.9 points
  • Redirects56 issues
    57 redirecting URLs, 5 of them chained.
    −0.3 points
  • Non-200 responses35 issues
    93 URLs did not return a 2xx response. 91 of them are pages, 35 with an error status; the rest are assets or redirects.
    −0.4 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability92 issues
    92 of 879 indexable pages have indexability warnings.
    −1 points
  • Image alt text823 issues
    823 of 17681 image references have no alt attribute. 9 use an empty alt (decorative), which is fine.
    −0.3 points
  • Heavy assets28 issues
    28 assets larger than 500 KB among 5057 fetched assets. 1560 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages477 issues
    477 pages have no internal links pointing at them.
    −2.2 points
  • Sitemap coverage3,369 issues
    1 sitemap listing 3556 URLs: 107 crawled pages missing, 503 listed URLs broken or redirecting, 2759 reachable only via the sitemap.
    −6 points
  • Internal link counts49 noted
    Internal link counts for 500 pages; 49 worth a look.
  • Thin content299 issues
    299 of 659 pages have fewer than 200 words. 220 noindex or canonicalized pages excluded.
    −2.7 points
  • Duplicate content2 issues
    1 group of pages with identical HTML.
  • URL format911 noted
    911 of 969 page URLs are harder to read, share or cache than they need to be.
  • Canonicals301 noted
    301 of 879 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 879 pages are open to search engines.
  • Anchor text21 noted
    21 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure165 noted
    165 of 659 pages could use the title, heading and snippet space better. 220 noindex or canonicalized pages excluded.
  • Image weight and alt length11 noted
    9 images over 100 KB; 2 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.
  • 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 879 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 cookies6 noted
    6 cookies set by the site, 6 missing a protective flag; 15 response headers recorded across 6026 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 879 pages; 792 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 InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this site sits among all scanned sites

2873 sites, median 80%, average 79%

floridarevenue.com scores 65%, higher than 9% 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 sites65% 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.

The site has multiple technical SEO issues, such as broken links, redirects, and missing title tags that need urgent fixes to improve its health score. Prioritizing these changes can enhance user experience and search visibility.

  1. 1

    Fix Broken Links

    Why: Resolving broken links enhances user experience and maintains authority.

    How: Identify each broken link and replace or remove it. Use a redirect if the page exists under a new URL.

    Checks: broken-links

  2. 2

    Resolve Redirect Issues

    Why: Chained redirects slow down page loading, affecting SEO.

    How: Streamline redirects by updating links to point directly to the final URL, thus removing unnecessary hops.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: Non-200 responses can hinder page indexing and user access.

    How: Investigate URLs returning errors and correct the underlying issues, either by fixing the server settings or updating links.

    Checks: status-codes

  4. 4

    Optimize Title Tags

    Why: Proper title tags improve click-through rates and search rankings.

    How: Shorten long titles and ensure unique titles for each page relevant to the content.

    Checks: titles

  5. 5

    Improve Meta Descriptions

    Why: Unique meta descriptions can enhance visibility and click-through rates in search results.

    How: Create unique and concise meta descriptions for each page, focusing on relevant keywords.

    Checks: meta-descriptions

  6. 6

    Add Image Alt Text

    Why: Alt text improves accessibility and helps search engines understand image content.

    How: Add descriptive alt attributes to images to convey their purpose or content.

    Checks: images-alt

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 vulnerabilities, primarily a lack of clickjacking protection and missing cookie security flags. It's essential to implement these changes to safeguard user data and enhance overall site integrity.

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

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, pages may be embedded in frames on malicious sites, exposing users to clickjacking attacks.

    Fix: Set the X-Frame-Options header to 'DENY' or use CSP 'frame-ancestors' directive.

    Evidence: Clickjacking protection

  2. 2

    Missing Secure Cookie FlagsMedium

    Why it matters: Cookies lack security flags (Secure, HttpOnly, SameSite), making them vulnerable to theft and misuse.

    Fix: Set Secure, HttpOnly, and SameSite flags on cookies.

    Evidence: Cookie flags

  3. 3

    Outdated JavaScript LibrariesMedium

    Why it matters: Using libraries with known vulnerabilities can lead to security exploits.

    Fix: Upgrade jQuery to at least version 3.5.0 and jQuery UI to 1.13.2.

    Evidence: Vulnerable JavaScript libraries

  4. 4

    Missing Referrer-Policy HeaderLow

    Why it matters: Without this policy, sensitive URL data may be sent to other sites when users navigate away.

    Fix: Add 'Referrer-Policy: no-referrer' or similar to your HTTP headers.

    Evidence: Referrer policy

  5. 5

    Mixed Content IssuesLow

    Why it matters: Loading resources over HTTP on HTTPS pages can enable man-in-the-middle attacks.

    Fix: Ensure all resources are loaded over HTTPS.

    Evidence: Mixed content

  6. 6

    No Permissions Policy HeaderInfo

    Why it matters: Lack of this header means that unnecessary browser features remain enabled, which could be exploited.

    Fix: Implement a Permissions-Policy header to disable unused features.

    Evidence: Permissions policy

What the checks found

  • FoundClickjacking protectionMedium

    866 of 879 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://floridarevenue.com/u002f/u002ffloridarevenue.com/u002fchildsupport/u002f_vti_bin/u002fSpellCheck.asmx → no x-frame-options
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4Subcat=60 → no x-frame-options
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4Subcat=26 → no x-frame-options
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4Subcat=46 → no x-frame-options
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4Subcat=43 → no x-frame-options
    • https://floridarevenue.com/u002f/u002ffloridarevenue.com/u002fproperty/u002f_vti_bin/u002fSpellCheck.asmx → no x-frame-options
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4Subcat=40 → no x-frame-options
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4Subcat=25 → no x-frame-options
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4Subcat=36 → no x-frame-options
    • https://floridarevenue.com/faq/Pages/faqsearch.aspx?Cat=4Subcat=37 → no x-frame-options
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4Subcat=59 → no x-frame-options
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4Subcat=35 → no x-frame-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://floridarevenue.com/faq/Pages/contactus.aspx → no referrer-policy
    • https://floridarevenue.com/Pages/mobile.aspx → no referrer-policy
    • https://floridarevenue.com/Pages/contact.aspx → no referrer-policy
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=1 → no referrer-policy
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=7 → no referrer-policy
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4 → no referrer-policy
    • https://floridarevenue.com/Pages/about_us.aspx → no referrer-policy
    • https://floridarevenue.com/Pages/communication_assistance.aspx → no referrer-policy
    • https://floridarevenue.com/Pages/forms_index.aspx → no referrer-policy
    • https://floridarevenue.com/Pages/media.aspx → no referrer-policy
    • https://floridarevenue.com/opengovt/Pages/meetings.aspx → no referrer-policy
    • https://floridarevenue.com/Pages/survey.aspx → 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://floridarevenue.com/faq/Pages/contactus.aspx → no permissions-policy
    • https://floridarevenue.com/Pages/mobile.aspx → no permissions-policy
    • https://floridarevenue.com/Pages/contact.aspx → no permissions-policy
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=1 → no permissions-policy
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=7 → no permissions-policy
    • https://floridarevenue.com/faq/Pages/FAQSearch.aspx?Cat=4 → no permissions-policy
    • https://floridarevenue.com/Pages/about_us.aspx → no permissions-policy
    • https://floridarevenue.com/Pages/communication_assistance.aspx → no permissions-policy
    • https://floridarevenue.com/Pages/forms_index.aspx → no permissions-policy
    • https://floridarevenue.com/Pages/media.aspx → no permissions-policy
    • https://floridarevenue.com/opengovt/Pages/meetings.aspx → no permissions-policy
    • https://floridarevenue.com/Pages/survey.aspx → no permissions-policy
  • FoundCookie flagsMedium

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

    • dtCookie (set by https://floridarevenue.com/faq/Pages/contactus.aspx) lacks Secure, HttpOnly, SameSite
    • TS019d1b6e (set by https://floridarevenue.com/faq/Pages/contactus.aspx) lacks Secure, HttpOnly, SameSite
    • BIGipServerSP19_FLRevenue_PRD_EXT (set by https://floridarevenue.com/Pages/mobile.aspx) lacks SameSite
    • SearchSession (set by https://floridarevenue.com/taxlaw/Pages/results.aspx) lacks HttpOnly, SameSite
    • TS0139c107 (set by https://floridarevenue.com/taxlaw/Pages/results.aspx) lacks Secure, HttpOnly, SameSite
    • TS01d72afa (set by https://www.floridarevenue.com/taxes/filepay) lacks Secure, HttpOnly, SameSite
  • FoundMixed contentLow

    2 resources on HTTPS pages are loaded over plain HTTP.

    • https://floridarevenue.com/Pages/subscribe.aspx loads image http://img.constantcontact.com/ui/images1/safe_subscribe_logo.gif
    • https://floridarevenue.com/Pages/subscribe.aspx loads image http://img.constantcontact.com/ui/images1/safe_subscribe_logo.gif
  • FoundVulnerable JavaScript librariesMedium

    5 libraries with published vulnerabilities: jQuery 1.10.2, jQuery 3.2.1, jQuery 3.4.1, jQuery 3.3.1, jQuery UI 1.11.2. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.10.2 in https://floridarevenue.com/_catalogs/masterpage/FDOR-Internet/js/common/jquery-…: 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://floridarevenue.com/childsupport/Site%20Assets/js/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
    • jQuery 3.4.1 in https://code.jquery.com/jquery-3.4.1.js: CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • jQuery 3.3.1 in https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.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
    • jQuery UI 1.11.2 in https://floridarevenue.com/_catalogs/masterpage/FDOR-Internet/js/common/jquery-…: CVE-2016-7103, CVE-2021-41182, CVE-2021-41183, CVE-2021-41184, CVE-2022-31160 (XSS through widget options); fixed in 1.13.2
  • 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 (40 script tags)
    • code.jquery.com (40 script tags)
    • whoson.floridarevenue.com (2 script tags)
    • cdnjs.cloudflare.com (21 script tags)
    • cdn.jsdelivr.net (41 script tags)
    • kit.fontawesome.com (1 script tag)
    • cse.google.com (1 script tag)
    • childsupportwebchat.floridarevenue.com (2 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 2 paths 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: /_private/
    • Disallow: /_private/
8 checks passed
  • OKHTTPS

    All 879 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

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

  • OKContent Security Policy

    A Content-Security-Policy is set on 866 of 879 pages.

  • OKMIME sniffing protection

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

  • OKSoftware version disclosure

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

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

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 floridarevenue.com

No other scans of this site yet.

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

Own floridarevenue.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 floridarevenue.com. Removal needs no account and no proof of purchase.