WordPress to Next.js Migration — 250 URLs, SEO Preservation

Boston Luxury Chauffeur is seeking an experienced Next.js developer with strong technical SEO and website migration experience to migrate our existing WordPress website to a complete Next.js website. The site has approximately 250 published URLs and existing Google rankings. Protecting our organic visibility, valuable content, and booking functionality is a core requirement. This is a full WordPress-to-Next.js migration, not a WordPress theme redesign. SCOPE AND DELIVERABLES 1. Audit and migration plan - Crawl and inventory all existing URLs, including pages, posts, images, existing redirects, and key landing pages. Establish an SEO and performance baseline using available Search Console/analytics data. - Document status codes, titles, meta descriptions, headings, canonical tags, indexability, schema, internal links, image URLs/alt text, and current content. - Provide a URL-by-URL migration mapping and launch checklist. Preserve important URLs and permalink structure wherever possible. Any necessary URL changes or content consolidation require approval and relevant one-to-one permanent redirects, with no redirect chains or blanket homepage redirects. 2. Complete Next.js build and content migration - Build a fast, responsive, mobile-friendly Next.js website with a polished luxury chauffeur presentation and clear booking calls to action. - Migrate all agreed published content and assets across approximately 250 URLs. Preserve valuable page content, search intent, titles, meta descriptions, structured data, internal links, images, and existing SEO signals. - Identify weak pages and propose useful content, navigation, and on-page SEO improvements instead of blindly copying problems. Do not remove or substantially rewrite ranking pages without approval. - Recommend a maintainable content-editing approach and explain whether WordPress would remain only as a headless CMS or be fully replaced, including costs and tradeoffs. The public website must be Next.js. 3. Technical SEO and performance - Use appropriate server rendering/static generation so important content and metadata are crawlable without relying on client-side JavaScript. - Implement correct canonical URLs, XML sitemap(s), robots directives, status codes, redirects, helpful 404 handling, and valid relevant structured data. Preserve or improve existing schema accurately; avoid duplicate metadata and broken internal links. - Optimize images, fonts, JavaScript, CSS, caching, and loading behavior. Measure mobile and desktop performance on representative templates and key landing pages, report before/after results, and propose measurable Core Web Vitals targets with any third-party limitations explained. - Preserve existing analytics, Search Console verification, and conversion tracking where present; validate booking-related events without duplicate tracking. 4. Keep Limo Anywhere Quick Res working - Preserve the existing Limo Anywhere Quick Res booking integration and booking links. - Test the complete booking journey on mobile and desktop, including embedded widgets/scripts, navigation, and confirmation behavior where test access permits. Coordinate test bookings so no unintended live reservations or charges occur. 5. Temporary domain, testing, and deployment - Build and deploy first on a temporary/staging domain. Keep staging out of search indexes and prevent duplicate-content exposure. - Store the source code in our GitHub repository and configure a documented GitHub-to-Hostinger Web Apps deployment workflow. Confirm the proposed Next.js architecture works with our Hostinger setup before implementation. - Fully test staging before switching the main domain: reconcile all inventoried URLs, verify content/metadata/schema/redirects/images/internal links, check responsive layouts and major browsers, and test booking and tracking. - Provide staging for approval with a QA report and no unresolved critical migration or booking defects. Do not switch the main domain until we approve. - Prepare backups and a rollback plan, then manage the approved production cutover, HTTPS/domain configuration, production crawl, sitemap submission/validation, and indexability checks. Ensure staging restrictions are removed from production appropriately. HANDOVER AND ACCEPTANCE Deliver the complete source code, migrated content/assets, URL and redirect mapping, audit and QA reports, deployment instructions, content-editing documentation, and a walkthrough. Include a proposed post-launch support period for monitoring crawl/indexing issues, redirects, booking functionality, and migration defects, and state exactly what is covered. SEO preservation is essential. We expect a careful, evidence-based migration and monitoring plan rather than a promise of guaranteed rankings. PROJECT AND QUOTE This is a fixed-price project. Please provide an itemized fixed-price quote for the complete scope, proposed milestones, estimated timeline, assumptions, exclusions, any ongoing CMS/hosting/service costs, and post-launch support. If an initial audit is needed to finalize pricing, separate its fixed cost and deliverables from the implementation estimate. No implementation or paid work begins until scope, price, and milestones are agreed. IN YOUR PROPOSAL, PLEASE ANSWER 1. Share 2–3 relevant WordPress-to-Next.js migrations, ideally sites with 200+ URLs, and explain your role and how you protected SEO. 2. How will you inventory and preserve URLs, metadata, schema, internal links, redirects, and ranking pages, and verify nothing important is lost? 3. What Next.js rendering/content-editing architecture do you recommend, and how will you deploy it from GitHub to Hostinger Web Apps? 4. How will you preserve and test Limo Anywhere Quick Res, and handle staging approval, production cutover, rollback, and post-launch monitoring? 5. What is your fixed total price, milestone breakdown, delivery timeline, availability, and included support period? Please explicitly confirm that your proposal covers a complete Next.js migration of approximately 250 published URLs, technical SEO improvements, temporary-domain testing, and a working booking integration.