Make the first response carry the content
On October 2, I worked on a gap between what visitors could read after bogdanalin.com started in the browser and what the first HTML response contained. A page can look complete during an ordinary visit while relying on JavaScript to supply its main content. The aim was to make the public content available earlier, while keeping the existing React application and its interactions.
I started with the English and Romanian FocusFlow project pages. This gave the change a representative pair with real project content and a language relationship to preserve. The build reused the existing renderer to put the content into static HTML. The pilot checks covered the initial text, canonical and language links, and the mounted page on desktop and mobile, including keyboard and reduced-motion behavior.
After the pilot was verified, I extended the same approach across the bilingual public pages. This was build-time rendering for a static website, not a move to a request-time application server. The browser still receives the React assets needed for interactive behavior, but the article and project information no longer depends entirely on waiting for that code to run before it appears in the document.
The release record distinguishes the deployed result from the local build. It records checks of the public initial HTML and matching page assets. The follow-up crawl no longer reported the previous main-content-requires-JavaScript warnings. That observation supports the specific change in content availability; it is not evidence of improved rankings, traffic or enquiries, and it does not mean that every possible crawl warning disappeared.
Reflection
The useful pattern was to prove one bilingual example before expanding the change. Initial HTML and interactive behavior are two parts of the same page experience. Checking both helped make the site easier to read from its first response without giving up the application already built around it.