B-Hive Living
Active build · review preview
In progress: the review preview is available at rent.b-hiveliving.com/home and remains noindex until the migration is ready.

TL;DR
B-Hive Living is separating its property enquiry journey from a new information site for renters, partners and local audiences in Bicester and Kidlington.
Problem: Separate the renter enquiry journey from the new brand and information site without disrupting the existing rental pages during migration.
What we did: Built the review site under /home, wired WordPress FAQ/blog content and connected structured enquiry attribution to B-Hive's Apointoo tenant.
Stack: Next.js 16 · React 19 · TypeScript · Tailwind CSS 4 · Zod · React Hook Form · WordPress · Apointoo

What was done
This is an active website build, not a completed launch. The review experience lives at /home on rent.b-hiveliving.com and is intentionally noindex, nofollow and excluded from the sitemap while the migration plan remains in progress.
The project gives two web surfaces different jobs. The existing rental site continues to handle homes, prices and enquiries. The new information site is being prepared for brand and partner pages, FAQs, legal information and a future blog. It has its own header, footer and route registry. Host-aware routing and redirects are prepared for the later domain switch, so the current rental journey can keep running during review.
The information site uses Next.js 16.4 App Router, React 19.2, TypeScript, Tailwind CSS 4, Zod and React Hook Form. WordPress supplies headless FAQ and blog content. This keeps editorial updates in the CMS while the website owns its layout, route visibility and migration rules.
The enquiry flow connects the B-Hive tenant in Apointoo through a server-side intake route. Its structured payload keeps first and last touch separate, carries click and campaign fields and GA session identifiers, and includes the CookieYes consent vector. Visitor and browser identifiers are gated by advertising consent. This gives the lead record useful acquisition context without collapsing it into the message field.
The next milestone is the domain switch. Until then, this case records implementation and review state only; it makes no traffic, lead or ranking claims.




