Your website
Technical files: robots.txt, ads.txt and verification files
Technical files are plain files your website serves at fixed addresses, such as robots.txt for search engines, ads.txt for ad networks, or a file a service asks you to upload to prove you own the domain. You manage them in your website's Settings under Technical files. Changes are live as soon as you save, so check them first with Preview.
Reviewed · English guide
Automatic, Custom and Off
- Automatic: Eyivo generates the file from your website, for example robots.txt with your sitemap address.
- Custom: your content is served exactly as you save it, up to 64 KB of text.
- Off: the file is not served, and visitors get a "not found" answer.
- Text you saved stays with the file while it is Automatic or Off, and returns when you switch back to Custom.
- Every save keeps the version it replaced. Use Restore previous version to undo your last change.
Standard files
- robots.txt (Automatic by default) tells search engines what they may crawl. In Custom mode Eyivo still adds the Sitemap line unless you turn it off. While your website is hidden from search engines, Eyivo keeps telling them not to index it, whatever the file says.
- ads.txt and app-ads.txt (Off by default) list the ad networks allowed to sell ads on your website or in your apps. Paste the lines your ad network gives you. Keep them Off until you have those lines: buyers read a file without seller lines as "no seller is authorized".
- llms.txt (Automatic by default) gives AI assistants a short guide to your website: its name, description and published pages.
- humans.txt (Off by default) credits the people behind your website.
- .well-known/security.txt (Off by default) tells security researchers how to reach you. Add at least one Contact line. Eyivo writes the Expires line for you and keeps it one year ahead.
- manifest.json (Automatic by default) lets browsers install your website like an app, using your website name, favicon or logo and brand colour.
Add a verification or app file
- Choose Add file under Your files and enter the file name exactly as the service gives it. Capital letters matter, so BingSiteAuth.xml and bingsiteauth.xml are different files.
- Names at the top level must end in .txt, .xml, .json, .html or .webmanifest.
- Under .well-known/ any name is allowed, for example .well-known/assetlinks.json or .well-known/apple-app-site-association.
- The content type is chosen from the file name. Files under .well-known/ without an extension are served as JSON, as Apple's app link file requires.
- A website can have up to 50 of these files. They count toward your database storage.
- Verification pages are shown exactly as issued but can never run scripts.
Check a file before and after saving
- Preview shows the address, status, headers and content the form would get, saved or not. Nothing is saved.
- Eyivo asks before saving a robots.txt that blocks your whole website, an ads.txt without seller lines, or a security.txt without a Contact line. You can still save.
- Open preview opens the saved file on your Eyivo address through a private link that works for 30 minutes. Search engines never see it.
- Once your website has its own domain, Open shows the live file.
Your own domain and your Eyivo address
- Your files are served on every domain connected to your website.
- On your Eyivo address, only Eyivo's automatic robots.txt is served. Services that verify a domain need your own domain.
- Ad networks read ads.txt from your root domain. If your website uses a subdomain such as shop.example.com, the ads.txt file belongs on example.com.
- sitemap.xml is always generated by Eyivo and is not listed here.