TamRank SEO – SEO Audit, Search Console, Schema & Redirects

TamRank SEO: Know exactly what to fix.

TamRank is a free WordPress SEO plugin for people who are ready to move on from Yoast SEO, Rank Math or All in One SEO (AIOSEO) without starting over. It covers what you already use in your current SEO plugin (meta titles and descriptions, schema, XML sitemaps and redirects) and adds a continuous SEO audit that puts the next fix right next to every score. Your Search Console clicks, impressions and positions sit in the same dashboard.

Switching from another SEO plugin?

You do not lose what you built. The migration wizard:

• Detects Yoast SEO, Rank Math and All in One SEO, and lets you pick the source when more than one is installed.
• Imports your SEO titles, meta descriptions, focus keywords, canonicals, robots settings, social titles and descriptions, and category and tag SEO.
• Brings over your robots.txt, sitemap exclusions and site identity, plus your redirects from Rank Math and Yoast SEO Premium.
• Shows what it found and what it will move before it writes anything, and keeps a backup.
• Can be rolled back later from Settings → Import / Export.
• Never changes or deletes your old plugin’s data, so you can go back if TamRank is not for you.

While your old plugin is still active, TamRank steps aside: it leaves the title, meta description, canonical, robots and social tags to that plugin and only adds the structured data it does not write, so nothing appears twice. Deactivate the old plugin when you are happy with the result.

Why TamRank?

• Know what to fix next with clear SEO priorities
• Search Console data directly inside WordPress
• SEO audit, schema, redirects and 404 monitoring in one place
• A safe move from Yoast SEO, Rank Math or All in One SEO, with a roll-back
• Fully usable for free, without turning the dashboard into an upsell

Free features

• A continuous SEO audit. Every page gets a score and plain-language steps on what to fix next.
• Meta you control per page. Titles, descriptions and canonicals per post, page and term, a focus keyword plus four secondary keywords with live scoring, and Open Graph previews.
• Search Console in your dashboard. Clicks, impressions and average position, last 7 and 28 days.
• Schema without code. A markup builder with 14 types, reusable templates and custom JSON-LD.
• Broken links caught early. A 404 monitor and a redirect manager, with regex rules and $1-$9 backreferences.
• Found by search engines. XML and HTML sitemaps, breadcrumbs, a robots.txt editor, robots directives and IndexNow.
• Lighter, tidier media. Automatic WebP conversion and automatic alt text from your own pattern.

TamRank PRO

PRO is a separate add-on, not bundled in this free plugin. It adds the AI tools, topical authority, per-post audit panels, a change tracker, index-status scanning and PageSpeed Insights. You receive it by email after purchase and install it like any other plugin. The free plugin is fully functional on its own and never downloads it for you.

External services

TamRank communicates with api.tamrank.com (operated by TamRank) for the following purposes. All calls are HTTPS-only.

• Setup tips opt-in (optional, requires consent). When you check “Yes, send the tips” on the wizard success screen, the plugin sends your site’s admin email, the chosen UI language, your site URL, the plugin version and an anonymous onboarding-variant marker (used only to pick which tips series to send) to https://api.tamrank.com/v1/sites/email-optin. This enrolls you in a short series of educational emails about TamRank features. Unsubscribing from any email removes you from the list. No tracking pixels, no marketing blasts. Without consent this call is never made. The opt-in service only accepts a site with an API key, so when you opt in the plugin also requests a free API key for your site, through the site registration handshake described below, unless it already has one. If that handshake fails, your opt-in stays on your site and the plugin tries again in the background, at most four times, twelve hours apart.
• Site registration (on explicit action — not on activation). Activating the plugin does not contact any server. The first time you click “Connect with Google” to link Google Search Console, opt in to the setup tips in the wizard, or switch on IndexNow, the plugin requests a free API key from https://api.tamrank.com. To prove you control the domain before any key is issued, the plugin runs a short ownership handshake: it asks the TamRank server for a one-time token, briefly publishes that token at https://your-site/.well-known/tamrank-challenge.txt and at the public REST route https://your-site/wp-json/tamrank/v1/site-verify (for hosts that block the first path), and the TamRank server fetches it back to confirm the match. That token is single-use and short-lived, it is not the API key, and both addresses return 404 when no handshake is in progress. Only your site domain, site URL, plugin version, WordPress version, PHP version, site language, the TamRank interface language and environment type (production or staging) are sent, so support can see your setup and staging sites are not counted against your site limit. That same list of fields rides along on the licence status check the plugin already makes once it has an API key, so upgrading PHP or WordPress is reflected without you re-registering; it adds no request of its own and sends nothing beyond those fields. The API key is requested once, cached, and is required for TamRank’s hosted SEO services (Google Search Console integration, Request indexing and IndexNow).
• Google Search Console data (proxied through TamRank). When you connect Google Search Console, the OAuth authorisation and every subsequent Search Console request — impressions, clicks, average position and per-page index status — are routed through https://api.tamrank.com/v1/search-console/..., not called against Google directly. TamRank performs the OAuth token exchange on your behalf and returns the data, which is then cached in your WordPress database. Nothing is sent until you explicitly click “Connect with Google”.
• Automatic indexing / “Request indexing” (optional, off by default). When automatic indexing is enabled (it is off by default) or you click “Request indexing” on a post, the post’s URL — not its content — is sent to https://api.tamrank.com/v1/search-console/index-url (and its status checked via .../index-status) so the page can be submitted to search engines. This requires a connected Search Console property and never runs without one.
• IndexNow (optional, off by default). IndexNow is switched off on a fresh install and the plugin makes no IndexNow call until you enable it under Settings → General. Switching the toggle on is what triggers the network activity: at that moment the plugin creates a random site key, publishes it as a small text file at https://your-site/<key>.txt (so the search engines can verify you control the domain), and — if your site does not have an API key yet — runs the same one-time ownership handshake described under “Site registration” above to obtain one. After that, publishing or updating a page sends that page’s URL — not its content — to https://api.tamrank.com/v1/indexnow/submit, which forwards it to https://api.indexnow.org. IndexNow shares one submission with every participating search engine (Amazon, Bing, Naver, Seznam.cz, Yandex, Yep). Pages marked noindex, pages of content types you excluded, drafts, revisions and password-protected pages are never submitted. Switching the toggle off stops every submission; the key file itself stays reachable so a verification the search engines already started can still finish — it contains a random token and nothing else, and grants no access to your site. IndexNow protocol: https://www.indexnow.org/
• License activation (PRO add-on only). The separately-installed TamRank PRO add-on sends its license key together with your site’s API key to https://api.tamrank.com/v1/sites/upgrade to verify and activate the license. The free plugin has no license-key field and never makes this call; it is listed here only for completeness.
• AI features (PRO add-on only). Provided by the separate PRO add-on: AI meta generation, alt-text generation, internal-link suggestions and topical-authority analysis send the relevant post content to https://api.tamrank.com/v1/... endpoints. These features are off by default and only fire on user action. The free plugin sends no content to these endpoints.

One more transfer goes to TamRank’s website rather than the API:

• Support form (only when you click “Report a problem”). The “Report a problem” button in the footer of every TamRank screen opens https://tamrank.com/support/ in a new tab with a form POST. That click itself sends technical site details to tamrank.com, which is how the support form opens filled in: the plugin version, WordPress and PHP version, plan (free or pro), site language, the TamRank screen you were on, your site URL, and a plain-text diagnostics block of at most 8 KB with the TamRank interface language, environment type, multisite yes or no, permalink structure, active theme (and parent theme), and the names and versions of your active, network-active and must-use plugins, plus the file path of any plugin that is still listed as active but is missing from disk. If a developer points the tamrank_diagnostics_log_file filter at a log file (the plugin never sets it itself), the last 20 lines of that file are added as well. Anything that looks like a credential is masked; no API key, password or licence key is included. The form takes these details along in the background; you do not see or edit them there. The plugin never sends them without that click.

In addition, the separate TamRank PRO add-on uses one third-party Google service directly:

• Google PageSpeed Insights (PRO add-on only). PageSpeed testing is a PRO feature. When you run a PageSpeed test in the PRO add-on, the URL of the page being tested is sent (using your own Google API key) to Google’s PageSpeed Insights API (https://www.googleapis.com/pagespeedonline/v5/runPagespeed) and the resulting performance metrics are returned. This only happens on your explicit action. When you save a PageSpeed API key while the PRO add-on is active, one test request with that key is sent to the same API to check that it works. The free plugin on its own does not make either call. Google’s terms: https://developers.google.com/speed/docs/insights/v5/about — Google privacy policy: https://policies.google.com/privacy.

Requests that stay on your own site:

• Loopback requests to your own pages. Some checks fetch a page of your own site over HTTP, the same way a visitor would: the content and schema analysis of a post, the “Test schema” tool on the Schema page, the one-time robots.txt check during setup, and the safety check after TamRank edits your .htaccess file. These requests are addressed to your own site and send nothing to TamRank or any third party; the content and schema checks and the robots.txt check also refuse another host or port and any redirect that leaves your site.
• URL check for administrators. An administrator-only SEO check can fetch a URL that the administrator enters, to read its title, description and headings. It sends a plain GET request to that URL and nothing else, refuses private and internal network addresses (also for every redirect it follows), reads at most 2 MB of the answer, and only runs when an administrator asks for it.

The TamRank service is operated by TamRank (Netherlands). Privacy policy: https://tamrank.com/privacy-policy/ — Terms of service: https://tamrank.com/terms-of-service/. Contact: [email protected].

Third-party libraries

This plugin bundles the following third-party libraries and assets. Their source is available at the locations below, and their full license texts ship with the plugin (assets/fonts/OFL.txt, includes/vendor/wp-html-api/LICENSE.txt):

• Plus Jakarta Sans font (SIL Open Font License 1.1) — https://github.com/tokotype/PlusJakartaSans
• WordPress HTML API v6.9.4 (GPLv2 or later) — https://wordpress.org/wordpress-6.9.4.tar.gz — isolated, unminified tokenizer and tree builder for schema source checks. Prefixed names and five documented compatibility patches; provenance and hashes: includes/vendor/wp-html-api/SOURCE.json.