Skip to content
Deal212 Audit

SEO and Performance

Search visibility and speed

The biggest loss here is discoverability: robots.txt and sitemap.xml return homepage HTML instead of text, and pages share generic titles with no canonical or social tags. Caching and assets follow.

At a glance

  • Crawlers read no crawl rules or sitemap (CR-01).
  • Titles are generic and shared across pages (HI-05).
  • No per-page canonical or social tags (HI-06).
  • Caching and assets are not tuned (MD-06, MD-07).
  • No structured data on the homepage (LW-01).

Findings

HI-05

Non-unique titles and descriptions across pages

High

Verified on live site

What was observed

The homepage and several other pages share the generic title 'Deal212 | Direct Deal Network'; /check uses a different title. No page has a unique, descriptive title and meta description.

Why it matters

Duplicate or generic titles and descriptions weaken search visibility and click-through and make pages hard to tell apart in results.

Fix or reference

Per-route head
<!-- Homepage -->
<title>Deal212 - NYC Off-Market Property Intel</title>
<meta name="description" content="Live NYC property reports: value, comparables, liens, violations.">

<!-- Property Check -->
<title>Property Check - Deal212</title>
<meta name="description" content="Enter an NYC address for estimated value, comps, liens, and violations.">

Remediation checklist

0 of 2 complete

HI-06

Missing robots.txt, sitemap.xml, and social/canonical meta

High

Verified on live site

What was observed

robots.txt and sitemap.xml return homepage HTML (covered in CR-01). Open Graph, Twitter card, and canonical tags are not consistently set per page.

Why it matters

Without these, crawlers cannot correctly index or discover pages, and social platforms render weak or broken link previews. Canonical tags prevent duplicate-content dilution.

Fix or reference

Canonical + social meta
<link rel="canonical" href="https://deal212.sites.tab.bot/check">
<meta property="og:title" content="Property Check - Deal212">
<meta property="og:description" content="Enter an NYC address for value, comps, liens, violations.">
<meta property="og:type" content="website">
<meta name="twitter:card" content="summary_large_image">
<meta property="og:image" content="https://deal212.sites.tab.bot/opengraph.jpg">

Remediation checklist

0 of 2 complete

MD-06

CDN caching is not tuned for assets or the lead endpoint

Medium

Verified on live site

What was observed

Caching policy is not tuned: no evidence of immutable, long-lived caching for hashed asset URLs, no clear short/no-cache rule for HTML, and no guarantee that POST /api/lead responses are never cached.

Why it matters

Wrong caching can serve stale HTML, waste bandwidth, or - worst case - cache lead-intake responses that contain submitted personal data.

Fix or reference

Cache-Control guidance
# Hashed assets: immutable, far-future
/assets/*.{js,css,woff2}    Cache-Control: public, max-age=31536000, immutable

# HTML: short or no-cache so deploys propagate fast
/*.html                     Cache-Control: public, max-age=0, must-revalidate

# Never cache lead intake
POST /api/lead               Cache-Control: no-store

# Never cache responses containing personal data
/api/lead          no-store, no-cache, must-revalidate

Remediation checklist

0 of 3 complete

MD-07

Asset optimization is incomplete

Medium

Verified on live site

What was observed

Images appear to be served in legacy formats without explicit dimensions, and bundles and fonts are not fully optimized, which slows first paint on mobile.

Why it matters

Oversized images, layout-shifting without width/height attributes, and blocking resources make the critical path heavier than it needs to be on the devices that matter most.

Fix or reference

Responsive image
<picture>
  <source type="image/avif" srcset="/hero.avif" />
  <source type="image/webp" srcset="/hero.webp" />
  <img
    src="/hero.jpg"
    alt="Property in New York City"
    width="1200"
    height="800"
    loading="lazy"
    decoding="async"
  />
</picture>

<!-- @font-face { font-display: swap; } -->
<!-- route-level code splitting; purge unused CSS and JS -->

Remediation checklist

0 of 3 complete

LW-01

No Organization or WebSite JSON-LD structured data

Low

Needs verification

What was observed

No Organization or WebSite JSON-LD schema was found on the homepage. This caps eligibility for rich search results and entity understanding.

Why it matters

Structured data helps search engines understand the site name and organization, and enables eligible rich results.

Fix or reference

JSON-LD
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Deal212",
  "url": "https://deal212.sites.tab.bot/"
}
</script>

Remediation checklist

0 of 2 complete