How To Add Google AdSense To Hostinger Website, Add Ads txt & Domain Verification code Easily 2026

Google AdSense gives you three separate snippets once you request site verification: a meta tag for domain verification, a single line of text for an ads.txt file, and a script block for the ad unit itself. Each ca-pub number in these snippets is unique to your account, so copy them exactly instead of reusing an example from a tutorial.

The verification tag comes first. Nothing else in AdSense unlocks until Google confirms the domain you're claiming belongs to you.

Your site is listed under the Websites section of hPanel, with a live domain and an Edit or Edit website button. Hostinger currently runs two separate builders from that same section: the point-and-click Website Builder, and Horizons, a prompt-based AI app builder sold on its own subscription.

The steps below follow Website Builder's editor, which has the three-dot menu and Integrations panel this guide uses. A Horizons project doesn't expose that panel; there you'd ask the AI assistant directly to insert the verification snippet into the page head, since Horizons has no separate custom-code settings screen of its own.

If the site runs on WordPress rather than either builder, the equivalent is your theme's header settings or a header/footer plugin. The verification tag itself is identical either way.

Inside the Website Builder editor, open the three-dot menu and choose Integrations to reach the Custom code field. Hostinger auto-places whatever you paste there by tag type: meta, link and style tags go into the page head automatically, while script, noscript and iframe tags go to the end of the body instead.

That's why the verification meta tag needs no extra wrapping. Paste it in as-is, then click Update website so the change publishes rather than sitting as an unsaved draft. Back in AdSense, trigger the verification check; it typically confirms within a few minutes once the tag is live on the published site.

On a Website Builder or Horizons site, ads.txt isn't a file you upload at all. The same Integrations settings that hold the Custom code field also have a dedicated Google AdSense field; paste the single line AdSense gave you there (it reads roughly like google.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0) and save.

Hostinger publishes it at yourdomain.com/ads.txt on its own. On a traditional Hostinger hosting plan running your own WordPress or static files, there's no such field.

There you create a plain text file named exactly ads.txt and drop it straight into public_html through File Manager, so it's reachable at the domain root and not inside a subfolder. Either way, load that URL directly afterward to confirm the line is actually there. Google's own guidance notes ads.txt changes can take several days to register, longer on low-traffic sites, so a same-day recheck can still show a stale result.

AdSense gives you two ways to show ads: Auto ads, where Google decides placement across the site, and manual ad units, which need their code sitting at one exact spot on a page. The sitewide Custom code field from step 3 isn't built for that job.

Script tags pasted there always land at the end of the body, not wherever you want an ad to sit in the page flow. For a manual ad unit at a specific spot, open the builder's Add elements panel, drag an Embed code element onto that spot on the page, click it, choose Enter code, paste the AdSense ad unit script, and confirm with Embed code.

Update the site to publish. This step is optional until AdSense approves the site, but placing it early means ads start appearing the moment approval lands instead of needing a second round of edits.

Check each piece independently instead of assuming success because the site loads normally. View the page source to confirm the meta tag sits in the head, open the ads.txt URL directly to confirm the line is live, and check the AdSense account for verification status. Catching a misplaced snippet here saves a rejected review and a wait for AdSense to recheck the site.