Description
SEO reports and site monitoring, inside WordPress.
Know which site needs attention today. Turtlereport checks your sites every day and tells you what changed. For your clients, or for yourself.
It reads Google Search Console and Google Analytics (GA4), read-only, and keeps everything on your own WordPress site. It’s free, with no account to create and no per-site fee.
Who it’s for
- Agencies and freelancers who look after their clients’ sites.
- Owners who look after their own sites.
- Sites on any platform. Only your own WordPress site runs Turtlereport; the sites you watch need nothing installed.
It isn’t a fit if you need ads or social media data, or want a hosted service.
Client Monitor: which sites need you
Once a day, each site’s last 28 days are compared with the 28 days before. An issue opens when:
- Google clicks fall 20% or more, with at least 100 before.
- Leads fall 25% or more, with at least 10 before.
- An important page loses 30% or more of its clicks.
- Keywords that brought clicks drop 3 or more places.
- A conversion event records nothing for 7 days while visitors keep arriving.
No AI here: fixed rules on your own numbers. Each issue shows its evidence: the numbers, what the data suggests and what to check next. Issues close when the numbers recover.
Mark an issue handled, snooze it, or send it to Slack. A weekly summary email can list the top priorities. If you only want to hear about big drops, one setting raises every threshold.
Reports with your name on them
- Each site’s report starts with what changed and what to do next, then the numbers: Search Console clicks, keywords and pages, GA4 traffic and leads, and visits from AI assistants.
- Compare periods, and split a report into segments such as brand and non-brand searches.
- Your logo and colour on the report, the PDF and every email. The Turtlereport credit stays off unless you turn it on.
- Report emails go out by themselves, weekly, every two weeks, monthly or quarterly, to the people you choose, with the PDF attached and a secure link to the report.
- Download any report as a PDF, and its data table as CSV.
Nothing wrong goes out
- Checked first. Every source is checked before each send. If data is missing, the report waits and tells you why. Missing data is never shown as zero.
- Review if you want. A report can wait for you: edit the highlights, add a note, approve.
- Proof it went. Every report email is logged with each recipient’s status. Failed ones are retried.
Choose who sees each site
Keep a site’s report private, share it with your team, or give a client their own login. Clients see only their own report, on desktop or phone.
Your data stays with you
- Turtlereport reads Google read-only and keeps everything on your WordPress site. Google data goes from Google to your site, never through our servers.
- Nothing is added to your public pages.
- Google sign-ins and keys are stored encrypted.
- Only people you allow see a report.
Connect Google your way
Sign in with Google, with no Google Cloud project to set up. Or use your own Google Cloud project, or a service-account key. Every way of connecting needs your site on HTTPS.
AI Advisor, if you want it
Ask about any site in plain English, such as “Why did this site’s clicks fall?”. Answers come from your own numbers.
- Off until you turn it on.
- Read-only: it changes nothing on any site.
- Uses your own OpenAI, Claude, Gemini or Grok API key, with daily and monthly limits.
Also
- Light and dark: each person picks their own theme.
- Left to right and right to left.
- Works on WordPress Multisite.
Set up in three steps
- Install Turtlereport.
- Connect Google with one sign-in.
- Add a site: pick its Search Console property and GA4 property.
Useful links
External services
This plugin connects to Google’s APIs to read reporting data. It only contacts Google after an administrator adds a connection (which needs the site on HTTPS), and only to read data for the sites and sections they set up. Google data is requested from your server and is never sent to the plugin author. Connections made with “Sign in with Google” use the plugin author’s sign-in service, described first below; connections with your own OAuth client or a service-account key don’t.
-
Turtleplugins Connect (connect.turtleplugins.com), run by the plugin author – used only for connections made with “Sign in with Google” on the Connections screen. It holds Turtlereport’s Google OAuth client, so you don’t need your own Google Cloud project. When an administrator signs in, their browser visits it with this site’s Turtlereport sign-in address, a one-time state value and a PKCE challenge; it shows which website is asking, then passes Google’s one-time authorisation code back to this site. This site’s server then sends it the code and the PKCE verifier to receive the Google tokens, and later sends the connection’s refresh token whenever it needs a new access token (about once an hour while Turtlereport reads data). It adds the OAuth client secret, forwards the request to Google and returns Google’s answer. It stores and logs none of these values and receives no Google report data. The Turtleplugins Privacy Policy and Terms of Service apply.
-
Google OAuth 2.0 (accounts.google.com, oauth2.googleapis.com) – signs in to Google, refreshes and revokes access, and exchanges service-account keys for access tokens. Sent: your OAuth client ID and secret or a signed service-account assertion, and authorisation codes or tokens. Revoking a “Sign in with Google” connection goes straight to Google too.
- Google Search Console API (www.googleapis.com/webmasters/v3) – lists your properties and reads search performance. Sent: the property and date range.
- Google Analytics Data API and Admin API (analyticsdata.googleapis.com, analyticsadmin.googleapis.com) – lists GA4 properties and key events, and reads event, traffic and channel reports. Sent: the property, date range, metrics and filters.
Access is read-only: Turtlereport asks Google only for the webmasters.readonly and analytics.readonly scopes.
-
Slack incoming webhooks (hooks.slack.com) – only if an administrator saves a Slack webhook in Settings → Client Monitor, and only when someone presses “Send to Slack” or “Send a test message”. Sent: the client’s name, the issue’s title, the affected address, its key numbers, what the data suggests, the recommended checks, the optional note, the name of the person sharing it and a link to the report in your WordPress admin. Slack’s Terms of Service and Privacy Policy apply.
-
AI providers – configured by an administrator in Settings → AI Advisor with a provider and that provider’s API key. Switching the Advisor on, or changing provider, requires an administrator to confirm that client data will be sent to that provider; the confirmation is recorded with their name and the date. Client data is sent only while the Advisor is switched on and a manager asks a question. “Test the connection” sends a generic connection-test prompt, and “Load my models” requests model names; these setup actions can run while the Advisor is switched off. Each request goes to the chosen provider:
- OpenAI (api.openai.com/v1/responses, /v1/models) – OpenAI’s Terms of Use and Privacy Policy apply.
- Anthropic Claude (api.anthropic.com/v1/messages, /v1/models) – Anthropic’s Commercial Terms and Privacy Policy apply.
- Google Gemini (generativelanguage.googleapis.com/v1beta/models) – the Gemini API Additional Terms of Service and Google’s Privacy Policy apply.
- xAI Grok (api.x.ai/v1/chat/completions, /v1/models) – xAI’s Terms of Service and Privacy Policy apply.
Sent: your API key (as an authorisation header), the question and earlier turns of that conversation, and for the clients it’s about their name, website, Search Console and GA4 numbers for the dates asked, the pages and keywords that changed most, visits from AI assistants, and their Client Monitor issues. WordPress account names, report-recipient email addresses and Google credentials are not included. Search queries, page addresses and other client report content may themselves contain personal data; review your client data and the provider’s terms before enabling the Advisor. Listing models sends only the API key.
Background jobs (daily connection checks, overnight report loading, the Client Monitor’s daily check and scheduled emails) make the same kinds of Google requests from your server. Scheduled emails are sent through your site’s own mail setup (wp_mail) to the addresses an administrator enters.
Google’s Terms of Service, Privacy Policy and API Services User Data Policy apply.
Third-party libraries
Bundled in assets/vendor/ (all MIT licensed, licences in assets/vendor/licenses/):
- Chart.js 4.5.1 – source/build tools: https://github.com/chartjs/Chart.js/tree/v4.5.1 (package.json and rollup.config.js).
This vendor JavaScript file corresponds to the version’s official npm distribution, omitting only the trailing source-map comment and trailing blank lines; its executable content is unchanged. Its build commands and dependency versions are provided in the pinned repository’s package.json.
The admin screens in assets/build/ are compiled from the plugin’s own source (see “Source code” below) with Turtlekit, Turtleplugins’ own component library. The Turtlekit code bundled in assets/build/ is distributed under the MIT licence (GPL-compatible). The bundles include Lucide icons (lucide-react 1.61.0, ISC licence, notice kept in the files). assets/build/turtlekit-fonts/ holds Geist Mono (https://github.com/vercel/geist-font) and Source Serif 4 (https://github.com/adobe-fonts/source-serif) – SIL Open Font License 1.1, licences beside the fonts.
PHP class loading uses Composer’s generated production autoloader. Its MIT licence is included at vendor/composer/LICENSE; Composer source is available at https://github.com/composer/composer . The plugin does not include its development Composer dependencies.
Font in assets/fonts/: Inter 4.001 (variable, Latin and Latin Extended), recorded source commit https://github.com/rsms/inter/tree/66647c0bbbe41a850d79d9c76fb13add3378940f – SIL Open Font License 1.1, licence in assets/fonts/OFL.txt. The pinned repository includes font source and build tools. It is served from your own site; no font is loaded from Google. assets/fonts/pdf/ holds the static Regular and SemiBold Inter files used to draw PDF reports on the server (same licence, assets/fonts/pdf/OFL.txt), and Noto Sans Arabic 2.013 Regular and SemiBold (https://github.com/notofonts/arabic, reduced to the Arabic letters and presentation forms), which draw Arabic, Persian and Urdu text in those PDFs – SIL Open Font License 1.1, licence in assets/fonts/pdf/OFL-NotoSansArabic.txt.
The server-side PDF is written by the plugin’s own code (src/Pdf/); no PDF library or external service is used.
Each report can be emailed to up to 50 unique addresses. Viewer recipients are considered first, then individually chosen users, then typed addresses; duplicate addresses count once. This mail-processing limit does not restrict report access or grant revocation. Credits on PDFs and emails are off unless you explicitly choose to show them in Settings.
Source code
The JavaScript in assets/build/ is minified. Its readable source ships with the plugin in resources/admin/src/ (TypeScript and React), with the build files: package.json, package-lock.json, vite.config.ts, tsconfig.json and the build scripts in tools/. The source builds with the npm package turtlekit (Turtleplugins’ component library). To build it, run npm ci, then npm run build; the bundles are written to assets/build/.
FAQ
Does it slow my website?
No. It adds nothing to your public pages. It works in your WordPress admin and in background jobs.
Do the sites I watch need anything installed?
No. Only your own WordPress site runs Turtlereport. It reads each site’s data from Google, so a site can run on any platform.
What does it cost?
Nothing. Turtlereport is free, with no per-site fee. The AI Advisor is optional and uses your own provider’s API key, which that provider bills.
Do I need a Google Cloud project?
No. “Sign in with Google” works without one. If you prefer, connect with your own Google Cloud project or a service-account key instead.
Why does connecting Google need HTTPS?
Google sign-ins come back to your site and keys are sent to it, so they must never travel unencrypted. Every way of connecting needs your site’s address to start with https://. Local development addresses such as localhost and .test also work.
Which PHP version do I need?
PHP 8.0 or later. Turtlereport is tested up to PHP 8.5.
Can someone see a report that isn’t theirs?
No. Administrators see every site. Everyone else sees only the reports you give them, and access is checked on the server.
Does it use AI?
Only if you turn on the AI Advisor. The Client Monitor uses fixed rules on your own numbers.
Why do the numbers differ slightly from Google’s own screens?
Search Console runs about two days behind and hides rare searches. Reports are cached for up to three hours, and a day for older periods; “Refresh data” fetches fresh numbers.
Do scheduled emails need anything special?
They use WP-Cron, which runs when your site gets visits, so on a quiet site a report can go out late. For on-time emails, add a server cron job that calls wp-cron.php every 15 minutes. An SMTP plugin is recommended so emails don’t land in spam. “Accepted” means your mail server took the email; it can’t confirm the email reached the inbox.
Can I keep the encryption key out of the database?
Yes. Define TURTLEREPORT_ENCRYPTION_KEY in wp-config.php before adding connections. By default the key comes from your site’s security salts, so changing those means reconnecting.
What happens to my data if I delete the plugin?
Deactivating keeps everything. Deleting the plugin revokes its Google sign-ins where possible and removes its sites, settings, connections, keys, history and the Report viewer role. Users keep their accounts.
Screenshots









Changelog
2.1
- Turtlereport now needs PHP 8.0 or later.
- Client Monitor: the issues that need you lead the page, each one a single click to its evidence, with your clients in a compact strip below.
- Reports: the key figures in one row above the chart, small daily counts such as leads drawn as bars, and what changed beside what to do next.
- If a new period or segment can’t load, the report goes back to the period its figures are for, says what didn’t load and offers Try again.
- A new install shows the same first step on every screen: connect Google, then add a site.
- One header and tab row on every screen, and one look for every status, from Connected to Waiting for review.
- Connections, Sites & access, Settings and Email deliveries: one name for each place, each thing said once, and layouts that hold together from phone to wide screen.
2.0
- A new Turtlereport for anyone who looks after sites: agencies, freelancers and owners of their own sites.
- One app inside your WordPress admin, with its own sidebar: Client Monitor, Email deliveries, each site’s report, Sites & access, Connections and Settings, in light and dark, left to right and right to left.
- Client Monitor: every site’s health at a glance, the issues that need attention first, and each issue’s evidence and next step.
- Reports: what changed and why it matters first, then the figures by source, with segments and comparisons.
- One client report: the PDF you download is the PDF your clients get by email, with real text, A4 or US Letter, and Arabic, Persian and Urdu.
- Report emails built for email apps, with dark mode, a secure link to the report and a plain-text version.
- Connect Google with Sign in with Google, your own Google Cloud project or a service-account key; one connection per Google account. Every way of connecting needs the site on HTTPS.
- Removed: Business Profile reports. Turtlereport reads Search Console and Google Analytics only.
