Skip to content

Landing Page & SEO

Tech stack

The landing page is built on Next.js (React, static generation) and TypeScript, plus nodemailer — indicating the landing page has a server-side contact/lead-capture form or an email-sending route.

npm run dev    # local dev server
npm run build
npm run start

Note

See Deployment for how this app is built and deployed relative to the rest of the platform, and Architecture Overview for where it sits among the project's other surfaces.

SEO strategy

The SEO strategy was written after reviewing four named competitor sites in the apartment-locator-data space. The common pattern identified across all of them was topical depth, concrete product language, clear stated market coverage, credibility signals, and many genuinely crawlable pages — not keyword repetition.

Technical SEO implementation

Checklist, current as of the strategy doc:

  • Exact browser-tab title Foundational Data, with a distinctive brand-mark favicon.
  • The homepage stays single-hero-focused; topical depth lives on dedicated, crawlable product/guide/methodology/pricing/market pages.
  • High-intent pages specifically target "apartment locator data" and "locator commission" search queries.
  • A crawlable market directory links to each supported metro's own page, each with unique geography/market context — not templated boilerplate.
  • Every indexable page has a unique title, description, and self-referential canonical tag.
  • robots.txt, an XML sitemap, a web manifest, and Open Graph/Twitter card metadata are all present.
  • Structured data types in use: Organization, SoftwareApplication, Service, HowTo, Article, FAQ.
  • The hero image uses the Next.js image pipeline with responsive sizing and priority loading, rather than a CSS background image.
  • Pages are statically generated so crawlers get full HTML without waiting on client-side rendering.

Why not a large number of near-duplicate city pages

Search engines classify near-duplicate location pages built mainly to capture regional search volume as doorway-page abuse. New market pages are only added once real coverage/inventory/verification data exists for that market — never proactively, purely for SEO volume.

Warning

Avoid generic AI-written "best apartments in every city" content — it doesn't demonstrate the project's actual data advantage and risks being classified as scaled/doorway content by search engines.

Ranking action plan

Ongoing checklist, maintained outside the codebase itself:

  1. Verify the domain in Google Search Console and Bing Webmaster Tools.
  2. Submit the sitemap, inspect key product/market URLs, and resolve any indexing/canonical warnings.
  3. Publish evidence-led market reports at least monthly (original rent, availability, operator, and commission-trend data) as the core defensible content advantage.
  4. Expand each market page with non-sensitive aggregate local stats, a stated methodology date, a sample record, and a named editor/reviewer.
  5. Earn links/citations from locator associations, multifamily industry groups, broker resources, customers, and data partners.
  6. Add real customer proof — attributed case studies, measurable outcomes, testimonials, product screenshots.
  7. Track non-branded search queries per page/market; optimize on impressions/CTR/qualified conversions, not raw traffic.

  8. Measure Core Web Vitals with real field data. Targets:

    Metric Target
    LCP (Largest Contentful Paint) ≤ 2.5s
    INP (Interaction to Next Paint) ≤ 200ms
    CLS (Cumulative Layout Shift) ≤ 0.1

Content sequence

Priority order for what to publish first:

  1. A quarterly apartment-locator-commission report by supported metro.
  2. Market-specific guides to referral registration and verification.
  3. Apartment management-company portfolio indexes sourced from public information.
  4. A building-data methodology and freshness report.
  5. Original analyses of rent, concessions, new supply, and management changes.

Needs verification

The SEO strategy doesn't specify a structured target-keyword list with search volumes — only qualitative target phrases. If a precise keyword table is needed, it will need to be sourced separately (e.g. from page metadata/content in the landing/ codebase itself), not from this strategy document.