Zoofi Ads.txt Helper for AdSense
| 开发者 |
asifshaikhtsn
zoofiai |
|---|---|
| 更新时间 | 2026年8月28日 23:06 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Normalizes
ca-pub-1234567890123456,pub-1234567890123456, or the 16 digits alone. - Loads the standard Google AdSense site-wide publisher script in the document head through the WordPress Script API.
- Serves the matching Google
DIRECTrecord at the site's root/ads.txtURL. - Shows the exact generated ads.txt record in WordPress admin.
- Provides an administrator-triggered live diagnostic that fetches only the site's own public homepage and
/ads.txtURL. - Detects missing, duplicate, or mismatched Google publisher loaders in public homepage HTML.
- Verifies that
/ads.txtis publicly reachable and contains the expected publisher record. - Flags a physical root-level
ads.txtfile that may override WordPress rewrites. - Flags active plugins commonly used for advertising or header-code insertion as potential overlap signals.
- Stores no analytics and sends no configuration data to Zoofi.
- Shows administrators an optional review reminder after three days of configured use, with Maybe Later and permanent opt-out controls.
安装:
- Upload the
zoofi-ads-txt-helper-for-adsensefolder to/wp-content/plugins/, or install the plugin ZIP from Plugins > Add New > Upload Plugin. - Activate Zoofi Ads.txt Helper for AdSense.
- Go to Settings > Zoofi Ads.txt Helper for AdSense.
- Enter your Google publisher ID.
- Click Save & Apply.
- Click Run Live Diagnostics to verify the public installation.
常见问题:
Which publisher ID formats are accepted?
You can enter ca-pub-1234567890123456, pub-1234567890123456, or only the 16 numeric digits. The plugin stores the normalized pub- form.
Does this edit header.php?
No. The Google publisher loader is added through the WordPress Script API, so theme files are not modified.
Does this write a physical ads.txt file?
No. The plugin serves a virtual /ads.txt response through WordPress rewrites. A physical root-level ads.txt file may be served by the web server before WordPress; the plugin reports that condition in diagnostics instead of overwriting the file.
What do the diagnostics check?
When an administrator explicitly runs diagnostics, the plugin requests the site's own public homepage and /ads.txt URL. It checks HTTP availability, the expected publisher ID, duplicate Google publisher loaders, mismatched publisher IDs, the expected Google DIRECT ads.txt row, physical ads.txt conflicts, and common plugin-overlap signals.
Does the overlap check disable other plugins?
No. It only reports active plugins commonly used for advertising or header-code insertion so an administrator knows where to investigate a duplicate setup. It never edits or disables another plugin.
Does this create ad units or guarantee AdSense approval?
No. It configures and verifies the publisher loader and the Google ads.txt declaration. It does not create ad units, manage an AdSense account, or guarantee approval, monetization, crawl timing, or policy compliance.
Does Zoofi receive my publisher ID or diagnostic data?
No. The saved publisher ID remains in the WordPress database. The live diagnostic requests only the WordPress site's own public URLs. No diagnostic data is sent to Zoofi.
Does the plugin ask for a review?
After a publisher ID has been configured for three days, administrators may see a small WordPress admin notice asking for an honest review. Maybe Later snoozes the reminder for 30 days, and Don’t Ask Again permanently disables it. The reminder does not block the dashboard and no review is required to use any plugin feature.
What happens on uninstall?
The saved publisher ID, cached diagnostic result, and review-reminder preferences are removed.
更新日志:
- Added an optional WordPress admin review reminder after three days of configured use.
- Added Leave a Review, Maybe Later (30-day snooze), and Don’t Ask Again controls.
- Review-reminder preferences stay local to WordPress and are removed on uninstall.
- Updated the WordPress.org contributor username to
zoofiaiafter plugin ownership transfer. - Prepared new plugin-specific WordPress.org icons that represent ads.txt setup and verification.
- Added the plugin version to the enqueued publisher script to prevent stale browser caching and satisfy WordPress resource-version checks.
- Renamed the plugin to Zoofi Ads.txt Helper for AdSense to clarify that AdSense is a third-party integration.
- Changed the requested WordPress.org slug and Text Domain to
zoofi-ads-txt-helper-for-adsense. - Updated the Contributors field to match the submitting WordPress.org account.
- Updated WordPress compatibility header to Tested up to 7.1.
- Aligned the package identifiers and Text Domain after automated submission checks.
- Added the declared
/languagesdirectory for translation compatibility.
- Improved the plugin display name for clearer purpose and WordPress.org listing clarity.
- Updated the plugin slug, text domain, admin labels, and package identifiers to match the new name.
- Added live publisher diagnostics for the site's own homepage and
/ads.txt. - Added duplicate Google loader detection.
- Added configured-ID mismatch detection.
- Added public ads.txt HTTP and record verification.
- Added foreign Google publisher ID warnings.
- Added physical root ads.txt conflict detection.
- Added potential overlap signals for common advertising and header-code plugins.
- Switched publisher loader output to the WordPress Script API.
- Expanded privacy and external-service documentation.
- Removed the non-unique root Plugin URI header.
- Initial release.
- Added one-field publisher ID setup.
- Added automatic Google publisher header loader.
- Added virtual root
/ads.txtoutput. - Added validation and uninstall cleanup.