Automatic deployment to Hostinger from GitHub
How to publish a site to Hostinger automatically from a GitHub repository: Git deployment in hPanel, a webhook, a GitHub Actions build and keeping secrets safe.
For several years this site ran on WordPress with WPML: nine languages, a blog, service pages and about 540 indexed URLs. It had to be rebuilt around a new focus — AI-first development — without losing a single page in search. Instead of another theme and a set of plugins, the site moved to a setup where changes are made by an AI agent and every edit goes through a Git repository.
A script pulled posts and pages through the WordPress REST API, converted the HTML to Markdown and saved each page as a file with metadata: language, URL, translation key, SEO title and description. Links between translations were rebuilt from the hreflang data in the old sitemaps. Images were downloaded into the repository.
The site is built with Next.js into plain HTML files. The server runs no PHP and has no database — nothing to hack and nothing to patch every week. The sitemap with hreflang, an RSS feed per language, llms.txt for AI assistants and the .htaccess rules are generated at build time.
All 541 URLs from the old sitemaps were checked automatically: 423 open at the same address, 118 redirect permanently (301) to their new location. WordPress services, for example, moved into their own /wordpress/ section, and links inside articles were rewritten to the new addresses so there is no extra redirect hop.
From here the site evolves through requests in plain language. An AI coding agent (Claude Code) worked in the project folder: editing content and templates, running the build and checks and showing the result in a local preview. That is how the following were done:
Every change is a commit that can be reviewed and reverted.
After review, changes go to a GitHub repository. GitHub Actions builds the site and puts the result into a separate branch, and the host (Hostinger) pulls it through Git deployment. No more manual FTP uploads.
Sites whose content does not change every minute: company and service sites, blogs, documentation and multilingual sites. If a site needs customer accounts or a complex shop, WordPress can stay — with its code in a repository and managed through an agent as well.
Want the same for your site? See how the agentic website management service works.
Need help with this?
Local machine → repository → server: you ask, an AI agent changes the site, every change is reviewed, saved and deployed automatically. I set it up and teach your team.
How it works →

How to publish a site to Hostinger automatically from a GitHub repository: Git deployment in hPanel, a webhook, a GitHub Actions build and keeping secrets safe.

Two ways to put a WordPress site under Git: keep the theme and plugins in a repository, or export the content into a static site. What to commit and how to deploy.

How managing a website through an AI coding agent works: what to prepare, the cycle from request to publishing, and which tasks to trust an agent with.

Contact
An AI agent, an automation, a website improvement or a full rebuild — describe the task in a few lines and I will reply within one business day.
Tallinn, Estonia · working remotely across Europe
The site does not use cookies. Visit statistics are collected without them. Learn more