websites.new

Eight platforms, every path, judged by your pages

Alternatives, chosen from evidence.

Start with your own siteFree · instant

What does this site run on?

Enter a website address

One read of the public homepage: platform, weight, headers and structured data. Nothing is stored and no email is asked for.

Every alternatives list online is written by someone selling one of the options. These guides sit beside a check that reads your own homepage first, so the recommendation starts from what your site ships, and staying put is always one of the answers.

Pick the platform you run.

Each guide covers why teams leave, the support and export facts with their dates and sources, ten to twelve alternatives in one list, and the conditions under which you should stay.

Where sites land, and why.

Six destinations cover almost every move. The platform check names the one that fits your page and the ones that also fit, with the reason for each.

01 · Astro with a headless CMS

Content and marketing sites. Pages are built ahead of time, ship little JavaScript, and the content lives in Sanity or in the repository. The default for most sites that leave a builder or a plugin-heavy CMS.

02 · Next.js with a headless CMS

Sites with an application behind them, personalization, many editors or many locales. Sanity or Contentful hold the content; the front end is code your team reviews.

03 · Keep the CMS, replace the front end

Headless WordPress or decoupled Drupal: editors keep their tools, and the theme and plugins leave the request path. The middle path when the content model is the asset.

04 · Another builder

Webflow or Framer when no developer is on hand and the site stays under their CMS and plan limits. The honest answer for many Wix and Squarespace sites.

05 · Keep the checkout

Shopify stays for payments and orders; a headless storefront or a separate marketing site replaces the heavy theme. Most Shopify stores do not need a platform move.

06 · Stay

A light page on good hosting is a reason to stay. Every guide here includes that case and its conditions; the platform check says it to your face when it applies.

Check what your site runs on

Questions, answered.

01Who writes these alternatives pages?

Gautam Khorana, who built the assessment and consults on moving legacy and WordPress estates to modern stacks. No vendor sponsors a position here, every list includes a stay-put entry, and the platform check reads your own site before anything is recommended to you.

02Which modern stack do you recommend?

It depends on what your pages show. Astro for content and marketing sites, Next.js with a headless CMS when there is an application, many editors or many locales, a builder when nobody on your team writes code, and the checkout you already have when you run a store.

03Do you move sites to WordPress?

No. New builds and migrations here land on Astro or Next.js with a headless CMS. Headless WordPress is sometimes the right middle step for a team that wants to keep its editor, and the WordPress guide covers when that pays off and when it does not.

04What does the 30-minute consultation cover?

Your goals, the platform you run, the constraints that matter and the next useful step. Bring the platform check card or a report link. It is a conversation, not a quote; scope and pricing follow once the shape of the work is clear.

Talk it through

Bring your site. Leave with a path.