Tech Akhil SEO Audit Tool
| 开发者 | techakhil |
|---|---|
| 更新时间 | 2026年11月2日 00:20 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
安装:
- Back up your site and test on staging before production use.
- In WordPress, go to Plugins > Add New Plugin > Upload Plugin and upload the ZIP.
- Activate the plugin.
- Add [seo_audit_checklist_tool] to a page using a Shortcode block or supported page builder, then publish it.
- Open the SEO Audit menu to use the admin form and settings.
屏幕截图:
常见问题:
Does the built-in audit require a third-party API?
No. The core audit uses WordPress HTTP functions to request the supplied URL and selected same-host pages. Google Search Console is an optional integration. PageSpeed Insights and the Schema Markup Validator are opened as external websites; this plugin does not call their APIs from the server.
Does the plugin show Google rankings, search volume, or keyword difficulty?
No. The Focus Keyword Analyzer checks selected on-page locations for user-supplied terms. Its score is not a Google ranking score.
Does the crawler inspect all pages and JavaScript-rendered content?
No. Crawling is bounded, limited to the same host, and does not execute JavaScript. Some pages, links, and signals may be missed.
Is Google Search Console required?
No. The core audit works without it. The optional integration requires an administrator to configure OAuth credentials and authorize access to an eligible property.
Are reports stored permanently?
No. Audit Activity optionally stores a normalized domain and timestamp, de-duplicates the same domain per day, prunes records older than one year, and caps the list at 2,000 records. CSV export data is temporary and its random, single-use link expires after two hours.
Does a successful audit guarantee better rankings?
No. Results are selected technical/on-page signals and heuristics; no ranking or performance outcome is guaranteed.
更新日志:
- Validate the selected Search Console property before saving refresh requests and verify inspected URLs against the selected property.
- Keep optional Audit Activity opt-in and document local-only data handling and public cooldown acknowledgement.
- Use strict allow-list sanitizers for boolean settings.
- Document Google OAuth/Search Console data flow with Google API Terms, Privacy Policy, and User Data Policy links.
- Retain enqueued JavaScript assets and WordPress inline-style API rather than inline script blocks.
- Harden CSV export input handling and spreadsheet formula mitigation.
- Use a narrowly scoped safe redirect for Google OAuth authorization and allow only accounts.google.com for that redirect.
- Separate raw public audit URL extraction from HTTP(S)-only URL sanitization.
- Keep plugin metadata, setup documentation, and the user guide aligned with version 1.9.14.
- Sanitize and validate the Google OAuth authorization code once before use.
- Pass an explicit CSV escape parameter to avoid PHP 8.4 fputcsv deprecation warnings.
- Update setup documentation and move older release notes to changelog.txt.
- Move report print behavior to the enqueued front-end script.
- Move inline styles to enqueued stylesheets or the WordPress inline-style API.
- Harden scalar validation for request inputs. See changelog.txt in the plugin package for older release notes.