| 开发者 | useinlay |
|---|---|
| 更新时间 | 2026年7月14日 00:04 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<head> of every public page. Placements, URL targeting, and the auction all run on Inlay's servers; there is nothing else to configure in WordPress.yourdomain.com/ads.txt with the seller lines Inlay generates for your active SSP integrations, refreshed every 12 hours. Add your own lines for other partners you work with directly.inlay folder to /wp-content/plugins/, or install through the WordPress plugins screen.In your Inlay dashboard under Sites → your site. It is the long string after /api/script/ in your embed code. You can also paste the entire embed snippet into the plugin — it extracts the ID for you.
No. Inlay decides where ads appear from the placements and URL patterns you configure in the Inlay dashboard. The script injects ads that match your site's design automatically.
Ads are held back until you approve your first AI-generated template in the Inlay dashboard. Visit a matching page once to trigger generation, then approve it under Sites → your site.
The plugin caches Inlay's generated ads.txt for 12 hours. Use "Sync & verify" on the settings screen to refresh immediately. If a physical ads.txt file exists in your WordPress root directory, your web server serves that file first — delete it to let the plugin manage ads.txt.
The embed script works everywhere. Automatic ads.txt serving requires WordPress to answer requests at your domain root; on subdirectory sites host ads.txt at the root manually (the settings screen links to your generated content).