Description
Configure search appearance, social metadata, breadcrumbs, and schema. Review internal links, manage sitemap and robots files, and run SEO/CRO scans from the WordPress dashboard.
External services
360 Digital Marketing scan service
Endpoint: https://seo.360digitalmarketing.org
Provides crawling, SEO/CRO analysis, stored reports and exports. Scan creation sends the project name, start URL, maximum page count and depth, query-URL preference, exclusion patterns, robots.txt preference and the saved SEO key when present. Listing scans sends site URL, filters and SEO key; report, status, export and deletion requests send the scan ID (deletion also sends the SEO key). The service fetches the site’s public pages. Like other HTTP services, it receives the server’s IP address and HTTP headers.
No calls are made until an administrator saves the explicit service opt-in. After opt-in, loading Site Audit retrieves recent scans, polling retrieves progress, and manual scan/report/export/delete actions contact the service. A separate, unchecked-by-default daily audit option allows automatic scans of up to 1,000 pages and depth 6, with the first run due after five minutes. WordPress cron controls the actual run time. Disabling either consent option stops future scheduled scans; disabling the service blocks all scan-service requests. Activation alone does not enable or contact the service.
Service website: https://360digitalmarketing.org/
Terms of Service and Privacy Policy (combined page): https://360digitalmarketing.org/privacy-policy/
Google PageSpeed Insights
Endpoint: https://www.googleapis.com/pagespeedonline/v5/runPagespeed
Provides mobile and desktop performance, accessibility, best-practices and SEO scores. When an authorized administrator requests performance analysis through the analyze-performance or combined analyze endpoint, the plugin sends the tested URL, saved Google API key, device strategy and requested categories to Google. Google fetches the tested public page. There are no PageSpeed requests on activation or when no API key has been saved. Clearing the API key disables this integration. The separate 360 Digital Marketing Site Scan button does not invoke the plugin’s PageSpeed analyzer.
Terms of Service: https://policies.google.com/terms
Privacy Policy: https://policies.google.com/privacy
360 Digital Marketing SEO key validation
Endpoint: https://seo.360digitalmarketing.org/v1/validate-seo-key
Validates the saved SEO key against the site’s URL. After an administrator explicitly enables this service in Site Audit, clicking Store & Validate sends the key and site URL as GET query parameters. Validation does not run on activation or automatically. The SEO key is also published in the homepage seokey meta tag for verification; it is separate from the Google API key.
The service operator’s Terms of Service and Privacy Policy are available at https://360digitalmarketing.org/privacy-policy/.
Direct page checks
Local analysis fetches the requested public URL and may check its linked public resources using WordPress HTTP functions. Those sites receive the requested URL and the server’s normal HTTP headers/IP address. This is separate from the services listed above.
Source code
All JavaScript and CSS source is included in assets/js/ and assets/css/. The shipped scripts are readable source files, not generated or minified bundles. No build step or third-party frontend library is needed; WordPress-provided APIs (including jQuery and the media picker) are used where applicable. Edit these source files directly. Optional formatting: Prettier 3.8.3, using –tab-width 4 –single-quote –print-width 100 –end-of-line lf. Export styles are in assets/css/report.css and embedded via the WordPress styles API so downloaded HTML remains self-contained.
Installation
- Upload the plugin directory and activate 360 SEO in WordPress.
- Open the plugin dashboard and complete the Setup Wizard.
- For remote scans, explicitly enable the 360 Digital Marketing service in Site Audit. Daily scheduled scans require a separate opt-in. Both are disabled by default, including on upgrade until consent is saved.
- For Google performance analysis, save your own PageSpeed Insights API key in Site Audit.
PHP DOM and mbstring support are required. The plugin reports missing extensions without loading its features.
FAQ
-
Do scans require a remote service?
-
Yes. Configure access to the scan service for remote analysis and reports. Local metadata controls operate within WordPress.
-
Are sitemap.xml and llms.txt written to my site root?
-
No. Sitemaps are served dynamically at sitemap_index.xml (also sitemap.xml); llms.txt is served dynamically after enabling it in SEO Fixes. Content updates are reflected without regenerating physical files. WordPress virtual robots.txt includes the sitemap URL. Existing physical files from earlier releases are not deleted or overwritten. Remove an old physical llms.txt or sitemap.xml using your file manager if it masks the corresponding dynamic URL, and update any physical robots.txt separately. The web server must route these URLs to WordPress, as it does for pretty permalinks.
-
Which WordPress versions support whole-page SEO enhancements?
-
WordPress 6.9 or later supports optional whole-page enhancements through its managed template output filter. Older versions retain the plugin’s ordinary metadata hooks and saved-content fixes, but whole-page fallback injection is unavailable. The plugin does not start a frontend output buffer of its own.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“360 Digital Marketing SEO Analyzer” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “360 Digital Marketing SEO Analyzer” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.4.0
- Require explicit remote-service consent and a separate daily-audit opt-in; stop legacy scheduled scans without consent.
- Store administrator-supplied PageSpeed and scan API credentials in WordPress options.
- Serve sitemap and llms.txt dynamically without root-file writes.
- Use WordPress styles and template-enhancement APIs and remove unused core includes.
- Ship readable JavaScript source and document service data flows and runtime requirements.
1.3.2
- Harden admin output and request handling.
- Use WordPress post queries and filesystem permission checks.
- Normalize source line endings and document export escaping exceptions.