HomeAPI StatusFree ToolsSEO Help Articles

Frameset Test

The Frameset Test scans any URL for the legacy <frameset> and <frame> elements used in 1990s and early-2000s websites to split a window into independently scrolling regions. Framesets are obsolete, removed from HTML5, inaccessible to most modern tools and totally invisible to Googlebot — pages built with them effectively have no SEO. Modern alternatives are <iframe> for embedded content or proper component-based layouts.

What This Tool Checks

  • Presence of <frameset>, <frame> or <noframes> elements
  • iframes used in their place
  • Page accessible without frame navigation
  • Indexability of individual frame contents
  • HTML5 doctype mismatch with frameset usage

Why It Matters for SEO

Framesets break virtually every modern web pattern: deep linking, mobile rendering, accessibility, search indexing. A page that uses <frameset> as its main layout is almost invisible to Google because each frame is indexed as a separate orphan URL with no context. The fix is a full conversion to a proper layout — usually a quick win because frame-based sites tend to be small, old and overdue for redesign anyway.

How to Fix It

Replace the entire frameset with a modern HTML5 layout. Use <iframe> for embedding genuinely separate documents. For navigation panels and headers, use shared component templates rendered server-side or client-side as appropriate.

How It Works

We parse the page HTML and look for the obsolete frameset elements. Any usage is reported with the modern replacement pattern (iframes for embeds, component layouts for everything else).

Common Mistakes to Avoid

  • Continuing to maintain a 1998-era frameset site
  • Using <frameset> instead of CSS Grid because the team is unfamiliar with modern layout
  • Loading external sites in <frame> when modern <iframe> with sandboxing is correct
  • Treating framesets as "good enough" for an internal admin tool
  • Ignoring the SEO and accessibility cost because the team has not been audited recently

Quick Checklist

  • No <frameset>, <frame> or <noframes> in production HTML
  • iframes used only for genuinely embedded content
  • Mobile-friendly responsive layout in place
  • Each URL is indexable as a standalone page
  • HTML5 doctype with no frameset usage

Frequently Asked Questions