On our own website, we moved WordPress to another server, connected forms in four languages and updated the blog layout. We checked 350 pages and articles during the move. This case brings together the work, enquiry checks and email delivery tests.
Project website: Marketologiya
What needed to change
After the move, we needed to check pages, images, HTTPS, forms and language versions. Enquiry storage and notification delivery were checked separately.
The work took place in September and October 2026. The screenshots show the support page when the case was prepared, including later improvements.
Work and results
| Work | Result | Period or source |
|---|---|---|
| Moving WordPress to another server | 350 pages and articles checked | September 2026 |
| Saving enquiries in four languages | 4 language versions connected | October 2026 |
| A shared article template | 3 articles formatted and linked | October 2026 |
| Notifications to two email addresses | 2 email addresses connected | October 2026 |
| The header and menu at different screen sizes | 6 screen sizes checked | September 2026 |
Moving WordPress to another server
350 pages and articles checked · September 2026
We moved WordPress, its files and database to another server. We checked 350 Russian and Spanish pages and articles, images and HTTPS.
We checked URLs, content and the loading of related files. Opening the homepage alone was not enough to accept the move.
Saving enquiries in four languages
4 language versions connected · October 2026
We connected Russian, Spanish, English and Romanian forms to a shared handler. Each enquiry is saved in the admin panel before notifications are sent.
In October, we added a signed arithmetic question, session checks, limits and protection against duplicate submissions. Newsletter subscriptions require separate email confirmation.
The success message means the enquiry was saved. Email delivery attempts and confirmed subscriptions have separate statuses; this message does not guarantee inbox receipt.
A shared article template
3 articles formatted and linked · October 2026
We first formatted three articles with their assigned author and expert, breadcrumbs, metadata and article markup. We placed their cards on the support page and checked them on mobile.
We then applied the shared template to existing blog posts. It shows actual dates, reading time, assigned people and a contents list. On desktop, the contents sit beside the text; on mobile, above it.
We translated three useful articles for the Spanish and Romanian versions. Cards lead to the matching language, and the language switcher connects translations.
Notifications to two email addresses
2 email addresses connected · October 2026
We configured notifications to two email addresses and fixed the domain’s SPF and DKIM email settings. After setup, we confirmed a new email in the inbox.
Delivery statuses are stored and retries are available. Acceptance by the email service and inbox receipt are checked separately.
The header and menu at different screen sizes
6 screen sizes checked · September 2026
We made the header and menu consistent and checked them at six screen sizes covering phones, tablets and wide screens.
We tested the header separately from articles and forms, including intermediate widths, to find overlapping elements and awkward navigation.
How we checked the results
Before releases, we saved the original files and text. After publication, we read them back from the server and compared checksums. We checked public pages on desktop and mobile.
Form processing was tested with changes rolled back and email and external requests intercepted. Browser submissions were intercepted too. These checks created no permanent test enquiries or external test emails.
The screenshots show the public support page. Private enquiries, visitors’ contacts and delivery settings are not published.
What to keep in mind
350 URLs and four languages describe the relevant stages of work. They are not traffic or sales figures.
One email in the inbox confirms a specific test after setup. Subsequent delivery needs monitoring through statuses and the email channel.
Before similar work
On a multilingual website, check the entire path: the form in the right language, enquiry storage, notification delivery and links to articles. Each step needs its own recorded result.