On our own Marketologiya website, we combined WordPress migration, enquiry handling and article layout. This case study follows the stages: checking 350 pages and posts during migration, connecting forms in four languages, email delivery and development of a shared blog template.
Project website: Marketologiya
Initial task
After a website migration, checks need to extend beyond the homepage to content, images, HTTPS, forms and language versions. For an enquiry, storing the record and delivering notifications are separate results.
The case combines several releases of September and October 2026. The screenshots show the state of the support page as of the date of preparation of the analysis, including later improvements.
Work and documented results
| Work | Result | Period or source |
|---|---|---|
| Migration to another server | 350 pages and articles checked | September 2026 |
| Forms and enquiry storage | 4 language versions connected | October 2026 |
| Blog article layouts | 3 articles formatted and linked | October 2026 |
| Enquiry email delivery | 2 email addresses connected | October 2026 |
| Responsive header layout | 6 screen sizes checked | September 2026 |
Migration to another server
350 pages and articles checked · September 2026
We migrated WordPress, files and the database. Checked Russian and Spanish pages and articles, images and HTTPS.
We moved WordPress, files and database to another server. After the transfer, we checked 350 pages and articles in Russian and Spanish, images and HTTPS.
Checking the URL and content helped ensure that the transition was not limited to the successful opening of the main page. We separately checked the loading of related resources and the correctness of protected addresses.
Forms and enquiry storage
4 language versions connected · October 2026
We connected Russian, Spanish, English and Romanian forms to a shared handler. Enquiries are stored in the admin area before notifications are sent.
We connected forms in Russian, Spanish, English and Romanian to a shared handler. The enquiry is saved in the admin panel before notifications are sent.
In October, we added a signed arithmetic question, session checks, rate limits and duplicate protection. Newsletter subscriptions require a separate email confirmation; ordinary service enquiries are stored as requests.
This separates a saved enquiry, a notification delivery attempt and a subscription awaiting confirmation. The success message confirms that the enquiry was saved; it does not guarantee that an email has reached the recipient's inbox.
Blog article layouts
3 articles formatted and linked · October 2026
We added the author, expert, breadcrumbs and article structured data. Displayed previews on the support page and checked them on phones.
In the first stage, we formatted three articles and linked them from the support page. We added the assigned author and expert, breadcrumbs, metadata and responsive layouts.
We later applied the shared template to existing blog posts. It displays actual dates, reading time, assigned author and expert cards, and a table of contents. The table of contents sits beside the article on desktop and before it on mobile.
For Spanish and Romanian support, we have prepared full translations of three useful articles. Cards now lead to texts in the appropriate language; versions are linked by a language switch.
Enquiry email delivery
2 email addresses connected · October 2026
We configured delivery to two addresses and fixed domain SPF and DKIM. A new message arrived in the inbox after setup.
We configured notifications to two email addresses and corrected the domain's SPF and DKIM records. A new email was confirmed in the inbox after setup.
Delivery statuses and retries are recorded for enquiries. Technical acceptance by the mail transport and receipt in an inbox are separate results; the first does not prove the second.
Responsive header layout
6 screen sizes checked · September 2026
We made the header and menu consistent. Checked their display on phones, tablets and wide screens.
We brought the header and menu into a consistent layout and checked six screen sizes, including phones, tablets and wide screens.
The header was checked separately from reading articles and filling out forms. This way you can notice overlapping elements and transitions that become awkward only at intermediate widths.
How we verified the result
When releasing, we saved the original files and content, read them again after publication and compared the hashes. Public pages were checked on a computer and phone.
We tested server-side form processing in database transactions that were rolled back, with email and external requests intercepted. Browser submission tests were also intercepted, leaving no permanent test enquiries or outgoing test emails.
Screenshots show the public support interface. Private requests, visitor contacts and delivery settings are not included in the case.
Scope of the result
350 verified addresses and four languages describe the corresponding stages of work. They are not traffic or sales indicators.
Confirming one email in your inbox refers to a specific delivery check after setup. It does not guarantee receipt of every subsequent email; This requires status monitoring and channel control.
What to consider for a similar project
When supporting a multilingual site, it is useful to check the entire chain: the interface of the desired language, the saved enquiry, notifications and transitions to materials. Each stage must have its own verifiable result.