robusty.io

Design, copy and structure patterns. These are weak, capped signals — plenty of hand-made sites share them.

• Classic landing page structure weak +2 pts
  UI_HERO_FEATURES_TESTIMONIAL_CTA · design

  The page follows the classic hero / features / testimonials / call-to-action layout. Generated landing pages use it a lot, but it is the standard marketing layout, so this is only a weak hint.

  blocks:

  ["hero","features","pricing","cta"]

• Repeated rounded cards with shadows weak +1 pt
  UI_REPEATED_ROUNDED_CARDS · design

  The markup repeats rounded "card" elements with shadows or borders. This pattern is common in generated landing pages but equally common in hand-made and template sites, so it is only a weak hint.

  css_rules:

  0

  card_like_elements:

  11

• Uniform section rhythm weak +1 pt
  UI_SAME_SECTION_RHYTHM · design

  Many page sections repeat nearly identical markup. Generated landing pages often do this, but so does any consistent component-based design, so this is only a weak hint.

  sections:

  5

  points_before_cap:

  2

  largest_repeated_group:

  5

• Stock Tailwind class combinations weak +1 pt
  UI_STOCK_TAILWIND_COMBOS · design

  Several stock Tailwind class combinations appear in the markup. They come from documentation and templates and are used by people and generators alike, so this is a very weak hint.

  combinations:

  ["flex items-center justify-center","container mx-auto px-4","inline-flex items-center justify-center rounded-md","min-h-screen bg-background"]

Frameworks, libraries and hosting we noticed. Context only — popular tools are not evidence of AI generation and add 0 points.

• Hosting / CDN hint context 0 pts
  TECH_HOSTING_HINT · technology

  The static HTML suggests a known hosting / CDN provider. This is technology context only and adds no points: it is common in both hand-written and generated sites.

  signals:

  ["Vercel response header","Server: Vercel"]

• Uses Lucide icons context 0 pts
  TECH_LUCIDE · technology

  The static HTML suggests Lucide icons. This is technology context only and adds no points: it is common in both hand-written and generated sites.

  signals:

  ["36 SVG icons with lucide classes"]

• Uses Next.js context 0 pts
  TECH_NEXT · technology

  The static HTML suggests Next.js. This is technology context only and adds no points: it is common in both hand-written and generated sites.

  signals:

  ["asset path: /_next/static/chunks/27xodkd_jp4eo.js","App Router flight data"]

• Uses React context 0 pts
  TECH_REACT · technology

  The static HTML suggests React. This is technology context only and adds no points: it is common in both hand-written and generated sites.

  signals:

  ["Next.js runtime (React based)","React runtime bootstrap in inline script"]

• Uses shadcn/ui or Radix UI context 0 pts
  TECH_SHADCN_RADIX · technology

  The static HTML suggests shadcn/ui or Radix UI. This is technology context only and adds no points: it is common in both hand-written and generated sites.

  signals:

  ["shadcn/ui theme tokens: bg-background, text-foreground, text-muted-foreground, bg-primary, text-primary-foreground"]

• Uses Tailwind CSS context 0 pts
  TECH_TAILWIND · technology

  The static HTML suggests Tailwind CSS. This is technology context only and adds no points: it is common in both hand-written and generated sites.

  signals:

  ["103 distinct Tailwind-style utility classes","--tw-* custom properties in CSS"]

• Only a common tech stack context 0 pts
  LIMIT_GENERIC_TECH · constraint

  Only common technologies were detected, with no builder-specific marker. Frameworks such as React, Tailwind or shadcn/ui are used by countless hand-written sites and are not evidence of AI generation.

  technologies:

  ["TECH_LUCIDE","TECH_NEXT","TECH_REACT","TECH_SHADCN_RADIX","TECH_TAILWIND"]