Next.js SSR / SSG - correction of the SEO architecture of the real estate website

Good day! I am a Full-Stack JavaScript developer (React / Next.js) with practical experience in migrating SPA projects to SSR/SSG, optimizing Core Web Vitals, and technical SEO for marketplaces and catalog websites.

How do I implement SSR / SSG?
• I am migrating the code from finder-egypt.com to Next.js 14 (App Router).
• Types of pages:
 – home, districts, catalog – SSG + ISR (on-demand revalidate to update offers without a full build).
 – object card – SSG with getStaticPaths (URL based on slug/ID) and getStaticProps (property data).
 – articles / FAQ – SSG (Markdown or CMS-API).
• All HTML is generated on the server / during the build, so Google sees the content without JS.
… • SEO-head through next/head: , , canonical, hreflang (uk | ru | en).
• I create the sitemap and robots.txt through next-sitemap; I include all cards, ISR online updates.
• Images through next/image (alt, lazy loading), 1 per page.
• Internationalization: Next i18n routing / subdomain or /uk-/ru-/en-prefixes (at your choice).

Do you have experience with Next.js + SEO?
Yes, for the last 3 years:
• Realty Portal – migration from Vue-SPA to Next SSR, +65% organic traffic in 4 months.
• e-store EU – SSG catalog with ~60,000 products with ISR and multilingual support (DE/EN/FR).
• law-blog – SSG blog + ISR, PageSpeed Desktop 98/100.
(Additional links can be provided privately.)

Timeline and budget
• SPA and API code review – 0.5 days
• Basic migration to Next.js (layout, navigation, i18n) – 3 days
• Catalog, districts, articles – 3 days
• Object card (SSG + dynamic routes, images, CTA) – 2 days
• SEO basics: sitemap, robots, canonical, hreflang – 1 day
• Googlebot testing (fetch + render), Lighthouse, deployment – 1 day

Total ≈ 10 working days (2 weeks with a buffer for revisions).
Budget: starting from 45,000 UAH depending on the state of the current API and the volume of additional adjustments in the layout.

I am ready to discuss the details and show a demo approach on one test page before starting. Thank you for your attention, and I hope to collaborate!

Best regards,
Roman

Show original

Translate

Hello!

I have reviewed the website finder-egypt.com and the technical specifications. I understand the task as purely technical — currently, the site operates as a SPA, which prevents Google from receiving the ready HTML with content.

I plan to implement it on Next.js with the correct choice of rendering:
- object cards — SSR or ISR (full HTML from the server: title, description, H1, text, images with alt, CTA);
- catalog and areas — SSG / ISR;
- main page, articles, FAQ — SSG or ISR depending on the frequency of updates.

… A basic technical SEO infrastructure will also be implemented: sitemap.xml (including objects), robots.txt, canonical, hreflang (uk/ru/en), 1 H1 per page. The content will be visible without executing JavaScript (checked via View Source).
I suggest starting with a short technical audit (0.5–1 day) to correctly assess the data source, the structure of the SPA, and confirm the final scope of work.
I am ready to discuss the details.

Show original

Translate

Hello. I have reviewed the task description and requirements. Below are the responses by points.

How I will implement SSR / SSG

I am migrating the project to Next.js with the correct choice of rendering mode for the type of page:

SSG + ISR — for static pages (home, districts, articles, FAQ).

SSR — for the catalog and object cards with dynamic data.
…
For each indexed page, ready HTML is generated on the server, available in view-source without executing JavaScript.

Data is fetched through getStaticProps / getStaticPaths / getServerSideProps from the existing API or backend.

Content (title, meta description, h1, text, images with alt, CTA) is rendered by the server.

Experience with Next.js + SEO

Yes, I have practical experience:

building SSR/SSG projects on Next.js for websites with catalogs and product/object cards;

correct SEO foundation: Head, canonical, sitemap, robots, hreflang;

checking indexing through view-source, Google Rich Results Test, Search Console;

optimizing speed and crawl budget.

SEO foundation (implementation)

robots.txt

sitemap.xml (including all objects)

canonical

hreflang (uk / ru / en)

1 H1 per page

unique SEO meta for object cards

correct URLs without SPA traps

Object card (critical)

For each object:

unique SEO URL

full HTML:

title / description

h1

text

images with alt

CTA

the page is fully indexable without JS

Project examples

My latest project on next.js getmon.vercel.app

Timeline

Approximately:

analysis of the current SPA + API: 1–2 days

implementation of SSR/SSG page structure: 5–7 days

SEO foundation + sitemap + indexing testing: 2–3 days

In total: 8–12 working days.

Budget

Estimate: 40–60 hours → 800–1200 USD.
I will confirm the exact estimate after a quick audit of the current code and API.

Show original

Translate

Hello
ready to implement the transition from SPA to Server-side rendering
How do you implement SSR / SSG?
only app router, if the page needs to pull data from the database, it will be SSR, the main thing is to fetch data before rendering. SSG will be automatically generated during the build

Do you have experience with Next.js + SEO?
yes, I have experience, on two projects
Examples of projects (if available)
only in private
… Deadlines and budget
need to see the project.
but approximately 3 weeks, $15/h

Show original

Translate

Hello, Yulia.

What platform is your website currently on?
Could you please respond in private, I will be waiting.

Show original

Translate

Hello.
I understand the task as a purely technical migration from the client-side SPA to an SSR/SSG architecture based on Next.js, so that Google receives fully rendered HTML with all necessary SEO elements, without relying on JavaScript execution. I would implement Next.js using a combination of SSG/ISR for static sections (main, regions, articles/FAQ) and SSR or ISR for dynamic pages, such as the property catalog and property cards, ensuring that each URL returns complete HTML with proper meta tags, H1, content, images with alt, canonical tags, hreflang, sitemap, and robots.txt. I have practical experience implementing Next.js projects with high SEO requirements, including large catalogs and detail pages indexed through SSR/SSG, and I can provide examples and explain the exact rendering strategy for each type of page. The estimated completion time is 3-4 weeks, and the budget will be discussed after reviewing the data sources and the current SPA structure, focusing on a clean, maintainable, production-ready solution rather than shortcuts.

Show original

Translate

Good day.
It is not a problem to implement, but we need to have the development environment files if we just explain. That is, not the build.
Write to me privately, we will discuss.
Regarding the budget, write to me, we will discuss.

Show original

Translate

Hello.
I am interested in your project. I have experience working with Next.js, as well as with SEO and indexing-oriented projects (SSR / SSG). I have implemented static page generation in Next.js, where the content was delivered as ready HTML, and sitemap.xml and robots.txt were automatically generated. I have practical experience with Next.js + SEO. I suggest discussing the deadlines and budget after a brief technical clarification.

I am ready to discuss the project and start working. I would appreciate the opportunity to collaborate.

Show original

Translate

I can redesign finder-egypt.com from SPA to Next.js SSR/SSG/ISR, so Google receives ready HTML with all content (title/description/h1/text/alt/CTA) without executing JS.

How I will implement SSR / SSG:
I will transfer the project to Next.js (prioritizing SSR + ISR): pages will be rendered on the server, and for "object cards" — ISR with auto-updating.
I will set up dynamic routes for objects/areas/articles with unique URLs.
I will create server-side generation of meta (title/description), canonical, hreflang (uk/ru/en), 1 H1 per page.
I will add sitemap.xml with objects, robots.txt, check "view source" and indexing.
Experience with Next.js + SEO
Yes, I have experience in technical SEO: SSR/SSG/ISR, correct meta tags, sitemap/robots/canonical/hreflang, speed and indexing optimization.
…
In the end
Access to the project, sitemap/robots, examples of pages ("view source"), deployment instructions (if needed).
I have a few questions left regarding the data source (API/CRM) and languages/URL structure, let's discuss them in private messages.

Show original

Translate