Seotune Search Insights connects to Google Search Console, stores search analytics in your WordPress database, and provides an admin dashboard with KPIs, reports, and actionable SEO insights.<\/p>\n\n
For setup help, see the Documentation<\/a>.<\/p>\n\n Without external accounts:<\/strong> The plugin installs and activates like any other plugin, but reports and sync require<\/strong> a Google Cloud OAuth client and a Google account with access to a Search Console property for your site. Until you complete connection in Seotune Search Insights \u2192 Settings<\/strong>, no Search Console data is fetched and dashboards stay empty.<\/p>\n\n Features<\/strong><\/p>\n\n Data is synced for the last 3 days on manual run or via a daily cron. After the first successful connection<\/strong> to Google Search Console, Seotune Search Insights automatically imports the last 28 days<\/strong> so that the Dashboard and reports are not empty; you can then use Sync & Import to extend or restart the import for a larger range. After the first import, data is updated automatically every day via cron. Historical data can be imported in background batches (by default 7 days per batch and 1000 rows per DB write) that stay within sensible Google Search Console usage and are tuned for performance; you can adjust these values from Settings \u2192 Sync & Import if needed. The Sync & Import card also includes an Import diagnostics<\/strong> panel that shows recent import activity, cron status, and common issues (e.g. cron not running, API quota, PHP\/DB limits) without exposing sensitive query data. Custom database tables use a plugin-specific<\/strong> prefix (in addition to your WordPress table prefix).<\/p>\n\n This plugin does not<\/strong> send your site\u2019s front-end visitor traffic to Seotune Search Insights or to a proprietary Seotune API. It does not<\/strong> add visitor tracking, advertising pixels, or marketing analytics to the public site.<\/p>\n\n Declared service data (administrators)<\/strong><\/p>\n\n Responsibility<\/strong>: Site owners should inform end users where required by law (e.g. privacy policy, cookie\/consent flows) that Search Console-related data is processed when administrators connect Google services.<\/p>\n\n Technical map (endpoints, when requests run): In Seotune Search Insights \u2192 Settings \u2192 Sync & Import<\/strong> you will find an Import diagnostics<\/strong> box:<\/p>\n\n The panel is read-only and is meant to help you and support quickly understand what is happening on your server.<\/p>\n\n \u201cCron may not be running regularly\u201d \/ \u201cNo plugin cron jobs have run in the last few hours\u201d<\/strong> \u201cHistorical import is marked as running, but no backfill batches have completed yet\u201d<\/strong> \u201cHistorical import seems stuck (no progress for a while)\u201d<\/strong> Search Console quota \/ rate limit errors in the log<\/strong> PHP execution time, memory, or database errors in the log<\/strong> Seotune Search Insights\u2019 historical import<\/strong> runs in the background via WordPress cron: each cron run processes one batch (a few days of data), then schedules the next. For the import to complete without blocking or stalling, the hosting environment must meet the following.<\/p>\n\n Default settings<\/strong> (7 days per batch, 60 seconds delay between batches, 1000 rows per DB batch) are chosen to work on most hosting. On servers with more resources you can increase Days per batch<\/strong> and reduce Delay between batches<\/strong> in Seotune Search Insights \u2192 Settings \u2192 Sync & Import for a faster import.<\/p>\n\n Minimum (plugin runs, import may be slow or need tuning)<\/strong><\/p>\n\n Recommended (smooth, reliable import)<\/strong><\/p>\n\n Restrictive shared hosting (e.g. some Aruba, or low-resource plans)<\/strong><\/p>\n\n On hosting with strict limits (low memory, 30s execution time, or cron that rarely runs), the import can block, time out, or appear stuck. To improve reliability:<\/p>\n\n If the import still fails or gets stuck, use Import diagnostics<\/strong> in Settings (and Copy log for support<\/strong>) to see whether the cause is cron not running, timeouts, memory, or API quota; then adjust the above or contact the host with the requested limits.<\/p>\n\n Backend (Composer)<\/strong><\/p>\n\n Frontend (React)<\/strong><\/p>\n\n Release zip(s) (from plugin root, after Translations (i18n)<\/strong><\/p>\n\n Video tutorial (installation & setup)<\/strong> Bundled documentation (HTML)<\/strong> (in the full source tree \/ developer checkout; omitted from the production \n
Privacy<\/h3>\n\n
\n
documentation\/network-and-privacy.txt<\/code>. Narrative guide: documentation\/index.html<\/code> (Privacy & third-party services).<\/p>\n\nTroubleshooting<\/h3>\n\n
Import diagnostics panel<\/h3>\n\n
\n
Common messages and what to do<\/h3>\n\n
\n
\nThis usually means WordPress cron is disabled or not being triggered. Check wp-config.php<\/code> for DISABLE_WP_CRON<\/code>. If it is set to true<\/code>, configure a real server cron job that calls wp-cron.php<\/code> every few minutes, or ask your hosting provider to set this up.<\/p><\/li>\n
\nThe backfill state is \u201crunning\u201d but no historical batches are logged. This is typically another sign that cron is not firing. Verify the cron configuration as above, then wait a few minutes and refresh the page.<\/p><\/li>\n
\nIf the progress bar stays at 0% or does not move for a long time, use Stop \/ Reset import<\/strong> in the Sync & Import card, then start a new import with smaller batches (lower \u201cDays per batch\u201d). Also make sure cron is running.<\/p><\/li>\n
\nIf recent log entries mention quota or rate-limit errors from the Google Search Console API, try lowering Days per batch<\/strong> for the historical import, and consider running imports at quieter times of day. If the issue persists, you may need to wait for quotas to reset or use a dedicated Google Cloud project.<\/p><\/li>\n
\nMessages mentioning maximum execution time, memory limits, or database connection issues indicate that the server limits are too strict for large imports. Try reducing Days per batch<\/strong> and, if needed, ask your hosting provider to increase PHP memory_limit<\/code> and max_execution_time<\/code>, or to relax database limits for background jobs.<\/p><\/li>\n<\/ul>\n\nHosting requirements (for smooth import)<\/h3>\n\n
\n
DISABLE_WP_CRON<\/code> is set to true<\/code> in wp-config.php<\/code>, a system cron job<\/strong> must call wp-cron.php<\/code> (or trigger WordPress cron) every few minutes; otherwise the import never advances.<\/li>\n\n
\n
DISABLE_WP_CRON<\/code>, set up a real cron job (e.g. *\/5 * * * *<\/code> to hit https:\/\/yoursite.com\/wp-cron.php?doing_wp_cron<\/code> or run wp cron event run --due-now<\/code> via WP-CLI every few minutes). Ask the host (e.g. Aruba) how to add a cron job and what the URL\/command should be.<\/li>\nDevelopment<\/h3>\n\n
\n
composer install<\/code>.<\/li>\nvendor\/<\/code> directory when deploying (plugin requires it for the Google API client).<\/li>\ncomposer.json<\/code> uses a classmap<\/strong> for includes\/<\/code> (no PSR-4 path mismatch warnings).<\/li>\nmonolog\/monolog<\/code> is required by google\/apiclient<\/code>; it stays in composer.json<\/code> as ^2.9<\/code> to pin Monolog 2.x and remain compatible with PHP 8.0 (Monolog 3 needs PHP 8.1+).<\/li>\n<\/ul>\n\n\n
admin\/react-app<\/code>: npm install<\/code> then npm run build<\/code>.<\/li>\nadmin\/assets\/js\/admin-app.js<\/code> (IIFE bundle for classic wp_enqueue_script<\/code>, no import.meta<\/code>) plus admin\/assets\/js\/admin-app.css<\/code> (extracted CSS). Deploy both files; without the built JS, a placeholder script is loaded.<\/li>\nadmin\/react-app\/<\/code> (Vite\/React sources, package-lock.json<\/code>; node_modules<\/code> excluded \u2014 run npm ci<\/code> inside admin\/react-app<\/code> to rebuild). Compiled admin-app.js<\/code> + admin-app.css<\/code> are also present. Optional: add a public git mirror<\/strong> URL below for convenience. Details: documentation\/source-and-build.txt<\/code>.<\/li>\ncomposer<\/code> \/ npm<\/code> as needed)<\/strong><\/p>\n\n\n
scripts\/README-release.txt<\/code> (Stable tag, version constant in seotune-search-insights.php<\/code> aligned with the plugin header, changelog, Subversion tag folder).<\/li>\nnpm run release<\/code> \u2014 creates a zip in dist\/<\/code> (includes admin\/react-app<\/code> sources; excludes node_modules<\/code> and documentation\/<\/code>).<\/li>\nnpm run release:src<\/code> \u2014 creates only the *-with-sources.zip<\/code> variant with the same contents<\/strong> (alias for workflows that expect the filename).<\/li>\nnpm run release:all<\/code> \u2014 writes both filenames; the archives are identical (duplicate name for compatibility).<\/li>\n<\/ul>\n\n\n
seotune-search-insights<\/code>. PHP uses load_plugin_textdomain<\/code> with languages\/<\/code>.<\/li>\n@wordpress\/i18n<\/code> (__()<\/code>, sprintf<\/code>, _n<\/code>) in JSX; wp_set_script_translations()<\/code> loads Jed JSON for the built script.<\/li>\n
\n wp i18n make-pot . languages\/seotune-search-insights.pot --slug=seotune-search-insights --domain=seotune-search-insights --exclude=vendor,admin\/react-app\/node_modules,dist,admin\/assets,documentation,scripts
\nUpdate languages\/seotune-search-insights-en_US.po<\/code> with wp i18n update-po languages\/seotune-search-insights.pot languages\/seotune-search-insights-en_US.po<\/code>.
\nBuild JS JSON (maps all React sources to the single bundle):
\n wp i18n make-json languages\/seotune-search-insights-en_US.po --use-map=languages\/wp-i18n-map.json --domain=seotune-search-insights --extensions=jsx,js
\nCommit languages\/seotune-search-insights.pot<\/code>, languages\/seotune-search-insights-en_US.po<\/code>, languages\/wp-i18n-map.json<\/code>, and languages\/seotune-search-insights-*-*.json<\/code> with the plugin.<\/li>\n<\/ul>\n\n\n
\nhttps:\/\/www.youtube.com\/watch?v=QF8Wkk7Sg1I<\/p>\n\n\n
seotune-search-insights<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\nnpm run release<\/code> zip to keep the download smaller)<\/em><\/p>\n\n\n
documentation\/index.html<\/code> in a browser, or print to PDF from the browser.<\/li>\n