Skip to main content
View Categories

Keeping property URLs on a custom-coded site

Yes, with one condition. HomeRunner’s any-website version adds search, listings, property pages and checkout to a custom-coded site, such as one built with Next.js, Astro or Vercel, as drop-in components.

How pages are served. When your domain runs through Cloudflare, HomeRunner places a small worker in front of your site. The worker serves the property, listings and checkout routes with the content already in the HTML, including title tags, structured data and a property sitemap. Search engines read these routes the way they read server-rendered pages. Live rates and availability load in the browser on top of that content. Checkout stays on your domain.

Keeping your property URLs. Property URLs are configured as routes, so you can keep an existing pattern such as /property/<slug>/. Exact slugs are confirmed during setup. If any other pages move, you handle the redirects for them on your side.

Current limitations. Feature parity with the WordPress version is still in progress, and the AI Concierge is not yet available on the any-website version.